CN109274510B - Message processing method, device, client, server and storage medium - Google Patents
Message processing method, device, client, server and storage medium Download PDFInfo
- Publication number
- CN109274510B CN109274510B CN201811039397.XA CN201811039397A CN109274510B CN 109274510 B CN109274510 B CN 109274510B CN 201811039397 A CN201811039397 A CN 201811039397A CN 109274510 B CN109274510 B CN 109274510B
- Authority
- CN
- China
- Prior art keywords
- message
- session
- server
- client
- list
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
- H04L65/403—Arrangements for multi-party communication, e.g. for conferences
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Theoretical Computer Science (AREA)
- Multimedia (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a message processing method, a message processing device, a client, a server and a storage medium. In the method, a first latest version of a message list of a first session stored by a client is obtained, wherein the first message list stores messages in the first session; sending the first latest version to the server; receiving a notification message returned by the server; the notification message carries a session identifier of the second session, and the notification message is used for indicating that a legacy message which is not received by the client exists in a message list of the second session; it is determined from the notification message that there is a legacy message in the message list of the second session that is not received by the client. In the application, all messages in the session received by the user do not need to be sent to the server, and whether the legacy messages which are not received by the client exist can be determined according to the first latest version, so that network resources can be saved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a message processing method, an apparatus, a client, a server, and a storage medium.
Background
At present, the demand for mutual communication among users is increasing, and in order to improve the communication efficiency, more and more users form a group and communicate with each other in the group. In the users joining the group, when one user needs to send a message in the group, the message can be sent to the server, and then the server forwards the message to each of the other users in the group, thereby realizing mutual communication.
Generally, users joining a group are not online at all times, and users who are not online cannot receive messages forwarded by a server.
When a user who is not online later comes online, in order to obtain a message which is not received because the user is not online, the user needs to send all received messages in the group to the server after the user comes online, so that the server compares the received messages with all messages in the group to determine whether a message which is not received by the user exists, and then sends a notification message to the user to notify the user of the existence of the message which is not received.
However, the inventor found that the user needs to send all the received messages in the group to the server, and if there are many received messages in the group, then it will occupy many network resources.
Disclosure of Invention
In order to overcome the problems in the related art, the application provides a message processing method, a message processing device, a client, a server and a storage medium.
According to a first aspect of the present application, there is provided a message processing method applied to a client, the method including:
acquiring a first latest version of a message list of a first session stored by the client, wherein the first message list stores messages in the first session;
sending the first latest version to a server;
receiving a notification message returned by a server, where the notification message is sent to a client when a second latest version of a message list of a second session in which the client participates, stored by the server, is greater than the first latest version, the notification message carries a session identifier of the second session, the notification message is used to indicate that a legacy message that is not received by the client exists in the message list of the second session, and the second message list stores all messages in the second session;
determining that a legacy message not received by the client exists in a message list of the second session according to the notification message.
In an optional implementation manner, after determining that there is a legacy message that is not received by the client in the message list of the second session according to the notification message, the method further includes:
the legacy message is obtained from the server.
In an optional implementation manner, the message numbers of the messages stored in the message list of the second session are sequentially increased according to the sequence of the receiving times of the messages in the second session received by the server;
the obtaining the legacy message from the server includes:
sending a message acquisition request to the server, where the message acquisition request carries a first message number and a session identifier of the second session, and the first message number is the largest message number in message numbers of all messages in a message list of the second session stored in the client;
receiving a legacy message returned by the server according to the acquisition request, wherein the legacy message comprises: and the message which is stored in the server and corresponds to the message number which is greater than the first message number in the message list of the second session.
In an optional implementation manner, after obtaining the legacy message from the server, the method further includes:
and displaying the legacy messages in the order of the message numbers from small to large.
In an optional implementation manner, the notification message further carries the second latest version;
the method further comprises the following steps:
updating the first latest version with the second latest version.
According to a second aspect of the present application, there is provided a message processing method applied to a server, the method including:
receiving a first latest version of a message list of a first session stored by a client, wherein messages in the first session are stored in the first message list;
obtaining a second latest version of a message list of a second session in which the client participates, which is stored in the server, the second message list storing all messages in the second session;
when the second latest version is different from the first latest version, generating a notification message, where the notification message carries a session identifier of the second session, and the notification message is used to indicate that a legacy message that is not received by the client exists in a message list of the second session,
and sending the notification message to the client.
In an optional implementation manner, the message numbers of the messages stored in the message list of the second session are sequentially increased according to the sequence of the receiving times of the messages in the second session received by the server;
the method further comprises the following steps:
receiving a message acquisition request sent by the client, wherein the message acquisition request carries a first message number and a session identifier of the second session, and the first message number is the largest message number in the message numbers of all messages in a message list of the second session stored in the client;
obtaining a legacy message, the legacy message comprising: and the message which is stored in the server and corresponds to the message number which is greater than the first message number in the message list of the second session.
In an optional implementation manner, the notification message further carries the second latest version.
According to a third aspect of the present application, there is provided a message processing apparatus applied to a client, the apparatus comprising:
a first obtaining module configured to obtain a first latest version of a message list of a first session stored by the client, wherein the first message list stores messages in the first session;
a first sending module configured to send the first latest version to a server;
a first receiving module, configured to receive a notification message returned by a server, where the notification message is sent to a client when a second latest version of a message list of a second session in which the client participates, stored by the server, is greater than the first latest version, the notification message carries a session identifier of the second session, the notification message is used to indicate that a legacy message that is not received by the client exists in the message list of the second session, and the second message list stores all messages in the second session;
a determining module configured to determine, according to the notification message, that there is a legacy message in a message list of the second session that is not received by the client.
In an optional implementation, the apparatus further comprises:
a second obtaining module configured to obtain the legacy message from the server.
In an optional implementation manner, the message numbers of the messages stored in the message list of the second session are sequentially increased according to the sequence of the receiving times of the messages in the second session received by the server;
the second acquisition module includes:
a sending unit, configured to send a message obtaining request to the server, where the message obtaining request carries a first message number and a session identifier of the second session, and the first message number is a largest message number of message numbers of all messages in a message list of the second session stored in the client;
a receiving unit, configured to receive a legacy message returned by the server according to the acquisition request, where the legacy message includes: and the message which is stored in the server and corresponds to the message number which is greater than the first message number in the message list of the second session.
In an optional implementation, the apparatus further comprises:
a display module configured to display the legacy messages in order of message numbers from small to large.
In an optional implementation manner, the notification message further carries the second latest version;
the device further comprises:
an update module configured to update the first latest version with the second latest version.
According to a fourth aspect of the present application, there is provided a message processing apparatus applied to a server, the apparatus including:
a second receiving module configured to receive a first latest version of a message list of a first session stored by a client, wherein the first message list stores messages in the first session;
a third obtaining module configured to store, at the server, a second latest version of a message list of a second session in which the client participates, the second message list storing all messages in the second session;
a generating module configured to generate a notification message when the second latest version is different from the first latest version, where the notification message carries a session identifier of the second session, and the notification message is used to indicate that a legacy message that is not received by the client exists in a message list of the second session,
a second sending module configured to send the notification message to the client.
In an optional implementation manner, the message numbers of the messages stored in the message list of the second session are sequentially increased according to the sequence of the receiving times of the messages in the second session received by the server;
the device further comprises:
a third receiving module, configured to receive a message obtaining request sent by the client, where the message obtaining request carries a first message number and a session identifier of the second session, and the first message number is the largest message number among message numbers of all messages in a message list of the second session stored in the client;
a fourth obtaining module configured to obtain a legacy message, the legacy message comprising: and the message which is stored in the server and corresponds to the message number which is greater than the first message number in the message list of the second session.
In an optional implementation manner, the notification message further carries the second latest version.
According to a fifth aspect of the present application, there is provided a client comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to perform the message processing method of the first aspect.
According to a sixth aspect of the present application, there is provided a server comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to perform the message processing method according to the second aspect.
According to a seventh aspect of the present application, there is provided a non-transitory computer readable storage medium, wherein instructions, when executed by a processor of a client, enable the client to perform the message processing method according to the first aspect.
According to an eighth aspect of the present application, there is provided a non-transitory computer readable storage medium having instructions therein which, when executed by a processor of a server, enable the server to perform the message processing method according to the second aspect.
According to a ninth aspect of the present application, there is provided a computer program product, wherein the instructions of the computer program product, when executed by a processor of a client, enable the client to perform the message processing method according to the first aspect.
According to a tenth aspect of the present application, there is provided a computer program product, wherein the instructions of the computer program product, when executed by a processor of a server, enable the server to perform the message processing method according to the second aspect.
The technical scheme provided by the application can comprise the following beneficial effects:
in the method, a first latest version of a message list of a first session stored by a client is obtained, wherein the first message list stores messages in the first session; sending the first latest version to the server; receiving a notification message returned by the server; the notification message is sent to the client when a second latest version of a message list of a second session in which the client participates, which is stored by the server, is greater than the first latest version, the notification message carries a session identifier of the second session, and the notification message is used for indicating that a legacy message which is not received by the client exists in the message list of the second session; it is determined from the notification message that there is a legacy message in the message list of the second session that is not received by the client. In the application, all messages in the session received by the user do not need to be sent to the server, and whether the legacy messages which are not received by the client exist can be determined according to the first latest version, so that network resources can be saved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
Fig. 1 is a flowchart of a message processing method shown in the present application.
Fig. 2 is a flowchart of a message processing method shown in the present application.
Fig. 3 is a block diagram of a message processing apparatus shown in the present application.
Fig. 4 is a block diagram of a message processing apparatus shown in the present application.
Fig. 5 is a block diagram of a client shown in the present application.
Fig. 6 is a block diagram of a server shown in the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
Fig. 1 is a flowchart of a message processing method shown in the present application, and the method is applied to a client, as shown in fig. 1, and includes the following steps.
In step S101, a first latest version of a message list of a first session stored by a client is obtained, where the first message list stores messages in the first session;
in this embodiment of the present application, at least two users may form a session, for example, a point-to-point session between two users, or more than three users form a group, each user in the group may send a message in the group, and each user may see messages sent by other users in the group, where the group is a session.
For any session, when a certain user participating in the session needs to send a message in the session, the user first needs to send the message and a session identifier of the session to a server, and the server receives the message and the session identifier and forwards the message to other users participating in the session according to the session identifier.
However, if some of the other users participating in the session are not online, even if the server forwards the message to the some users, the some users cannot receive the message, and under a related mechanism, the server may not actively forward the message to the some users again in the following, so that the some users cannot receive the message.
In this application, each user participating in the session may send a message in the session, and after receiving a message sent by a user participating in the session, the server may set a message number for the message, where the message number may be represented by a number, and the message numbers may gradually increase in sequence according to the receiving sequence of the messages received by the server in the session, for example, the message number of the first message received by the server in the session is 001, the message number of the second message received by the server in the session is 002, the message number of the third message received by the server in the session is 003, and so on.
The message number set for the message may be added to a preset field in the message, and then the message with the added message number is forwarded to other users in the session.
Or, the message and the message number set for the message form a corresponding table entry, and the corresponding table entry is stored in the first corresponding relationship between the message and the message number stored in the server, and then the corresponding table entry including the message and the message number set for the message is sent to other users in the session.
For any one of the other users, if the user is online at the moment, that is, if the user logs in the server by using the client at the moment, the client receives the message sent by the server, the user can also check the message, but the client does not know whether the server sent the history message in the session to the client when the client logged in the server was not logged in before, if the client logged in the server was not logged in before, the server sent the history message in the session to the client, because the client is not logged in at the moment, the client does not receive the history message sent by the server to the client, and because of the relevant mechanism, the server does not actively send the history message to the client again in the following, so the client cannot receive the history message, the history message is a legacy message.
In this application, a user may participate in one session or simultaneously participate in multiple sessions, a client stores a message list in the client for each session in which the user participates, in this application, a session corresponding to the message list stored in the client is a first session, after the user logs in a server using the client, in order to determine whether there are missing messages that the client has not received in the session in which the client participates, the client may obtain a first latest version of the message list of the first session stored in the client, the messages in the first session are stored in the first message list, and then step S102 is executed.
In the present application, a session in which a user using a client participates is a session in which the client participates, and for any session in which the client participates, whenever the client receives a new message in the session sent by a server, the new message is stored in a message list of the session stored in the client, and a latest version of the message list of the session needs to be updated, for example, after a message 1 is stored in the message list of the session for the first time, the latest version of the message list of the session is set to V1.0, after a message 2 is stored in the message list of a certain session, the latest version of the message list of the session is set to V2.0, after a message 3 is stored in the message list of a certain session, the latest version of the message list of the session is set to V3.0, and so on.
In step S102, the first latest version is sent to the server;
in the present application, the server stores a list of messages for the second sessions in which the client is currently participating, and stores a second latest version of the list of messages for each second session, the second list of messages storing all messages in the second session.
In this application, the second session may be one session or a plurality of different sessions, and the second session may be the same as the first session, or the first session may be a partial session in the second session, or the like.
For any session in the second session, whenever the server sends a new message in the session sent by other users, the new message is stored in the message list of the session stored by the server, and the version of the message list of the session needs to be updated, for example, after storing message 1 in the message list of the session for the first time, the latest version of the message list of the session is set to V1.0, after storing message 2 in the message list of a certain session, the latest version of the message list of the session is set to V2.0, after storing message 3 in the message list of a certain session, the latest version of the message list of the session is set to V3.0, and so on.
After the server stores the new message in the message list of the session, the client may not receive the new message sent by the server because the client is not logged in to the server at that time. Therefore, in this application, after the server receives the first latest version of the message list of the first session stored by the client, the server may determine, at the second latest version of the message list of the second session in which the client participates stored by the server, whether the second latest version is the same as the first latest version, and when the second latest version is different from the first latest version, generate a notification message carrying a session identifier of the second session, the notification message being used to indicate that there is a legacy message that is not received by the client in the message list of the second session, and then send the notification message to the client.
When the number of the second sessions is multiple, since the message list of each second session has its own version, in the present application, the second latest version of the message list of the second session, which is stored in the server and in which the client participates, is the highest version of the message lists of each second session.
In step S103, receiving a notification message returned by the server; the notification message is sent to the client when a second latest version of a message list of a second session in which the client participates, which is stored by the server, is greater than the first latest version, the notification message carries a session identifier of the second session, and the notification message is used for indicating that a legacy message which is not received by the client exists in the message list of the second session;
the second message list stores all messages in the second session;
in step S104, it is determined from the notification message that there is a legacy message in the message list of the second session that is not received by the client.
In the method, a first latest version of a message list of a first session stored by a client is obtained, wherein the first message list stores messages in the first session; sending the first latest version to the server; receiving a notification message returned by the server; the notification message is sent to the client when a second latest version of a message list of a second session in which the client participates, which is stored by the server, is greater than the first latest version, the notification message carries a session identifier of the second session, and the notification message is used for indicating that a legacy message which is not received by the client exists in the message list of the second session; it is determined from the notification message that there is a legacy message in the message list of the second session that is not received by the client. In the application, all messages in the session received by the user do not need to be sent to the server, and whether the legacy messages which are not received by the client exist can be determined according to the first latest version, so that network resources can be saved.
In the application, if a legacy message which is not received by the client exists in the message list of the second session, the client often needs to acquire the legacy message from the server so that a user using the client can view the legacy message, wherein in order to acquire the legacy message from the server, the client can send a message acquisition request to the server, and message numbers of messages stored in the message list of the second session are sequentially increased according to the sequence of receiving times when the server receives the messages in the second session; the message acquiring request carries a first message number and a session identifier of a second session, wherein the first message number is the largest message number in the message numbers of all messages in a message list of the second session stored in the client; wherein the session identities of different sessions are different.
The server receives a message acquisition request sent by a client, extracts a first message number and a session identifier of a second session from the message acquisition request, and acquires a legacy message according to the session identifier, wherein the legacy message comprises: and returning the legacy message to the client side after the message corresponding to the message number which is greater than the first message number in the message list of the second session stored in the server. And the client receives the legacy message returned by the server according to the message acquisition request.
Further, in order to improve the user experience, after the legacy messages are acquired from the server, the legacy messages may be displayed in the order of the message numbers from small to large.
In another embodiment, the notification message also carries the second latest version; therefore, the client may also update the first latest version with the second latest version, that is, the second latest version is used as the latest version of the message list of the first session stored by the client, so that other legacy messages may be continuously obtained from the server according to the updated latest version.
Fig. 2 is a flowchart of a message processing method shown in the present application, which is applied to a server, as shown in fig. 1, and includes the following steps.
In step S201, receiving a first latest version of a message list of a first session stored by a client, where messages in the first session are stored in the first message list;
in step S202, a second latest version of a message list of a second session in which the client participates, which is stored in the server, is acquired, and the second message list stores all messages in the second session;
in step S203, when the second latest version is different from the first latest version, a notification message is generated, where the notification message carries a session identifier of the second session, and the notification message is used to indicate that a legacy message that is not received by the client exists in a message list of the second session;
in step S204, the notification message is sent to the client.
According to the method and the device, the client side can determine whether the legacy messages which are not received by the client side exist in the server only according to the first latest version without sending all messages in the session which are received by the user to the server, so that network resources can be saved.
After sending the notification message to the client, the client often needs to acquire the legacy message from the server to allow a user using the client to view the legacy message, wherein, in order to acquire the legacy message from the server, the client may send a message acquisition request to the server, and message numbers of messages stored in a message list of the second session are sequentially incremented according to a sequence of receiving times of messages in the second session received by the server; the message acquiring request carries a first message number and a session identifier of a second session, wherein the first message number is the largest message number in the message numbers of all messages in a message list of the second session stored in the client; wherein the session identities of different sessions are different.
The server receives a message acquisition request sent by a client, extracts a first message number and a session identifier of a second session from the message acquisition request, and acquires a legacy message according to the session identifier, wherein the legacy message comprises: and returning the legacy message to the client side after the message corresponding to the message number which is greater than the first message number in the message list of the second session stored in the server. And the client receives the legacy message returned by the server according to the message acquisition request.
In another embodiment, the notification message also carries the second latest version; therefore, the client may also update the first latest version with the second latest version, that is, the second latest version is used as the latest version of the message list of the first session stored by the client, so that other legacy messages may be continuously obtained from the server according to the updated latest version.
Fig. 3 is a block diagram of a message processing apparatus shown in the present application. Referring to fig. 3, the apparatus includes:
a first obtaining module 11, configured to obtain a first latest version of a message list of a first session stored by the client, where messages in the first session are stored in the first message list;
a first sending module 12 configured to send the first latest version to a server;
a first receiving module 13, configured to receive a notification message returned by a server, where the notification message is sent to the client when a second latest version of a message list of a second session in which the client participates, stored by the server, is greater than the first latest version, the notification message carries a session identifier of the second session, the notification message is used to indicate that a legacy message that is not received by the client exists in the message list of the second session, and the second message list stores all messages in the second session;
a determining module 14 configured to determine, according to the notification message, that there is a legacy message in the message list of the second session that is not received by the client.
In an optional implementation, the apparatus further comprises:
a second obtaining module configured to obtain the legacy message from the server.
In an optional implementation manner, the message numbers of the messages stored in the message list of the second session are sequentially increased according to the sequence of the receiving times of the messages in the second session received by the server;
the second acquisition module includes:
a sending unit, configured to send a message obtaining request to the server, where the message obtaining request carries a first message number and a session identifier of the second session, and the first message number is a largest message number of message numbers of all messages in a message list of the second session stored in the client;
a receiving unit, configured to receive a legacy message returned by the server according to the acquisition request, where the legacy message includes: and the message which is stored in the server and corresponds to the message number which is greater than the first message number in the message list of the second session.
In an optional implementation, the apparatus further comprises:
a display module configured to display the legacy messages in order of message numbers from small to large.
In an optional implementation manner, the notification message further carries the second latest version;
the device further comprises:
an update module configured to update the first latest version with the second latest version.
In the method, a first latest version of a message list of a first session stored by a client is obtained, wherein the first message list stores messages in the first session; sending the first latest version to the server; receiving a notification message returned by the server; the notification message is sent to the client when a second latest version of a message list of a second session in which the client participates, which is stored by the server, is greater than the first latest version, the notification message carries a session identifier of the second session, and the notification message is used for indicating that a legacy message which is not received by the client exists in the message list of the second session; it is determined from the notification message that there is a legacy message in the message list of the second session that is not received by the client. In the application, all messages in the session received by the user do not need to be sent to the server, and whether the legacy messages which are not received by the client exist can be determined according to the first latest version, so that network resources can be saved.
Fig. 4 is a block diagram of a message processing apparatus shown in the present application. Referring to fig. 4, the apparatus includes:
a second receiving module 21, configured to receive a first latest version of a message list of a first session stored by a client, where messages in the first session are stored in the first message list;
a third obtaining module 22 configured to store, at the server, a second latest version of a message list of a second session in which the client participates, the second message list storing all messages in the second session;
a generating module 23, configured to generate a notification message when the second latest version is different from the first latest version, where the notification message carries a session identifier of the second session, and the notification message is used to indicate that there is a legacy message that is not received by the client in a message list of the second session,
a second sending module 24 configured to send the notification message to the client.
In an optional implementation manner, the message numbers of the messages stored in the message list of the second session are sequentially increased according to the sequence of the receiving times of the messages in the second session received by the server;
the device further comprises:
a third receiving module, configured to receive a message obtaining request sent by the client, where the message obtaining request carries a first message number and a session identifier of the second session, and the first message number is the largest message number among message numbers of all messages in a message list of the second session stored in the client;
a fourth obtaining module configured to obtain a legacy message, the legacy message comprising: and the message which is stored in the server and corresponds to the message number which is greater than the first message number in the message list of the second session.
In an optional implementation manner, the notification message further carries the second latest version.
According to the method and the device, the client side can determine whether the legacy messages which are not received by the client side exist in the server only according to the first latest version without sending all messages in the session which are received by the user to the server, so that network resources can be saved.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
Fig. 5 is a block diagram of a client 800 shown in the present application. For example, client 800 may be a mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, and the like.
Referring to fig. 5, client 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communication component 816.
The processing component 802 generally controls overall operation of the client 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or a portion of the steps of the message processing method described above and shown in fig. 1. Further, the processing component 802 can include one or more modules that facilitate interaction between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support operation at the device 800. Examples of such data include instructions for any application or method operating on client 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The multimedia component 808 includes a screen that provides an output interface between the client 800 and the user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front facing camera and/or a rear facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the device 800 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 810 is configured to output and/or input audio signals. For example, audio component 810 includes a Microphone (MIC) configured to receive external audio signals when client 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.
The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
In an exemplary embodiment, the client 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described message processing method as shown in fig. 1.
In an exemplary embodiment, a non-transitory computer-readable storage medium comprising instructions, such as memory 804 comprising instructions, executable by processor 820 of client 800 to perform the message processing method described above and shown in fig. 1 is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Fig. 6 is a block diagram of a server 1900 shown in the present application. For example, server 1900 may be provided as a server.
Referring to FIG. 6, the server 1900 includes a processing component 1922 further including one or more processors and memory resources, represented by memory 1932, for storing instructions, e.g., applications, executable by the processing component 1922. The application programs stored in memory 1932 may include one or more modules that each correspond to a set of instructions. Further, the processing component 1922 is configured to execute instructions to perform the message processing method described above with respect to fig. 2.
The server 1900 may further include a power component 1926 configured to perform power management of the server 1900, a wired or wireless network interface 1950 configured to connect the server 1900 to a network, and an input/output (I/O) interface 1958. The server 1900 may operate based on an operating system stored in memory 1932, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
A1, a message processing method, applied to a client, the method comprising:
acquiring a first latest version of a message list of a first session stored by the client, wherein the first message list stores messages in the first session;
sending the first latest version to a server;
receiving a notification message returned by a server, where the notification message is sent to a client when a second latest version of a message list of a second session in which the client participates, stored by the server, is greater than the first latest version, the notification message carries a session identifier of the second session, the notification message is used to indicate that a legacy message that is not received by the client exists in the message list of the second session, and the second message list stores all messages in the second session;
determining that a legacy message not received by the client exists in a message list of the second session according to the notification message.
A2, after the determining, according to the notification message, that there is a legacy message not received by the client in the message list of the second session, according to the method of A1, further comprising:
the legacy message is obtained from the server.
A3, according to the method in a2, the message numbers of the messages stored in the message list of the second session are sequentially increased according to the sequence of the receiving time of the messages in the second session received by the server;
the obtaining the legacy message from the server includes:
sending a message acquisition request to the server, where the message acquisition request carries a first message number and a session identifier of the second session, and the first message number is the largest message number in message numbers of all messages in a message list of the second session stored in the client;
receiving a legacy message returned by the server according to the acquisition request, wherein the legacy message comprises: and the message which is stored in the server and corresponds to the message number which is greater than the first message number in the message list of the second session.
A4, according to the method of a1, after the obtaining the legacy message from the server, further comprising:
and displaying the legacy messages in the order of the message numbers from small to large.
A5, according to the method of A1, the notification message also carries the second latest version;
the method further comprises the following steps:
updating the first latest version with the second latest version.
A6, a message processing method, applied to a server, the method comprising:
receiving a first latest version of a message list of a first session stored by a client, wherein messages in the first session are stored in the first message list;
obtaining a second latest version of a message list of a second session in which the client participates, which is stored in the server, the second message list storing all messages in the second session;
when the second latest version is different from the first latest version, generating a notification message, where the notification message carries a session identifier of the second session, and the notification message is used to indicate that a legacy message that is not received by the client exists in a message list of the second session,
and sending the notification message to the client.
A7, according to the method in a6, the message numbers of the messages stored in the message list of the second session are sequentially increased according to the sequence of the receiving time of the messages in the second session received by the server;
the method further comprises the following steps:
receiving a message acquisition request sent by the client, wherein the message acquisition request carries a first message number and a session identifier of the second session, and the first message number is the largest message number in the message numbers of all messages in a message list of the second session stored in the client;
obtaining a legacy message, the legacy message comprising: and the message which is stored in the server and corresponds to the message number which is greater than the first message number in the message list of the second session.
A8, the notification message further carrying the second latest version according to the method of A6.
A9, a message processing device applied to a client, the device comprising:
a first obtaining module configured to obtain a first latest version of a message list of a first session stored by the client, wherein the first message list stores messages in the first session;
a first sending module configured to send the first latest version to a server;
a first receiving module, configured to receive a notification message returned by a server, where the notification message is sent to a client when a second latest version of a message list of a second session in which the client participates, stored by the server, is greater than the first latest version, the notification message carries a session identifier of the second session, the notification message is used to indicate that a legacy message that is not received by the client exists in the message list of the second session, and the second message list stores all messages in the second session;
a determining module configured to determine, according to the notification message, that there is a legacy message in a message list of the second session that is not received by the client.
A10, the apparatus of A9, further comprising:
a second obtaining module configured to obtain the legacy message from the server.
A11, according to the apparatus of A10, the message numbers of the messages stored in the message list of the second session are sequentially increased according to the sequence of the receiving time of the messages in the second session received by the server;
the second acquisition module includes:
a sending unit, configured to send a message obtaining request to the server, where the message obtaining request carries a first message number and a session identifier of the second session, and the first message number is a largest message number of message numbers of all messages in a message list of the second session stored in the client;
a receiving unit, configured to receive a legacy message returned by the server according to the acquisition request, where the legacy message includes: and the message which is stored in the server and corresponds to the message number which is greater than the first message number in the message list of the second session.
A12, the apparatus of A9, further comprising:
a display module configured to display the legacy messages in order of message numbers from small to large.
A13, the apparatus of A9, the notification message further carrying the second latest version;
the device further comprises:
an update module configured to update the first latest version with the second latest version.
A14, a message processing device, applied to a server, the device comprising:
a second receiving module configured to receive a first latest version of a message list of a first session stored by a client, wherein the first message list stores messages in the first session;
a third obtaining module configured to store, at the server, a second latest version of a message list of a second session in which the client participates, the second message list storing all messages in the second session;
a generating module configured to generate a notification message when the second latest version is different from the first latest version, where the notification message carries a session identifier of the second session, and the notification message is used to indicate that a legacy message that is not received by the client exists in a message list of the second session,
a second sending module configured to send the notification message to the client.
A15, according to the apparatus of A14, the message numbers of the messages stored in the message list of the second session are sequentially increased according to the sequence of the receiving time of the messages in the second session received by the server;
the device further comprises:
a third receiving module, configured to receive a message obtaining request sent by the client, where the message obtaining request carries a first message number and a session identifier of the second session, and the first message number is the largest message number among message numbers of all messages in a message list of the second session stored in the client;
a fourth obtaining module configured to obtain a legacy message, the legacy message comprising: and the message which is stored in the server and corresponds to the message number which is greater than the first message number in the message list of the second session.
A16, the apparatus of A14, the notification message also carrying the second latest version.
Claims (20)
1. A message processing method is applied to a client, and the method comprises the following steps:
after a client logs in a server, acquiring a first latest version of a message list of a first session stored by the client, wherein messages in the first session are stored in the first message list;
sending the first latest version to the server;
receiving a notification message returned by a server, where the notification message is sent to a client when a second latest version of a message list of a second session in which the client participates, stored by the server, is greater than the first latest version, the notification message carries a session identifier of the second session, the notification message is used to indicate that a legacy message that is not received by the client exists in the message list of the second session, and the second message list stores all messages in the second session;
determining that a legacy message which is not received by the client exists in a message list of the second session according to the notification message;
the legacy message is a history message in the second session, which is forwarded to the client by the server when the client is in the unregistered state and is not forwarded by the server any more in the following;
the message forwarding mechanism of the method is as follows: for any session, when a certain user participating in the session needs to send a message in the session, the client of the user sends the message and the session identifier of the session to the server, and the server receives the message and the session identifier and actively forwards the message to the clients of other users participating in the session according to the session identifier.
2. The method of claim 1, wherein after determining that there is a legacy message not received by the client in the message list of the second session according to the notification message, further comprising:
the legacy message is obtained from the server.
3. The method according to claim 2, wherein the message numbers of the messages stored in the message list of the second session are sequentially increased according to the sequence of the receiving time of the messages in the second session received by the server;
the obtaining the legacy message from the server includes:
sending a message acquisition request to the server, where the message acquisition request carries a first message number and a session identifier of the second session, and the first message number is the largest message number in message numbers of all messages in a message list of the second session stored in the client;
receiving a legacy message returned by the server according to the acquisition request, wherein the legacy message comprises: and the message which is stored in the server and corresponds to the message number which is greater than the first message number in the message list of the second session.
4. The method of claim 1, wherein after obtaining the legacy message from the server, further comprising:
and displaying the legacy messages in the order of the message numbers from small to large.
5. The method of claim 1, wherein the notification message further carries the second latest version;
the method further comprises the following steps:
updating the first latest version with the second latest version.
6. A message processing method applied to a server, the method comprising:
receiving a first latest version of a message list of a first session stored by a client to a server after the client logs in the server, wherein messages in the first session are stored in the first message list;
obtaining a second latest version of a message list of a second session in which the client participates, which is stored in the server, the second message list storing all messages in the second session;
when the second latest version is different from the first latest version, generating a notification message, where the notification message carries a session identifier of the second session, and the notification message is used to indicate that a legacy message that is not received by the client exists in a message list of the second session, where the legacy message is a history message in the second session that the server has forwarded to the client when the client is in an unregistered state and that the server will not forward any more in a subsequent active manner;
sending the notification message to the client;
the message forwarding mechanism of the method is as follows: for any session, when a certain user participating in the session needs to send a message in the session, the client of the user sends the message and the session identifier of the session to the server, and the server receives the message and the session identifier and actively forwards the message to the clients of other users participating in the session according to the session identifier.
7. The method according to claim 6, wherein the message numbers of the messages stored in the message list of the second session are sequentially increased according to the sequence of the receiving time of the messages in the second session received by the server;
the method further comprises the following steps:
receiving a message acquisition request sent by the client, wherein the message acquisition request carries a first message number and a session identifier of the second session, and the first message number is the largest message number in the message numbers of all messages in a message list of the second session stored in the client;
obtaining a legacy message, the legacy message comprising: and the message which is stored in the server and corresponds to the message number which is greater than the first message number in the message list of the second session.
8. The method of claim 6, wherein the notification message further carries the second latest version.
9. A message processing apparatus, applied to a client, the apparatus comprising:
the client terminal comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is configured to acquire a first latest version of a message list of a first session stored by the client terminal after the client terminal logs in a server, and the first message list stores messages in the first session;
a first sending module configured to send the first latest version to the server;
a first receiving module, configured to receive a notification message returned by a server, where the notification message is sent to a client when a second latest version of a message list of a second session in which the client participates, stored by the server, is greater than the first latest version, and the notification message carries a session identifier of the second session, where the notification message is used to indicate that a legacy message that is not received by the client exists in the message list of the second session, and the second message list stores all messages in the second session, where the legacy message is a history message in the second session that the server forwards to the client when the client is in an unregistered state and the server subsequently does not forward on its own initiative any more;
a determining module configured to determine, according to the notification message, that there is a legacy message in a message list of the second session that is not received by the client;
wherein, the message forwarding mechanism of the device is as follows: for any session, when a certain user participating in the session needs to send a message in the session, the client of the user sends the message and the session identifier of the session to the server, and the server receives the message and the session identifier and actively forwards the message to the clients of other users participating in the session according to the session identifier.
10. The apparatus of claim 9, further comprising:
a second obtaining module configured to obtain the legacy message from the server.
11. The apparatus according to claim 10, wherein the message numbers of the messages stored in the message list of the second session are sequentially incremented according to the sequence of the receiving times of the messages in the second session received by the server;
the second acquisition module includes:
a sending unit, configured to send a message obtaining request to the server, where the message obtaining request carries a first message number and a session identifier of the second session, and the first message number is a largest message number of message numbers of all messages in a message list of the second session stored in the client;
a receiving unit, configured to receive a legacy message returned by the server according to the acquisition request, where the legacy message includes: and the message which is stored in the server and corresponds to the message number which is greater than the first message number in the message list of the second session.
12. The apparatus of claim 9, further comprising:
a display module configured to display the legacy messages in order of message numbers from small to large.
13. The apparatus of claim 9, wherein the notification message further carries the second latest version;
the device further comprises:
an update module configured to update the first latest version with the second latest version.
14. A message processing apparatus, applied to a server, the apparatus comprising:
a second receiving module, configured to receive a first latest version of a message list of a first session stored by a client to a server after the client logs in the server, wherein the first message list stores messages in the first session;
a third obtaining module configured to store, at the server, a second latest version of a message list of a second session in which the client participates, the second message list storing all messages in the second session;
a generating module, configured to generate a notification message when the second latest version is different from the first latest version, where the notification message carries a session identifier of the second session, and the notification message is used to indicate that a legacy message that is not received by the client exists in a message list of the second session, where the legacy message is a history message in the second session that the server has forwarded to the client when the client is in an unregistered state and that the server will not forward any more subsequently;
a second sending module configured to send the notification message to the client;
wherein, the message forwarding mechanism of the device is as follows: for any session, when a certain user participating in the session needs to send a message in the session, the client of the user sends the message and the session identifier of the session to the server, and the server receives the message and the session identifier and actively forwards the message to the clients of other users participating in the session according to the session identifier.
15. The apparatus according to claim 14, wherein the message numbers of the messages stored in the message list of the second session are sequentially incremented according to the sequence of the receiving times of the messages in the second session received by the server;
the device further comprises:
a third receiving module, configured to receive a message obtaining request sent by the client, where the message obtaining request carries a first message number and a session identifier of the second session, and the first message number is the largest message number among message numbers of all messages in a message list of the second session stored in the client;
a fourth obtaining module configured to obtain a legacy message, the legacy message comprising: and the message which is stored in the server and corresponds to the message number which is greater than the first message number in the message list of the second session.
16. The apparatus of claim 14, wherein the notification message further carries the second latest version.
17. A client, the client comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to perform the message processing method of any of claims 1-5.
18. A server, characterized in that the server comprises:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to perform the message processing method of any of claims 6-8.
19. A non-transitory computer readable storage medium, instructions in which, when executed by a processor of a client, enable the client to perform the message processing method of any of claims 1-5.
20. A non-transitory computer readable storage medium, instructions in which, when executed by a processor of a server, enable the server to perform the message processing method of any one of claims 6-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811039397.XA CN109274510B (en) | 2018-09-06 | 2018-09-06 | Message processing method, device, client, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811039397.XA CN109274510B (en) | 2018-09-06 | 2018-09-06 | Message processing method, device, client, server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109274510A CN109274510A (en) | 2019-01-25 |
| CN109274510B true CN109274510B (en) | 2022-01-21 |
Family
ID=65188501
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811039397.XA Active CN109274510B (en) | 2018-09-06 | 2018-09-06 | Message processing method, device, client, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109274510B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110286854B (en) * | 2019-06-12 | 2021-10-29 | 北京达佳互联信息技术有限公司 | Method, device, equipment and storage medium for group member management and group message processing |
| CN110401709A (en) * | 2019-07-23 | 2019-11-01 | 北京云中融信网络科技有限公司 | Processing method, device and the storage medium of session in a kind of instant messaging application |
| CN110620699B (en) * | 2019-08-02 | 2021-12-28 | 北京字节跳动网络技术有限公司 | Message arrival rate determination method, device, equipment and computer readable storage medium |
| CN112769677B (en) * | 2020-12-30 | 2023-05-23 | 北京达佳互联信息技术有限公司 | Data synchronization method, apparatus, electronic device, storage medium, and program product |
| CN113014470B (en) * | 2021-01-07 | 2022-04-08 | 腾讯科技（深圳）有限公司 | Receipt processing method and device for session message in instant messaging application |
| CN113099306B (en) * | 2021-03-23 | 2022-11-22 | 北京达佳互联信息技术有限公司 | Message processing method, device, equipment, server, medium and product |
| CN113204449B (en) * | 2021-05-20 | 2023-02-14 | 深圳软牛科技有限公司 | Session backup method, computer-readable storage medium and terminal device |
| CN113630465B (en) * | 2021-08-10 | 2024-03-12 | 北京百度网讯科技有限公司 | Message processing method, device, equipment and storage medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8112529B2 (en) * | 2001-08-20 | 2012-02-07 | Masterobjects, Inc. | System and method for asynchronous client server session communication |
| CN103051520B (en) * | 2013-01-05 | 2015-11-25 | 小米科技有限责任公司 | The method of synchronous offline session message and device in JICQ |
| CN105610836B (en) * | 2015-12-31 | 2019-01-15 | 浙江省公众信息产业有限公司 | A kind of method and system of data transmission |
| CN105933213B (en) * | 2016-06-24 | 2021-01-15 | 腾讯科技（深圳）有限公司 | Chat message processing method, related equipment and system |
-
2018
- 2018-09-06 CN CN201811039397.XA patent/CN109274510B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN109274510A (en) | 2019-01-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109274510B (en) | Message processing method, device, client, server and storage medium | |
| EP2978234A1 (en) | Method and apparatus for sharing video information | |
| CN109521918B (en) | Information sharing method and device, electronic equipment and storage medium | |
| CN109388625B (en) | Method and device for processing configuration file in multi-distributed file system | |
| EP3223147A2 (en) | Method for accessing virtual desktop and mobile terminal | |
| CN106254192B (en) | Prompting method, prompting device and prompting system | |
| CN112291631A (en) | Information acquisition method, device, terminal and storage medium | |
| CN109302341B (en) | Instant messaging method, instant messaging device, electronic equipment and storage medium | |
| CN106375178B (en) | Message display method and device based on instant messaging | |
| CN107272896B (en) | Method and device for switching between VR mode and non-VR mode | |
| CN112616053B (en) | Transcoding method and device for live video and electronic equipment | |
| CN113901353A (en) | Information display method, device and system, electronic equipment and server | |
| CN106878654B (en) | Video communication method and device | |
| CN110690979B (en) | Group message processing method, device, server, client and storage medium | |
| CN106506808B (en) | Method and device for prompting communication message | |
| CN109245992B (en) | Request processing method and device, electronic equipment and storage medium | |
| CN105827513B (en) | Video information sharing method, device and equipment | |
| CN109831538B (en) | Message processing method, device, server, terminal and medium | |
| CN105656639B (en) | Group message display method and device | |
| CN109787890B (en) | Instant messaging method, device and storage medium | |
| CN107846481B (en) | Account management method and device | |
| CN107277422B (en) | Video call method, device and system | |
| CN107026941B (en) | Method and device for processing reply of unread message | |
| US11483263B2 (en) | Method and terminal for facilitating chat between users of two terminals | |
| CN106708930B (en) | Method and device for refreshing application page |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |