Instant communication message synchronization method and device, electronic equipment and storage medium

Abstract

The invention provides an instant messaging message synchronization method and device, electronic equipment and a storage medium, and relates to the technical field of information, in particular to the technical field of instant messaging. The specific implementation scheme is as follows: in response to a login instruction triggered by a user, obtaining a session list corresponding to a user identifier from a server; after the session list is synchronized, obtaining a latest session message corresponding to a session in the session list from the server, and recording a starting point identifier and an end point identifier of the obtained session message to construct a confidence interval; and if a target session message pulling request is received, determining to pull a message from a local database or a server according to a relationship between the current confidence interval and a pulled message interval carried in the message pulling request so as to synchronize the message. The method can effectively reduce the number of requests for the server, reduces the load of the server, accelerates the message synchronization speed, and improves the message obtaining efficiency and the user experience.

Description

Technical Field

[0001] The present disclosure relates to the field of information technology, specifically to the field of instant communication technology, and in particular to an instant communication message synchronization method, device, electronic device and storage medium. Background Art

[0002] In the instant messaging (IM) business, the generation and processing of messages is one of its core functions. With the growth of the user base and the extension of the server's message retention time, the amount of messages in the user's mailbox continues to accumulate, which puts higher requirements on the synchronization of messages between the client and the server. Especially when the user has not logged in for a long time or logs in again after uninstalling and reinstalling the application, a large number of messages need to be synchronized with the server in a short period of time, which may not only cause the client performance to degrade, but also cause huge pressure on the server. For IM systems serving individual users (C-end), the traditional push-pull combination mechanism can usually meet the needs, that is, the client records the location of the last message pull, and only pulls the new messages added since then when logging in next time. However, for corporate users (B-end), especially those with a large number of fans, their message volume is huge. Whether it is the first login or the subsequent incremental update, a large number of messages need to be processed and synchronized. This requires a new mechanism that can reduce the frequency of message pull and reduce the pressure on the server, while maintaining the synchronization of messages between the client and the server to meet the special needs of B-end users. Summary of the invention

[0003] The present disclosure provides an instant messaging message synchronization method, device, electronic device and storage medium.

[0004] According to one aspect of the present disclosure, a method for synchronizing instant messaging messages is provided, the method comprising:

[0005] In response to a login instruction triggered by a user, obtaining a session list corresponding to the user identifier from a server;

[0006] After the conversation list is synchronized, the latest conversation message corresponding to the conversation in the conversation list is obtained from the server, and the starting point identifier and the end point identifier of the obtained conversation message are recorded to construct a confidence interval;

[0007] If a target session message pull request triggered by a user is received, it is determined to pull messages from the local database or the server to synchronize messages according to the relationship between the current confidence interval and the message pull interval carried in the message pull request.

[0008] According to another aspect of the present disclosure, there is provided an instant messaging message synchronization device, comprising:

[0009] A response module, configured to obtain a session list corresponding to the user identifier from a server in response to a login instruction triggered by a user;

[0010] A construction module, configured to obtain, after the synchronization of the conversation list, the latest conversation message corresponding to the conversation in the conversation list from the server, and record the start point identifier and the end point identifier of the obtained conversation message to construct a confidence interval;

[0011] The message pulling module is used to determine whether to pull messages from the local database or the server to synchronize messages based on the relationship between the current confidence interval and the message pulling interval carried in the message pulling request if a target session message pulling request triggered by a user is received.

[0012] According to a third aspect of the present disclosure, there is provided an electronic device, including:

[0013] at least one processor; and

[0014] a memory communicatively connected to the at least one processor; wherein,

[0015] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any method in any of the above technical solutions.

[0016] According to a fourth aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to enable the computer to execute any one of the methods described in the above technical solutions.

[0017] According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer program, wherein the computer program implements any one of the methods described in the above technical solutions when executed by a processor.

[0018] The present disclosure provides an instant messaging message synchronization method, device, equipment and storage medium. The present disclosure obtains a session list from a server in response to a user login instruction, that is, after the user logs in, the user directly obtains the session list from the server, so that the user can see the changed session more quickly, and the time for the user to see the changed session is greatly shortened, and other sessions will not be updated slowly due to the synchronization of a certain session message. After the session list is synchronized, the latest message is pulled to build a confidence interval, and the source of the message is intelligently determined based on the relationship between the confidence interval and the user request. This can effectively reduce the number of requests to the server, reduce the server load, and speed up the message synchronization speed, improve the efficiency of message acquisition and user experience. It can be seen that the method of the present disclosure enables users to receive the latest messages in a timely manner, thereby maintaining the high performance and response speed of the instant messaging system in large-scale message processing and high concurrency scenarios.

[0019] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present disclosure.

[0021] Figure 1 is a schematic diagram of an exemplary process of message synchronization when an instant messaging user logs in for the first time;

[0022] Figure 2 It is a schematic diagram of a flow of an exemplary instant messaging user synchronizing messages by using an incremental pull method;

[0023] Figure 3 is a schematic diagram of the steps of the instant messaging message synchronization method in an embodiment of the present disclosure;

[0024] Figure 4 It is a flowchart of a non-first-time login instant messaging message synchronization method in an embodiment of the present disclosure;

[0025] Figure 5 is a flowchart of a message synchronization method in an embodiment of the present disclosure;

[0026] Figure 6 is a flowchart of an instant messaging message synchronization method in an embodiment of the present disclosure;

[0027] Figure 7 A principle block diagram of an instant messaging synchronization device in an embodiment of the present disclosure;

[0028] Figure 8It is a block diagram of an electronic device used to implement the instant messaging message synchronization method of the embodiment of the present disclosure. DETAILED DESCRIPTION

[0029] The following is a description of exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0030] In the related technical solution, see Figure 1 , Figure 1 It is a flowchart of message synchronization when an exemplary instant messaging user logs in for the first time. Specifically, the process includes: for the first login: the user opens the IM application and logs in. Pull from the beginning: since it is the first login, all messages are pulled from the server from the beginning, that is, the request starts from the earliest message and obtains all message records of the user. Next, pull messages: by communicating with the server, pull message data from the server according to the requested range. Message storage: The pulled messages are stored in the local database so that the user can access these messages when offline. Determine whether there are more: check whether there are more messages to be pulled. This is usually based on the response of the server. If the server indicates that there are more messages that have not been pulled, the process will continue. If yes (that is, there are more messages), the process returns to the "pull message" step and continues to pull the remaining messages. If not (that is, all messages have been pulled), the process continues to the next step. End: Once all messages are pulled and stored in the local database, the process ends.

[0031] This flowchart shows how a typical IM system handles the message synchronization problem when logging in for the first time. This approach ensures that users can see all previous messages after logging in, providing complete context for subsequent communications. However, this method of pulling messages from scratch may encounter performance issues when the message volume is large or the user has not logged in for a long time, such as long loading time or high pressure on the server. Therefore, some IM systems may adopt a more efficient incremental pull strategy, pulling only the new messages generated after the user last logged in, in order to optimize performance and user experience.

[0032] See also Figure 2 , Figure 2This is a flow chart of an exemplary instant messaging user using incremental pull to synchronize messages. Specifically, incremental pull: after the user logs in, instead of pulling all messages from the beginning, only the new messages generated since the last login are pulled. This is based on the message position recorded when the user last logged in, so you can know where to start pulling new messages. Then pull the message: send a request to the server to pull the new messages generated since the last login. This request will contain the identifier of the latest message at the time of the last login so that the server knows from which point to start sending messages. Message storage: the pulled new messages are stored in the local database, and the user's message record is updated to ensure that the user can see all new messages since the last login. Are there more: check whether the server has more messages that have not been pulled. This is usually based on the server's response. If the server indicates that there are more messages that have not been pulled, the process will continue. If yes (that is, there are more messages), the process returns to the "message pull" step to continue pulling the remaining messages. If not (that is, all new messages have been pulled), the process continues to the next step. End: Once all new messages have been pulled and stored in the local database, the process ends.

[0033] For IM systems that need to meet the needs of both C-end and B-end users, the traditional push-pull mechanism can basically meet the usage scenarios of C-end users, that is, the client records the location of the message pulled last time, and only pulls the incremental part the next time you log in. However, for B-end users who may have hundreds of thousands or even millions of fans, the amount of messages in their mailboxes is difficult to estimate. At this time, whether it is the first login pull or the incremental pull, there will be a lot of messages that need to be synchronized. Therefore, a pull mechanism that can reduce the pull frequency and keep the client and server (Server) message synchronization is needed.

[0034] In order to solve the above technical problems, the present invention provides a new instant messaging message synchronization method. Figure 3 As shown, Figure 3 1 is a schematic diagram of the steps of an instant messaging message synchronization method in an embodiment of the present disclosure. The method can be applied to a client, and the method includes:

[0035] Step S301: in response to a login instruction triggered by a user, a session list corresponding to the user identifier is obtained from a server.

[0036] Specifically, when a user triggers a login command, the instant messaging system will respond to this operation and retrieve and obtain a list of all sessions related to the user from the server through the user's unique identifier (user ID). This process involves the user logging in and authenticating, sending a request to the backend server, and the server querying the database based on the user ID and returning a list of all sessions in which the user participates. This session list usually includes chat sessions in which the user communicates with others, and each session may involve one or more conversation partners. Obtaining a session list is the first step in IM system message synchronization and display. It enables users to quickly access and manage their chat sessions, laying the foundation for subsequent message synchronization and user interaction.

[0037] Optionally, the login instruction may include the first login or non-first login. If it is the first login, directly obtain the session list. If it is non-first login, refer to Figure 4 As shown, Figure 4 It is a flowchart of the instant messaging message synchronization method for non-first login in the embodiment of the present disclosure. User login: The user opens the IM application and logs in. Incremental pull: This solution does not pull all messages from the beginning, but adopts an incremental pull strategy to only pull new messages generated since the last login. Session storage: The pulled session list is stored in the local database, and the user's message record is updated to ensure that the user can see all new messages since the last login. Update notification: Update the user interface to notify the user that there is a new session list update. The number of session lists meets N: Check whether the number of session lists stored in the local database has reached a preset threshold N. This threshold may be to limit the number of sessions loaded at one time to avoid interface freezes or excessive consumption of resources. If yes (that is, the number of session lists is full), the process continues to check whether there are more sessions. If not (that is, the number of session lists is not full), directly check whether there are more sessions. There are more sessions: The system checks whether there are more unpulled sessions on the server. If yes (that is, there are more sessions), the process returns to the "incremental pull" step to continue pulling the remaining session messages. If not (i.e. all sessions have been pulled), the process continues to the next step. End: Once all new sessions are pulled and stored in the local database and the preset threshold N is met, the process ends. This process design helps balance performance and user experience. By limiting the number of messages loaded at one time, system overload can be avoided while ensuring that users can get new session updates in a timely manner.

[0038] In this way, by instantly obtaining the session list corresponding to the user ID from the server when the user triggers the login instruction, it can ensure that the user quickly receives the latest session after logging in, which is conducive to improving the efficiency and accuracy of message synchronization. This approach reduces the possibility of the system processing and displaying outdated data, enhances the user experience, and also reduces the burden of the client processing historical data, optimizing the overall system performance.

[0039] Step S302: after the conversation list is synchronized, the latest conversation message corresponding to the conversation in the conversation list is obtained from the server, and the start point identifier and the end point identifier of the obtained conversation message are recorded to construct a confidence interval.

[0040] Specifically, the "conversation list" refers to an overview of all chat sessions that the user has participated in, while the "conversation messages" are the specific exchanges in these sessions. When the user's conversation list is synchronized with the server, the latest messages in each conversation are further obtained from the server. These messages are used to update the local conversation view and ensure that the user can see the most recent message activity. Optionally, see Figure 5 As shown, Figure 5 : is a flowchart of the message synchronization method in the embodiment of the present disclosure. The process includes synchronizing messages: checking whether there are new messages to be synchronized. Sessions to be synchronized: checking whether there are sessions that have not been synchronized. If yes (i.e., there are sessions to be synchronized), the process continues to the next step. If no (i.e., all sessions have been synchronized), the process ends. Pulling session messages: pulling messages in sessions that have not been synchronized from the server. Message storage: The pulled messages are stored in the local database so that users can access these messages. Messages meet N: checking whether the number of pulled messages reaches a preset threshold N. If yes (i.e., the number of messages has met N), the process continues to check whether there are more messages. If no (i.e., the number of messages does not meet N), the process ends. There are more messages: checking whether there are more unpulled messages on the server. If yes (i.e., there are more messages), the process returns to the "pulling session messages" step and continues to pull the remaining messages. If no (i.e., all messages have been pulled), the process ends. End: Once all new messages are pulled and stored in the local database and the preset threshold N is met, the process ends. This flowchart shows a cyclic process that continuously checks whether there are new messages to be synchronized until all messages are processed. This design helps ensure that users can get new messages in a timely manner, while also controlling the number of messages processed at one time to avoid excessive pressure on system resources. In this way, the IM system can maintain the continuity and integrity of messages while optimizing resource usage and improving user experience.

[0041] For the disclosed embodiment, the latest conversation message corresponding to the conversation in the conversation list is obtained from the server, and the starting point identifier and the end point identifier of the obtained conversation message are recorded to construct a confidence interval. Among them, the "starting point identifier" and the "end point identifier" refer to the message IDs of the beginning and end of the range of pulled messages, respectively. They are unique identifiers of messages and are used to accurately locate and synchronize messages. By recording these identifiers, a "confidence interval" is constructed, which is an interval containing all synchronized messages from the starting point to the end point, ensuring the integrity of the messages and the accuracy of synchronization. This process not only improves the efficiency of message synchronization, but also optimizes the user experience, because users can trust that they are seeing the latest and complete conversation records.

[0042] In this way, by obtaining the latest message of each session from the server after the session list is synchronized, and recording the start and end identifiers of these messages to build a confidence interval, the integrity and accuracy of the message can be effectively ensured, data redundancy and repeated requests can be reduced, and the efficiency of message synchronization can be improved. In this way, user requests for specific session messages can be quickly responded to, and messages can be provided directly from the local database instead of being pulled from the server every time, thereby reducing the server load, speeding up the message loading speed, and improving the user experience. This optimization is particularly important in poor network conditions or high concurrency situations.

[0043] Step S303: if a target session message pull request triggered by a user is received, it is determined to pull messages from a local database or server according to the relationship between the current confidence interval and the message pull interval carried in the message pull request to synchronize the messages.

[0044] Specifically, when a user requests to view messages of a specific session, a "target session message pull request" will be received. This request contains the start and end point identifiers of the messages that the user wants to pull, that is, the message range that the user wants to view. "Confidence intervals" refer to those message intervals that the client has confirmed to be synchronized with the server. They are composed of the start and end identifiers of the messages that were successfully pulled and recorded from the server before. The message interval in the user's pull request is compared with the existing confidence interval. If the user's request interval falls completely within the confidence interval, it means that these messages already exist in the local database, and these messages will be pulled directly from the local database, which can reduce requests to the server and speed up message loading. If the requested interval exceeds the confidence interval, it is necessary to pull the missing message part from the server, update the local database, and expand the confidence interval. This process ensures that the synchronization of messages is efficient and accurate, while also optimizing the use of server resources and improving user experience.

[0045] In this way, by intelligently judging the relationship between the user's session message pull request and the current confidence interval, and deciding whether to pull messages from the local database or the server, it can effectively reduce unnecessary server requests, reduce network latency, speed up message loading, and improve user experience. At the same time, this method also reduces the burden on the server and improves the processing power of the client, especially in high-concurrency scenarios, it can manage message synchronization more efficiently and ensure the smooth operation of the instant messaging system.

[0046] The present disclosure provides an instant messaging message synchronization method, apparatus, device and storage medium. The present disclosure obtains a session list from a server in response to a user login instruction, that is, after the user logs in, the user directly obtains the session list from the server, so that the user can see the changed session more quickly, and the time for the user to see the changed session is greatly shortened, and other sessions will not be updated slowly due to the synchronization of a certain session message. After the session list is synchronized, the latest message is pulled to build a confidence interval, and the source of the message is intelligently determined based on the relationship between the confidence interval and the user request, which can effectively reduce the number of requests to the server, reduce the server load, and speed up the message synchronization speed, improve the efficiency of message acquisition and user experience. It can be seen that the method of the present disclosure enables users to receive the latest messages in a timely manner, thereby maintaining the high performance and response speed of the instant messaging system in large-scale message processing and high concurrency scenarios.

[0047] In some optional embodiments, according to the relationship between the current confidence interval and the message pull interval carried in the message pull request, determining to pull the message from the local database or server to synchronize the message includes:

[0048] Obtain the identifier of the message pull start point and the identifier of the message pull end point carried in the message pull request;

[0049] The interval from the message pulling start point to the message pulling end point is determined as the message pulling interval;

[0050] According to the intersection relationship between the current confidence interval and the message pulling interval, it is determined whether to pull the message from the local database or from the server to perform message synchronization.

[0051] Specifically, when a user requests to view a series of messages in a specific session, the identifier of the message pull start point (also called msgid) and the identifier of the message pull end point carried in the message pull request are obtained, that is, the starting point and the end point of the message range that the user wants to retrieve need to be identified. Subsequently, the "interval from the message pull start point to the message pull end point is determined as the pull message interval", and this interval represents the specific message range requested by the user. Next, according to the intersection relationship between the current confidence interval and the pull message interval, it is determined whether to pull messages from the local database or from the server to perform message synchronization. Here, the confidence interval refers to the message interval that the client knows is completely synchronized with the server. If the message interval requested by the user has an intersection with the confidence interval, it indicates that part or all of the required messages are already in the local database and can be directly obtained from the local database; if they do not intersect, the missing message part needs to be pulled from the server to ensure that the user can receive the complete message history. This process optimizes the efficiency of message synchronization, reduces dependence on the server, speeds up message loading, and improves user experience.

[0052] In this way, by accurately obtaining the start and end point identifiers of the message pull requested by the user, and determining the message pull interval based on this, and then combining the intersection relationship between the confidence interval and the request interval to intelligently decide the message source, the efficiency and accuracy of message synchronization can be significantly improved. This method allows missing messages to be pulled from the server only when necessary, reducing unnecessary data transmission, reducing server load, and speeding up local message retrieval, improving user experience, especially when network conditions are poor or users request a large number of historical messages. This optimization effect is more obvious. In addition, this method also helps save data traffic and improve the response speed of the application, making the instant messaging system more stable and efficient when processing large-scale messages.

[0053] In some optional embodiments, determining to pull messages from a local database or from a server to perform message synchronization based on the intersection relationship between the current confidence interval and the message pulling interval includes:

[0054] If the current confidence interval does not intersect with the message pull interval, the message corresponding to the message pull interval is pulled from the server to perform message synchronization;

[0055] The current confidence interval is updated according to the message received from the server to obtain a new confidence interval.

[0056] Specifically, the "confidence interval" refers to the message interval that the client and the server are fully synchronized, while the "pull message interval" refers to the range of messages that the user requests to pull. When the user's request interval (pull message interval) does not overlap with the known synchronization interval (confidence interval), it means that the message requested by the user is not in the local database. At this time, the message corresponding to the pull message interval will be pulled from the server for message synchronization. This process involves sending a request to the server to retrieve and receive the message data required by the user. Once these messages are successfully pulled and stored in the local database, the current confidence interval is updated according to the pulled messages to obtain a new confidence interval. By updating the current confidence interval according to the pulled messages, this means that a new confidence interval will be expanded or created to include the newly pulled messages, ensuring that future requests can be processed more efficiently and maintaining data consistency between the local database and the server. Such a mechanism ensures that efficient and accurate data synchronization can be maintained even when the user requests messages that exceed the existing synchronization range.

[0057] In this way, by pulling missing messages from the server when the confidence interval does not intersect with the pull message interval requested by the user, and updating the confidence interval based on these new messages, it is possible to ensure that even when faced with user requests for historical messages or new messages, a complete message history can be quickly responded to and provided. This not only improves the accuracy and completeness of message synchronization and reduces user waiting time, but also enhances the flexibility and reliability of the client, ensuring that users can always access the latest communication data, while optimizing data storage and retrieval efficiency and reducing unnecessary burden on the server caused by repeated requests for the same data.

[0058] In some optional embodiments, determining to pull messages from a local database or from a server to perform message synchronization based on the intersection relationship between the current confidence interval and the message pulling interval includes:

[0059] If the pulled message interval is within the current confidence interval, the message corresponding to the pulled message interval is pulled from the local database to synchronize the messages.

[0060] Specifically, when the message range (pull message interval) requested by the user is completely within the known synchronization interval (confidence interval), this means that the required message is already stored in the local database. In this case, the message corresponding to the pull message interval requested by the user will be pulled directly from the local database without initiating a request to the server again. This processing method reduces dependence on the server, reduces network latency, speeds up message loading, and improves user experience. At the same time, this also reduces the burden on the server, especially in high concurrency situations, helping to improve the stability and efficiency of the entire instant messaging system.

[0061] In this way, when the message pull interval is completely within the current confidence interval, the message is directly pulled from the local database, which significantly improves the efficiency of message synchronization, reduces the number of requests to the server, reduces network latency, speeds up message loading, and optimizes user experience. At the same time, this method reduces the burden on the server, saves bandwidth resources, and improves the stability and response speed of the client system. This optimization effect is more obvious, especially when there are a large number of users or a large amount of data, which helps to improve the processing capacity and performance of the entire instant messaging system.

[0062] In some optional embodiments, determining to pull messages from a local database or from a server to perform message synchronization based on the intersection relationship between the current confidence interval and the message pulling interval includes:

[0063] If the message pull start point is within the current confidence interval, and the message pull end point is outside the current confidence interval, then pull messages from the message pull start point to the end point of the current confidence interval from the local database, and pull messages from the end point of the current confidence interval to the message pull end point from the server, to obtain messages corresponding to the pulled message interval;

[0064] The message corresponding to the pulled message interval is synchronized, and the current confidence interval is updated according to the message received from the server to obtain a new confidence interval.

[0065] Specifically, when part of the message range requested by the user is within the current confidence interval, and the other part is outside the confidence interval, the embodiment of the present disclosure will take two steps to satisfy the request: first, pull the messages from the message pull start point to the current confidence interval end point from the local database, which have been synchronized with the server and stored locally; second, for messages beyond the current confidence interval, a request will be initiated to the server to pull the messages from the confidence interval end point to the message pull end point requested by the user. In this way, the messages within the entire message interval requested by the user can be fully obtained. Subsequently, these messages are synchronized, and the current confidence interval is updated according to the new messages received from the server to form a new confidence interval, which ensures that the messages in the local database are kept up to date with the server, and also provides a wider range of local messages for future requests, thereby improving the efficiency of message synchronization and the response speed of the system.

[0066] In this way, this mechanism intelligently handles the user's demand for messages. When the message interval requested by the user spans the locally synchronized confidence interval, the corresponding message segments are pulled from the local database and the server respectively, and then these messages are merged to meet the user's request. This method not only improves the efficiency of message acquisition and reduces the request pressure on the server, but also ensures that users can seamlessly receive the complete message history. In addition, updating the confidence interval after synchronization further optimizes the subsequent message pulling process because it expands the range of locally synchronized messages and reduces the amount of data that needs to be pulled from the server in the future, thereby reducing network latency, improving user experience, and enhancing the stability and performance of the client system.

[0067] In some optional embodiments, determining to pull messages from a local database or from a server to perform message synchronization based on the intersection relationship between the current confidence interval and the message pulling interval includes:

[0068] If the message pull end point is within the current confidence interval, and the message pull start point is outside the current confidence interval, then pull messages from the starting point of the current confidence interval to the message pull end point from the local database, and pull messages from the message pull start point to the starting point of the current confidence interval from the server, to obtain messages corresponding to the pulled message interval;

[0069] The message corresponding to the pulled message interval is synchronized, and the current confidence interval is updated according to the message received from the server to obtain a new confidence interval.

[0070] Specifically, when part of the message range requested by the user is outside the current confidence interval, and the other part is within the confidence interval, two steps will be taken to satisfy the request: first, pull the messages from the starting point of the confidence interval to the end point of the message pull requested by the user from the local database. This part of the messages has been synchronized with the server and stored locally; second, for messages outside the current confidence interval, a request will be initiated to the server to pull the messages from the starting point of the message pull requested by the user to the starting point of the confidence interval. In this way, the messages within the entire message range requested by the user can be fully obtained. Subsequently, these messages are synchronized, and the current confidence interval is updated according to the new messages received from the server to form a new confidence interval. This ensures that the messages in the local database are kept up to date with the server, and also provides a wider range of local messages for future requests, thereby improving the efficiency of message synchronization and the response speed of the system.

[0071] In this way, by intelligently pulling messages from the local database and the server respectively, the user-requested message interval is fully covered, ensuring the integrity and continuity of the message. It not only improves the efficiency of message acquisition and reduces the request pressure on the server, but also ensures that users can seamlessly receive the complete message history. In addition, updating the confidence interval after synchronization further optimizes the subsequent message pulling process because it expands the scope of local synchronized messages and reduces the amount of data that needs to be pulled from the server in the future, thereby reducing network latency, improving user experience, and enhancing system stability and performance.

[0072] In some optional embodiments, updating the current confidence interval according to the message received from the server to obtain a new confidence interval includes:

[0073] Obtain the message start point identifier and the message end point identifier received from the server to obtain a new message interval;

[0074] Calculate the union of the new message interval and the current confidence interval to get the new confidence interval.

[0075] Specifically, after receiving a batch of messages from the server, the starting point (message starting point identifier) ​​and the ending point (message end point identifier) ​​of these messages are recorded to determine a new message interval. This interval represents the range of the latest synchronized messages. Subsequently, the union of this new message interval and the currently known confidence interval (that is, the message interval that has been confirmed to be completely synchronized with the server) is calculated. By merging the two intervals, a new confidence interval can be obtained. This new confidence interval expands the range of known synchronized messages in the local database, including all messages from the earliest message starting point to the latest message end point. This process ensures that the message synchronization between the local database and the server is up to date, while also providing a larger local message range for future message pull requests, thereby improving the efficiency and responsiveness of the system.

[0076] In this way, the new message interval is determined by obtaining the start and end point identifiers of the server message, and the union of this interval and the existing confidence interval is calculated to update the confidence interval, thereby ensuring that the message synchronization of the instant messaging system is always kept up to date. This method improves the accuracy of message synchronization, expands the range of confirmed synchronized messages in the local database, reduces dependence on the server for future synchronization, and reduces the frequency of network requests, thereby improving the response speed and stability of the system. At the same time, it also optimizes resource utilization, reduces server load, and enhances the system's ability to handle a large number of message synchronization requests, providing users with a smoother and more reliable communication experience.

[0077] In some optional embodiments, the method further comprises:

[0078] In response to a message sending instruction and a message deleting instruction triggered by a user, the current confidence interval is updated according to the message sending instruction and the message deleting instruction to obtain an updated confidence interval.

[0079] Specifically, the "confidence interval" refers to the interval of messages that have been confirmed to be fully synchronized with the server. When a user performs operations such as sending or deleting messages, these instructions will change the state of the local message, so the current confidence interval needs to be updated to reflect these changes. Specifically, if a user sends a new message, the message is added to the local database and the confidence interval is expanded to include the new message; conversely, if a user deletes a message, the message is removed from the local database and the confidence interval is adjusted to exclude the deleted message. This process ensures that the confidence interval always accurately reflects the state of the message in the local database that is synchronized with the server, thereby maintaining the consistency and reliability of message synchronization. In this way, it is possible to respond to user operations in a timely manner, ensuring that the sending and deletion operations of messages can be correctly recorded and synchronized, while also providing users with an accurate and up-to-date view of communication records.

[0080] In this way, by responding to the user's instructions to send and delete messages and updating the current confidence interval accordingly, the accuracy and real-time nature of message synchronization in the instant messaging system are ensured. This mechanism can dynamically reflect the impact of user operations on message history, maintain the consistency of the local database with the user's actual operations, and thus provide users with an accurate and updated message history view. In addition, timely updating of confidence intervals can also help improve the efficiency of subsequent message pulling, thereby reducing unnecessary server requests, optimizing system performance, and improving user experience.

[0081] In order to facilitate the overall understanding of the technical solution of this application, the following examples are given: Figure 6 , Figure 6: is a flowchart of an instant messaging message synchronization method in an embodiment of the present disclosure, which describes the decision-making process of message pulling and synchronization in an instant messaging (IM) system, especially how to optimize the pulling of messages according to the message status of local storage and server. Specifically, pull messages: the process starts with the system trying to pull new messages. There is a corresponding session locally: check whether there is a corresponding session in the local database. If yes, it means that there is already a message record of this session locally, and the system will update the endMsgId (end message identifier) ​​to the lastMsgId (last message identifier) ​​of the session, that is, the ID of the last message. If not, it means that there is no message record of this session locally, and the process continues to the next step. Determine whether the confidence interval contains the interval to be pulled: check whether the current confidence interval (that is, the message interval that has been confirmed to be synchronized locally) contains the message interval requested by the user. If yes, it means that the requested message interval has been stored locally, and these messages will be returned locally. If not, it means that the requested message interval is not completely stored locally, and the process continues to the next step. Determine whether the number of intervals meets the number of pulls: check whether the number of messages in the confidence interval meets the number of pulls requested by the user. If yes, these messages will be returned locally. If no, the process continues to the next step. The start of the interval is 0: Check whether the starting point of the message interval requested to be pulled is 0. If yes, this usually means that the user requests to pull messages from the beginning of the session, and all available messages will be returned locally. If no, the process continues to the next step. Pull messages from the server: If none of the above conditions are met, the missing messages will be pulled from the server. Update the confidence interval: Regardless of whether the message is returned locally or pulled from the server, the confidence interval will be updated to reflect the latest synchronized message status. End: The process ends and the user can view the latest synchronized messages.

[0082] This flowchart shows an intelligent message pulling strategy, which checks the message status of local storage and server and decides whether to return messages directly from the local database or pull new messages from the server, thereby optimizing the efficiency and performance of message synchronization.

[0083] The following describes an apparatus embodiment of the present application, which can be used to execute the instant messaging message synchronization method in the above-mentioned embodiment of the present application. For details not disclosed in the apparatus embodiment of the present application, please refer to the above-mentioned instant messaging message synchronization method embodiment of the present application.

[0084] The present disclosure also provides an instant messaging message synchronization device 700, such as Figure 7 As shown, including:

[0085] A response module 701 is used to obtain a session list corresponding to the user identifier from a server in response to a login instruction triggered by a user;

[0086] A construction module 702 is used to obtain the latest session message corresponding to the session in the session list from the server after the session list is synchronized, and record the start point identifier and the end point identifier of the obtained session message to construct a confidence interval;

[0087] The message pulling module 703 is used to determine whether to pull messages from a local database or server to synchronize messages based on the relationship between the current confidence interval and the message pulling interval carried in the message pulling request if a target session message pulling request triggered by a user is received.

[0088] In some optional embodiments, the message pulling module 703 determines to pull messages from a local database or a server to synchronize messages according to the relationship between the current confidence interval and the message pulling interval carried in the message pulling request, including:

[0089] Obtain the identifier of the message pull start point and the identifier of the message pull end point carried in the message pull request;

[0090] The interval from the message pulling start point to the message pulling end point is determined as the message pulling interval;

[0091] According to the intersection relationship between the current confidence interval and the message pulling interval, it is determined whether to pull the message from the local database or from the server to perform message synchronization.

[0092] In some optional embodiments, the message pulling module 703 determines to pull messages from a local database or from a server according to the intersection relationship between the current confidence interval and the message pulling interval to perform message synchronization, including:

[0093] If the current confidence interval does not intersect with the message pull interval, the message corresponding to the message pull interval is pulled from the server to perform message synchronization;

[0094] The current confidence interval is updated according to the message received from the server to obtain a new confidence interval.

[0095] In some optional embodiments, the message pulling module 703 determines to pull messages from a local database or from a server according to the intersection relationship between the current confidence interval and the message pulling interval to perform message synchronization, including:

[0096] If the pulled message interval is within the current confidence interval, the message corresponding to the pulled message interval is pulled from the local database to synchronize the messages.

[0097] In some optional embodiments, the message pulling module 703 determines to pull messages from a local database or from a server according to the intersection relationship between the current confidence interval and the message pulling interval to perform message synchronization, including:

[0098] If the message pull start point is within the current confidence interval, and the message pull end point is outside the current confidence interval, then pull messages from the message pull start point to the end point of the current confidence interval from the local database, and pull messages from the end point of the current confidence interval to the message pull end point from the server, to obtain messages corresponding to the pulled message interval;

[0099] The message corresponding to the pulled message interval is synchronized, and the current confidence interval is updated according to the message received from the server to obtain a new confidence interval.

[0100] In some optional embodiments, the message pulling module 703 determines to pull messages from a local database or from a server according to the intersection relationship between the current confidence interval and the message pulling interval to perform message synchronization, including:

[0101] If the message pull end point is within the current confidence interval, and the message pull start point is outside the current confidence interval, then pull messages from the starting point of the current confidence interval to the message pull end point from the local database, and pull messages from the message pull start point to the starting point of the current confidence interval from the server, to obtain messages corresponding to the pulled message interval;

[0102] The message corresponding to the pulled message interval is synchronized, and the current confidence interval is updated according to the message received from the server to obtain a new confidence interval.

[0103] In some optional embodiments, the message pulling module 703 updates the current confidence interval according to the message received from the server to obtain a new confidence interval, including:

[0104] Obtain the message start point identifier and the message end point identifier received from the server to obtain a new message interval;

[0105] Calculate the union of the new message interval and the current confidence interval to get the new confidence interval.

[0106] In some optional embodiments, the message pulling module 703 is further configured to respond to a message sending instruction and a message deleting instruction triggered by a user, and then update the current confidence interval according to the message sending instruction and the message deleting instruction to obtain an updated confidence interval.

[0107] In the technical solution disclosed herein, the acquisition, storage and application of user personal information involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0108] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.

[0109] Figure 8 A schematic block diagram of an example electronic device 800 that can be used to implement an embodiment of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present disclosure described and / or required herein.

[0110] like Figure 8 As shown, the electronic device 800 includes a computing unit 801, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 802 or a computer program loaded from a storage unit 808 into a random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the device 800 can also be stored. The computing unit 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0111] A number of components in the device 800 are connected to the I / O interface 805, including: an input unit 806, such as a keyboard, a mouse, etc.; an output unit 807, such as various types of displays, speakers, etc.; a storage unit 808, such as a disk, an optical disk, etc.; and a communication unit 809, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 809 allows the device 800 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0112] The computing unit 801 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 801 performs the various methods and processes described above, such as an instant messaging message synchronization method. For example, in some embodiments, the instant messaging message synchronization method may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 808. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 800 via ROM 802 and / or communication unit 809. When the computer program is loaded into RAM 803 and executed by the computing unit 801, one or more steps of the applet distribution described above may be performed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform the instant messaging message synchronization method in any other appropriate manner (e.g., by means of firmware).

[0113] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0114] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0115] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0116] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0117] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0118] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship with each other. The server may be a cloud server, a server of a distributed system, or a server combined with a blockchain.

[0119] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.

[0120] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A method for synchronizing instant messaging messages, the method comprising: In response to a login instruction triggered by a user, obtaining a session list corresponding to the user identifier from a server; After the conversation list is synchronized, the latest conversation message corresponding to the conversation in the conversation list is obtained from the server, and the starting point identifier and the end point identifier of the obtained conversation message are recorded to construct a confidence interval; If a target session message pull request triggered by a user is received, it is determined to pull messages from the local database or the server to synchronize messages according to the relationship between the current confidence interval and the message pull interval carried in the message pull request.

2. The method according to claim 1, wherein: The determining to pull messages from a local database or the server to synchronize messages according to a relationship between a current confidence interval and a message pull interval carried in the message pull request includes: Obtaining the identifier of the message pull starting point and the identifier of the message pull end point carried in the message pull request; Determine the interval from the message pulling start point to the message pulling end point as the message pulling interval; According to the intersection relationship between the current confidence interval and the message pulling interval, it is determined to pull the message from the local database or from the server to perform message synchronization.

3. The method according to claim 2, wherein: The determining, based on the intersection relationship between the current confidence interval and the message pulling interval, to pull messages from the local database or from the server to perform message synchronization includes: If the current confidence interval does not have an intersection with the message pulling interval, then pulling messages corresponding to the message pulling interval from the server to perform message synchronization; The current confidence interval is updated according to the message received from the server to obtain a new confidence interval.

4. The method according to claim 2, wherein: The determining, based on the intersection relationship between the current confidence interval and the message pulling interval, to pull messages from the local database or from the server to perform message synchronization includes: If the pulled message interval is within the current confidence interval, messages corresponding to the pulled message interval are pulled from the local database to synchronize the messages.

5. The method according to claim 2, wherein: The determining, based on the intersection relationship between the current confidence interval and the message pulling interval, to pull messages from the local database or from the server to perform message synchronization includes: If the message pulling start point is within the current confidence interval, and the message pulling end point is outside the current confidence interval, then pulling messages from the message pulling start point to the end point of the current confidence interval from the local database, and pulling messages from the end point of the current confidence interval to the message pulling end point from the server, so as to obtain messages corresponding to the pulled message interval; The message corresponding to the pulled message interval is synchronized, and the current confidence interval is updated according to the message received from the server to obtain a new confidence interval.

6. The method according to claim 2, wherein: The determining, based on the intersection relationship between the current confidence interval and the message pulling interval, to pull messages from the local database or from the server to perform message synchronization includes: If the message pulling end point is within the current confidence interval, and the message pulling start point is outside the current confidence interval, then pulling messages from the starting point of the current confidence interval to the message pulling end point from the local database, and pulling messages from the message pulling start point to the starting point of the current confidence interval from the server, so as to obtain messages corresponding to the pulled message interval; The message corresponding to the pulled message interval is synchronized, and the current confidence interval is updated according to the message received from the server to obtain a new confidence interval.

7. The method according to claim 3, 5 or 6, wherein: The updating of the current confidence interval according to the message received from the server to obtain a new confidence interval includes: Obtaining a message start point identifier and a message end point identifier received from the server to obtain a new message interval; The union of the new message interval and the current confidence interval is calculated to obtain a new confidence interval.

8. The method according to any one of claims 1 to 6, wherein: The method further comprises: In response to a message sending instruction and a message deleting instruction triggered by a user, the current confidence interval is updated according to the message sending instruction and the message deleting instruction to obtain an updated confidence interval.

9. An instant messaging message synchronization device, comprising: A response module, configured to obtain a session list corresponding to the user identifier from a server in response to a login instruction triggered by a user; A construction module, configured to obtain, after the synchronization of the conversation list, the latest conversation message corresponding to the conversation in the conversation list from the server, and record the start point identifier and the end point identifier of the obtained conversation message to construct a confidence interval; The message pulling module is used to determine whether to pull messages from the local database or the server to synchronize messages based on the relationship between the current confidence interval and the message pulling interval carried in the message pulling request if a target session message pulling request triggered by a user is received.

10. The device according to claim 9, wherein: The message pulling module determines to pull messages from the local database or the server according to the relationship between the current confidence interval and the message pulling interval carried in the message pulling request to synchronize the messages, including: Obtaining the identifier of the message pull starting point and the identifier of the message pull end point carried in the message pull request; Determine the interval from the message pulling start point to the message pulling end point as the message pulling interval; According to the intersection relationship between the current confidence interval and the message pulling interval, it is determined to pull the message from the local database or from the server to perform message synchronization.

11. The device according to claim 10, wherein: The message pulling module determines to pull messages from the local database or from the server according to the intersection relationship between the current confidence interval and the message pulling interval to perform message synchronization, including: If the current confidence interval does not have an intersection with the message pulling interval, then pulling messages corresponding to the message pulling interval from the server to perform message synchronization; The current confidence interval is updated according to the message received from the server to obtain a new confidence interval.

12. The device according to claim 10, wherein: The message pulling module determines to pull messages from the local database or from the server according to the intersection relationship between the current confidence interval and the message pulling interval to perform message synchronization, including: If the pulled message interval is within the current confidence interval, messages corresponding to the pulled message interval are pulled from the local database to synchronize the messages.

13. The device according to claim 10, wherein: The message pulling module determines to pull messages from the local database or from the server according to the intersection relationship between the current confidence interval and the message pulling interval to perform message synchronization, including: If the message pulling start point is within the current confidence interval, and the message pulling end point is outside the current confidence interval, then pulling messages from the message pulling start point to the end point of the current confidence interval from the local database, and pulling messages from the end point of the current confidence interval to the message pulling end point from the server, so as to obtain messages corresponding to the pulled message interval; The message corresponding to the pulled message interval is synchronized, and the current confidence interval is updated according to the message received from the server to obtain a new confidence interval.

14. The device according to claim 10, wherein: The message pulling module determines to pull messages from the local database or from the server according to the intersection relationship between the current confidence interval and the message pulling interval to perform message synchronization, including: If the message pulling end point is within the current confidence interval, and the message pulling start point is outside the current confidence interval, then pulling messages from the starting point of the current confidence interval to the message pulling end point from the local database, and pulling messages from the message pulling start point to the starting point of the current confidence interval from the server, so as to obtain messages corresponding to the pulled message interval; The message corresponding to the pulled message interval is synchronized, and the current confidence interval is updated according to the message received from the server to obtain a new confidence interval.

15. The device according to claim 11, 13 or 14, wherein: The message pulling module updates the current confidence interval according to the message received from the server to obtain a new confidence interval, including: Obtaining a message start point identifier and a message end point identifier received from the server to obtain a new message interval; The union of the new message interval and the current confidence interval is calculated to obtain a new confidence interval.

16. The device according to any one of claims 9 to 14, wherein: The message pulling module is further configured to respond to a message sending instruction and a message deleting instruction triggered by a user, and then update the current confidence interval according to the message sending instruction and the message deleting instruction to obtain an updated confidence interval.

17. An electronic device comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 8.

18. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-8.

19. A computer program product, comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 8.

Images