Message processing method and apparatus, and storage medium

Abstract

The application relates to a message processing method and device and a storage medium. The method comprises the following steps: in response to a message reminder generated by a collaboration object in a collaboration space, displaying a reminder item corresponding to the message reminder in a conversation list of a message processing interface, and associating an unread identifier with the reminder item; in response to the reminder item being triggered in the message processing interface, displaying collaboration content of the collaboration object in the message processing interface. Thus, the operation path of repeatedly switching between the message processing interface and the collaboration space interface is eliminated, context break caused by interface separation is avoided, the user can complete message positioning, viewing and processing in a continuous interaction process, and therefore, the operation complexity is reduced, and the continuity and efficiency of message processing are improved.

Description

Technical Field

[0001] This application relates to the field of computers, and more particularly to a message processing method, apparatus, and storage medium. Background Technology

[0002] In team collaboration scenarios, Team Space, as a lightweight collaboration tool, can aggregate and manage resources such as documents, tasks, and files to improve collaboration efficiency. However, in existing technologies, Team Space and instant messaging processing functions are usually independent of each other, presented in different tabs. Specifically, message notifications generated by collaborative activities such as group chats and document comments within Team Space are only displayed in the Team Space tab; while users' daily instant messaging conversations (such as one-on-one chats and regular group chats) are displayed in a separate Messages tab. If users need to handle all pending messages, they must repeatedly switch between the Messages tab and the Team Space tab to view and process unread messages in each interface.

[0003] The above design results in fragmented operation paths and disconnected contexts, making it difficult for users to efficiently complete all message processing tasks on the same interface, and also making it difficult to easily trace back the history of messages that have been communicated within the team space, which seriously affects the continuity of team collaboration and the efficiency of message processing. Summary of the Invention

[0004] This application provides a message processing method, apparatus, and storage medium to solve the technical problem in the prior art where users have to repeatedly switch between the message tab and the team space tab to view and process unread messages in their respective interfaces, resulting in scattered operation paths, fragmented context, and seriously affecting the coherence of team collaboration and message processing efficiency.

[0005] Firstly, this application provides a message processing method, the method comprising: In response to a message notification generated by a collaborating object in the collaboration space, the notification item corresponding to the message notification is displayed in the session list of the message processing interface, and an unread flag is associated with the notification item. In response to triggering the reminder item in the message processing interface, the collaborative content of the collaborating object is displayed in the message processing interface.

[0006] In one possible implementation, the collaborative content of the collaborating objects is displayed in the message processing interface, including: Expand the view of the collaboration space in the message processing interface. The view is used to display the collection of collaboration objects in the collaboration space and the collaboration resources associated with the collaboration space.

[0007] In one possible implementation, the method further includes: In response to entering a target session from the view of the collaboration space, the session interface of the target session is displayed, and a document sending control is provided in the session interface; The document sending control is used to select a document from the collaboration space and send the selected document as a message to the target session.

[0008] In one possible implementation, in response to a message notification generated by a collaborating object in the collaboration space, the notification item corresponding to the message notification is displayed in the session list of the message processing interface, and an unread flag is associated with the notification item, including: In response to message notifications generated by collaborating objects within the collaboration space, the notification item corresponding to the collaboration space is located in the session list of the message processing interface; wherein, the notification item corresponding to the collaboration space is used to aggregate and display message notifications from all collaborating objects within the collaboration space; If there is no reminder item corresponding to the collaboration space in the session list, add a reminder item corresponding to the collaboration space to the session list and associate an unread flag with the reminder item; If a reminder item corresponding to the collaboration space already exists in the session list, update the unread flag of the reminder item.

[0009] In one possible implementation, message notifications generated by collaborative objects created within the collaborative space, as well as those created outside the collaborative space and then added to the collaborative space, are all assigned to the corresponding notification item in the collaborative space for display.

[0010] In one possible implementation, the method further includes: In response to the current user joining the collaboration space, a reminder item corresponding to the collaboration space is generated in the session list of the message processing interface, and the historical message reminders in the collaboration space are displayed in the reminder item; The historical message reminders include message reminders generated within the collaboration space before the current user joined the collaboration space.

[0011] In one possible implementation, the reminders in the conversation list are arranged according to a preset sorting rule, which includes: The reminders are sorted according to the timestamp of the latest message notification corresponding to each reminder item; wherein, for reminder items corresponding to collaboration spaces, the timestamp of the latest message notification is the maximum value among the timestamps of the latest message notifications of all collaboration objects within the collaboration space; Alternatively, the reminders can be sorted according to the number of unread message reminders for the corresponding collaborative objects; wherein, for reminders corresponding to a collaborative space, the number of unread message reminders is the sum of the number of unread message reminders for all collaborative objects within the collaborative space; Alternatively, the reminders can be sorted according to their pinning status in the message processing interface.

[0012] In one possible implementation, the method further includes: In response to completing the viewing of the collaborative content, the unread flag of the notification item is cleared.

[0013] In one possible implementation, the method further includes: In response to clearing the unread flag of the reminder item in the message processing interface, the unread status of the corresponding collaboration object in the collaboration space interface is simultaneously cleared. Alternatively, in response to clearing the unread status of the collaborative object in the interface of the collaborative space, the unread flag of the corresponding reminder item in the message processing interface is cleared simultaneously.

[0014] In one possible implementation, the method further includes: In response to the collaborating object receiving a reminder message mentioning the current user, the reminder item corresponding to the reminder message is displayed in the first message display area of ​​the message processing interface; wherein, the first message display area is independent of the second message display area of ​​the message processing interface.

[0015] In one possible implementation, the method further includes: In response to receiving an access request to the collaboration object or the collaboration space via an external link, the external link is parsed, the user is redirected to the message processing interface, and the reminder item corresponding to the collaboration object is highlighted in the message processing interface.

[0016] In one possible implementation, the method further includes: In response to receiving a search request in the message processing interface, the search results are displayed in the message processing interface; wherein, the search results include the collaborating objects that match the search request and their corresponding reminder items, and the identification information of the collaborating space to which the collaborating objects belong is displayed in association in the search results.

[0017] Secondly, this application provides a message processing apparatus, the apparatus comprising: The message aggregation module is used to respond to message reminders generated by collaborative objects in the collaborative space, display the reminder items corresponding to the message reminders in the session list of the message processing interface, and associate the reminder items with an unread flag; The display module is used to display the collaborative content of the collaborating object in the message processing interface in response to triggering the reminder item in the message processing interface.

[0018] In one possible implementation, the display module is specifically used for: Expand the view of the collaboration space in the message processing interface. The view is used to display the collection of collaboration objects in the collaboration space and the collaboration resources associated with the collaboration space.

[0019] In one possible implementation, the device further includes: The document sending module is used to respond to entering the target session from the view of the collaboration space, display the session interface of the target session, and provide document sending controls in the session interface; The document sending control is used to select a document from the collaboration space and send the selected document as a message to the target session.

[0020] In one possible implementation, the message aggregation module is specifically used for: In response to message notifications generated by collaborating objects within the collaboration space, the notification item corresponding to the collaboration space is located in the session list of the message processing interface; wherein, the notification item corresponding to the collaboration space is used to aggregate and display message notifications from all collaborating objects within the collaboration space; If there is no reminder item corresponding to the collaboration space in the session list, add a reminder item corresponding to the collaboration space to the session list and associate an unread flag with the reminder item; If a reminder item corresponding to the collaboration space already exists in the session list, update the unread flag of the reminder item.

[0021] In one possible implementation, message notifications generated by collaborative objects created within the collaborative space, as well as those created outside the collaborative space and then added to the collaborative space, are all assigned to the corresponding notification item in the collaborative space for display.

[0022] In one possible implementation, the device further includes: The historical message synchronization module is used to generate a reminder item corresponding to the collaboration space in the session list of the message processing interface in response to the current user joining the collaboration space, and to display the historical message reminders in the collaboration space in the reminder item; The historical message reminders include message reminders generated within the collaboration space before the current user joined the collaboration space.

[0023] In one possible implementation, the reminders in the conversation list are arranged according to a preset sorting rule, which includes: The reminders are sorted according to the timestamp of the latest message notification corresponding to each reminder item; wherein, for reminder items corresponding to collaboration spaces, the timestamp of the latest message notification is the maximum value among the timestamps of the latest message notifications of all collaboration objects within the collaboration space; Alternatively, the reminders can be sorted according to the number of unread message reminders for the corresponding collaborative objects; wherein, for reminders corresponding to a collaborative space, the number of unread message reminders is the sum of the number of unread message reminders for all collaborative objects within the collaborative space; Alternatively, the reminders can be sorted according to their pinning status in the message processing interface.

[0024] In one possible implementation, the device further includes: The identifier clearing module is used to clear the unread identifier of the reminder item in response to completing the viewing operation of the collaborative content.

[0025] In one possible implementation, the device further includes: The status synchronization module is used to synchronously clear the unread status of the corresponding collaborative object in the interface of the collaboration space in response to clearing the unread flag of the reminder item in the message processing interface; Alternatively, in response to clearing the unread status of the collaborative object in the interface of the collaborative space, the unread flag of the corresponding reminder item in the message processing interface is cleared simultaneously.

[0026] In one possible implementation, the device further includes: The message partition display module is used to respond to the collaborative object receiving a reminder message mentioning the current user, and to display the reminder item corresponding to the reminder message in the first message display area of ​​the message processing interface; wherein, the first message display area is independent of the second message display area of ​​the message processing interface.

[0027] In one possible implementation, the device further includes: The interface jump module is used to respond to an access request received via an external link pointing to the collaboration object or the collaboration space, parse the external link, jump to the message processing interface, and highlight the reminder item corresponding to the collaboration object in the message processing interface.

[0028] In one possible implementation, the device further includes: The search module is used to respond to a search request received in the message processing interface and display search results in the message processing interface; wherein, the search results include collaborative objects that match the search request and their corresponding reminder items, and the identification information of the collaborative space to which the collaborative object belongs is displayed in the search results.

[0029] Thirdly, this application provides an electronic device, including: a processor and a memory, wherein the processor is configured to execute a message processing program stored in the memory to implement the message processing method described in any one of the first aspects.

[0030] Fourthly, this application provides a storage medium storing one or more programs that can be executed by one or more processors to implement the message processing method described in any one aspect.

[0031] Compared with the prior art, the technical solution provided in this application has the following advantages: The method provided in this application generates message reminders in response to collaborative objects in the collaborative space, displays the corresponding reminder item in the session list of the message processing interface, and associates the reminder item with an unread flag. This allows users to intuitively understand the distribution of all pending messages in a unified interface without actively entering each collaborative space. When a user triggers a reminder item in the message processing interface, the collaborative content of the corresponding collaborative object is directly displayed in the message processing interface, allowing the user to view and initially process the message without switching to the collaborative space interface. This process eliminates the user's repeated switching between the message processing interface and the collaborative space interface, avoiding contextual breaks caused by interface separation, and enabling users to locate, view, and process messages in a continuous interactive flow. Therefore, this application achieves unified aggregation and rapid response of message reminders, reduces operational complexity, and improves the continuity and efficiency of message processing. Attached Figure Description

[0032] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0033] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0034] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0035] Figure 1 A flowchart illustrating an embodiment of a message processing method provided in this application; Figure 2 This is a schematic diagram of the interface for an application scenario involved in an embodiment of this application; Figure 3 A flowchart illustrating an embodiment of a message processing apparatus provided in this application; Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0036] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0037] The following disclosure provides numerous different embodiments or examples for implementing various structures of this application. To simplify the disclosure, specific examples of components and arrangements are described below. These are merely examples and are not intended to limit the scope of this application. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.

[0038] To address the technical problem in existing technologies where users must repeatedly switch between the Messages tab and the Team Space tab to view and process unread messages on each interface, resulting in fragmented operation paths and contextual breaks that severely impact the continuity of team collaboration and message processing efficiency, this application provides a message processing method, apparatus, and storage medium. This eliminates the need for users to repeatedly switch between the message processing interface and the collaboration space interface, avoiding contextual breaks caused by interface separation. It allows users to locate, view, and process messages within a continuous interactive flow, thereby reducing operational complexity and improving the continuity and efficiency of message processing.

[0039] Figure 1This is a flowchart illustrating an embodiment of a message processing method provided in this application. In one embodiment, the method is applied to a collaboration platform, which includes a message processing interface and at least one collaboration space; wherein the message processing interface is used to display a list of instant messaging sessions, and the collaboration space is a container used to host and manage various types of collaboration objects and collaboration resources. Figure 1 As shown, the method includes the following steps: Step 101: In response to a message notification generated by a collaborating object in the collaboration space, display the corresponding notification item in the conversation list of the message processing interface, and associate an unread flag with the notification item.

[0040] First, the collaboration space is an aggregated collaboration container used to organize, host, and uniformly manage various types of collaboration objects and resources, including instant messaging group chats, documents, files, and tasks. The collaboration space has an independent member system and access control, enabling centralized display and unified management of dispersed collaboration resources. In this application, the collaboration space and the message processing interface are two independent interfaces within the same collaboration platform, with different functional orientations: the core function of the message processing interface is instant messaging chat, used to display a list of conversations the user participates in (such as one-on-one chats and regular group chats), and supports users to directly send, receive, and view messages within this interface; while the collaboration space interface provides a complete resource view within a space and supports users to perform collaborative operations within the space, including but not limited to browsing the collaboration object directory, viewing the member list, sending messages in group chats, and editing documents.

[0041] Collaboration objects refer to specific collaborative entities belonging to the collaboration space, such as group chats, documents, and tasks. When an event requiring user attention occurs within a collaboration object (such as a new message, task assignment, @mention, approval request, etc.), the collaboration platform generates a "message alert." Message alerts are notification signals generated by the collaboration platform to prompt users with pending tasks.

[0042] A notification item is a visual display unit of message notifications in the message processing interface, similar to a conversation entry in an instant messaging application. In this application, each notification item corresponds to a conversation entity, which can be a collaborative object within a collaboration space (such as a group chat, document, task, etc.) or a native conversation independent of the collaboration space (i.e., a native conversation in the message processing interface, such as a one-on-one chat or a regular group chat). For example, a notification item includes the identifier (such as the name) of the corresponding entity, the content of the message notification (specific content or summary content), the time of generation, and other information.

[0043] To enable users to distinguish between processed and unprocessed message notifications, this application associates an "unread icon" with each notification item. The unread icon can take the form of an unread count badge, a red dot, a bold title, etc., to visually indicate that there are unread message notifications within the entity corresponding to that notification item. In actual product implementation, the unread icon can adopt various visual styles to adapt to different scenarios. For example, a red dot can be used to represent a regular new message; for messages with a specific number of unread messages, a numerical badge (such as "3") can be used to precisely display the number of unread messages; for high-priority messages (such as @mentions), special animations (such as flashing or magnification effects) can be added to the red dot to further attract the user's attention. Furthermore, the unread icon can be cleared not only by viewing the message, but also by the user manually swiping left on the notification item and selecting "Mark as Read," or by clearing the unread icons of multiple notification items at once through batch operations. These interactive methods are all within the scope of protection of this application.

[0044] In the specific implementation of step 101, the collaboration platform listens for events from collaboration objects in the collaboration space (which can be all collaboration objects in the collaboration space or a specific collaboration object). When a message notification is detected from a collaboration object, the platform displays the corresponding notification item in the session list of the message processing interface and associates an unread flag with that notification item.

[0045] In one embodiment, in response to a message notification generated by a collaborating object in the collaboration space, a notification item corresponding to the message notification is displayed in the session list of the message processing interface, and an unread flag is associated with the notification item. This includes: in response to a message notification generated by a collaborating object in the collaboration space, locating the notification item corresponding to the collaboration space in the session list of the message processing interface, wherein the notification item corresponding to the collaboration space is used to aggregate and display message notifications from all collaborating objects within the collaboration space. If no notification item corresponding to the collaboration space exists in the session list, a new notification item corresponding to the collaboration space is added to the session list, and an unread flag is associated with the notification item; if a notification item corresponding to the collaboration space already exists in the session list, the unread flag of the notification item is updated.

[0046] In this embodiment, considering that a collaborative space may contain multiple collaborative objects (such as multiple group chats, documents, tasks, etc.), if each collaborative object generates a separate reminder item in the message processing interface when it generates a message reminder, then when a user participates in multiple collaborative spaces and there are many collaborative objects in each collaborative space, the reminder item list in the conversation list of the message processing interface will rapidly expand, making it difficult for the user to quickly locate important information and reducing message processing efficiency. Therefore, this application provides a space-level aggregated reminder mechanism.

[0047] Specifically, message notifications generated by collaborative objects created within a collaborative space, as well as those created outside the collaborative space and then added to it, are all displayed under the corresponding notification item for that collaborative space. Based on this, when any collaborative object associated with a collaborative space generates a message notification, the collaboration platform first locates the notification item corresponding to that collaborative space (hereinafter referred to as "space-level notification item") in the session list of the message processing interface. If it does not exist, it means that no message notifications have been generated in that collaborative space before. In this case, the collaboration platform adds a new space-level notification item to the session list of the message processing interface and associates an unread flag with it, for example, initializing the unread count to 1. If a space-level notification item already exists for that collaborative space, it means that other collaborative objects in that collaborative space have generated unprocessed message notifications. In this case, the collaboration platform does not need to add a new space-level notification item, but instead updates the unread flag of the existing space-level notification item, for example, incrementing the unread count by 1 and refreshing its summary content to the latest message notification.

[0048] In this way, regardless of how many collaborating objects generate message notifications within the collaboration space, and regardless of whether these objects were created within the space or added externally, the message processing interface always displays only one space-level notification. Clicking this notification takes the user to the collaboration space interface, allowing them to centrally manage all unread messages within that space. This mechanism effectively prevents the notification list from becoming excessively large, enabling users to manage unread messages uniformly by space dimension, significantly improving the information carrying capacity of the message processing interface and the ease of user operation.

[0049] In one embodiment, the reminder items in the conversation list of the message processing interface are arranged according to a preset sorting rule, which includes: sorting by the timestamp of the latest message reminder corresponding to the reminder item; wherein, for reminder items corresponding to collaboration spaces, the timestamp of the latest message reminder is the maximum value among the timestamps of the latest message reminders of all collaboration objects in the collaboration space; or, sorting by the number of unread message reminders of the collaboration objects corresponding to the reminder item; wherein, for reminder items corresponding to collaboration spaces, the number of unread message reminders is the sum of the number of unread message reminders of all collaboration objects in the collaboration space; or, sorting by the pinned status of the reminder items in the message processing interface.

[0050] In this embodiment, multiple optional sorting rules are provided, allowing users to choose or combine them according to their habits or scenario needs. Specifically, when sorting by the timestamp of the latest message notification for each reminder item, the occurrence time of the latest message for each reminder item is used as the sorting basis, with reminder items more recent in time appearing first, helping users prioritize handling the latest messages. For reminder items corresponding to collaboration spaces (i.e., space-level reminder items), the timestamp of its latest message notification is taken as the maximum value among the timestamps of the latest message notifications of all collaboration objects within that collaboration space, ensuring that collaboration spaces containing the latest activities are promptly displayed at the top of the list. When sorting by the number of unread message notifications for each reminder item, reminder items with a larger number of unread messages appear first, helping users prioritize handling conversations with a large backlog of messages; for reminder items corresponding to collaboration spaces, the number of unread messages is taken as the sum of the number of unread message notifications of all collaboration objects within that collaboration space, allowing users to perceive the overall unread status. When sorting by the pinned status of reminder items in the message processing interface, reminder items manually pinned by the user will always be placed at the top of the list, unaffected by timestamps and unread counts, making it easier for users to focus on certain important collaboration objects or collaboration spaces.

[0051] Through the aforementioned flexible and targeted sorting rules, this application enables users to quickly filter and locate high-priority or high-urgency message notifications in the message processing interface according to their actual needs, significantly improving the information presentation efficiency and user experience of the message processing interface.

[0052] Step 102: In response to triggering a reminder item in the message processing interface, display the collaborative content of the collaborating object in the message processing interface.

[0053] Here, "trigger" refers to an interactive action performed by the user on the reminder item, such as clicking, touching, or selecting it with a keyboard. In this application, the trigger action indicates that the user wants to view the specific collaborative content corresponding to the reminder item.

[0054] Collaborative content refers to the information carried by the collaborating objects. For example, for group chats, collaborative content refers to the conversation message record (including new and historical messages); for documents, it refers to the document text and comments; for tasks, it refers to task details, subtask list, and status; and for schedules, it refers to complete information such as the schedule's time, location, and participants. The specific form of collaborative content depends on the type of collaborating object. The core of this application is that, regardless of the type of collaborating object, after a user triggers a reminder, the collaboration platform directly displays the collaborative content in the message processing interface, without requiring the user to switch to a separate collaboration space interface.

[0055] In the specific implementation of step 102, when a user clicks on a notification item in the message processing interface, the collaboration platform first parses the collaboration object identifier associated with the notification item to determine its type and the collaboration space it belongs to. Then, it displays the collaboration content of the collaboration object in the current message processing interface.

[0056] For example, the display methods can take various forms, such as embedded panels, modal views, and side slide-out areas. Embedded panels dynamically replace the original notification list area with a collaborative content display area in the message processing interface; users can restore the list view using a back button or gesture. Side slide-outs involve sliding out a floating panel from the right (or left) side of the screen, displaying collaborative content while the main body of the message processing interface remains semi-transparent or visible; users can close the panel by clicking the outer area. Modal views pop up a centered or full-screen dialog box displaying collaborative content; users return to the list after closing the dialog box. These display methods can be configured according to device type (mobile, PC) and user preferences. For example, on mobile devices, due to limited screen size, full-screen modal views or side slide-outs are typically used; on PCs, embedded panels or sidebars can be used to fully utilize widescreen space.

[0057] These formats share the common characteristic that users remain within the message processing interface without switching interfaces or jumping to different tabs. Users can immediately return to the reminder list after viewing and processing the current collaborative content to continue handling other unread reminders. This design avoids the tedious switching between multiple collaboration spaces, significantly improving the continuity and efficiency of message processing.

[0058] In addition, once a user has finished viewing the collaborative content (e.g., read all new messages, marked the task as completed, etc.), the collaboration platform can automatically clear the unread flag associated with the reminder and synchronize the cleared status to the corresponding collaboration space (see subsequent embodiments for details).

[0059] In one embodiment, displaying the collaborative content of collaborative objects in the message processing interface includes: expanding a view of the collaborative space in the message processing interface, which is used to display the collection of collaborative objects in the collaborative space and the collaborative resources associated with the collaborative space.

[0060] In this embodiment, considering that after a user triggers a notification, they not only need to view the specific message content of the current collaborating object, but may also want to understand other resources within the collaboration space to which the collaborating object belongs (such as other group chats, documents, tasks, etc. within the same space) to obtain more complete contextual information, this application provides an implementation method for directly expanding the collaboration space view within the message processing interface. Specifically, when a user triggers a notification in the message processing interface, the collaboration platform does not simply pop up a simple message window in the message processing interface, but dynamically expands a complete collaboration space view within the message processing interface. This view can be presented in the form of an embedded panel, a side slide-out, or a modal overlay, etc. Its core feature is that the view can relatively completely display the structure of the collaboration space, including the collection of collaborating objects within the collaboration space and the collaborative resources associated with the collaboration space, and the collaborating object corresponding to the notification triggered by the user is highlighted in the view, while the collaborative content of the collaborating object (such as group chat message records, document text, etc.) is displayed. In this way, users can handle messages related to the current notification within the message processing interface, easily browse other resources within the space, and even directly switch to other collaborative objects within the space for processing, without having to close the current view and then open a separate collaborative space interface. This embodiment, while maintaining the message processing interface as a unified entry point, provides users with a richer space context, avoiding repeated switching between multiple interfaces and further improving collaboration efficiency.

[0061] When expanding the collaboration space view, the collaboration platform can automatically determine the initial state of the view based on the type of notification. For example, if a user triggers a group chat notification, the expanded view directly navigates to the group chat's conversation interface and automatically scrolls to the latest unread message; if a task notification is triggered, the view navigates to the task details page and highlights the task's key fields. Independent navigation is supported within the view, allowing users to freely browse the space directory and switch collaboration objects without affecting the underlying state of the message processing interface.

[0062] For example, see Figure 2 The view described above uses a two-column layout, which includes: a first column displaying a directory of collaborative objects within the collaboration space. Figure 2As can be seen, collaboration objects with unread messages are also marked as unread, allowing users to intuitively identify which collaboration objects have pending processing within the same directory structure, without needing to navigate to each collaboration object to understand the distribution of unread messages. The second column displays the collaboration content of the currently selected collaboration object. Through this two-column layout, users can quickly browse all collaboration objects and their unread statuses using the directory tree in the first column, and directly view and process specific content in the second column, achieving efficient navigation of resources and unified message processing within the space.

[0063] In addition, such as Figure 2 As shown, the view also provides basic information about the collaboration space, such as "28 documents, 32 space members." It also offers interactive extension capabilities; for example, certain controls can trigger other functions, such as viewing space information and group members. Thus, when handling message notifications, users can not only focus on the collaborative content of the current collaborator but also easily obtain an overall overview of the space and perform space-level management operations. This integrates message processing with space management, further improving the usability of the collaboration space and user operational efficiency.

[0064] It should be noted that, Figure 2 This is merely an illustrative example, and the layout of the views described in this application is not limited. For example, on a PC, this application also supports a three-column layout as a preferred option. The three-column layout adds a middle column between the first column (collaboration object directory) and the second column (collaboration content) to display a list of reminders for the currently selected collaboration object (e.g., a list of unread messages arranged in reverse chronological order). Users can quickly browse summaries of multiple unread messages in the middle column, and after clicking on one, the right column displays the detailed content of that message. This three-column layout is suitable for scenarios requiring the processing of a large number of messages one by one, such as customer service systems or teams with intensive project communication. Due to screen limitations, mobile devices typically adopt a layered structure: the message processing interface displays a list of reminders, and clicking on a reminder leads to a collaboration space view, which then uses a two-column or single-column layout. Regardless of the layout used, the core principle is to keep the user in the same interactive flow, avoiding the cognitive burden caused by interface switching.

[0065] Furthermore, in one embodiment, in response to entering the target session from the view of the collaboration space, a session interface of the target session is displayed, and a document sending control is provided in the session interface; wherein the document sending control is used to select a document from the collaboration space and send the selected document as a message to the target session.

[0066] In this embodiment, after the collaboration space view is expanded, users can not only browse the collection of sessions and document content in the space view, but also further enter a specific target session. Specifically, when a user clicks or selects a target session (such as a group chat) from the collaboration space view, the collaboration platform responds to the operation by displaying the session interface of the target session. In this session interface, a document sending control is provided. This control allows users to select documents from the collaboration space within the session interface and send the selected documents as messages to the target session. This document sending control can be in the form of a button, icon, or menu item. For example, a "Send Document" button can be placed near the input box in the session interface; clicking it will pop up a list of documents in the collaboration space for the user to select. Alternatively, drag-and-drop operations can be supported, allowing users to drag documents directly from the space directory to the input area of ​​the session interface to trigger document sending. All of the above methods are implementation methods of the document sending control described in this embodiment.

[0067] It's important to note that the document sending control is located within the session interface, not in the space view or elsewhere. In other words, if a user wants to send a document from within the collaboration space as a message to a session, they must first enter the session's interface and then use the control to select and send the document. For example, a user may see a document in the space view, but can only find the document sending option and send the document to the current group chat after entering the group chat interface related to that document.

[0068] The solution provided in this embodiment ensures that document sending operations always occur within a specific session context, avoiding context loss caused by directly sending documents in the space view. When a user sends a document in the session interface, they can simultaneously see the message stream of the current session, clearly knowing which session the document is to be sent to and to whom, thus ensuring the accuracy of communication and the continuity of context. Furthermore, since the document originates from the collaboration space, users can easily share and discuss document content with team members, further improving collaboration efficiency.

[0069] The technical solution provided in this application responds to message notifications generated by collaborating objects in the collaboration space. The notification item is displayed in the session list of the message processing interface, and an unread flag is associated with it. This allows users to intuitively see the distribution of all pending messages in a unified interface without actively entering individual collaboration spaces. When a user triggers a notification item in the message processing interface, the collaboration content of the corresponding collaborating object is directly displayed in the message processing interface, allowing the user to view and initially process the message without switching to the collaboration space interface. This process eliminates the user's repeated switching between the message processing interface and the collaboration space interface, avoiding contextual breaks caused by interface separation. It enables users to locate, view, and process messages within a continuous interactive flow. Therefore, this application achieves unified aggregation and rapid response of message notifications, reduces operational complexity, and improves the continuity and efficiency of message processing.

[0070] based on Figure 1 The message processing method exemplified in this application is further illustrated by the following embodiments: In one embodiment, in response to the current user joining the collaboration space, a reminder item corresponding to the collaboration space is generated in the session list of the message processing interface, and the historical message reminders in the collaboration space are displayed in the reminder item; wherein, the historical message reminders include message reminders generated in the collaboration space before the current user joined the collaboration space.

[0071] When a new user joins a collaborative space, they may lack knowledge of past communication records and collaborative content, easily missing discussions or decisions that occurred before they joined. To address this, this application provides a historical message reminder mechanism to ensure that new members can quickly grasp the historical context of the space after joining.

[0072] Specifically, in response to the current user joining a collaboration space, a corresponding notification item is generated for that collaboration space in the conversation list of the message processing interface. This notification item not only displays new message notifications generated after joining, but more importantly, it also displays historical message notifications within the collaboration space. Here, "historical message notifications" refers to message notifications generated within the collaboration space before the current user joined.

[0073] For example, suppose User A joins "Project A Space" on May 1, 2024. Prior to this, two collaboration objects already existed in this space: a "Project Communication Group" and a "Requirements Document." These two collaboration objects had generated multiple messages in April. After joining, User A will see a notification item for "Project A Space" in the conversation list of the message processing interface. This notification item will not only display new messages after joining but also historical message notifications generated in April (e.g., displaying "Project A Space has 15 historical messages" or showing summary information of historical messages). After clicking on this notification item to enter the collaboration space, the user can view the chat history and document comments before joining, understand the project's background, and avoid repeating questions or missing important decisions due to information gaps.

[0074] The beneficial effects of this embodiment are as follows: After a new member joins the collaboration space, there is no need to browse through the history of each group chat or document, nor to ask existing members "what was discussed before." They can intuitively perceive the existence of historical messages in the space through the space reminder item in the message processing interface, and enter the space to view the details with one click. This allows new members to quickly integrate into team collaboration, shortens the time cost of information synchronization, and improves the overall collaboration efficiency of the team.

[0075] In one embodiment, the unread flag of a notification item is cleared in response to completing the viewing of collaborative content.

[0076] In the technical solution provided in this embodiment, after a user completes the viewing operation of the collaborative content, the collaboration platform automatically clears the unread icon associated with the reminder item. Here, "completed the viewing operation" can be defined as various specific behaviors, such as: after the user clicks on the reminder item and enters the collaborative content area, the collaboration platform detects that the user has viewed the latest message; or the user manually marks it as read; or the user interacts by replying within the collaborative object. After clearing the unread icon, the red dot, badge, and other visual markers of the reminder item disappear from the message processing interface to prevent the user from repeatedly viewing read messages.

[0077] This mechanism ensures the accuracy of unread flags, enabling the message processing interface to accurately reflect the user's unread status and reduce information interference.

[0078] In one embodiment, in response to clearing the unread flag of a reminder item in the message processing interface, the unread status of the corresponding collaborative object in the collaboration space interface is simultaneously cleared; or, in response to clearing the unread status of a collaborative object in the collaboration space interface, the unread flag of the corresponding reminder item in the message processing interface is simultaneously cleared.

[0079] This embodiment provides a two-way synchronization mechanism for unread status between the message processing interface and the collaboration space interface. Specifically, when a user clears the unread flag of a notification item directly in the message processing interface (e.g., swiping left to mark it as read or selecting multiple notification items to clear in batches), the collaboration platform can simultaneously send a command to the corresponding collaboration space to clear the unread status of the corresponding collaboration object in that collaboration space, ensuring that after the user marks the notification as read in the message processing interface, the collaboration space interface no longer displays the unread flag for that collaboration object. Conversely, when a user finishes processing a collaboration object's messages in the collaboration space interface (e.g., reading all new messages one by one in a group chat), the collaboration platform can also simultaneously clear the unread flag of the corresponding notification item in the message processing interface.

[0080] In addition, this embodiment also supports batch clearing operations: users can select multiple reminders (including reminders from different collaboration spaces) at once in the message processing interface, and the collaboration platform sends synchronous clearing instructions to each collaboration space in parallel to achieve batch clearing of unread messages across spaces.

[0081] Through a two-way synchronization mechanism, regardless of which entry point a user uses to process a message, the unread status on the other side will automatically remain consistent, avoiding duplication of work and confusion caused by inconsistent status.

[0082] In one embodiment, in response to a collaborative object receiving a reminder message that mentions the current user, the reminder item corresponding to the reminder message is displayed in the first message display area of ​​the message processing interface; wherein, the first message display area is independent of the second message display area of ​​the message processing interface.

[0083] When messages mentioning the current user appear in collaborations (such as group chats, documents, tasks) (e.g., mentioning the current user, assigning a task to the current user, mentioning the current user in document comments, inviting the current user to participate in scheduled events, etc.), these messages often have high urgency and importance, requiring the user to handle them first. To prevent these messages from being buried among regular message notifications, this embodiment extracts the notification items corresponding to the mention messages and displays them separately in a dedicated first message display area within the message processing interface. This first message display area can be located at the top or in a prominent position within the message processing interface, independent of the second display area that displays regular message notifications. Users can process the mention message notifications in the first message display area first, and then process the notifications in the regular area.

[0084] In addition, the above sorting rules (such as reverse chronological order) can also be applied to the reminders in the first message display area. Once a message has been processed (e.g., the user clicks to view or reply), the reminder is automatically removed from the first message display area to avoid accumulating too many processed reminders and affecting the user's ability to quickly identify and process important unprocessed messages.

[0085] Meanwhile, removed reminders can be archived in the message history according to user-preset storage rules, making it convenient for users to review the relevant collaboration context when needed, ensuring the integrity and traceability of message processing.

[0086] In addition, if a user marks a reminder as "to be processed later", the reminder can be temporarily kept in the first message display area and distinguished from unprocessed items by special markings (such as bolding or highlighting), further improving the flexibility of message management.

[0087] This partitioned display method significantly reduces the risk of users missing important messages and improves the processing efficiency of high-priority messages.

[0088] In one embodiment, in response to receiving an access request to a collaboration object or collaboration space via an external link, the external link is parsed, the user is redirected to a message processing interface, and the reminder item corresponding to the collaboration object is highlighted in the message processing interface.

[0089] In practical applications, users may access collaboration platforms through various external links, such as message links in system push notifications, collaboration space links shared by other applications, and document links in emails. In existing technologies, these external links typically jump directly to the native interface of the corresponding collaboration object or collaboration space, bypassing the message processing interface and causing users to lose a unified entry point for handling all messages. This embodiment parses external links to identify whether their target is a collaboration object or a collaboration space. Instead of directly jumping to the target interface, it first jumps to the message processing interface and highlights the corresponding notification item in the message processing interface. For example, after a user clicks the "New message in project communication group" link in a push notification, the collaboration platform opens the message processing interface and highlights the "Project Communication Group" item in the notification list. The user can then click on this item to access the collaborative content.

[0090] This mechanism ensures that external links can also be incorporated into a unified message processing flow, maintaining a consistent and coherent user experience.

[0091] In one embodiment, in response to receiving a search request in the message processing interface, search results are displayed in the message processing interface; wherein, the search results include collaborative objects that match the search request and their corresponding reminders, and the identification information of the collaborative space to which the collaborative objects belong is displayed in association in the search results.

[0092] To facilitate quick location of specific content among numerous notifications, this embodiment integrates a search function into the message processing interface. Users can directly enter keywords (such as collaboration object name, collaboration space name, message content, etc.) in the message processing interface, and the collaboration platform will perform a search within the scope of the user's current access permissions. The search results are still displayed in the message processing interface, including collaboration objects matching the search request and their corresponding notifications. In particular, since different collaboration spaces may contain collaboration objects with the same name (e.g., multiple spaces may have "requirements discussion" group chats), to help users distinguish them, the search results can be associated with and display the identification information (such as space name and space icon) of the collaboration space to which each collaboration object belongs. After clicking on a notification in the search results, the user can then proceed according to... Figure 1 The workflow will redirect to the collaborating object and display the collaborative content.

[0093] This embodiment deeply integrates the search function with the message processing interface, further improving the efficiency of users in finding and processing specific message notifications.

[0094] Figure 3 This is a block diagram illustrating an embodiment of a message processing apparatus provided in this application. Figure 3 As shown, the device includes: The message aggregation module 31 is used to respond to message reminders generated by collaborative objects in the collaborative space, display the reminder items corresponding to the message reminders in the session list of the message processing interface, and associate the reminder items with unread flags; The display module 32 is used to display the collaborative content of the collaborating object in the message processing interface in response to triggering the reminder item in the message processing interface.

[0095] In one possible implementation, the display module 32 is specifically used for: Expand the view of the collaboration space in the message processing interface. The view is used to display the collection of collaboration objects in the collaboration space and the collaboration resources associated with the collaboration space.

[0096] In one possible implementation, the device further includes: The document sending module is used to respond to entering the target session from the view of the collaboration space, display the session interface of the target session, and provide document sending controls in the session interface; The document sending control is used to select a document from the collaboration space and send the selected document as a message to the target session.

[0097] In one possible implementation, the message aggregation module 31 is specifically used for: In response to message notifications generated by collaborating objects within the collaboration space, the notification item corresponding to the collaboration space is located in the session list of the message processing interface; wherein, the notification item corresponding to the collaboration space is used to aggregate and display message notifications from all collaborating objects within the collaboration space; If there is no reminder item corresponding to the collaboration space in the session list, add a reminder item corresponding to the collaboration space to the session list and associate an unread flag with the reminder item; If a reminder item corresponding to the collaboration space already exists in the session list, update the unread flag of the reminder item.

[0098] In one possible implementation, message notifications generated by collaborative objects created within the collaborative space, as well as those created outside the collaborative space and then added to the collaborative space, are all assigned to the corresponding notification item in the collaborative space for display.

[0099] In one possible implementation, the device further includes: The historical message synchronization module is used to generate a reminder item corresponding to the collaboration space in the session list of the message processing interface in response to the current user joining the collaboration space, and to display the historical message reminders in the collaboration space in the reminder item; The historical message reminders include message reminders generated within the collaboration space before the current user joined the collaboration space.

[0100] In one possible implementation, the reminders in the conversation list are arranged according to a preset sorting rule, which includes: The reminders are sorted according to the timestamp of the latest message notification corresponding to each reminder item; wherein, for reminder items corresponding to collaboration spaces, the timestamp of the latest message notification is the maximum value among the timestamps of the latest message notifications of all collaboration objects within the collaboration space; Alternatively, the reminders can be sorted according to the number of unread message reminders for the corresponding collaborative objects; wherein, for reminders corresponding to a collaborative space, the number of unread message reminders is the sum of the number of unread message reminders for all collaborative objects within the collaborative space; Alternatively, the reminders can be sorted according to their pinning status in the message processing interface.

[0101] In one possible implementation, the device further includes: The identifier clearing module is used to clear the unread identifier of the reminder item in response to completing the viewing operation of the collaborative content.

[0102] In one possible implementation, the device further includes: The status synchronization module is used to synchronously clear the unread status of the corresponding collaborative object in the interface of the collaboration space in response to clearing the unread flag of the reminder item in the message processing interface; Alternatively, in response to clearing the unread status of the collaborative object in the interface of the collaborative space, the unread flag of the corresponding reminder item in the message processing interface is cleared simultaneously.

[0103] In one possible implementation, the device further includes: The message partition display module is used to respond to the collaborative object receiving a reminder message mentioning the current user, and to display the reminder item corresponding to the reminder message in the first message display area of ​​the message processing interface; wherein, the first message display area is independent of the second message display area of ​​the message processing interface.

[0104] In one possible implementation, the device further includes: The interface jump module is used to respond to an access request received via an external link pointing to the collaboration object or the collaboration space, parse the external link, jump to the message processing interface, and highlight the reminder item corresponding to the collaboration object in the message processing interface.

[0105] In one possible implementation, the device further includes: The search module is used to respond to a search request received in the message processing interface and display search results in the message processing interface; wherein, the search results include collaborative objects that match the search request and their corresponding reminder items, and the identification information of the collaborative space to which the collaborative object belongs is displayed in the search results.

[0106] like Figure 4 As shown in the figure, this application provides an electronic device, including a processor 111, a communication interface 112, a memory 113, and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114. Memory 113 is used to store computer programs; In one embodiment of this application, when the processor 111 executes a program stored in the memory 113, it implements the message processing method provided in any of the foregoing method embodiments, including: In response to a message notification generated by a collaborative object associated with the collaboration space, the notification item corresponding to the message notification is displayed in the message processing interface, and an unread flag is associated with the notification item; wherein, the message processing interface is independent of the interface of the collaboration space; In response to triggering the notification item in the message processing interface, the view of the collaboration space is expanded in the message processing interface, and the collaboration content of the collaboration object is displayed in the view.

[0107] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the message processing method provided in any of the foregoing method embodiments.

[0108] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0109] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented using software plus a general-purpose hardware platform, or of course, using hardware. Based on this understanding, the above technical solutions, in essence or the parts that contribute to the related technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0110] It should be understood that the terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “described” as used herein may also include the plural forms. The terms “comprising,” “including,” “containing,” and “having” are inclusive and therefore indicate the presence of the stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not construed as requiring them to be performed in a particular order described or illustrated unless the order of performance is explicitly indicated. It should also be understood that additional or alternative steps may be used.

[0111] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A message processing method, characterized in that, The method includes: In response to a message notification generated by a collaborating object in the collaboration space, the notification item corresponding to the message notification is displayed in the session list of the message processing interface, and an unread flag is associated with the notification item. In response to triggering the reminder item in the message processing interface, the collaborative content of the collaborating object is displayed in the message processing interface.

2. The method according to claim 1, characterized in that, The display of the collaborative content of the collaborating object in the message processing interface includes: Expand the view of the collaboration space in the message processing interface. The view is used to display the collection of collaboration objects in the collaboration space and the collaboration resources associated with the collaboration space.

3. The method according to claim 2, characterized in that, The method further includes: In response to entering a target session from the view of the collaboration space, the session interface of the target session is displayed, and a document sending control is provided in the session interface; The document sending control is used to select a document from the collaboration space and send the selected document as a message to the target session.

4. The method according to claim 1, characterized in that, The system responds to message notifications generated by collaborating objects in the collaboration space, displays the corresponding notification item in the session list of the message processing interface, and associates an unread flag with the notification item, including: In response to message notifications generated by collaborating objects within the collaboration space, the notification item corresponding to the collaboration space is located in the session list of the message processing interface; wherein, the notification item corresponding to the collaboration space is used to aggregate and display message notifications from all collaborating objects within the collaboration space; If there is no reminder item corresponding to the collaboration space in the session list, add a reminder item corresponding to the collaboration space to the session list and associate an unread flag with the reminder item; If a reminder item corresponding to the collaboration space already exists in the session list, update the unread flag of the reminder item.

5. The method according to claim 4, characterized in that, Message notifications generated by collaborative objects created within the collaborative space, as well as collaborative objects created outside the collaborative space and then added to the collaborative space, are all displayed under the corresponding notification item of the collaborative space.

6. The method according to claim 1, characterized in that, The method further includes: In response to the current user joining the collaboration space, a reminder item corresponding to the collaboration space is generated in the session list of the message processing interface, and the historical message reminders in the collaboration space are displayed in the reminder item; The historical message reminders include message reminders generated within the collaboration space before the current user joined the collaboration space.

7. The method according to claim 1, characterized in that, The reminders in the conversation list are arranged according to a preset sorting rule, which includes: The reminders are sorted according to the timestamp of the latest message notification corresponding to each reminder item; wherein, for reminder items corresponding to collaboration spaces, the timestamp of the latest message notification is the maximum value among the timestamps of the latest message notifications of all collaboration objects within the collaboration space; Alternatively, the reminders can be sorted according to the number of unread message reminders for the corresponding collaborative objects; wherein, for reminders corresponding to a collaborative space, the number of unread message reminders is the sum of the number of unread message reminders for all collaborative objects within the collaborative space; Alternatively, the reminders can be sorted according to their pinned status in the message processing interface.

8. The method according to claim 1, characterized in that, The method further includes: In response to completing the viewing of the collaborative content, the unread flag of the notification item is cleared.

9. The method according to claim 1, characterized in that, The method further includes: In response to clearing the unread flag of the reminder item in the message processing interface, the unread status of the corresponding collaboration object in the collaboration space interface is simultaneously cleared. Alternatively, in response to clearing the unread status of the collaborative object in the interface of the collaborative space, the unread flag of the corresponding reminder item in the message processing interface is cleared simultaneously.

10. The method according to claim 1, characterized in that, The method further includes: In response to the collaborating object receiving a reminder message mentioning the current user, the reminder item corresponding to the reminder message is displayed in the first message display area of ​​the message processing interface; wherein, the first message display area is independent of the second message display area of ​​the message processing interface.

11. The method according to claim 1, characterized in that, The method further includes: In response to receiving an access request to the collaboration object or the collaboration space via an external link, the external link is parsed, the user is redirected to the message processing interface, and the reminder item corresponding to the collaboration object is highlighted in the message processing interface.

12. The method according to claim 1, characterized in that, The method further includes: In response to receiving a search request in the message processing interface, the search results are displayed in the message processing interface; wherein, the search results include the collaborating objects that match the search request and their corresponding reminder items, and the identification information of the collaborating space to which the collaborating objects belong is displayed in association in the search results.

13. A message processing device, characterized in that, The device includes: The message aggregation module is used to respond to message reminders generated by collaborative objects in the collaborative space, display the reminder items corresponding to the message reminders in the session list of the message processing interface, and associate the reminder items with an unread flag; The display module is used to display the collaborative content of the collaborating object in the message processing interface in response to triggering the reminder item in the message processing interface.

14. A storage medium, characterized in that, The storage medium stores one or more programs, which can be executed by one or more processors to implement the message processing method according to any one of claims 1-12.

Images