WO2023015982A1

WO2023015982A1 - Message sending method, message sending end, and server

Info

Publication number: WO2023015982A1
Application number: PCT/CN2022/091259
Authority: WO
Inventors: 吴庆彪; 孙仁峰; 傅力; 曾伟; 谢东; 谢小亮
Original assignee: 中兴通讯股份有限公司
Priority date: 2021-08-10
Filing date: 2022-05-06
Publication date: 2023-02-16
Also published as: CN115706720A

Abstract

A message sending method, a message sending end, and a server. The method comprises: the message sending end sends a first request message to a chain type message server, the first request message carrying a first target chain type message name; the message sending end receives a first target chain type message returned by the chain type message server according to the first target chain type message name; the message sending end sends, to a message application server, a second request message carrying at least one client identifier, so that the message server forwards the first target chain type message to a target client corresponding to the client identifier.

Description

Message sending method, message sending end and server

Cross References to Related Applications

This application is based on a Chinese patent application with application number 202110915580.7 and a filing date of August 10, 2021, and claims the priority of this Chinese patent application. The entire content of this Chinese patent application is hereby incorporated by reference into this application.

technical field

The present application relates to the technical field of communication, in particular to a method for sending a message, a message sending end and a server.

Background technique

When users use social software, if they want to share a chat process, they will generally send screenshots of the chat records to the other party, and the complete screenshots may contain a large number of simple words, chat particles, text or pictures that have nothing to do with the chat topic, so As a result, the receiver cannot quickly understand the topic or point of view of the chat. If the message is sent in the form of selecting a part of the message, it will be difficult for the user to operate when the time span of the message is relatively large, and the message cannot be associated across contacts.

In addition, most of the news (news, notices, announcements, etc.) released by government agencies or enterprises through social software is scattered and isolated. If the recipient wants to understand the cause and effect, they often need to search for relevant information by themselves, which is not only a waste of time, Moreover, the searched information may not be useful, resulting in a decline in user experience.

Contents of the invention

Embodiments of the present application provide a method for sending a message, a message sending end, a server, and a computer-readable storage medium.

In the first aspect, the embodiment of the present application provides a method for sending a message, the method comprising: the message sending end sends a first request message to the chain type message server, wherein the first request message carries the name of the first target chain type message , the chain type message server stores at least one chain type message constructed by the message sending end, each of the chain type messages includes a chain type message name and a plurality of associated messages; the message sending end receives the The first target chain type message returned by the chain type message server according to the name of the first target chain type message; the message sender sends a second request message carrying at least one client identifier to the message application server, so that the The message server forwards the first target chain type message to the target client corresponding to the client identifier.

In a second aspect, an embodiment of the present application provides a method for sending a message, the method including: the chain type message server receives a first request message sent by the message sending end, and the first request message carries the name of the first target chain type message; The chain type message server obtains the first target chain type message matching the first target chain type message name according to the first target chain type message name; the chain type message server sends the first target chain type message type message is sent to the message sender, so that the message sender sends a second request message carrying at least one client identifier to the message application server, and the message server forwards the first target chain type message to The target client corresponding to the client ID.

In the third aspect, the embodiment of the present application provides a message sending terminal, including: a memory, a processor, and a computer program stored on the memory and operable on the processor. When the processor executes the computer program, the above The message sending method provided by the first aspect.

In a fourth aspect, an embodiment of the present application provides a server, including: a memory, a processor, and a computer program stored on the memory and operable on the processor. When the processor executes the computer program, the above second The message sending method provided by the aspect.

In the fifth aspect, the embodiment of the present application provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the method for sending a message as provided in the first or second aspect above is implemented.

Description of drawings

The accompanying drawings are used to provide a further understanding of the technical solution of the present application, and constitute a part of the specification, and are used together with the embodiments of the present application to explain the technical solution of the present application, and do not constitute a limitation to the technical solution of the present application.

FIG. 1 is a schematic diagram of an implementation environment of a message sending method provided by an embodiment of the present application;

FIG. 2 is a schematic flowchart of a message sending method provided by an embodiment of the present application;

3 is a schematic structural diagram of a chain type message stored by a chain type message server according to an embodiment of the present application;

Fig. 4 is a schematic diagram of a chain type message map provided by the embodiment of the present application;

Fig. 5 is a schematic diagram of a chain type message display style provided by the embodiment of the present application;

FIG. 6 is a schematic flowchart of a message sending method provided by an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a message sending end provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a server provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application, not to limit the present application.

It should be understood that in the description of the embodiments of the present application, if there are descriptions of "first", "second", etc., it is only for the purpose of distinguishing technical features, and should not be understood as indicating or implying relative importance or implicitly indicating The number of indicated technical features or implicitly indicates the order of the indicated technical features. "At least one" means one or more, and "plurality" means two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three kinds of relationships, for example, A and/or B may indicate that A exists alone, A and B exist simultaneously, or B exists alone. Among them, A and B can be singular or plural. The character "/" generally indicates that the contextual objects are an "or" relationship. "At least one of the following" and similar expressions refer to any group of these items, including any group of single or plural items. For example, at least one of a, b, and c can represent: a, b, c, a and b, a and c, b and c, or, a and b and c, where a, b, c can be a single , or more than one.

In addition, the technical features involved in the various embodiments of the present application described below may be combined with each other as long as they do not constitute a conflict with each other.

The embodiment of the present application provides a message sending method, a message sending end, a server, and a computer-readable storage medium, which can combine multiple scattered but related messages into a chain type message, thereby realizing message sending End users provide message association and sorting functions. It can also help target client users who receive chain-type messages to quickly understand the cause and effect of events and the topics of chat discussions.

In order to make it easier for those skilled in the art to understand the embodiment of the present application, the implementation environment of the message sending method provided by the embodiment of the present application will be described below.

FIG. 1 is a schematic diagram of an implementation environment of a message sending method provided by an embodiment of the present application. Referring to Fig. 1, the implementation environment includes a chain type message server 100, a message application server (Instant message application server, IMAS) 110, a file server 120, a message that is a platform (Massage as a platform, MAAP) 130, a chat robot (Chatbot) The server 140 and multiple clients, in some examples, the multiple clients here include a first client 151 and a second client 152 . Among them, the message application server 110 is interactively connected with the chain type message server 100, MAAP130, and file server 120 respectively through a wired network or a wireless network; the Chatbot server 140 is interactively connected with the MAAP130 through a wired network or a wireless network; Or the wireless network is interactively connected with the message application server 110 .

The message application server 110 is a server for implementing various application services of instant messages.

The chain type message server 100 is used for receiving chain type messages uploaded by each message issuer, storing the chain type messages, and providing chain type message application services.

MAAP130 is a platform for messaging between third-party companies and users. It is based on RCS rich media message function and uses chatbot (chatbot), natural language processing (NLP, Natural Language Processing), artificial intelligence (Artificial Intelligence, AI) and other technologies to realize an industry-oriented message service platform.

The chatbot server 140 is used to provide a service for industry customers to send conversations to end users. The service is usually based on artificial intelligence software, simulating human intelligence conversations, and providing users with specific service functions.

The file server 120 is used to provide file services and stores files such as multimedia files.

A client is a terminal device that can provide dialogue services for users. Specifically, the client may be a handheld device, a vehicle-mounted device, a wearable device or a computing device with a wireless communication function. For example, mobile phone (mobile phone), tablet computer, laptop computer, desktop computer, smart watch, etc., but not limited thereto.

Embodiment one

Fig. 2 is a schematic flowchart of a message sending method provided by an embodiment of the present application. Referring to FIG. 2 , the message sending method provided by the embodiment of the present application includes the following step S210.

S210, the message sender sends a first request message to the chain type message server, wherein the first request message carries the name of the first target chain type message, and the chain type message server stores at least one chain type constructed by the message sender Messages, each chain type message includes a chain type message name and multiple associated messages.

It should be noted that the message sending end in this embodiment of the present application may be any client in the above-mentioned implementation environment, and may also be a Chatbot server in the above-mentioned implementation environment.

In a specific embodiment, the message sender is the first client in the above implementation environment. The interaction between the first client and the chain-type message server is performed through the message application server, that is, the interaction messages between the first client and the chain-type message server need to be forwarded through the message application server.

The user of the first client can send multiple associated messages to the chain message server through one or more message association operations, so as to form a chain message and store the chain message by the chain message server. The chain type message includes a chain type message name and a plurality of associated messages. Here, the multiple associated message types may be any one or a combination of chat messages, multimedia files (video, audio or pictures, etc.), link addresses (such as news links).

The structure of the chain type message stored by the chain type message server can be seen in FIG. 3 . The structure of the chain type message includes the chain type message name, message identification (ID), creation time, validity period, authority, and message content. Each item of information in the chain type message structure is described as follows.

Message name: The name of the chain type message, generally named with keywords and sentences that can summarize the chain type message.

Message ID: identifies a chain type message, which can be in UUID format.

Creation Time: The time when the chain type message was created.

Validity period: Chain type messages are automatically deleted after the validity period ends.

Permissions: including public, forwarding, forbidden forwarding, and private; public means that other users can search and forward; forwarding means that they cannot be searched, but can be forwarded; forbidden forwarding means that they cannot be searched and forwarded are prohibited; private means that they can only be seen by themselves.

Message content: the content of the message can be a short message of one or more messages; each short message includes time, summary (or complete content), multimedia file (optional), link address (optional), and the short message can also include another Chain type message.

It can be understood that the first client obtains the chain type message stored in the chain type message server by sending a first request message to the chain type message server. Specifically, the first client may send the first request message to the chain type message server through the message application server, that is, the first client first sends the first request message to the message application server, and the message application server then sends the first request message Forwarded to the chain type message server.

It can be understood that, when the first client sends the first request message to the chain type message server, it also inserts the name of the chain type message requested to be acquired (ie, the name of the first target chain type message) in the first request message, so as to The chain type message server returns the corresponding chain type message according to the name of the first target chain type message.

In another specific embodiment, the message sending end is a chatbot server. The chatbot server interacts with the chain-type message server through the MAPP and the message application server, that is, the interactive message between the first client and the chain-type message server needs to be forwarded through the MAPP and the message application server.

The chain type message server stores the chain type messages constructed by the chatbot server. The chain type message includes a chain type message name and a plurality of associated messages. The chatbot server chooses to associate multiple associated messages here, for example, associate multiple messages of a certain news event, or associate multiple multimedia files corresponding to a certain film and television work.

The chatbot server may forward the first request message to the chain-type message server through MAAP or the message application server. The first request message carries the name of the chain message requested by the chatbot server (namely the name of the first target chain message), so that the chain message server returns the corresponding chain message according to the first target chain message name.

It should be noted that when the message sending end only includes the chatbot server, the chain type message server can be integrated in the chatbot server. In this case, the chain type message server can be considered as a module inside the chatbot server, and the chatbot server can directly communicate with Chain type message server to interact.

S220. The message sending end receives the first target chain type message returned by the chain type message server according to the name of the first target chain type message.

It can be understood that, after receiving the first request message from the message sender, the chain type message server obtains the first target chain type message name from the first request message, and then obtains the corresponding first target chain type message name according to the first target chain type message name chain type message, and then return the first target chain type message to the message sender, and the message sender receives the first target chain type message from the chain type message server.

S230, the message sending end sends a second request message carrying at least one client identifier to the message application server, so that the message server forwards the first target chain type message to the target client corresponding to the client identifier .

It can be understood that after receiving the first target chain type message returned by the chain type message server, the message sender can select the target client that wants to receive the first target chain type message, and then insert the identity of the target client into the second In the second request message, the second request message carrying the client identifier is sent to the message application server, so that the message server forwards the first target chain type message to the target client corresponding to the client identifier.

In a specific embodiment, the message sending end is the first client in the above-mentioned implementation environment, and user A performs one or more operations through the first client to upload multiple associated chat messages to the chain type message server, To form a chain-type message, the multiple associated chat messages here may be chat messages between user A and one or more contacts in the address book, for example, including chat messages between user A and contact A and contact B, that is to say , you can associate chat messages across contacts. In specific operations, user A can first send the chat message with contact A to the chain type message server, so as to add the chat message with contact A to the chain type message named "chat record 1", and then send the chat message with contact A to the chain type message server. The chat message of person B is sent to the chain type message server, so as to add the chat message with contact B to the chain type message named "chat record 1". The first client sends the first request message carrying the name of the first target chain type message "chat record 1" to the chain type message server. After receiving the first request message, the chain type message server sets the name as "chat record 1" The chain type message returned to the first client, user A selects the target client that wants to receive the chain type message on the first client, and the first client responds to the target client selected by the user and sends the client with the target client The identified second request message is sent to the message application server, so that the message server forwards the first target chain type message to the target client. Assuming that the target client includes the second client in the above implementation environment, user B receives the chain-type message sent by user A through the second client, and can easily understand the chat content between user A and contacts A and B.

It should be noted that, in the above embodiments, only the first client sends a chain type message and the second client receives a chain type message as an example. In some embodiments, the second client can also send a chain type message. message, the first client receives the chain-type message. In some embodiments, the client that sends the chain-type message and the client that receives the chain-type message may also be the same client, which is not specifically limited in this embodiment of the present application .

In another specific embodiment, the message sending end is the chatbot server in the above-mentioned implementation environment, and the user can log in the chatbot server through the management terminal, and send multiple associated messages (such as news related to event A) through one or more This operation is uploaded to the chain-type message server to form a chain-type message, and with the development of news event A, new related messages can be continuously uploaded to the chain-type message to update the chain-type message. The chatbot server sends the first request message carrying the first target chain type message name "news event A" to the chain type message server to the chain type message server, obtains the latest chain type message about news event A from the chain type message server, and then The second request message carrying the client identifier is sent to the message application server through the MAAP, and the message application server forwards the chain type message to the corresponding target client after receiving the second request message. It should be understood that the target client here may be a client that has subscribed to the "news event A" message.

It can be understood that, before the message sending end sends the first request message to the chain type message server in the embodiment of the present application, it may further include: the message sending end displays a list of chain type message names, so that the user can select from the chain type message name list. Select the first target chain type message name in the type message name list; the message sending end obtains the first target chain type message name selected by the user, and makes the first request message carry the first target chain type message name.

Here, the message sending end is used as an example for illustration. The first client displays a chain type message name list on the user interface, and user A selects the name of the chain type message to be obtained from the chain type message name list, and the first client obtains the name selected by user A, and sends the user A The name selected by A is used as the name of the first target chain type message.

Those skilled in the art should understand that, when the message sending end is a chatbot server, the above method steps are also applicable, and details are not repeated here.

The message sending method provided by the embodiment of the present application may further include the following steps: the message sending end displays a list of chain-type message names, so that the user selects a second target chain-type message name from the list of chain-type message names; The message sending end obtains the second target chain type message name selected by the user, and obtains at least one target message selected locally by the user; the message sending end sends a third request message to the chain type message server, and the The third request message carries the second target chain type message name and the target message, so that the chain type message server adds the target message to the chain type corresponding to the second target chain type message name in the news.

In a specific embodiment, the message sending end is the first client. When user A of the first client wants to add a new message to the chain type message, the first client is triggered to display the chain type message name list on the user interface through a preset operation instruction, and user A selects from the chain type message name list Select the second target chain type message name; the first client obtains the second target chain type message name selected by the user, and at least one target message selected by the user locally, where the target message refers to the user wishing to add to the second target message The message of the chain type message corresponding to the chain type message name. The first client sends a third request message to the chain type message server, and the third request message carries the second target chain type message name and target message selected by the user; the chain type message server receives the third request message After the message is requested, a processing step of adding the target message to the chain type message corresponding to the name of the second target chain type message is performed.

It should be understood that, before the message sending end displays the chain type message name list, the message sending method provided in the embodiment of the present application may further include: the message sending end responds to the user's new chain type message instruction, sending the message to the The chain type message server sends a fourth request message, so that the chain type message server creates a chain type message according to the fourth request message.

Here continue to use the message sender as the first client for illustration. If user A thinks that there is no chain type message suitable for adding the current target message among the constructed chain type messages, user A can choose to create a new chain type message. During specific implementation, user A can trigger a new chain-type message instruction on the first client through a preset operation command, and the first client sends a fourth chain-type message server to the chain-type message server in response to user A's new chain-type message instruction. request message, so that the chain type message server executes the processing steps of creating a chain type message according to the fourth request message.

It can be understood that when the first client responds to the user's new chain type message instruction, it also obtains the setting information input by the user for the new chain type message instruction, and makes the fourth request The message carries the setting information. Here, the setting information may include at least one of chain type message name, validity period and authority.

Continue to use the message sender as the first client for example. When user A triggers a new chain type message instruction on the first client, the first client responds to the new chain type message instruction of user A, and displays the setting interface of the chain type message, which may include the chain type message name, One or more of validity period and authority, user A sets and submits the above information in the setting interface, the first client obtains the setting information submitted by user A, and inserts the setting information into the fourth request message , make the chain type message server set the name, validity period and authority of the newly created chain type message according to the setting information submitted by user A. It should be noted that, when the message sending end is a chatbot server, the above method steps are also applicable, and will not be repeated here.

The embodiment of the present application may further include the following steps before the message sending end displays the chain type message name list: the message sending end receives the keyword input by the user, and sends the keyword to the chain type message server , so that the chain type message server generates a chain type message name list according to the keyword; the message sending end receives the chain type message name list sent by the chain type message server.

Continue to use the message sender as the first client for example. User A inputs a keyword in the first client to obtain a list of chain type message names related to the keyword. In response to the keyword input by user A, the first client sends the keyword to the chain type message server, and after receiving the keyword, the chain type message server searches for the relevant chain type according to the keyword message name, and generate a list of chain-type message names to return to the first client; after receiving the list of chain-type message names, the first client displays the list of chain-type message names matching the keyword input by the user. In this way, the user can quickly and easily select the target chain type message name. It should be noted that, when the message sending end is a chatbot server, the above method steps are also applicable, and will not be repeated here.

The method in the embodiment of the present application may also include the following steps: the message sending end responds to the chain type message acquisition instruction input by the user for the current message title, and the message sending end sends a fifth request message to the chain type message server, the The fifth request message carries the current message header, so that the chain message server returns a second target chain message to the message sender according to the current message header.

Continue to use the message sender as the first client for example. If the title of the message currently browsed by user A on the first client is the content of the previously constructed chain-type message, user A clicks on the current message title to trigger a chain-type message acquisition instruction on the first client, and the first client responds to the chain-type message type message acquisition instruction, sending a fifth request message to the chain type message server, where the fifth request message carries the current message title. The chain type message server searches for the corresponding second target chain type message according to the current message title, and returns the second target chain type message to the first client. After receiving the second target link message returned by the link message server, the first client displays the second target link message. It should be noted that, when the message sending end is a chatbot server, the above method steps are also applicable, and will not be repeated here.

The method in the embodiment of the present application may further include the following steps: the message sending end responds to the message map acquisition instruction input by the user for the current chain type message, and the message sending end sends a sixth request message to the chain type message server, The sixth request message carries the message name of the current chain message, so that the chain message server returns a message map to the message sender according to the message name.

Continue to use the message sender as the first client for example. User A wants to obtain the message map of the chain type message currently browsed on the first client, and can click on the current chain type message to trigger the message map acquisition instruction, and the first client responds to the message map acquisition instruction to the chain type message server Send a sixth request message, where the sixth request message carries the message name of the current chain type message. The chain type message server searches for the corresponding chain type message according to the message name, and generates a message graph according to the found chain type message, and the chain type message server sends the generated message graph to the first client end. The first client shows the message graph to user A, so that user A can conveniently sort out the context of events through the message graph.

Fig. 4 is a schematic structural diagram of a message graph provided by an embodiment of the present application. Referring to FIG. 4 , the message graph includes a plurality of message nodes, and each message node includes at least one item of time information, message title and message content. Among them, the message node may include a main node and multiple sub-nodes, the main node includes the current chain type message name and multiple short messages, and each short message may include time information and message title. Multiple sub-nodes correspond one-to-one to multiple short messages in the main node, and each sub-node includes time information, message title and message content respectively.

Fig. 5 is a schematic diagram of a display style of a chain type message provided by an embodiment of the present application. After the first client, the second client or the chatbot server receive the chain type message from the chain type message server, the chain type message is displayed. Referring to Fig. 5, the display style of the chain type message can include the chain type message name and Multiple text messages. For the most recent newsletter, it can also be displayed in the form of graphics and text.

Embodiment two

Fig. 6 is a schematic flowchart of another message sending method provided by the embodiment of the present application. Referring to Fig. 6, the method includes the following step S410.

S410. The chain type message server receives a first request message sent by the message sender, where the first request message carries a first target chain type message name.

It can be understood that at least one chain type message constructed by the message sending end is stored in the chain type message server, and each chain type message includes a chain type message name and a plurality of associated messages. Here, the message sending end may be any client in the above-mentioned implementation environment, and may also be a Chatbot server in the above-mentioned implementation environment.

The structure of the chain type message in the chain type message server can be seen in FIG. 3 . The structure of the chain type message includes the chain type message name, message identification (ID), creation time, validity period, authority, and message content. Please refer to the relevant description in Embodiment 1 for descriptions of various information in the chain type message structure, which will not be repeated here.

S420. The chain-type message server acquires, according to the name of the first target chain-type message, a first target chain-type message matching the name of the first target chain-type message.

The chain type message server searches for the first target chain type message matching the first target chain type message name based on the first target chain type message name carried in the first request message.

S430, the chain type message server sends the first target chain type message to the message sender, so that the message sender sends a second request message carrying at least one client identifier to the message application server, by The message server forwards the first target chain type message to the target client corresponding to the client identifier.

After the chain type message server finds the first target chain type message matching the name of the first target chain type message, it returns the first target chain type message to the message sender, and the message sender sends a message carrying at least one client message to the message application server. The message server forwards the first target chain type message to the target client corresponding to the client identifier.

For the specific implementation process of steps S410 to S430, refer to the related descriptions of steps S210 to S230 above, which will not be repeated here.

In some examples, the method provided by the embodiment of the present application may further include the following steps: the chain type message server receives a third request message sent by the message sending end, and the third request message carries the second target chain type message name and target message; the chain type message server adds the target message to the chain type message corresponding to the name of the second target chain type message.

It can be understood that after the chain type message server receives the third request message sent by the message sender, it obtains the second target chain type message name and the target message from the third request message, and searches for the second target chain type message. The chain type message corresponding to the message name, and add the target message to the found chain type message.

In some examples, the method provided by the embodiment of the present application may further include: the chain type message server receiving the fourth request message sent by the message sending end; the chain type message server creating a new link according to the fourth request message type message, and configure the message identification ID for the new chain type message; wherein, the fourth request message carries the setting information input by the user for the new chain type message instruction, and the setting information includes the chain type message name, validity period and At least one of the permissions. The chain-type message server performs related settings for the newly created chain-type message according to the setting information.

In some examples, the method provided by the embodiment of the present application may further include: the chain type message server receiving the keyword sent by the message sending end; Word matching chain type message names, and generate a chain type message name list according to the found chain type message names; the chain type message server sends the chain type message name list to the message sending end.

In some examples, the method provided by the embodiment of the present application may further include: the chain type message server receiving a fifth request message sent by the message sending end, the fifth request message carrying the current message title; the chain type The message server searches for a second target chain type message matching the current message title according to the current message title, and sends the found second target chain type message to the message sending end.

In some examples, the method provided by the embodiment of the present application may further include: the chain type message server receiving a sixth request message sent by the message sending end, the sixth request message carrying the message name of the current chain type message; The chain type message server determines the message identification ID matching the message name according to the message name; the chain type message server searches for the chain type message according to the message ID, and searches for the chain type message according to the found chain type message Generate a message map; the chain type message server sends the message map to the message sender; wherein, the message map includes a plurality of message nodes, and each message node includes time information, message title and message content at least one.

It should be noted that, in the above embodiments, the descriptions of each embodiment have their own emphases, and for parts that are not detailed or recorded in a certain embodiment, refer to the relevant descriptions of other embodiments.

In the embodiment of this application, on the one hand, the message sender can send multiple associated messages to the chain-type message server to form a chain-type message and the chain-type message server will store the chain-type message. Through this chain-type message The structure provides message association and sorting functions for message sender users. On the other hand, the message sender can send the first request message carrying the name of the first target chain type message to the chain type message server, so that the chain type message server returns the first target chain type message corresponding to the first target chain type message name message, and then the message sender sends a second request message carrying at least one client identifier to the message application server, so that the message server forwards the first target chain type message to the target client corresponding to the client identifier In this way, a chain-type message that collects multiple related messages is delivered to the target client, so that the user of the target client can easily understand the development of the event or understand the content of the chat discussion through the chain-type message, improving user experience.

FIG. 7 shows a message sending terminal 500 provided by the embodiment of the present application. As shown in FIG. 7 , the message sending end 500 includes but is not limited to: a memory 510 for storing programs; a processor 520 for executing the programs stored in the memory 510, and when the processor 520 executes the programs stored in the memory 510, processing The device 520 is configured to execute the method for sending a message described in the first embodiment above.

The processor 520 and the memory 510 may be connected through a bus or in other ways.

As a non-transitory computer-readable storage medium, the memory 510 can be used to store non-transitory software programs and non-transitory computer-executable programs, such as the message sending method described in any embodiment of the present application. The processor 520 executes the non-transitory software program and instructions stored in the memory 510 to implement the message sending method described in the first embodiment above.

The memory 510 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required by at least one function; the data storage area may store the above-mentioned message sending method. In addition, the memory 510 may include a high-speed random access memory, and may also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some implementations, the memory 510 may include memory located remotely relative to the processor 520, and these remote memories may be connected to the processor 520 through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The non-transitory software programs and instructions required to implement the above message sending method are stored in the memory 510, and when executed by one or more processors 520, execute the message sending method provided by any embodiment of the present application.

FIG. 8 shows a server 600 provided by an embodiment of the present application. As shown in Figure 8, the server 600 includes but is not limited to: a memory 610 for storing programs; a processor 620 for executing the programs stored in the memory 610, when the processor 620 executes the programs stored in the memory 610, the processor 620 The method for executing the message sending described in the first embodiment above.

The processor 620 and the memory 610 may be connected through a bus or in other ways.

As a non-transitory computer-readable storage medium, the memory 610 can be used to store non-transitory software programs and non-transitory computer-executable programs, such as the message sending method described in any embodiment of the present application. The processor 620 executes the non-transitory software programs and instructions stored in the memory 610 to implement the message sending method described in the first embodiment above.

The memory 610 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required by at least one function; the data storage area may store the above-mentioned message sending method. In addition, the memory 610 may include a high-speed random access memory, and may also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some embodiments, the memory 610 may include memory located remotely relative to the processor 620, and these remote memories may be connected to the processor 620 through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The non-transitory software programs and instructions required to implement the above message sending method are stored in the memory 610, and when executed by one or more processors 620, execute the message sending method provided by any embodiment of the present application.

The embodiment of the present application also provides a storage medium storing computer-executable instructions, and the computer-executable instructions are used to execute the above method for sending a message.

In one embodiment, the storage medium stores computer-executable instructions, and the computer-executable instructions are executed by one or more control processors, for example, executed by one or more processors in the above-mentioned message sending end, or executed by Execution by one or more processors in the server may cause the one or more processors to execute the method for sending a message provided in any embodiment of the present application.

In the embodiment of this application, on the one hand, the message sender can send multiple associated messages to the chain-type message server to form a chain-type message and the chain-type message server will store the chain-type message. Through this chain-type message The structure provides message association and sorting functions for message sender users. On the other hand, the message sender can send the first request message carrying the name of the first target chain type message to the chain type message server, so that the chain type message server returns the first target chain type message corresponding to the first target chain type message name message, and then the message sender sends a second request message carrying at least one client identifier to the message application server, so that the message server forwards the first target chain type message to the target client corresponding to the client identifier In this way, a chain-type message that collects multiple related messages is sent to the target client, so that the user of the target client can easily understand the development of the event or understand the content of the chat discussion through the chain-type message, which improves the user experience.

The embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware, or in the form of hardware plus software functional units.

Those skilled in the art can understand that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware and an appropriate combination thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit . Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As known to those of ordinary skill in the art, the term computer storage media includes both volatile and nonvolatile media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. permanent, removable and non-removable media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tape, magnetic disk storage or other magnetic storage devices, or can Any other medium used to store desired information and which can be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, communication media typically embody computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

The above is a specific description of some implementations of the present application, but the present application is not limited to the above-mentioned embodiments, and those skilled in the art can also make various equivalent deformations or replacements without violating the sharing conditions of the scope of the present application. Equivalent modifications or replacements are all within the scope defined by the claims of the present application.

Claims

A message sending method, the method comprising:

The message sender sends a first request message to the chain-type message server, wherein the first request message carries the name of the first target chain-type message, and the chain-type message server stores at least one message constructed by the message sender. Chain type messages, each of which includes a chain type message name and a plurality of associated messages;

The message sending end receives the first target chain type message returned by the chain type message server according to the name of the first target chain type message;

The message sending end sends a second request message carrying at least one client identifier to the message application server, so that the message server forwards the first target chain type message to the target client corresponding to the client identifier .
The method according to claim 1, wherein, before the message sending end sends the first request message to the chain type message server, the method further comprises:

The message sending end displays a chain type message name list, so that the user selects a first target chain type message name from the chain type message name list;

The message sending end obtains the first target chain type message name selected by the user, and makes the first request message carry the first target chain type message name.
The method according to claim 1, further comprising:

The message sending end displays a chain type message name list, so that the user selects a second target chain type message name from the chain type message name list;

The message sending end obtains the name of the second target chain type message selected by the user, and obtains at least one target message locally selected by the user;

The message sending end sends a third request message to the chain type message server, and the third request message carries the name of the second target chain type message and the target message, so that the chain type message server sends the The target message is added to the chain type message corresponding to the name of the second target chain type message.
The method according to claim 3, wherein, before the message sending end displays a chain type message name list, the method further comprises:

The message sending end sends a fourth request message to the chain message server in response to the user's instruction to create a chain message, so that the chain message server creates a chain message according to the fourth request message.
The method according to claim 4, wherein, when the message sending end responds to the user's new chain type message instruction, it also obtains the setting information input by the user for the new chain type message instruction, and makes the The fourth request message carries the setting information;

The setting information includes at least one of chain type message name, validity period and authority.
The method according to claim 2 or 3, wherein, before the message sending end displays a chain type message name list, the method further comprises:

The message sending end receives the keyword input by the user, and sends the keyword to the chain type message server, so that the chain type message server generates a chain type message name list according to the keyword;

The message sending end receives the chain type message name list sent by the chain type message server.
The method according to claim 1, further comprising:

The message sending end responds to the chain type message acquisition instruction input by the user for the current message title, and the message sending end sends a fifth request message to the chain type message server, and the fifth request message carries the current message title to The chain type message server returns a second target chain type message to the message sending end according to the current message title.
The method according to claim 1, further comprising:

The message sender sends a sixth request message to the chain type message server in response to the message map acquisition instruction input by the user for the current chain type message, and the sixth request message carries the current chain type The message name of the message, so that the chain type message server returns a message map to the message sending end according to the message name;

The message graph includes a plurality of message nodes, and each message node includes at least one item of time information, message title and message content.
The method according to claim 1, wherein the message sending end is a client or a Chatbot server.
A message sending method, comprising:

The chain type message server receives the first request message sent by the message sender, and the first request message carries the name of the first target chain type message;

The chain type message server obtains the first target chain type message matching the name of the first target chain type message according to the name of the first target chain type message;

The chain type message server sends the first target chain type message to the message sender, so that the message sender sends a second request message carrying at least one client identifier to the message application server, and the The message server forwards the first target chain type message to the target client corresponding to the client identifier.
The method of claim 10, further comprising:

The chain type message server receives a third request message sent by the message sender, and the third request message carries a second target chain type message name and target message;

The chain type message server adds the target message to the chain type message corresponding to the name of the second target chain type message.
The method of claim 10, further comprising:

The chain type message server receives the fourth request message sent by the message sender;

The chain type message server creates a new chain type message according to the fourth request message, and configures a message identification ID for the newly created chain type message;

Wherein, the fourth request message carries setting information entered by the user for the instruction of creating a new chain type message, and the setting information includes at least one of a chain type message name, validity period, and authority.
The method of claim 10, further comprising:

The chain type message server receives the keyword sent by the message sender;

The chain type message server searches for the chain type message name matching the keyword according to the keyword, and generates a chain type message name list according to the found chain type message name;

The chain type message server sends the chain type message name list to the message sender.
The method of claim 10, further comprising:

The chain type message server receives a fifth request message sent by the message sender, and the fifth request message carries a current message title;

The chain type message server searches for a second target chain type message matching the current message title according to the current message title, and sends the found second target chain type message to the message sending end.
The method of claim 10, further comprising:

The chain type message server receives the sixth request message sent by the message sender, and the sixth request message carries the message name of the current chain type message;

The chain type message server determines the message identification ID matching the message name according to the message name;

The chain type message server searches for a chain type message according to the message ID, and generates a message map according to the found chain type message;

The chain type message server sends the message graph to the message sender;

The message graph includes a plurality of message nodes, and each message node includes at least one item of time information, message title and message content.
A message sending terminal, comprising: a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein, when the processor executes the computer program, the implementation of claim 1 - The message sending method described in any one of 9.
A server, comprising: a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein, when the processor executes the computer program, the implementation of claims 10-15 Any one of the message sending methods.
A computer-readable storage medium storing a computer program, wherein, when the computer program is executed by a processor, the message sending method according to any one of claims 1-15 is implemented.