Message processing method and related device

By displaying a message aggregation window and an announcement message page on the session list page, the problem of announcement messages being easily overlooked across organizational structures is solved, and cross-organizational structure announcement message management and visibility are achieved.

CN117014545BActive Publication Date: 2026-02-06TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202210948063.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-08-09
Publication Date
2026-02-06
Estimated Expiration
2042-08-09

AI Technical Summary

Technical Problem

In existing technologies, announcements across organizational structures are easily overlooked and are inconvenient to manage, especially when sent via instant messaging group notifications, where they are easily overwhelmed by other messages.

Method used

The message aggregation window is displayed on the session list page of the first application, which aggregates the received announcement messages and responds to the triggered operation to display the announcement message page. It supports editing the announcement content and determining the scope across organizational structures, and sends announcement messages to related organizational objects.

Benefits of technology

It enables cross-organizational management of announcement messages, reducing the probability of users ignoring announcement messages and improving the visibility and management efficiency of announcement messages.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117014545B_ABST
    Figure CN117014545B_ABST
Patent Text Reader

Abstract

The application discloses a message processing method and related equipment, and related embodiments can be applied to various scenes such as cloud technology, artificial intelligence, auxiliary driving and intelligent transportation; at least one announcement message is received, the announcement message is an announcement message sent by a first object to a second object in a message system, the first object is in a first object organization, the second object is in a second object organization, and the first object organization and the second object organization are associated organizations; a message aggregation window is displayed in a session list page of the first application; in response to a triggering operation on the message aggregation window, an announcement message page is displayed, and the announcement message page includes the at least one announcement message. The application can send announcement messages to objects in associated organizations, and can also aggregate announcement messages in a message aggregation window, so that users are less likely to ignore announcement messages, and it is also beneficial to manage announcement messages.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a message processing method and related equipment. BACKGROUND

[0002] With the rapid development of network technology and communication technology, various application programs (APPs) based on mobile terminals have been widely used, and users can use various APPs for entertainment, learning, work, etc. In a specific scenario, when an APP needs to be updated or has a major event to be announced, an announcement message is usually sent to users through an announcement system.

[0003] In the related art, only users in the same organizational structure can be pushed the announcement message, and for users in different organizational structures, the message notification needs to be sent through an IM (Instant Messaging) session group. Since there is a high probability that the notification will be brushed away by other session messages, the user is likely to ignore the notification, and the notification message sent through the IM group is not convenient for managing the notification message. SUMMARY

[0004] Embodiments of the present application provide a message processing method and related equipment, which can include a message processing apparatus, an electronic device, a computer readable storage medium and a computer program product, and can be beneficial for managing announcement messages.

[0005] Embodiments of the present application provide a message processing method, which includes:

[0006] receiving at least one announcement message, the announcement message being an announcement message sent by a first object to a second object in a message system, the message system being a system corresponding to a first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations;

[0007] displaying a message aggregation window in a session list page of the first application, the message aggregation window being used to aggregate the received at least one announcement message;

[0008] in response to a triggering operation on the message aggregation window, displaying an announcement message page, the announcement message page including the at least one announcement message.

[0009] Embodiments of the present application provide a message processing method, which includes:

[0010] displaying an announcement publishing page of a first application;

[0011] In response to a notice editing operation of a first object on the notice publishing page in a message system, obtain a notice content and a notice object range, the notice object range including a second object, the message system being a system corresponding to the first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations;

[0012] Send a notice message including the notice content to objects in the notice object range, so as to aggregate the notice message in a message aggregation window of a client where the objects in the notice object range are located.

[0013] Correspondingly, an embodiment of the present application provides a message processing apparatus, comprising:

[0014] A receiving unit is configured to receive at least one notice message, the notice message being a notice message sent by a first object to a second object in a message system, the message system being a system corresponding to a first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations;

[0015] A first display unit is configured to display a message aggregation window in a session list page of the first application, the message aggregation window being configured to aggregate the received at least one notice message;

[0016] A second display unit is configured to display a notice message page in response to a triggering operation on the message aggregation window, the notice message page including the at least one notice message.

[0017] Correspondingly, an embodiment of the present application provides a message processing apparatus, comprising:

[0018] A third display unit is configured to display a notice publishing page of a first application;

[0019] A receiving unit is configured to receive at least one notice message, the notice message being a notice message sent by a first object to a second object in a message system, the message system being a system corresponding to a first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations;

[0020] A sending unit is configured to send a notice message including the notice content to objects in the notice object range, so as to aggregate the notice message in a message aggregation window of a client where the objects in the notice object range are located.

[0021] Optionally, in some embodiments of the present application, the announcement message comprises a second application announcement message, the second application being an application in the message system, and the message aggregation window is used for aggregating at least one received announcement message of the second application.

[0022] Optionally, in some embodiments of the present application, the session list page further comprises at least one session message window, and the message aggregation window is located above all the session message windows.

[0023] Optionally, in some embodiments of the present application, the message processing apparatus can further comprise a read mark unit, which is configured to:

[0024] The read mark unit is configured to mark the announcement message in the message aggregation window as unread in response to an unread mark operation on the message aggregation window.

[0025] Optionally, in some embodiments of the present application, the first object organization and the second object organization are different organizations, and the first object organization is an organization having an upstream relationship with the second object organization.

[0026] Optionally, in some embodiments of the present application, the second display unit can comprise a classification subunit and a first display subunit, which are configured to:

[0027] The classification subunit is configured to classify the received at least one announcement message based on the message sending object of the announcement message, to obtain at least one announcement message set, different announcement message sets aggregating at least one announcement message sent by different message sending objects.

[0028] The first display subunit is configured to display each announcement message set in the announcement message page based on the message receiving time of the announcement message in response to a trigger operation on the message aggregation window.

[0029] Optionally, in some embodiments of the present application, the announcement publishing page comprises an announcement content editing area and an announcement range determining area.

[0030] The acquisition unit can comprise a content acquisition subunit, a second display subunit and a range determining subunit, which are configured to:

[0031] The content acquisition subunit is configured to acquire announcement content in response to an editing operation of the first object in the message system on the announcement content editing area.

[0032] The second display subunit is configured to display an object selection page comprising at least one candidate object organization in response to a trigger operation of the first object in the message system on the announcement range determining area.

[0033] a range determining sub-unit, configured to determine a range of the announcement object based on a selection operation on the candidate object organization.

[0034] Optionally, in some embodiments of the present application, the second display sub-unit can be specifically configured to, in response to a triggering operation of a first object in the message system on the announcement range determining area, acquire an organization relationship chain corresponding to the first object organization; and display a candidate organization list in an object selection page according to the organization relationship chain, candidate object organizations in the candidate organization list having an association relationship with the first object organization.

[0035] Optionally, in some embodiments of the present application, the object selection page further includes an upstream and downstream import area; and the message processing apparatus can further include an organization updating unit, configured to update the candidate object organization; specifically, the organization updating unit can include a third display sub-unit, a establishing sub-unit and an updating sub-unit, as follows:

[0036] the third display sub-unit is configured to, in response to a triggering operation on the upstream and downstream import area, display an import page, the import page including at least one candidate import organization;

[0037] the establishing sub-unit is configured to, in response to a selection operation on a target import organization in the candidate import organization, establish an upstream and downstream relationship between the first object organization and the target import organization;

[0038] the updating sub-unit is configured to update the candidate object organization based on the upstream and downstream relationship, the updated candidate object organization including the target import organization.

[0039] Optionally, in some embodiments of the present application, the third display unit can include a fourth display sub-unit and a fifth display sub-unit, as follows:

[0040] the fourth display sub-unit is configured to display a publishing application selection page corresponding to a first application, the publishing application selection page including application identifiers of at least one candidate application, the candidate application including the first application and a second application, the second application being an application in the message system;

[0041] the fifth display sub-unit is configured to, in response to a selection operation on an application identifier of a target application in the candidate application, display an announcement publishing page of the first application, the announcement publishing page including the application identifier of the target application;

[0042] the sending unit can be specifically configured to send an announcement message of the target application containing the announcement content to objects within the announcement object range.

[0043] Optionally, in some embodiments of the present application, the target application is the second application.

[0044] The sending unit can be specifically configured to send the second application's announcement message containing the announcement content to the objects within the announcement object range when the first object is within the visible range corresponding to the second application.

[0045] Optionally, in some embodiments of the present application, the sending unit can be further configured to authorize the first object to send the second application's announcement message when the first object is not within the visible range corresponding to the second application; and send the second application's announcement message containing the announcement content to the objects within the announcement object range when the first object is successfully authorized.

[0046] Optionally, in some embodiments of the present application, the sending unit can include a judgment subunit, a determination subunit and a sending subunit, as follows:

[0047] The judgment subunit is configured to judge whether the objects within the announcement object range have the viewing right for the announcement message.

[0048] The determination subunit is configured to determine the actual announcement object from the objects within the announcement object range according to the judgment result.

[0049] The sending subunit is configured to send the announcement message containing the announcement content to the actual announcement object.

[0050] Optionally, in some embodiments of the present application, the message processing apparatus can further include a historical announcement editing unit, which is configured to edit the historical announcement message; specifically, the historical announcement editing unit can include a sixth display subunit, a seventh display subunit and an execution subunit, as follows:

[0051] The sixth display subunit is configured to display the historical announcement page of the first application, the historical announcement page including at least one historical announcement message sent by the first object.

[0052] The seventh display subunit is configured to display the operation page of the target historical announcement message in response to the selection operation of the target historical announcement message in the historical announcement page.

[0053] The execution subunit is configured to execute the response event corresponding to the editing operation of the target historical announcement message in the operation page.

[0054] Optionally, in some embodiments of the present application, the historical announcement page comprises an application selection control; the sixth display sub-unit can be specifically configured to display an application selection page in response to a triggering operation on the application selection control, the application selection page comprising applications that have published historical announcement messages, the applications comprising the first application and a second application, the second application being an application in the message system; and update the historical announcement page displaying the first application based on a selection operation on a target application in the application selection page, the updated historical announcement page comprising historical announcement messages corresponding to the target application.

[0055] An electronic device provided in an embodiment of the present application comprises a processor and a memory, the memory storing a plurality of instructions, and the processor loads the instructions to perform the steps in the message processing method provided in the embodiment of the present application.

[0056] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program is executed by a processor to implement the steps in the message processing method provided in the embodiment of the present application.

[0057] In addition, an embodiment of the present application further provides a computer program product comprising a computer program or instructions, which are executed by a processor to implement the steps in the message processing method provided in the embodiment of the present application.

[0058] An embodiment of the present application provides a message processing method and related devices, which can receive at least one announcement message, the announcement message being an announcement message sent by a first object to a second object in a message system, the message system being a system corresponding to a first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations; display a message aggregation window in a session list page of the first application, the message aggregation window being used to aggregate the received at least one announcement message; and display an announcement message page in response to a triggering operation on the message aggregation window, the announcement message page comprising the at least one announcement message. The present application can implement sending of an announcement message to an object in an associated organization, and can also aggregate the announcement message in a message aggregation window, so that a user is less likely to ignore the announcement message, and it is also beneficial to manage the announcement message. BRIEF DESCRIPTION OF DRAWINGS

[0059] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without any creative effort.

[0060] Figure 1a is a scenario diagram of a message processing method provided by an embodiment of the present application;

[0061] Figure 1b is a flowchart of a message processing method provided by an embodiment of the present application;

[0062] Figure 2a is another flowchart of a message processing method provided by an embodiment of the present application;

[0063] Figure 2b is a page diagram of a message processing method provided by an embodiment of the present application;

[0064] Figure 2c is another page diagram of a message processing method provided by an embodiment of the present application;

[0065] Figure 2d is another page diagram of a message processing method provided by an embodiment of the present application;

[0066] Figure 2e is another flowchart of a message processing method provided by an embodiment of the present application;

[0067] Figure 2f is another page diagram of a message processing method provided by an embodiment of the present application;

[0068] Figure 2g is another page diagram of a message processing method provided by an embodiment of the present application;

[0069] Figure 2h is another flowchart of a message processing method provided by an embodiment of the present application;

[0070] Figure 3a is a structural diagram of a message processing apparatus provided by an embodiment of the present application;

[0071] Figure 3b is another structural diagram of a message processing apparatus provided by an embodiment of the present application;

[0072] Figure 4 is a structural diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0073] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work fall within the scope of protection of the present application.

[0074] Embodiments of the present application provide a message processing method and related devices, which can include a message processing apparatus, an electronic device, a computer readable storage medium and a computer program product. The message processing apparatus can be integrated in an electronic device, which can be a terminal or a server.

[0075] Specifically, embodiments of the present application provide a message processing apparatus (for distinction, can be referred to as a first message processing apparatus) applicable to a first electronic device, which can be a terminal or the like. Embodiments of the present application also provide a message processing apparatus (for distinction, can be referred to as a second message processing apparatus) applicable to a second electronic device, which can be a terminal or a server. The terminal can be a mobile phone, a tablet computer, a notebook computer, or a personal computer (PC, Personal Computer) or the like. The server can be a single server or a server cluster composed of multiple servers.

[0076] The message processing method provided by the present application can be applied to an application environment as shown in the scenario in the present application. Figure 1a The message processing system provided by embodiments of the present application includes a sending end 110 and a receiving end 120. The sending end 110 and the receiving end 120 are connected through a network, such as a wired or wireless network connection.

[0077] In one embodiment, the sending end 110 can display a notice publishing page of a first application. In response to a notice editing operation of a first object in a message system on the notice publishing page, the sending end 110 obtains a notice content and a notice object range, the notice object range including a second object, the message system being a system corresponding to the first application, the first object being in a first object organization, the second object being in a second object organization, and the first object organization and the second object organization being associated organizations. The sending end 110 sends a notice message including the notice content to objects in the notice object range, so as to aggregate the notice message in a message aggregation window of a client (specifically, the receiving end 120) of the objects in the notice object range.

[0078] The receiving end 120 can be configured to receive at least one announcement message sent by the sending end 110, the announcement message being an announcement message sent by a first object to a second object in a message system, the message system being a system corresponding to a first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations; display a message aggregation window in a session list page of the first application, the message aggregation window being configured to aggregate the received at least one announcement message; and in response to a triggering operation on the message aggregation window, display an announcement message page, the announcement message page including the at least one announcement message.

[0079] The sending end 110 and the receiving end 120 can be terminals, which can be various personal computers, notebook computers, smart phones, tablet computers, smart home appliances, vehicle-mounted devices, and the like. The terminals can further include a client, which can be an application client or a browser client. The sending end 110 can also be a server or a server cluster.

[0080] The message processing method provided by the embodiments of the present application relates to voice technology and natural language processing in the field of artificial intelligence.

[0081] Artificial intelligence (AI) is a theory, method, technology, and application system for simulating, extending, and expanding human intelligence by using a digital computer or a machine controlled by a digital computer to perceive an environment, acquire knowledge, and use the knowledge to obtain optimal results. In other words, artificial intelligence is a comprehensive technology of computer science, which aims to understand the essence of intelligence and produce a new intelligent machine that can react in a similar way to human intelligence. Artificial intelligence is the design principle and implementation method of various intelligent machines, enabling machines to have perception, reasoning, and decision-making functions. Artificial intelligence technology is a comprehensive subject that involves a wide range of fields, including both hardware and software technologies. The artificial intelligence software technology mainly includes computer vision technology, speech processing technology, natural language processing technology, and machine learning / deep learning, automatic driving, intelligent transportation, and several other directions.

[0082] The key technologies of speech technology include automatic speech recognition technology, speech synthesis technology, and voiceprint recognition technology. Enabling computers to hear, see, speak, and feel is the development direction of future human-computer interaction, and voice has become one of the most promising human-computer interaction methods in the future.

[0083] Among them, nature language processing (Nature Language processing, NLP) is an important direction in the field of computer science and artificial intelligence. It studies the various theories and methods that can realize the effective communication between people and computers with natural language. Natural language processing is a science that integrates linguistics, computer science and mathematics. Therefore, the research in this field will involve natural language, that is, the language used in daily life, so it is closely related to the study of linguistics. Natural language processing technology usually includes text processing, semantic understanding, machine translation, robot question and answer, knowledge graph and other technologies.

[0084] The following will be described in detail. It should be noted that the order of description of the following embodiments is not limited as the preferred order of the embodiments.

[0085] It can be understood that in the specific embodiments of the present application, data related to user information is involved, and when the above embodiments of the present application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of relevant countries and regions.

[0086] The present embodiment will be described from the perspective of the first message processing device, which can be integrated in the first electronic device, which can be a terminal or the like.

[0087] In addition, it should be noted that the present embodiment can be applied to various scenarios such as cloud technology, artificial intelligence, intelligent transportation, and assisted driving.

[0088] As shown in Figure 1b The specific flow of the message processing method can be as follows:

[0089] 101、receive at least one announcement message, the announcement message is an announcement message sent by a first object to a second object in a message system, the message system is a system corresponding to a first application, the first object is in a first object organization, the second object is in a second object organization, the first object organization and the second object organization are associated organizations.

[0090] Among them, the announcement message can refer to the message that the application publicly informs the user, which can be used to indicate the changes and activity preview information in the application. The announcement message can include but is not limited to announcement content, timestamp, announcement name and other information. The type of the announcement message is not limited, which can be video, audio, image and text, etc.

[0091] The first application can be a message interaction application, specifically, an instant messaging (IM) application, or a payment application, or a shopping application, etc., and the present embodiment does not limit the same. The message system is a system corresponding to the first application, and the message system can include an account system corresponding to the first object and the second object. The first application can log in an object account (such as an object account of the first object or the second object) under the account system, and the account system is an account system used by the object in the first application. For example, the account system is an enterprise account system, corresponding to an enterprise message system.

[0092] The first object is the notifier of the announcement message, and the second object is the notified party of the announcement message. The first object is in a first object organization, and the second object is in a second object organization. The first object organization and the second object organization are associated organizations. The associated organizations can be the same organization or different organizations. If the first object organization and the second object organization are different organizations, the association between the first object organization and the second object organization can be an upstream-downstream relationship.

[0093] In an industrial chain, the flow direction of commodities, technologies, or services is similar to water flow, and the sequence relationship of the first and the second due to the difference in relative time points and positions is called an upstream-downstream relationship. For example, the materials, products, components, and semi-finished products supplied from the supply end to the procurement end belong to the upstream and the downstream, respectively, and they belong to an upstream-downstream relationship.

[0094] Optionally, in the present embodiment, the first object organization and the second object organization are different organizations, and the first object organization is an organization having an upstream-downstream relationship with the second object organization.

[0095] Specifically, the first object organization can be an upstream organization of the second object organization, and the second object organization can be a downstream organization of the first object organization. In this case, the first object is an upstream user of the second object, and the second object is a downstream user of the first object.

[0096] For example, the first object organization and the second object organization are associated in an industrial chain, and specifically, the first object organization and the second object organization can have an industrial upstream-downstream relationship. For example, the first application is an enterprise type message interaction application, the first object organization can be an upstream enterprise in an industrial chain, and the second object organization can be a downstream enterprise in the industrial chain. If the game product of the upstream enterprise is updated, the object (such as an administrator) in the first object organization can send an announcement message about the game product update to the user of the downstream enterprise.

[0097] Specifically, upstream and downstream industrial chains can also be called extended industrial chains. This involves extending an existing industrial chain as much as possible upstream and downstream. Upstream extension typically leads to basic industry and technology research and development, while downstream extension leads to market expansion. The essence of an industrial chain is the connection between companies in different industries, and this industrial connection is essentially the supply and demand relationship between companies in each industry.

[0098] For example, in the game industry chain, upstream organizations can include content providers and game developers, specifically companies responsible for game content creation and game development. Content providers are responsible for providing basic game content support to game developers, while game developers can be responsible for game design, creation, and research and development. The corresponding downstream organizations can be companies that operate games.

[0099] In a specific scenario, the first application is a messaging application for enterprises. Enterprises in the first application can create their own upstream and downstream spaces and establish upstream and downstream relationships with other enterprises in the first application. Upstream and downstream spaces can be used to aggregate and manage a certain type of business partners of an enterprise. Through upstream and downstream spaces, the contacts of business partners such as suppliers, distributors, and platform merchants can be managed in a unified manner, enabling rapid communication with members of other enterprises.

[0100] 102. Display a message aggregation window on the session list page of the first application, the message aggregation window being used to aggregate at least one received announcement message.

[0101] The conversation list page displays the conversation message windows for each conversation corresponding to the second object. A conversation message window for a specific conversation aggregates the messages sent by its members. These message windows are sorted and displayed in ascending order based on the message reception time. A conversation can be a one-on-one chat (or a group with two members) or a group chat (a multi-person group). Users can access the corresponding conversation page by triggering an action (such as clicking) on ​​a conversation in the conversation list page.

[0102] The message aggregation window is used to aggregate received announcement messages; this window is also known as the message notification window. Different applications can have different message aggregation windows, meaning announcement messages from different applications can be aggregated in different message aggregation windows, with each window containing announcement messages from its respective application. The conversation list page can simultaneously display message aggregation windows for multiple applications. These applications can include the first application itself and other applications within the first application's messaging system.

[0103] Optionally, in the embodiment, the announcement message comprises a second application announcement message, the second application is an application in the message system, and the message aggregation window is configured to aggregate at least one received second application announcement message.

[0104] The second application can refer to an application in the message system other than the first application, and specifically, the second application can also be an application program dependent on the first application. For example, the second application can be a self-built application or a third-party application corresponding to the first application.

[0105] The self-built application can be an application program accessed by the first application through an API to increase certain business services. For example, if the first application is an enterprise type message interaction application, it can access more personalized office applications for the first application by providing APIs (Application Programming Interface) of application programs such as address book management, customer contact, identity verification, application management, message push, material management, efficiency tools, enterprise payment, enterprise interconnection, conversation content archive, electronic invoice, home-school communication, home-school application, government-citizen communication, etc. These applications can be regarded as self-built applications of the first application.

[0106] The third-party application can be an external application managed by a third party corresponding to the first application, which specifically aims to facilitate users of the first application to use the cloud application of the third party through simple operations. The core mechanism to achieve this goal can include that the service provider and the developer of the first application pre-register the application information of the first application on the management end of the third party. When a user in the first application selects to use the third-party application, the application can be installed by one key through an authorization process.

[0107] Optionally, in the embodiment, the session list page further comprises at least one session message window, and the message aggregation window is located above all the session message windows.

[0108] Specifically, the message aggregation window can be placed at the top of the session list page, so that the user can more easily notice the announcement message, which is conducive to avoiding the user ignoring the announcement message.

[0109] In some embodiments, the position arrangement of the session message windows and the message aggregation window in the session list page can also be determined according to the message receiving time of the latest message in the session message window and the message aggregation window. Specifically, the later the message receiving time of the latest message, the more forward the arrangement position of the message window.

[0110] Optionally, in the embodiment, the message processing method can further comprise:

[0111] In response to an unread marking operation on the message aggregation window, marking the announcement message in the message aggregation window as an unread state.

[0112] In the step of marking the announcement message in the message aggregation window as an unread state in response to the unread marking operation on the message aggregation window, the message aggregation window can be long-pressed, a function area corresponding to the message aggregation window can be displayed on a conversation list page, the function area can include an unread marking control, and the announcement message in the message aggregation window can be marked as an unread state based on a triggering operation (such as a click operation) on the unread marking control.

[0113] The embodiment can provide an unread marking function of the announcement message to remind a user to view the announcement message.

[0114] 103. In response to a triggering operation on the message aggregation window, an announcement message page is displayed, and the announcement message page includes the at least one announcement message.

[0115] The triggering operation on the message aggregation window can be a click operation or a sliding operation, and the embodiment is not limited in this regard. The announcement message page can be used to display the announcement message.

[0116] Specifically, the announcement message in the announcement message page can have a message format, which can be in the form of a card, that is, the announcement message can be presented in the form of a message card, and the message card can include announcement content, an announcement title, and information of a publisher of the announcement message corresponding to the announcement message.

[0117] In some embodiments, the announcement messages in the announcement message page can be arranged according to the message receiving time and the message sending object of the first application.

[0118] Optionally, in the embodiment, the step of displaying the announcement message page in response to the triggering operation on the message aggregation window can include:

[0119] Based on the message sending object of the announcement message, the received at least one announcement message is classified to obtain at least one announcement message set, and different announcement message sets aggregate at least one announcement message sent by different message sending objects.

[0120] In response to the triggering operation on the message aggregation window, each announcement message set is displayed in the announcement message page based on the message receiving time of the announcement message.

[0121] In this embodiment, the announcement messages sent by different message sending objects can be aggregated in different announcement message sets, that is, the announcement messages in the same announcement message set are sent by the same message sending object.

[0122] In this embodiment, the position arrangement of each announcement message set in the announcement message page can be determined based on the message receiving time of the latest announcement message in each announcement message set. Specifically, the later the message receiving time of the latest announcement message in the announcement message set, the more eye-catching the arrangement position of the announcement message set in the announcement message page.

[0123] As can be seen from the above, in this embodiment, at least one announcement message can be received, the announcement message being an announcement message sent by a first object to a second object in a message system, the message system being a system corresponding to a first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations; a message aggregation window is displayed in a conversation list page of the first application, the message aggregation window being used to aggregate the received at least one announcement message; in response to a triggering operation on the message aggregation window, an announcement message page is displayed, the announcement message page including the at least one announcement message. This application can realize sending of an announcement message to an object in an associated organization, and can also aggregate the announcement message in a message aggregation window, so that the user is less likely to ignore the announcement message, and it is also beneficial to manage the announcement message.

[0124] This embodiment will be described from the perspective of a second message processing device, which can be integrated in a second electronic device, which can be a terminal or a server or the like.

[0125] As shown in Figure 2a , the specific flow of the message processing method is as follows:

[0126] 201, an announcement publishing page of a first application is displayed.

[0127] The first application can be a message interaction application, specifically an instant messaging (IM) application, or a payment application, or a shopping application, etc.

[0128] The announcement publishing page can be a page for sending announcement messages to users.

[0129] Specifically, there are various ways for the user to enter the announcement publishing page of the first application, which are not limited in this embodiment.

[0130] For example, the session list page of the first application can include a notice publishing entry control, and in response to a triggering operation (such as a click operation) on the notice publishing entry control, a notice publishing page can be entered.

[0131] For another example, the workbench of the first application can include a notice publishing entry control, and in response to a triggering operation (such as a click operation) on the notice publishing entry control, a notice publishing page can be entered.

[0132] For another example, the first application is a message interaction application of an enterprise type, and the workbench of the first application can include an enterprise management area. In response to a notice publishing operation on the enterprise management area, a publishing application selection page can be displayed, and the publishing application selection page can include application identifiers of at least one candidate application. Specifically, a user can perform a selection operation on the application identifier of a certain application in the candidate application to enter a notice publishing page for publishing a notice message of the selected target application.

[0133] In this embodiment, the notice publishing page of the first application can be displayed through a client of a first object. The first object is specifically an object in a message system corresponding to the first application.

[0134] Specifically, the notice publishing page in this embodiment can be used to publish a notice message of the first application, and can also be used to publish a notice message of another application in the message system corresponding to the first application.

[0135] 202. In response to a notice editing operation of the first object on the notice publishing page in the message system, the notice content and a notice object range are obtained, the message system is a system corresponding to the first application, the first object is in a first object organization, the second object is in a second object organization, and the first object organization and the second object organization are associated organizations.

[0136] The notice object range is a range of objects to be notified by the notice content, and the notice object range can include objects belonging to the same organization as the first object or objects belonging to different organizations from the first object in the message system. This embodiment does not make strict restrictions on this. That is, the first object can publish the notice content across organizations in the first application, or can publish the notice content to objects in the same organization.

[0137] The second object is also an object in a message system corresponding to the first application, and the message system can include an account system corresponding to the first object and the second object. The first application can log in an object account (such as an object account of the first object or the second object) under the account system. The account system is also an account system used by the object in the first application. For example, the account system is an enterprise account system corresponding to an enterprise message system.

[0138] The first object is a notification party of the announcement message, and the second object can be a notified party of the announcement message. The first object is in a first object organization, and the second object is in a second object organization. The first object organization and the second object organization are associated organizations. The associated organizations can be the same organization or different organizations. If the first object organization and the second object organization are different organizations, the first object organization and the second object organization can be in an upstream-downstream relationship.

[0139] Optionally, in the embodiment, the first object organization and the second object organization are different organizations, and the first object organization is an organization in an upstream-downstream relationship with the second object organization.

[0140] Specifically, the first object organization can be an upstream organization of the second object organization, and the second object organization can be a downstream organization of the first object organization. The first object is an upstream user of the second object, and the second object is a downstream user of the first object.

[0141] For example, the first object organization and the second object organization are associated in an industry chain. Specifically, the first object organization and the second object organization can be in an upstream-downstream relationship in an industry. For example, the first application is a message interaction application of an enterprise type. The first object organization can be an upstream enterprise in an industry chain, and the second object organization can be a downstream enterprise in the industry chain. If a game product of the upstream enterprise is updated, an object (such as an administrator) in the first object organization can send an announcement message about the update of the game product to a user of the downstream enterprise.

[0142] Optionally, in the embodiment, the announcement publishing page includes an announcement content editing area and an announcement range determining area.

[0143] The step of "in response to an announcement editing operation of the first object on the announcement publishing page in the message system, obtaining the announcement content and the announcement object range" can include:

[0144] In response to an editing operation of the first object on the announcement content editing area in the message system, the announcement content is obtained.

[0145] In response to a trigger operation by a first object in the messaging system on the scope of the announcement, an object selection page is displayed, the object selection page including at least one candidate object organization;

[0146] Based on the selection operation of the candidate object organization, the scope of the announcement object is determined.

[0147] In this embodiment, the first user can input the announcement content to be notified in the announcement content editing area. This announcement content can be information such as changes in the application or event previews that need to be notified. Specifically, the announcement content can be obtained by recognizing the voice information input by the first user, or it can be determined directly from the text information input by the first user; this embodiment does not impose any restrictions on this. The type of announcement content is not limited, and can include, for example, video, audio, images, and text.

[0148] The triggering operation of the first object on the area defined by the announcement scope can be a click operation or a swipe operation on the area defined by the announcement scope, and this embodiment does not limit this.

[0149] The candidate object organization can include the first object organization to which the first object belongs, and can also include organizations that are related to the first object organization, where the relationship can be upstream or downstream. By selecting candidate object organizations, objects in the selected organizations can be added to the scope of the announcement object.

[0150] In one specific embodiment, such as Figure 2b As shown, page a is the announcement publishing page of the first application. The announcement publishing page may include an announcement content editing area and an announcement scope defining area. Users can trigger the announcement content editing area to bring up the input method panel and enter the announcement content in the announcement content editing area through the input method panel. In this embodiment, the user can also trigger the ">" icon on the right side of the announcement scope defining area to display, as shown in the image. Figure 2bPage b is the object selection page. This page can include the enterprise address book and upstream / downstream address book of the first object, indicating that the scope of the announcement can include objects in the enterprise address book as well as objects in the upstream / downstream address book. The enterprise address book of the first object can include the organization corresponding to the first object, such as the organization corresponding to the "production base". The upstream / downstream address book can include organizations that have upstream / downstream relationships with the organization of the first object, such as "200021", "200022", "20023", and the organization corresponding to "distributor 444 of the production base". Users can determine the scope of the announcement by selecting candidate object organizations on the object selection page, and then return to the announcement publishing page. For example, if the user selects the organization corresponding to "200021", the organization's identifier "200021" will be displayed in the announcement scope determination area of ​​the announcement publishing page. Figure 2b As shown on page a. In response to a user's triggering of the send control on the announcement publishing page, the announcement content can be sent to objects within the announcement object scope.

[0151] When a client within the scope of the announcement receives an announcement message containing that announcement content, a message aggregation window displaying the received announcement message can be shown on the session list page of the client's primary application, such as... Figure 2b As shown on page c. Alternatively, the conversation list page may also include other types of windows, such as check-in message windows, upstream / downstream message windows, meeting notification windows, and conversation message windows. Users can view announcement content by triggering actions on the message aggregation window; based on this triggering action, announcements can be displayed as follows: Figure 2b Page d shows the announcement message page, which can include received announcement messages. These messages can be presented as message cards, each containing the announcement title "Test Announcement," the announcement content "Test Announcement," and the publisher "j." Furthermore, as shown on page d, the message card may also include the publisher's organizational source identifier "External," indicating that the announcement message was sent by a member of another organization.

[0152] Optionally, in this embodiment, the step "in response to the first object in the messaging system triggering an operation on the announcement scope determination area, displaying the object selection page" may include:

[0153] In response to a trigger operation by a first object in the messaging system on the scope of the announcement, the organizational relationship chain corresponding to the organization of the first object is obtained.

[0154] Based on the organizational relationship chain, a list of candidate organizations is displayed on the object selection page, and the candidate object organizations in the list are associated with the first object organization.

[0155] The organization relationship chain corresponding to the first object organization includes relationships between the first object organization and other organizations, and based on the organization relationship chain, organizations having a correlation relationship with the first object organization can be determined, and these organizations having the correlation relationship can be determined as candidate object organizations. The correlation relationship can be an upstream-downstream relationship.

[0156] Optionally, in the embodiment, the object selection page further includes an upstream-downstream import area; and the message processing method can further include:

[0157] In response to a triggering operation on the upstream-downstream import area, an import page is displayed, and the import page includes at least one candidate import organization.

[0158] In response to a selection operation on a target import organization in the candidate import organization, an upstream-downstream relationship between the first object organization and the target import organization is established.

[0159] Based on the upstream-downstream relationship, the candidate object organization is updated, and the updated candidate object organization includes the target import organization.

[0160] The candidate import organization can be an organization that does not have a correlation relationship with the first object organization. The first object can send a request for establishing an upstream-downstream relationship to the target import organization through a selection operation on the target import organization in the candidate import organization. If the target import organization receives and agrees to the request, an upstream-downstream relationship between the first object organization and the target import organization can be established, and the target import organization can be added to the candidate object organization as a candidate organization to which the first object can send a notice.

[0161] The triggering operation on the upstream-downstream import area can be a click or a sliding operation on the upstream-downstream import area, and the embodiment does not limit the triggering operation.

[0162] 203. Send a notice message containing the notice content to the objects within the notice object range, so as to aggregate the notice message in a message aggregation window of a client of the objects within the notice object range.

[0163] The notice message can refer to a message that publicly informs a user in an application, and can be used to indicate changes and activity announcements in the application. The notice message can include, but is not limited to, notice content, a timestamp, a notice name, and the like. The type of the notice message is not limited, and can be a video, an audio, an image, and a text, and the like.

[0164] Specifically, after receiving the notice message, the objects within the notice object range can display a message aggregation window that receives a new notice message in a conversation list page of the first application of the client.

[0165] The session list page can be used to display session message windows of respective sessions. A session message window of a certain session can be used to aggregate session messages sent by session members in the session. The respective session message windows can be displayed in the session list page in an order from early to late based on receiving times of the session messages. The session can be a single chat (which can also be regarded as a group with a number of session members being 2) or a group chat (i.e., a multi-person group). A user can enter a session page corresponding to a certain session by triggering an operation (such as a click operation) on the session list page.

[0166] The message aggregation window can be used to aggregate received announcement messages. The message aggregation window is also a message notification window. Announcement messages corresponding to different applications can be aggregated in different message aggregation windows. Each message aggregation window can aggregate announcement messages of a corresponding application. The session list page can simultaneously display message aggregation windows corresponding to multiple applications. The applications can include the first application itself and other applications in the message system of the first application.

[0167] It should be noted that the announcement message sent by the first object can be an announcement message about the first application or an announcement message about other applications in the message system corresponding to the first application.

[0168] Optionally, in the embodiment, the step of "displaying the announcement publishing page of the first application" can include:

[0169] displaying a publishing application selection page corresponding to the first application, the publishing application selection page including application identifiers of at least one candidate application, the candidate application including the first application and a second application, the second application being an application in the message system;

[0170] in response to a selection operation on an application identifier of a target application in the candidate application, displaying an announcement publishing page of the first application, the announcement publishing page including the application identifier of the target application;

[0171] The step of "sending an announcement message including the announcement content to objects in the announcement object range" can include:

[0172] sending an announcement message of the target application including the announcement content to objects in the announcement object range.

[0173] The publishing application selection page can be used to select whether the announcement message to be published is an announcement message of which application, such as an announcement message of the first application or an announcement message of the second application. The publishing application selection page can include application identifiers of candidate applications. The application identifiers can be application names, etc.

[0174] The second application can refer to an application in the message system other than the first application, and specifically, the second application can also be an application program dependent on the first application. For example, the second application can be a self-built application or a third-party application corresponding to the first application.

[0175] The self-built application can be an application program accessed by the first application through an API to increase certain business services. For example, if the first application is an enterprise type message interaction application, it can access more personalized office applications for the first application by providing APIs (Application Programming Interface) of application programs such as address book management, customer contact, identity verification, application management, message push, material management, efficiency tools, enterprise payment, enterprise interconnection, conversation content archive, electronic invoice, home-school communication, home-school application, government-citizen communication, etc. These applications can be regarded as self-built applications of the first application.

[0176] The third-party application can be an external application managed by a third party corresponding to the first application, which specifically aims to facilitate users of the first application to use the cloud application of the third party through simple operations. The core mechanism to achieve this goal can include that the service provider and the developer of the first application pre-register the application information of the first application on the management end of the third party, and when the user in the first application selects to use the third-party application, the application can be installed by one key through the authorization process.

[0177] The selection operation on the application identifier of the target application in the candidate application can be a click or a sliding operation on the application identifier of the target application in the candidate application, which is not limited in the embodiment. The target application can be any application in the candidate application.

[0178] In a specific embodiment, as shown in FIG. 6, the “application message sending” page shown in page e includes the announcement publishing entry control of the first application, that is, the icon corresponding to the “message sending”. The user can enter the publishing application selection page corresponding to the first application as shown in page f by triggering the operation of the announcement publishing entry control. Figure 2c

[0179] The publishing application selection page can be used to select which application the announcement message to be published belongs to. The page can include the application identifiers of each candidate application, and the user can select any application, and specifically, Figure 2c The “announcement” shown in page f can represent the application identifier of the first application, and “application A”, “application B”, and “1111” are all application identifiers of the second application. The user can select the application identifier of any application to determine which application the announcement message to be published belongs to. After selecting the application, the user can enter the page g as shown in FIG. 7.​Figure 2c The application publishing page shown in page g in FIG. 11B, if the "1111" application is selected in the publishing application selection page, it indicates that the announcement message to be published is the announcement message of the "1111" application, and the application identifier of the "1111" application can be displayed on the application bar of the announcement publishing page. Then, the user can edit the announcement content in the announcement publishing page, such as inputting the announcement content of "test application message", and can also display the object selection page shown in page h in FIG. 11B through the triggering operation on the announcement range determination area in the announcement publishing page. Figure 2c The object selection page shown in page h in FIG. 11B can include at least one candidate object organization, such as a first object organization and an organization having an association relationship with the first object organization. The organization members in the first object organization are also the objects in the enterprise address book of the enterprise to which the first object belongs. The organization having an association relationship with the first object organization can be specifically an organization in the upstream and downstream address books of the first object organization. As shown in page h, the user can determine the first object organization "try a government industry" to which the user belongs as the announcement object range to be notified through the selection operation on the icon corresponding to "try a government industry". The user can also determine the organization "try a government industry's partner" having an upstream and downstream relationship with the first object organization as the announcement object range to be notified through the selection operation on the icon corresponding to "try a government industry's partner". After the user triggers the sending of the announcement message containing the announcement content to the objects in the announcement object range, the objects in the announcement object range can receive the announcement message, and display the message aggregation window receiving the new announcement message in the session list page of the first application on the client side, as shown in page i in FIG. 11B. Figure 2c The message aggregation window of the "1111" application can prompt that the announcement content "test application message" in the new announcement message is received, as shown in page i in FIG. 11B.

[0180] The object selection page can further include an upstream and downstream import area, such as the "import" icon shown in page h in FIG. 11B. In response to the triggering operation on the upstream and downstream import area, at least one candidate import organization can be obtained, and the first object can select a target import organization having an upstream and downstream relationship with the first object organization from the candidate import organization. When the upstream and downstream relationship is established successfully, the target import organization can also be determined as a candidate object organization. Figure 2c

[0181] Optionally, as shown in the "application message sending" page e in FIG. 11A, the "application message sending" page can further include a historical announcement message viewing entry control, that is, an icon corresponding to "sent messages". The historical announcement page can be entered and the historical announcement message can be viewed through the triggering operation on the historical announcement message viewing entry control. Figure 2c

[0182] ​​Optionally, in the embodiment, the target application is the second application.

[0183] The step of "sending the announcement message of the target application containing the announcement content to the objects in the announcement object range" can include:

[0184] When the first object is in the visible range corresponding to the second application, sending the announcement message of the second application containing the announcement content to the objects in the announcement object range.

[0185] Here, the visible range specifically refers to the permission of the first object to send the announcement message of the second application.

[0186] Specifically, the permission can be obtained by adding the first object to the visible range of the second application by the administrator of the first object organization. For example, when the second application is a third-party application of the first application, and the first object organization is an upstream enterprise, the administrator of the upstream enterprise needs to add the first object to the visible range of the third-party application, so that the first object can use the group sending function of the announcement message of the third-party application. In some embodiments, similarly, the administrator of a downstream enterprise also needs to add the enterprise members of the downstream enterprise to the visible range of the third-party application, so that the enterprise members of the downstream enterprise can be selected to join the sending range, that is, can be selected as the objects in the announcement object range, and can receive the announcement message of the third-party application sent by the first object.

[0187] Optionally, in the embodiment, the message processing method can further include:

[0188] When the first object is not in the visible range corresponding to the second application, authorizing the sending of the announcement message of the second application to the first object;

[0189] When the authorization to the first object is successful, sending the announcement message of the second application containing the announcement content to the objects in the announcement object range.

[0190] If the first object is not in the visible range corresponding to the second application, it means that the first object does not have the permission to send the announcement message of the second application. Specifically, the administrator of the first object organization can add the first object to the visible range of the second application to authorize the sending of the announcement message of the second application to the first object. When the authorization is successful, the first object has the permission to send the announcement message of the second application.

[0191] Optionally, in the embodiment, the step of "sending the announcement message containing the announcement content to the objects in the announcement object range" can include:

[0192] determine whether an object in the announcement object range has a viewing permission for the announcement message according to the judgment result;

[0193] determine actual announcement objects from the objects in the announcement object range according to the judgment result;

[0194] send an announcement message containing the announcement content to the actual announcement objects.

[0195] The announcement message can be an announcement message of an application. Whether an object in the announcement object range has a viewing permission for the announcement message can be determined by determining whether the object is in a visible range of the application. If the object is in the visible range of the application, the object has a viewing permission for the announcement message of the application. It should be noted that only an object in the visible range of the application has a viewing permission for the announcement message of the application.

[0196] The first object sends an announcement message to the objects in the announcement object range, but the objects in the announcement object range are not necessarily all actual announcement objects. Some objects in the announcement object range that do not meet the requirements need to be filtered out, for example, objects that do not have a viewing permission for the announcement message. Thus, actual announcement objects are determined to save sending resources.

[0197] In some embodiments, after the actual announcement objects are determined, a preset number of actual announcement objects can be taken as a batch, and the announcement message can be sent to the actual announcement objects in batches. The preset number can be set according to actual conditions, for example, the preset number can be set to 1000.

[0198] Optionally, in the embodiment, the message processing method can further include:

[0199] display a history announcement page of the first application, the history announcement page including at least one historical announcement message sent by the first object;

[0200] in response to a selection operation on a target historical announcement message in the history announcement page, display an operation page of the target historical announcement message;

[0201] in response to an editing operation on the target historical announcement message in the operation page, execute a response event corresponding to the editing operation.

[0202] The target historical announcement message can be any historical announcement message in the history announcement page. The selection operation on the target historical announcement message can be a click operation on the target historical announcement message, and the operation page corresponding to the target historical announcement message can be displayed through the selection operation.

[0203] The editing operation on the target historical announcement message can include a withdrawal or deletion operation on the target historical announcement message, and the target historical announcement message can be withdrawn or deleted based on the operation.

[0204] In an embodiment, the upstream user can manage the announcement messages received by the downstream user, and the first object can be the upstream user, as shown in page j in FIG. 10. Figure 2d The historical announcement page of the first application, as shown in page j in FIG. 10, can be entered by the first object to view the sent historical announcement messages. The historical announcement messages can include historical announcement messages of each application, such as historical announcement messages of the first application and historical announcement messages of the second application. The user can select an application to view the sent historical announcement messages of the application. Specifically, the control in the upper right corner of the historical announcement page can be an application selection control. The application selection page, as shown in page k in FIG. 10, can be displayed by triggering the application selection control. The application selection page can include applications that have published historical announcement messages. It should be noted that the icon of “announcement” in page k can represent the first application. The historical announcement messages of the selected application can be displayed in the historical announcement page by selecting an application in the application selection page. For example, if the icon corresponding to the first application is selected, only the historical announcement messages of the first application can be displayed in the historical announcement page. Figure 2d

[0205] The operation page of the target historical announcement message, as shown in page l in FIG. 10, can be displayed by selecting a historical announcement message in the historical announcement page. The operation page can include the sending time of the target historical announcement message, the announcement object range (i.e., the sending range), the publisher, the announcement content “test announcement”, the corresponding application, and the sharing settings. In addition, the operation page can also include a withdrawal control. The user can trigger the withdrawal control to withdraw the message. Figure 2d

[0206] Optionally, in the embodiment, the historical announcement page includes an application selection control. The step of “displaying the historical announcement page of the first application” can include:

[0207] In response to the triggering operation of the application selection control, an application selection page is displayed. The application selection page includes applications that have published historical announcement messages. The applications include the first application and a second application. The second application is an application in the message system.

[0208] ​​Based on the selection operation of the target application in the application selection page, the history announcement page displaying the first application is updated, and the updated history announcement page includes the history announcement message corresponding to the target application.

[0209] The trigger operation on the application selection control can be a click operation or a sliding operation, and the embodiment is not limited in this regard. The target application can be any application in the application selection page, and the selection operation on the target application can be a click operation.

[0210] In a specific embodiment, the technical solution corresponding to the message processing method can be based on front-end Native framework and H5 (HTML5, a language description method for building web content) mixed development to implement cross-enterprise announcement message mass sending. Specifically, when sending an announcement message, an upstream user can determine which application the announcement message to be sent belongs to by selecting a candidate application in the application selection page, and after determining the application to be published, an announcement publishing page can be displayed. By clicking the trigger operation on the announcement range determination area in the announcement publishing page, the corresponding data can be transmitted to the H5 page, the H5 page is loaded, and an object selection page as shown in page b is displayed. Figure 2b When the user selects the announcement object range, the H5 page can call back the client data for analysis, and the client updates and displays the user interface based on the analyzed data (re-renders the user interface), i.e., updates the sending range on the announcement publishing page, then assembles a msg (message structure) with the announcement content, announcement title, etc., and judges whether the upstream user has the right to send the announcement message. If the upstream user has the right to send the announcement message, a request can be initiated to the background to complete the push to the objects in the announcement object range, and finally the objects (i.e., downstream users) in the announcement object range receive the push of the announcement message, thereby viewing the announcement content in the announcement message. The process is as shown in Figure 2e The specific description is as follows:

[0211] The client can invoke the H5 page, pass the 'upstream and downstream' related parameters to the H5 through the JSAPI interface, and the H5 side responds and loads the address book page (i.e., the object selection page). The upstream user can determine the announcement object range based on the object selection operation on the address book page, and then the client can analyze the data returned by the H5 page. Specifically, the data format returned by the H5 can be as follows:

[0212] {

[0213] selectAll, / / old field

[0214] selectAllGroups, / / old field

[0215] selectedListInCorp, / / Old field

[0216] selectedListInCorpGroup, / / Old field

[0217] selectedListInCorpChain:{

[0218] touserlist:[],

[0219] topartylist:[],

[0220] tocorppartylist:[],

[0221] tocorplist:[],

[0222] chained: 'string'

[0223] }

[0224] }

[0225] Here, "selectedListInCorpChain" represents the list of selected organizational relationship chains, specifically the information of the announcement target scope. From "selectedListInCorpChain", we can parse touserlist, topartylist, tocorppartylist, and tocorplist, where touserlist, topartylist, tocorppartylist, and tocorplist represent users, departments, group nodes, and enterprise nodes, respectively. Based on the parsed data, the corresponding user interface can be rendered. For example, if the announcement target scope is "JS distributors", the rendered user interface could be as follows: Figure 2f As shown.

[0226] The specific process of rendering the user interface on the client side can be described as follows:

[0227] After the client receives the parsed data, it can append the names of users, departments, and other nodes selected from the address book page to the sending scope field on the announcement publishing page, such as... Figure 2f As shown, you can append the selected "JS distributors" to the sending scope field; then, you need to change the sharing settings based on whether the user's selected announcement target scope includes downstream enterprises; for example... Figure 2gIf the selected announcement object range of the user includes a downstream enterprise, the sharing setting can be changed from the page m's sharing within the enterprise to the page n's sharing within the enterprise in the sending range. This data of the sharing setting needs to be passed to the background for pushing the message.

[0228] In addition, the sharing setting can further include other settings such as "shareable to the outside", "not shareable and watermark displayed on the article", "not shareable and watermark displayed on the cover and the article", and the like. The user can select according to actual needs.

[0229] The specific process of the client processing the permission data can be as follows:

[0230] a) The client needs to determine whether the user has the permission to send the announcement message to the downstream enterprise. If not, the user can be prompted through a pop-up window, and the publishing of the announcement is terminated.

[0231] b) The client needs to determine whether the user has the downstream enterprise. If not, the user can be guided to invite the downstream enterprise.

[0232] c) The client can determine whether the user has the upstream and downstream. If not, the user can be guided to create the upstream and downstream space.

[0233] The specific process of the client processing the permission data can be as follows:

[0234] After the upstream user selects the announcement object range, the announcement content, the announcement title and the like can be encapsulated into a msg recognizable by the background, and a cgi (Common Gateway Interface) request is initiated. The background can be connected to the cgi of the client through the wwcorplogic program, and the SendWebMsg (network message sending of the development message logic service) interface is called to send the message. The wwopenmsglogicsvr (development message logic service) can store the sent message, determine whether the sender has the permission to send the announcement message, and if not, the sending fails. Then, the message queue (mq, Message Queue) is called to send asynchronously. According to the intersection calculation of the announcement object range, the visible range of the application and the management range of the sender, the actual sending range is calculated, and then the underlying message system is called to push the message in batches. After the message pushing is completed, the downstream user can view the pushed announcement message. The overall process is as shown in Figure 2h

[0235] ​In addition, the administrator of the upstream organization can also manage the sent announcement message, and the client initiates a deletion request to the background through the message identification (Identity document) of the announcement message, the background responds and deletes the announcement message, and the client is called back again to update the data according to the state.

[0236] In the prior art, only announcement messages can be sent to objects in the same organizational structure, and announcement messages cannot be pushed to downstream enterprises. Users need to send messages in groups through IM (Instant Messaging) session groups. For the IM group sending method, the user needs to initiate a group chat to a specified user and send specified content to the group chat. This affects the efficiency of processing transactions, increases the user's use cost, and also causes a waste of resources. In addition, through the IM group sending method, the pushed content cannot be recorded and managed, and the user is easy to forget the sent content over time.

[0237] Based on the message processing method provided in the present application, the group sending of announcement messages can be realized, and upstream and downstream address books are supported. Thus, the contact between upstream users and downstream users is more convenient, and the user experience of sending announcement messages is better, providing more efficient collaboration capabilities for cross-enterprise communication. In addition, the administrator of the upstream enterprise can view, withdraw, and delete the announcement messages pushed to the downstream enterprise, reducing the user's operation path, enhancing the flexibility of user use configuration, and being conducive to the management of the historical announcement messages by the enterprise manager. In addition, the group sending of announcement messages is suitable for all announcement message pushing in formal scenarios, such as policy notification.

[0238] As can be seen from the above, the present embodiment can display an announcement publishing page of a first application. In response to an announcement editing operation of a first object in a message system on the announcement publishing page, the announcement content and the announcement object range are obtained, the announcement object range includes a second object, the message system is a system corresponding to the first application, the first object is in a first object organization, the second object is in a second object organization, and the first object organization and the second object organization are associated organizations. An announcement message containing the announcement content is sent to objects in the announcement object range, so as to aggregate the announcement message in a message aggregation window of a client where the objects are located. The present application can realize sending announcement messages to objects in associated organizations, and can also aggregate the announcement messages in the message aggregation window. Thus, the user is less likely to ignore the announcement messages, and it is also conducive to managing the announcement messages.

[0239] In order to better implement the above method, the present application embodiment further provides a message processing system. The message processing system comprises a first message processing device 31 and a second message processing device 32. As shown inFigure 3a As shown, the first message processing apparatus 31 can include a receiving unit 3101, a first display unit 3102 and a second display unit 3103; as shown in the following: Figure 3b As shown, the second message processing apparatus 32 can include a third display unit 3201, an obtaining unit 3202 and a sending unit 3203, as shown in the following:

[0240] A. The first message processing apparatus 31

[0241] (1) The receiving unit 3101;

[0242] The receiving unit is configured to receive at least one announcement message, the announcement message being sent by a first object to a second object in a message system, the message system being a system corresponding to a first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations.

[0243] (2) The first display unit 3102;

[0244] The first display unit is configured to display a message aggregation window in a conversation list page of the first application, the message aggregation window being configured to aggregate the received at least one announcement message.

[0245] Optionally, in some embodiments of the present application, the announcement message includes an announcement message of a second application, the second application being an application in the message system, and the message aggregation window is configured to aggregate at least one announcement message of the second application.

[0246] Optionally, in some embodiments of the present application, the conversation list page further includes at least one conversation message window, and the message aggregation window is located above all the conversation message windows.

[0247] Optionally, in some embodiments of the present application, the message processing apparatus can further include a read mark unit, as shown in the following:

[0248] The read mark unit is configured to mark the announcement message in the message aggregation window as unread in response to an unread mark operation on the message aggregation window.

[0249] Optionally, in some embodiments of the present application, the first object organization and the second object organization are different organizations, and the first object organization is an organization having an upstream relationship with the second object organization.

[0250] (3) The second display unit 3103;

[0251] The second display unit is configured to display a bulletin message page in response to a triggering operation for the message aggregation window, the bulletin message page including the at least one bulletin message.

[0252] Optionally, in some embodiments of the present application, the second display unit can include a classification subunit and a first display subunit, as follows:

[0253] The classification subunit is configured to classify the received at least one bulletin message based on a message sending object of the bulletin message, to obtain at least one bulletin message set, different bulletin message sets aggregating at least one bulletin message sent by different message sending objects.

[0254] The first display subunit is configured to display each bulletin message set in a bulletin message page in response to a triggering operation for the message aggregation window, based on a message receiving time of the bulletin message.

[0255] B. The second message processing apparatus 32

[0256] (4) The third display unit 3201;

[0257] The third display unit is configured to display a bulletin publishing page of a first application.

[0258] (5) The acquisition unit 3202;

[0259] The acquisition unit is configured to acquire bulletin content and a bulletin object range in response to a bulletin editing operation of a first object on the bulletin publishing page in a message system, the bulletin object range including a second object, the message system being a system corresponding to the first application, the first object being in a first object organization, the second object being in a second object organization, and the first object organization and the second object organization being associated organizations.

[0260] Optionally, in some embodiments of the present application, the bulletin publishing page includes a bulletin content editing area and a bulletin range determination area.

[0261] The acquisition unit can include a content acquisition subunit, a second display subunit, and a range determination subunit, as follows:

[0262] The content acquisition subunit is configured to acquire bulletin content in response to an editing operation of a first object on the bulletin content editing area in a message system.

[0263] The second display subunit is configured to display an object selection page in response to a triggering operation of a first object on the bulletin range determination area in a message system, the object selection page including at least one candidate object organization.

[0264] A range determining sub-unit is configured to determine the announcement object range based on a selection operation on the candidate object organization.

[0265] Optionally, in some embodiments of the present application, the second display sub-unit can be specifically configured to, in response to a triggering operation of a first object in the message system on the announcement range determining area, acquire an organization relationship chain corresponding to the first object organization; and display a candidate organization list in an object selection page according to the organization relationship chain, candidate object organizations in the candidate organization list having an association relationship with the first object organization.

[0266] Optionally, in some embodiments of the present application, the object selection page further includes an upstream and downstream import area; and the message processing apparatus can further include an organization updating unit configured to update the candidate object organization; specifically, the organization updating unit can include a third display sub-unit, a establishing sub-unit and an updating sub-unit, as follows:

[0267] The third display sub-unit is configured to, in response to a triggering operation on the upstream and downstream import area, display an import page, the import page including at least one candidate import organization;

[0268] The establishing sub-unit is configured to, in response to a selection operation on a target import organization in the candidate import organization, establish an upstream and downstream relationship between the first object organization and the target import organization;

[0269] The updating sub-unit is configured to update the candidate object organization based on the upstream and downstream relationship, the updated candidate object organization including the target import organization.

[0270] (6) a sending unit 3203;

[0271] The sending unit is configured to send an announcement message including the announcement content to objects within the announcement object range, so as to aggregate the announcement message in a message aggregation window of a client where the objects are located.

[0272] Optionally, in some embodiments of the present application, the third display unit can include a fourth display sub-unit and a fifth display sub-unit, as follows:

[0273] The fourth display sub-unit is configured to display a publishing application selection page corresponding to a first application, the publishing application selection page including application identifiers of at least one candidate application, the candidate application including the first application and a second application, the second application being an application in the message system;

[0274] The fifth display subunit is configured to display a publishing page of the first application in response to a selection operation on an application identifier of a target application in the candidate applications, the publishing page including the application identifier of the target application.

[0275] The sending unit can be specifically configured to send a publishing message of the target application containing the publishing content to the objects within the publishing object range.

[0276] Optionally, in some embodiments of the present application, the target application is the second application.

[0277] The sending unit can be specifically configured to send a publishing message of the second application containing the publishing content to the objects within the publishing object range when the first object is within the visible range corresponding to the second application.

[0278] Optionally, in some embodiments of the present application, the sending unit can be further configured to authorize the sending of a publishing message of the second application to the first object when the first object is not within the visible range corresponding to the second application; and send a publishing message of the second application containing the publishing content to the objects within the publishing object range when the authorization to the first object is successful.

[0279] Optionally, in some embodiments of the present application, the sending unit can include a judgment subunit, a determination subunit and a sending subunit, as follows:

[0280] The judgment subunit is configured to judge whether the objects within the publishing object range have a viewing right for the publishing message.

[0281] The determination subunit is configured to determine actual publishing objects from the objects within the publishing object range according to the judgment result.

[0282] The sending subunit is configured to send a publishing message containing the publishing content to the actual publishing objects.

[0283] Optionally, in some embodiments of the present application, the message processing apparatus can further include a historical publishing editing unit, the historical publishing editing unit being configured to edit a historical publishing message; specifically, the historical publishing editing unit can include a sixth display subunit, a seventh display subunit and an execution subunit, as follows:

[0284] The sixth display subunit is configured to display a historical publishing page of the first application, the historical publishing page including at least one historical publishing message sent by the first object.

[0285] A seventh display sub-unit is configured to display an operation page of the target historical announcement message in response to a selection operation on the target historical announcement message in the historical announcement page.

[0286] An execution sub-unit is configured to execute a response event corresponding to an editing operation on the target historical announcement message in the operation page.

[0287] Optionally, in some embodiments of the present application, the historical announcement page comprises an application selection control; the sixth display sub-unit can be specifically configured to display an application selection page in response to a triggering operation on the application selection control, the application selection page comprising applications that have published historical announcement messages, the applications comprising the first application and a second application, the second application being an application in the message system; and based on a selection operation on a target application in the application selection page, update the historical announcement page of the first application, the updated historical announcement page comprising historical announcement messages corresponding to the target application.

[0288] As can be seen from the above, the present embodiment can receive at least one announcement message by the receiving unit 3101, the announcement message being an announcement message sent by a first object to a second object in a message system, the message system being a system corresponding to a first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations; display a message aggregation window in a conversation list page of the first application by the first display unit 3102, the message aggregation window being configured to aggregate the received at least one announcement message; and display an announcement message page by the second display unit 3103 in response to a triggering operation on the message aggregation window, the announcement message page comprising the at least one announcement message.

[0289] Alternatively, the first application announcement publishing page can also be displayed by the third display unit 3201; the announcement content and the announcement object range can be obtained by the obtaining unit 3202 in response to an announcement editing operation on the announcement publishing page by the first object in the message system, the announcement object range comprising the second object, the message system being the system corresponding to the first application, the first object being in the first object organization, the second object being in the second object organization, and the first object organization and the second object organization being associated organizations; and the announcement message containing the announcement content can be sent to objects in the announcement object range by the sending unit 3203, so as to aggregate the announcement message in a message aggregation window of a client of the objects in the announcement object range.

[0290] The application can send the announcement message to the object in the associated organization, and can also aggregate the announcement message in the message aggregation window, so that the user is not easy to ignore the announcement message, and it is also beneficial to manage the announcement message.

[0291] The application also provides an electronic device, such as Figure 4 As shown in the figure, a structure schematic diagram of an electronic device related to the application is shown, which can be a terminal or a server, etc. Specifically, the electronic device can include:

[0292] The electronic device can include a processor 401 with one or more processing cores, a memory 402 with one or more computer readable storage media, a power supply 403, and an input unit 404, etc. Those skilled in the art can understand that the structure of the electronic device shown in the figure does not constitute a limitation on the electronic device, and can include more or fewer components than the figure, or combine certain components, or different component arrangements. Among them: Figure 4

[0293] The processor 401 is the control center of the electronic device, which connects all parts of the electronic device through various interfaces and lines, and performs various functions of the electronic device and processes data by running or executing software programs and / or modules stored in the memory 402, and calling data stored in the memory 402. Optionally, the processor 401 can include one or more processing cores; preferably, the processor 401 can integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application program, etc., and the modem processor mainly processes wireless communication. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 401.

[0294] The memory 402 can be used to store software programs and modules, and the processor 401 executes various function applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 can mainly include a program storage area and a data storage area, wherein the program storage area can store the operating system, at least one application program required by the function (such as sound playing function, image playing function, etc.), etc.; the data storage area can store the data created according to the use of the electronic device, etc. In addition, the memory 402 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state memory device. Accordingly, the memory 402 can also include a memory controller to provide access for the processor 401 to the memory 402.

[0295] ​The electronic device can further include a power supply 403 for supplying power to each component. Preferably, the power supply 403 can be logically connected to the processor 401 through a power management system, so that the power management system can perform functions such as management of charging, discharging, and power consumption management. The power supply 403 can further include one or more DC or AC power sources, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.

[0296] The electronic device can further include an input unit 404 for receiving input digital or character information, and generating keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.

[0297] Although not shown, the electronic device can further include a display unit and the like, which will not be described here. In the present embodiment, the processor 401 in the electronic device loads one or more executable files corresponding to processes of one or more application programs into the memory 402, and runs the application programs stored in the memory 402 according to the following instructions, thereby implementing various functions, as follows:

[0298] receiving at least one announcement message, the announcement message being an announcement message sent by a first object to a second object in a message system, the message system being a system corresponding to a first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations; displaying a message aggregation window in a conversation list page of the first application, the message aggregation window being used to aggregate the received at least one announcement message; in response to a triggering operation on the message aggregation window, displaying an announcement message page, the announcement message page including the at least one announcement message;

[0299] or, an announcement publishing page of the first application can also be displayed; in response to an announcement editing operation of the first object on the announcement publishing page in the message system, obtaining announcement content and an announcement object range, the announcement object range including the second object, the message system being a system corresponding to the first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations; sending an announcement message including the announcement content to objects in the announcement object range, so as to aggregate the announcement message in a message aggregation window of a client in which the objects are located.

[0300] The specific implementation of each operation can refer to the foregoing embodiments, which will not be described here.

[0301] According to the above, the embodiment can receive at least one announcement message, the announcement message being sent by a first object to a second object in a message system, the message system being a system corresponding to a first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations; display a message aggregation window in a session list page of the first application, the message aggregation window being used to aggregate the received at least one announcement message; in response to a triggering operation on the message aggregation window, display an announcement message page, the announcement message page including the at least one announcement message;

[0302] Alternatively, an announcement publishing page of the first application can also be displayed; in response to an announcement editing operation of the first object on the announcement publishing page in the message system, obtain announcement content and an announcement object range, the announcement object range including the second object, the message system being the system corresponding to the first application, the first object being in the first object organization, the second object being in the second object organization, the first object organization and the second object organization being associated organizations; send an announcement message including the announcement content to objects in the announcement object range, so as to aggregate the announcement message in a message aggregation window of a client in which the objects are located.

[0303] The application can implement sending of an announcement message to objects in an associated organization, and can also aggregate the announcement message in a message aggregation window, so that a user is less likely to ignore the announcement message, and it is also beneficial to management of the announcement message.

[0304] Those skilled in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructions, or by related hardware controlled by the instructions, the instructions can be stored in a computer readable storage medium and loaded and executed by a processor.

[0305] To this end, the embodiment provides a computer readable storage medium, which stores a plurality of instructions, the instructions can be loaded by a processor to execute steps in any message processing method provided by the embodiment.

[0306] receiving at least one announcement message, the announcement message being an announcement message sent by a first object to a second object in a message system, the message system being a system corresponding to a first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations; displaying a message aggregation window in a session list page of the first application, the message aggregation window being used for aggregating the received at least one announcement message; in response to a triggering operation on the message aggregation window, displaying an announcement message page, the announcement message page including the at least one announcement message;

[0307] Alternatively, an announcement publishing page of the first application is displayed; in response to an announcement editing operation of the first object on the announcement publishing page in the message system, announcement content and an announcement object range are obtained, the announcement object range including the second object, the message system being a system corresponding to the first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations; an announcement message including the announcement content is sent to objects in the announcement object range, so as to aggregate the announcement message in a message aggregation window of a client in which the objects are located.

[0308] The specific implementation of each operation can refer to the foregoing embodiments, which will not be described here.

[0309] The computer readable storage medium can include a read only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0310] Since the instructions stored in the computer readable storage medium can execute the steps in any one of the message processing methods provided by the embodiments of the present application, the beneficial effects that can be achieved by any one of the message processing methods provided by the embodiments of the present application can be achieved, which will not be described here.

[0311] According to an aspect of the present application, a computer program product or computer program is provided, which includes computer instructions stored in a computer readable storage medium. A processor of a computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method provided in the various optional implementations of the message processing aspect.

[0312] The message processing method and the related device provided by the embodiments of the present application are described in detail above, and the principles and implementation manners of the present application are described by applying specific examples. The above description of the embodiments is only used to help understand the method of the present application and its core idea; meanwhile, for those skilled in the art, according to the idea of the present application, the specific implementation manners and application ranges will be changed, and the above description should not be understood as a limitation on the present application.

Claims

1. A message processing method characterized by, The application is applied to a first electronic device, and comprises: receiving at least one announcement message, the announcement message being an announcement message sent by a first object to a second object in a message system, the message system being a system corresponding to a first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations; wherein the message system comprises an account system corresponding to the first object and the second object, the first application being logged in an object account under the account system, the account system being an account system used by an object in the first application; wherein the announcement message is obtained in the following manner: a second electronic device displays an announcement publishing page of the first application; in response to an announcement editing operation of the first object on the announcement publishing page in the message system, obtaining announcement content and an announcement object range, the announcement object range including the second object; sending an announcement message containing the announcement content to objects in the announcement object range to aggregate the announcement message in a message aggregation window of a client of the objects in the announcement object range; the announcement message being a message disclosed to a user in an application, and the announcement publishing page being a page for sending announcement messages to users; displaying a message aggregation window in a conversation list page of the first application, the message aggregation window being used to aggregate at least one received announcement message; in response to a triggering operation on the message aggregation window, displaying an announcement message page, the announcement message page including the at least one announcement message.

2. The method of claim 1, wherein, The announcement message includes an announcement message of a second application, the second application being an application in the message system, and the message aggregation window is used to aggregate at least one announcement message of the second application received.

3. The method of claim 1, wherein, The conversation list page further includes at least one conversation message window, and the message aggregation window is located above all the conversation message windows.

4. The method of claim 1, wherein, The method further comprises: in response to an unread marking operation on the message aggregation window, marking the announcement message in the message aggregation window as unread.

5. The method of claim 1, wherein, The first object organization and the second object organization are different organizations, and the first object organization is an organization having an upstream relationship with the second object organization; Specifically, the first object organization is an upstream organization of the second object organization.

6. The method of claim 1, wherein, The response to the triggering operation on the message aggregation window to display the announcement message page comprises: based on a message sending object of the announcement message, classifying the at least one received announcement message to obtain at least one announcement message set, different announcement message sets aggregating at least one announcement message sent by different message sending objects; in response to the triggering operation on the message aggregation window, displaying each announcement message set in the announcement message page based on a message receiving time of the announcement message.

7. A message processing method characterized by, The application is applied to a second electronic device, and comprises: displaying an announcement publishing page of a first application; In response to a first object in a message system performing an announcement editing operation on the announcement publishing page, obtain announcement content and an announcement object range, the announcement object range including a second object, the message system being a system corresponding to the first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations; wherein the message system includes an account system corresponding to the first object and the second object, the first application logging in an object account under the account system, the account system being an account system used by an object in the first application; Send an announcement message including the announcement content to objects in the announcement object range, so that the first electronic device receives at least one announcement message, the announcement message being an announcement message sent by the first object to the second object in the message system, a message aggregation window is displayed in a conversation list page of the first application, the message aggregation window being used to aggregate the received at least one announcement message; in response to a triggering operation on the message aggregation window, an announcement message page is displayed, the announcement message page including the at least one announcement message, so as to aggregate the announcement message in a message aggregation window of a client of an object in the announcement object range; wherein the announcement message refers to a message disclosed to a user in an application program, and the announcement publishing page refers to a page for sending announcement messages to users.

8. The method of claim 7, wherein, The announcement publishing page includes an announcement content editing area and an announcement range determination area; The response to the first object in the message system performing the announcement editing operation on the announcement publishing page includes: In response to the first object in the message system performing an editing operation on the announcement content editing area, obtain the announcement content; In response to the first object in the message system performing a triggering operation on the announcement range determination area, display an object selection page, the object selection page including at least one candidate object organization; Determine the announcement object range based on a selection operation on the candidate object organization.

9. The method of claim 8, wherein, The response to the first object in the message system performing a triggering operation on the announcement range determination area includes: In response to the first object in the message system performing a triggering operation on the announcement range determination area, obtain an organization relationship chain corresponding to the first object organization; According to the organization relationship chain, display a candidate organization list in the object selection page, the candidate object organizations in the candidate organization list having an association relationship with the first object organization.

10. The method of claim 8, wherein, The object selection page further includes an upstream and downstream import area; the method further includes: In response to a triggering operation on the upstream and downstream import area, display an import page, the import page including at least one candidate import organization; In response to a selection operation on a target import organization in the candidate import organization, establish an upstream and downstream relationship between the first object organization and the target import organization; Based on the upstream and downstream relationship, update the candidate object organization, the updated candidate object organization including the target import organization.

11. The method of claim 7, wherein, The display first application's announcement publishing page, including: Display the first application corresponding publishing application selection page, the publishing application selection page includes at least one candidate application's application identifier, the candidate application includes the first application and second application, the second application is the application in the message system; In response to the selection operation of the application identifier of the target application in the candidate application, the display first application's announcement publishing page, the announcement publishing page includes the application identifier of the target application; The target application is the second application; The target application is the second application; 12. The method of claim 11, wherein, When the first object is in the visible range corresponding to the second application, the second application's announcement message containing the announcement content is sent to the object in the announcement object range. The method further comprises: When the first object is not in the visible range corresponding to the second application, the first object is authorized to send the announcement message of the second application; 13. The method of claim 12, wherein, When the first object is authorized successfully, the second application's announcement message containing the announcement content is sent to the object in the announcement object range. The method further comprises: Determine whether the object in the announcement object range has the viewing right for the announcement message; 14. The method of claim 7, wherein, According to the determination result, the actual announcement object is determined from the object in the announcement object range; The actual announcement object is sent to the announcement message containing the announcement content. The method further comprises: Display the first application's historical announcement page, the historical announcement page includes at least one historical announcement message sent by the first object; 15. The method of claim 7, wherein, In response to the selection operation of the target historical announcement message in the historical announcement page, the operation page of the target historical announcement message is displayed; In response to the editing operation of the target historical announcement message in the operation page, the corresponding response event of the editing operation is executed. The historical announcement page includes application selection control; The display first application's historical announcement page, comprising: In response to the trigger operation of the application selection control, the application selection page is displayed, and the application selection page includes the application that has published historical announcement message, and the application includes the first application and second application, and the second application is the application in the message system; 16. The method of claim 15, wherein, Based on the selection operation of the target application in the application selection page, the first application's historical announcement page is updated, and the updated historical announcement page includes the historical announcement message corresponding to the target application. Applied to the first electronic equipment, comprising: ​ 17. A message processing device, characterized by ​ The receiving unit is configured to receive at least one announcement message, the announcement message being an announcement message sent by a first object to a second object in a message system, the message system being a system corresponding to a first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations; wherein the message system comprises an account system corresponding to the first object and the second object, the first application being logged in an object account under the account system, the account system being an account system used by an object in the first application; wherein the announcement message is obtained in the following manner: a second electronic device displays an announcement publishing page of the first application; in response to an announcement editing operation of the first object on the announcement publishing page in the message system, obtaining announcement content and an announcement object range, the announcement object range comprising the second object; sending an announcement message comprising the announcement content to objects in the announcement object range, so as to aggregate the announcement message in a message aggregation window of a client of the objects in the announcement object range; the announcement message refers to a message disclosed to a user in an application program, and the announcement publishing page refers to a page for sending announcement messages to a user in a group; The first display unit is configured to display a message aggregation window in a conversation list page of the first application, the message aggregation window being used to aggregate the received at least one announcement message; The second display unit is configured to display an announcement message page in response to a triggering operation on the message aggregation window, the announcement message page comprising the at least one announcement message.

18. A message processing device, characterized by The application is applied to a second electronic device, and comprises: The third display unit is configured to display an announcement publishing page of the first application; The obtaining unit is configured to obtain announcement content and an announcement object range in response to an announcement editing operation of the first object on the announcement publishing page in the message system, the announcement object range comprising the second object, the message system being a system corresponding to the first application, the first object being in a first object organization, the second object being in a second object organization, the first object organization and the second object organization being associated organizations; wherein the message system comprises an account system corresponding to the first object and the second object, the first application being logged in an object account under the account system, the account system being an account system used by an object in the first application; The sending unit is configured to send a notification message containing the notification content to the objects within the notification object range, so that the first electronic device receives at least one notification message, the notification message being a notification message sent by a first object to a second object in a message system, a message aggregation window is displayed in the conversation list page of the first application, and the message aggregation window is used to aggregate the received at least one notification message; in response to a triggering operation on the message aggregation window, a notification message page is displayed, the notification message page including the at least one notification message, so as to realize aggregation of the notification message in the message aggregation window of a client of an object within the notification object range; wherein the notification message refers to a message disclosed to a user in an application program, and the notification publishing page refers to a page for sending a notification message to a user.

19. An electronic device, comprising: The computer readable storage medium stores a plurality of instructions adapted to be loaded by a processor to execute the operations in the message processing method of any one of claims 1 to 16.

20. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a plurality of instructions adapted to be loaded by a processor to execute the operations in the message processing method of any one of claims 1 to 16.

21. A computer program product comprising computer programs or instructions, characterized in that, The computer program or instructions, when executed by the processor, implement the steps in the message processing method of any one of claims 1 to 16.

Citation Information

Patent Citations

  • Method and device for presenting communication information

    CN102215178A

  • Information interaction method and system applied to multiple organizations and storage medium

    CN113905004A