Session processing method, device and communication system

Abstract

The present disclosure relates to a session processing method, device and communication system, wherein a server receives session setting information of a first user, the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to a first terminal device of the first user within a target time period; a first session message sent by a second user to the first user is received, and if it is determined that the session identifier corresponding to the first session message sent by the second user is consistent with the target session identifier, and the sending time of the first session message belongs to the target time period, the first session message is only sent to the second terminal device of the first user; wherein the second terminal device is the remaining terminal device except the first terminal device among the multiple terminal devices logged in by the first user at the same time. The technical solution provided by the embodiment of the present disclosure can meet the privacy requirements of users for session message push, improve the convenience of users using instant messaging applications, and provide users with a better user experience.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a session processing method, device and communication system. Background Art

[0002] In the related art, instant messaging (IM) products usually support users' accounts to log in to multiple terminal devices with IM applications installed at the same time, such as Android devices, iOS devices or PCs, etc. When a user and other users communicate instantly through an IM application, a session message will be generated. Usually, the server corresponding to the IM application will push the session message of the same user account to multiple terminals, that is, push the session message to all terminal devices that log in to the same user account.

[0003] However, in actual applications, considering the privacy of session messages, users may not want certain session messages to be pushed to all terminal devices that log in to the user account, but hope to push certain session messages only to specific terminal devices through personalized settings. Summary of the invention

[0004] The present disclosure provides a session processing method, device and communication system to at least solve the problem in the related art that when a server pushes a user's session message on multiple terminals, the privacy of the session message cannot be guaranteed. The technical solution of the present disclosure is as follows:

[0005] According to a first aspect of an embodiment of the present disclosure, a session processing method is provided, which is applied to a server and includes:

[0006] receiving session setting information of a first user, where the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to a first terminal device of the first user within a target time period;

[0007] receiving a first conversation message sent by a second user to the first user;

[0008] If it is determined that the session identifier corresponding to the first session message sent by the second user is consistent with the target session identifier, and the sending time of the first session message belongs to the target time period, the first session message is only sent to the second terminal device of the first user; wherein the second terminal device is the remaining terminal device except the first terminal device among the multiple terminal devices simultaneously logged in by the first user.

[0009] Optionally, after receiving the session setting information of the first user, the method further includes:

[0010] receiving a session pull request sent by the first terminal device, wherein the session pull request is used to obtain a session message that has not been obtained by a current pull time;

[0011] If it is determined according to the session setting information that the unobtained session message includes a second session message corresponding to the target session identifier generated within the target time period, and the pulling time belongs to the target time period, the remaining session messages except the second session message in the unobtained session message are sent to the first terminal device, and the second session message is a session message that is not sent to the first terminal device within the target time period.

[0012] Optionally, the determining that the session identifier corresponding to the first session message sent by the second user is consistent with the target session identifier, and the sending time of the first session message is after the target time period, the method further includes:

[0013] In response to an end of the target time period, determining that there is the first session message that has not been sent to the first terminal device within the target time period;

[0014] Sending a prompt message to the first terminal device;

[0015] Receiving a session pull request sent by the first terminal device based on the prompt message;

[0016] According to the session pull request, the first session message that has not been sent to the first terminal device is sent to the first terminal device.

[0017] Optionally, after receiving the session setting information of the first user, the method further includes:

[0018] Generate a scheduled task corresponding to the session setting information, wherein the scheduled task is triggered when the target time period ends;

[0019] In response to the end of the target time period, determining that there is the first session message that has not been sent to the first terminal device within the target time period includes:

[0020] The scheduled task is called to determine whether there is the first session message that has not been sent to the first terminal device within the target time period.

[0021] According to a second aspect of an embodiment of the present disclosure, a session processing method is provided, which is applied to a first terminal device and a second terminal device where a first user logs in simultaneously, and includes:

[0022] The first terminal device or the second terminal device sends the session setting information of the first user to the server, where the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to the first terminal device within a target time period;

[0023] The second terminal device receives the first conversation message sent by the server, wherein, when the server receives the first conversation message sent by the second user to the first user, if it is determined that the session identifier corresponding to the first conversation message is consistent with the target conversation identifier, and the sending time of the first conversation message belongs to the target time period, the first conversation message is only sent to the second terminal device.

[0024] Optionally, after the first terminal device or the second terminal device sends the session setting information of the first user to the server, the method further includes:

[0025] The first terminal device sends a session pull request to the server, where the session pull request is used to obtain session messages that have not been obtained by the current pull time;

[0026] The first terminal device receives the remaining session messages except the second session message in the unobtained session messages sent by the server, wherein, when the server receives the session pull request, if it is determined according to the session setting information that the unobtained session messages include the second session message corresponding to the target session identifier generated within the target time period, and the pull time belongs to the target time period, then the remaining session messages except the second session message in the unobtained session messages are sent to the first terminal device, and the second session message is a session message that has not been sent to the first terminal device within the target time period.

[0027] Optionally, the determining that the session identifier corresponding to the first session message sent by the second user is consistent with the target session identifier, and the sending time of the first session message is after the target time period, the method further includes:

[0028] The first terminal device receives the prompt information sent by the server, wherein the prompt information is sent in response to the end of the target time period when it is determined that there is the first conversation message that has not been sent to the first terminal device within the target time period;

[0029] The first terminal device sends a session pull request to the server based on the prompt message;

[0030] The first terminal device receives the first session message sent by the server and not sent to the first terminal device within the target time period.

[0031] According to a third aspect of an embodiment of the present disclosure, a session processing device is provided, which is applied to a server and includes:

[0032] a receiving unit, configured to receive session setting information of a first user, and receive a first session message sent by a second user to the first user, wherein the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to a first terminal device of the first user within a target time period;

[0033] The processing unit is configured to execute, if it is determined that the session identifier corresponding to the first session message sent by the second user is consistent with the target session identifier, and the sending time of the first session message belongs to the target time period, then only send the first session message to the second terminal device of the first user; wherein the second terminal device is the remaining terminal device except the first terminal device among the multiple terminal devices logged in by the first user at the same time.

[0034] Optionally, the receiving unit is further configured to receive a session pull request sent by the first terminal device, where the session pull request is used to obtain a session message that has not been obtained by the current pull time;

[0035] The processing unit is further configured to execute, if it is determined according to the session setting information that the unobtained session message includes a second session message corresponding to the target session identifier generated within the target time period, and the pulling time belongs to the target time period, then send the remaining session messages in the unobtained session messages except the second session message to the first terminal device, where the second session message is a session message that is not sent to the first terminal device within the target time period.

[0036] Optionally, the processing unit is further configured to execute, in response to the end of the target time period, determining that there is the first session message that has not been sent to the first terminal device within the target time period; sending a prompt message to the first terminal device; receiving a session pull request sent by the first terminal device based on the prompt message; and sending the first session message that has not been sent to the first terminal device to the first terminal device according to the session pull request.

[0037] Optionally, the processing unit is further configured to execute a timed task corresponding to the session setting information, wherein the timed task is triggered at the end of the target time period; and call the timed task to determine whether there is the first session message that has not been sent to the first terminal device within the target time period.

[0038] According to a fourth aspect of an embodiment of the present disclosure, a session processing device is provided, which is applied to a first terminal device and a second terminal device where a first user logs in simultaneously, including:

[0039] A sending unit, configured to execute the first terminal device or the second terminal device to send the session setting information of the first user to the server, wherein the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to the first terminal device within a target time period;

[0040] The receiving unit is configured to execute the second terminal device to receive the first conversation message sent by the server, wherein, when the server receives the first conversation message sent by the second user to the first user, if it is determined that the session identifier corresponding to the first conversation message is consistent with the target conversation identifier, and the sending time of the first conversation message belongs to the target time period, the first conversation message is only sent to the second terminal device.

[0041] Optionally, the sending unit is further configured to execute the first terminal device to send a session pull request to the server, where the session pull request is used to obtain a session message that has not been obtained by the current pull time;

[0042] The receiving unit is further configured to execute the first terminal device to receive the remaining session messages except the second session message in the unobtained session messages sent by the server, wherein, when the server receives the session pull request, if it is determined according to the session setting information that the unobtained session messages include the second session message corresponding to the target session identifier generated within the target time period, and the pull time belongs to the target time period, then the remaining session messages except the second session message in the unobtained session messages are sent to the first terminal device, and the second session message is a session message that is not sent to the first terminal device within the target time period.

[0043] Optionally, the receiving unit is further configured to execute the first terminal device to receive a prompt message sent by the server, wherein the prompt message is sent in response to the end of the target time period and it is determined that there is the first session message that has not been sent to the first terminal device within the target time period; the first terminal device receives the first session message sent by the server that has not been sent to the first terminal device within the target time period.

[0044] The sending unit is further configured to execute the first terminal device to send a session pull request to the server based on the prompt message.

[0045] According to a fifth aspect of an embodiment of the present disclosure, a communication system is provided, including:

[0046] A server, a first terminal device and a second terminal device of a first user;

[0047] The server is configured to receive session setting information sent by a first user through the first terminal device or the second terminal device, and receive a session message sent by a second user to the first user, wherein the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to the first terminal device within a target time period; and, if it is determined that the session identifier corresponding to the session message sent by the second user is consistent with the target session identifier, and the sending time of the session message belongs to the target time period, then only send the session message to the second terminal device, wherein the second terminal device is a remaining terminal device other than the first terminal device among multiple terminal devices simultaneously logged in by the first user;

[0048] The second terminal device is configured to receive the session message sent by the server.

[0049] Optionally, the first terminal device is further configured to execute sending a session pull request, where the session pull request is used to obtain a session message that has not been obtained by the current pull time;

[0050] The server is further configured to execute receiving a session pull request sent by the first terminal device; if it is determined according to the session setting information that the unobtained session message includes a second session message corresponding to the target session identifier generated within the target time period, and the pull time belongs to the target time period, then sending the remaining session messages except the second session message in the unobtained session message to the first terminal device, where the second session message is a session message that is not sent to the first terminal device within the target time period;

[0051] The first terminal device is further configured to receive remaining session messages except the second session message among the unobtained session messages sent by the server.

[0052] Optionally, the server is further configured to execute, in response to the end of the target time period, determining that there is the first session message that has not been sent to the first terminal device within the target time period; sending a prompt message to the first terminal device; receiving a session pull request sent by the first terminal device based on the prompt message; and sending the first session message that has not been sent to the first terminal device to the first terminal device according to the session pull request;

[0053] The first terminal device is further configured to receive prompt information sent by the server; send a session pull request to the server based on the prompt message; and receive the first session message sent by the server that has not been sent to the first terminal device within the target time period.

[0054] Optionally, the server is further configured to execute a scheduled task corresponding to the session setting information, wherein the scheduled task is triggered at the end of the target time period; and call the scheduled task to determine whether there is the first session message that has not been sent to the first terminal device within the target time period.

[0055] According to a sixth aspect of an embodiment of the present disclosure, there is provided an electronic device, including:

[0056] processor;

[0057] a memory for storing instructions executable by the processor;

[0058] The processor is configured to execute the instructions to implement any one of the session processing methods described above.

[0059] According to a seventh aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of a server, the server is enabled to execute any one of the session processing methods described above.

[0060] According to an eighth aspect of an embodiment of the present disclosure, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the computer program implements any one of the aforementioned session processing methods.

[0061] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:

[0062] In an embodiment of the present disclosure, a server receives session setting information of a first user, wherein the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to a first terminal device of the first user within a target time period; a first session message sent by a second user to the first user is received, and if it is determined that the session identifier corresponding to the first session message sent by the second user is consistent with the target session identifier, and the sending time of the first session message belongs to the target time period, the first session message is only sent to the second terminal device of the first user; wherein the second terminal device is the remaining terminal device except the first terminal device among the multiple terminal devices logged in by the first user at the same time.

[0063] By adopting the technical solution provided by the embodiment of the present disclosure, the first user can set the session message push mode of the instant messaging application according to the privacy degree of different session messages, and generate session setting information to send to the server. After the server receives the session setting information, when the second user sends the first session message to the first user, the server selectively sends the first session message to the second terminal device that meets the session setting conditions of the first user, rather than to all terminal devices of the first user, based on the session setting information of the first user. In this way, the privacy requirements of the user for the push of session messages can be met, the convenience of the user in using the instant messaging application is improved, and a better user experience is provided for the user.

[0064] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0066] Figure 1 It is a schematic diagram of a conversation scenario according to an exemplary embodiment.

[0067] Figure 2 The present invention is an interactive flow chart of a session processing method according to an exemplary embodiment.

[0068] Figure 3 The present invention is an interactive flow chart of a session processing method according to another exemplary embodiment.

[0069] Figure 4 The present invention is an interactive flow chart of a session processing method according to another exemplary embodiment.

[0070] Figure 5 The present invention is a block diagram of a session processing device according to an exemplary embodiment.

[0071] Figure 6 The block diagram of another session processing device is shown according to an exemplary embodiment.

[0072] Figure 7 It is a block diagram of a communication system according to an exemplary embodiment.

[0073] Figure 8 The present invention is a block diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0074] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0075] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0076] Below, some terms in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

[0077] The server serves the terminal, and its services include providing resources to the terminal and saving terminal data. The server corresponds to the application installed on the terminal and runs in conjunction with the application on the terminal. The server can be a physical server or a virtual server (virtual machine) in the cloud.

[0078] Terminal devices refer to electronic devices that have software applications (Application, APP for short) or clients installed, such as PCs, tablets, smart phones, etc. It has a visual display interface, can interact with users, and corresponds to the server to provide local services to customers. For software applications, except for some applications that only run locally, they are generally installed on ordinary client terminals and need to cooperate with the server to run. After the development of the Internet, more commonly used applications include IM applications. For this type of application, there needs to be corresponding servers and service programs in the network to provide corresponding services, such as database services, configuration parameter services, etc. In this way, specific communication connections need to be established between the client terminal and the server to ensure the normal operation of the application.

[0079] In the related art, IM products usually support the same user account to log in to multiple terminal devices with IM applications installed at the same time, such as Android devices, iOS devices or PCs, etc. When a user and other users communicate instantly through an IM application, a session message will be generated. Usually, the server corresponding to the IM application will push the session message to multiple terminals, that is, push the session message to all terminal devices that have logged in the user account.

[0080] However, in actual applications, taking PC as an example, because the PC itself has a large screen and is mostly used in office scenarios, the privacy is poor. When a user is communicating with other users in real time, the session messages pushed by the server to the PC may contain some highly private session messages. After these session messages are pushed to the PC, there is a risk of being seen by others. Considering the privacy of the session messages, the user does not want these private session messages to be pushed to the PC.

[0081] To this end, the embodiment of the present disclosure provides a session processing method. Among them, the user can set the session message push scheme of the instant messaging application according to the privacy degree of different session messages, and generate session setting information to send to the server. After receiving the session setting information, when the server sends the session message sent to the user by other users, it will send the session message to the terminal device that meets the user's session setting information conditions according to the user's session setting information, and will not push the session message to the terminal device to which the user does not want to be pushed. Therefore, the user's privacy requirements for session message push can be met, the convenience of the user using the instant messaging application is improved, and a better user experience is provided for the user.

[0082] Figure 1 is a schematic diagram showing a conversation scenario according to an exemplary embodiment. Figure 1 In the illustrated conversation scenario, user A and user B conduct instant communication through a terminal device installed with an IM application, that is, when conducting a conversation, the transmission process for each conversation message generated in the conversation is: the message sender sends the conversation message, the server receives the conversation message, and pushes the conversation message to the message receiver based on the data carried in the conversation message, such as the conversation identifier.

[0083] For user A, the above-mentioned conversation may refer to a one-to-one instant communication between user A and a contact, ie, a private chat conversation, or may refer to a one-to-many instant communication between user A and multiple group members in a group, ie, a group chat conversation.

[0084] exist Figure 1 In the scenario shown in which user A and user B are performing instant messaging, user B generally refers to any user who can perform instant messaging with user A, including: a contact who is performing a private chat session with user A, and any one of multiple group members who are participating in a group chat session in a group of user A. User B does not refer to a specific person.

[0085] It is easy to understand that each private chat session or group chat session has its specific session identifier, and the session messages generated during the session will carry its corresponding session identifier so that the server can send it.

[0086] In actual application scenarios, when user A and user B have a private chat or group chat, user A's account may be logged in on multiple terminal devices at the same time, for example Figure 1 In the Android device, iOS device and PC shown in the figure, considering the privacy of the session messages, it is assumed that user A does not want certain sessions to be pushed to certain terminal devices. In view of this requirement, in the technical solution provided by the embodiment of the present disclosure, user A can configure the session setting information on any logged-in terminal device through the configuration interface provided by the IM application. In order to improve the convenience of user use, the user can also set the time interval for prohibiting the push of session messages to certain terminal devices on the configuration interface.

[0087] For example, suppose user A does not want private chat session 1 with contact Zhang San (user B) and group chat session 2 corresponding to group i (a group shared by user A and user B) to be pushed to the PC between 9:00 and 17:00. When configuring the session setting information, the user can select the private chat session 1 and group chat session 2 that do not want to be pushed, as well as the terminal device PC that does not want to be pushed, through the configuration interface of the Android device (which can also be an iOS device or PC), and set the time interval that is not pushed to 9:00 to 17:00. When selecting the terminal device that does not want to be pushed, the terminal device can obtain the terminal device that user A has logged into the current account from the server, and generate a terminal device list for user A to select.

[0088] In the disclosed embodiment, when configuring the session setting information, there is no limitation on the order of selecting the sessions that do not want to be pushed, selecting the terminal devices that do not want to be pushed, and setting the time interval for prohibiting push. In addition, when configuring the session setting information, user A can configure the session setting information for multiple sessions at the same time according to his own needs, or can configure the session setting information for each session one by one to meet the session push requirements in a variety of different scenarios. In addition, for some commonly used scenarios, such as not pushing selected private chat sessions to the PC during working hours, a template can be pre-generated and displayed on the configuration interface. When configuring the session setting information, user A can directly use the pre-generated template and select the private chat session that is not to be pushed, and the session setting information configuration can be completed with one click.

[0089] After user A completes the configuration of the session setting information, in response to user A's confirmation operation on the configuration interface, the Android device sends user A's session setting information to the server, the server receives user A's session setting information, and establishes a corresponding relationship between user A's user ID and user A's session setting information. When the server receives a session message sent by other users to user A, it pushes the session message to user A's terminal device according to user A's session setting information. The process of configuring user B's session setting information is similar to that of user A, and will not be repeated here.

[0090] based on Figure 1 The session scenario and the assumptions in the above embodiments are illustrated, and the session processing method provided in the embodiments of the present disclosure is specifically described below.

[0091] Figure 2 is an interactive flow chart of a session processing method according to an exemplary embodiment. Figure 2 As shown, the session processing method includes the following steps:

[0092] In step S21, the server receives session setting information sent by the first user through the first terminal device or the second terminal device, where the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to the first terminal device of the first user within a target time period.

[0093] In step S22, the server receives a first conversation message sent by the second user to the first user.

[0094] In step S23, if the server determines that the session identifier corresponding to the first session message sent by the second user is consistent with the target session identifier, and the sending time of the first session message belongs to the target time period, the first session message is only sent to the second terminal device of the first user; wherein the second terminal device is the remaining terminal device except the first terminal device among the multiple terminal devices simultaneously logged in by the first user.

[0095] In the embodiment of the present disclosure, the first user corresponds to Figure 1 In the example, user A corresponds to user B, the first terminal device corresponds to user A's PC, and the second terminal device corresponds to user A's Android device and iOS device. Figure 2 In the session processing method shown, user A replaces the first user and user B replaces the second user in the following description.

[0096] exist Figure 2 In the illustrated session processing method, the process in step S21 where the server receives the session setting information sent by user A to the server through any one of the multiple terminal devices logged in can be referred to the above embodiment and will not be described in detail here.

[0097] Based on the scenario assumed in the aforementioned embodiment (user A does not want the private chat session 1 with contact Zhang San and the group chat session 2 corresponding to group i to be pushed to the PC between 9:00 and 17:00), corresponding to step S21, the target time period is 9:00 to 17:00, the target session identifier is the session identifier x of the private chat session 1 and the session identifier y of the group chat session 2, and the first terminal device is the PC of user A.

[0098] In the scenario where user B sends a conversation message to user A, the first conversation message refers to any conversation message sent by user B to user A. It should be noted that user B sending a conversation message to user A may refer to user B sending a private chat conversation message to user A, or may refer to a group chat conversation message sent by user B in a group shared by user A.

[0099] Assume that user B sends a first conversation message to user A through the server at 10:00, for example: "Let's go to XX Park together this afternoon." After receiving the first conversation message sent by user B, the server executes the judgment of step S23.

[0100] Corresponding to the above-mentioned hypothetical scenario, if user B is Zhang San, and the first conversation message sent by user B to user A is a private chat conversation message, it is easy to understand that the first conversation message sent by user B will carry a conversation identifier x. After receiving the first conversation message, the server determines that the conversation identifier x carried by the first conversation message matches the target conversation identifier, that is, the target conversation identifier includes the conversation identifier x carried by the first conversation message, and the sending time (10:00) of the first conversation message belongs to the target time period. Then, the server only sends the first conversation message to the second terminal device (Android device and iOS device) of user A, but does not send the first conversation message to the first terminal device (PC). For user A, only Android devices and iOS devices can receive the first conversation message, and accordingly, user A can only view the first conversation message on Android devices and iOS devices.

[0101] If user B is any group member participating in the group chat session in group i, it is easy to understand that the first session message sent by user B in group i will carry the session identifier y. After receiving the first session message, the server determines that the session identifier y carried in the first session message matches the target session identifier, that is, the target session identifier includes the session identifier y carried in the first session message, and the sending time (10:00) of the first session message belongs to the target time period. Then the server only sends the first session message to the second terminal device (Android device and iOS device) of user A, but does not send the first session message to the first terminal device (PC). For user A, only Android devices and iOS devices can receive the first session message, and accordingly user A can only view the first session message on Android devices and iOS devices.

[0102] If user B is neither Zhang San nor any group member participating in the group chat session in group i, it is easy to understand that the session identifier carried in the first session message sent by user B is neither the session identifier x nor the session identifier y. After receiving the first session message, the server determines that the session identifier carried in the first session message does not match the target session identifier, and the server sends the first session message to the Android device, iOS device and PC of user A. For user A, the Android device, iOS device and PC can all receive the first session message, and the user can view the first session message on the Android device, iOS device and PC.

[0103] During the specific implementation process, the server may send the first conversation message to the terminal device of user A in the form of a push notification.

[0104] The scenario described in the above embodiment is that after receiving the session message sent by user B to user A, the server actively pushes the session message to the terminal device of user A; for user A, his terminal device passively receives the session message. In the specific implementation process, in fact, user A can also actively send a session pull request to the server through the terminal device, requesting to obtain the session message that the current terminal device of user A has not yet obtained, and update the session messages of multiple sessions included in the session list. For example, user A can trigger the sending of a session pull request to the server by logging into an account on a terminal device, or user A can trigger the sending of a session pull request to the server by executing the session refresh operation corresponding to the IM application on the terminal device (clicking the refresh button, the message collection button, pulling down the session list, etc.).

[0105] The following describes the session processing method when the user actively pulls the session.

[0106] Figure 3is an interactive flow chart of a session processing method according to another exemplary embodiment. Figure 3 As shown, the session processing method includes the following steps:

[0107] In step S31, the server receives session setting information sent by the first user through the first terminal device or the second terminal device, where the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to the first terminal device of the first user within a target time period.

[0108] In step S32, the server receives a session pull request sent by the first terminal device, where the session pull request is used to obtain session messages that have not been obtained by the current pull time.

[0109] In step S33, if the server determines, based on the session setting information of the first user, that the session messages that have not been acquired include a second session message corresponding to the target session identifier generated within the target time period, and the pulling time belongs to the target time period, then the server sends the remaining session messages except the second session message in the session messages that have not been acquired to the first terminal device, where the second session message is a session message that has not been sent to the first terminal device within the target time period.

[0110] In the embodiment of the present disclosure, the first user corresponds to Figure 1 In the example, user A corresponds to user B, the first terminal device corresponds to user A's PC, and the second terminal device corresponds to user A's Android device and iOS device. Figure 3 In the session processing method shown, user A replaces the first user and user B replaces the second user in the following description.

[0111] exist Figure 3 In the illustrated session processing method, the process in step S31 where the server receives the session setting information sent by user A to the server through any one of the multiple terminal devices logged in can be referred to the above embodiment and will not be described in detail here.

[0112] Based on the assumed situation in the above embodiment (user A does not want the private chat session 1 with contact Zhang San and the group chat session 2 corresponding to group i to be pushed to the PC between 9:00 and 17:00), Figure 3 In the illustrated session processing method, the first user is user A, corresponding to step S31, the target time period is 9:00 to 17:00, the target session identifier is the session identifier x of the private chat session 1 and the session identifier y of the group chat session 2, and the first terminal device is the PC of user A.

[0113] It should be noted that, the session messages that have not been obtained by user A's PC as of the current time include session messages that the server has sent to user A's PC but have not received because the PC is not turned on or for other reasons, as well as session messages that the server determines are not to be sent to the PC for the time being because the sending time belongs to the target time period and the session identifier corresponds to the target session identifier, i.e., the second session messages.

[0114] It is easy to understand that after the server sends the session message to the terminal device, if the terminal device obtains the session message, the terminal device will send a feedback instruction containing the obtained session message to the server, so that the server can mark the session message, for example, mark it as: session message i has been obtained by the PC. Correspondingly, if the server does not receive the feedback instruction sent by the terminal device after sending the session message to the terminal device, the original mark of the session message remains unchanged, for example: session message j has not been obtained by the PC. Based on this, when the server receives the session pull request sent by the PC, it can determine the session messages that the PC has not obtained as of the current time.

[0115] Assume that user A sends a session pull request to the server through the PC at 10:00. The session messages that user A's PC has not obtained in the server as of the current pull time 10:00 include: private chat session messages sent by Zhang San, group session messages sent by group members participating in the session in group i, and private chat session messages sent by Li Si. It is easy to understand that there may be more than one private chat or group chat session message mentioned here, and all carry their corresponding session identifiers. For the sake of distinction, assume that the private chat session between Li Si and user A is private chat session 3, and the session identifier of private chat session 3 is session identifier z.

[0116] In step S32, after receiving the session pull request sent by user A through the PC, the server determines that the session messages that user A's PC has not obtained as of 10:00 include: the private chat session message sent by Zhang San, the group session message sent by group members participating in the session in group i, and the private chat session message sent by Li Si. Then, step S33 is executed.

[0117] In step S33, for the private chat session message sent by Zhang San and the group session message sent by the group members participating in the session in group i, the session identifiers they carry correspond to the session identifier x and the session identifier y in the target session identifier respectively. If their generation time is also within the target time period, the server confirms it as the second session message.

[0118] From the above assumptions, it can be seen that the time when user A pulls the session, 10:00, is within the target time period of 9:00 to 17:00. Since user A does not want the PC to receive the private chat session message sent by Zhang San and the group session message sent by the group members participating in the session in group i during the target time period, based on this, the server sends the remaining session messages, i.e., the private chat session message sent by Li Si, among the session messages not obtained by user A's PC, to user A's PC according to user A's session setting information. Then, user A's PC receives the private chat session message sent by Li Si forwarded by the server.

[0119] In a specific implementation process, the server may also directly determine the session message carrying the target session identifier among the session messages not obtained by the PC of user A as the second session message, without determining whether the generation time of the session message is within the target time period.

[0120] Through the above-mentioned session processing method, when the server receives a session pull request sent by the PC of user A, it can screen the session messages and send the appropriate session messages to the PC of user A, thereby avoiding sending the session messages that the user does not want to be pushed to the PC in response to the user's session pull request during inappropriate time periods. For example, it can be avoided that during the period from 9:00 to 17:00, in response to the session pull request sent by user A through the PC, the server pushes the private chat session messages sent by Zhang San and the group session messages sent by the group members participating in the session in group i to user A, thereby allowing user A to use the IM application with peace of mind without having to worry about unnecessary interruptions and leakage of session information of certain sessions, thereby facilitating the protection of user privacy and improving the user's usage experience.

[0121] It is easy to understand that in order to facilitate the user's use of IM applications on different session terminals and ensure the integrity of user session information, in response to the end of the target time period in the session setting information, the server can send session messages that have not been sent to the first terminal device within the target time period to the first terminal device.

[0122] Figure 4 is an interactive flow chart of a session processing method according to another exemplary embodiment. Figure 4 As shown, the session processing method is used in a server and includes the following steps:

[0123] In step S41, the server receives session setting information sent by the first user through the first terminal device or the second terminal device, where the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to the first terminal device of the first user within a target time period.

[0124] In step S42, the server receives a first conversation message sent by the second user to the first user.

[0125] In step S43, if the server determines that the session identifier corresponding to the first session message sent by the second user is consistent with the target session identifier, and the sending time of the first session message belongs to the target time period, the first session message is only sent to the second terminal device of the first user; wherein the second terminal device is the remaining terminal device except the first terminal device among the multiple terminal devices simultaneously logged in by the first user.

[0126] In step S44, in response to the end of the target time period, the server determines that there is a first session message that has not been sent to the first terminal device within the target time period.

[0127] In step S45, the server sends a prompt message to the first terminal device.

[0128] In step S46, the server receives a session pull request sent by the first terminal device based on the prompt message.

[0129] In step S47, the server sends the first session message that has not been sent to the first terminal device to the first terminal device according to the session pull request.

[0130] In the embodiment of the present disclosure, the first user corresponds to Figure 1 In the example, user A corresponds to user B, the first terminal device corresponds to user A's PC, and the second terminal device corresponds to user A's Android device and iOS device. Figure 4 In the session processing method shown, user A replaces the first user and user B replaces the second user in the following description.

[0131] exist Figure 4 In the illustrated session processing method, the process in step S41 where the server receives the session setting information sent by user A to the server through any one of the multiple terminal devices logged in can be referred to the above embodiment and will not be described in detail here.

[0132] Based on the assumed situation in the above embodiment (user A does not want the private chat session 1 with contact Zhang San and the group chat session 2 corresponding to group i to be pushed to the PC between 9:00 and 17:00), Figure 3 In the illustrated session processing method, the first user is user A, corresponding to step S31, the target time period is 9:00 to 17:00, the target session identifier is the session identifier x of the private chat session 1 and the session identifier y of the group chat session 2, and the first terminal device is the PC of user A.

[0133] Assume that between 9:00-17:00, the first session message received by the server includes a private chat session message sent by Zhang San and a group session message sent by group members participating in the session in group i. Based on user A's session setting information, after the server receives the private chat session message sent by Zhang San and the group session message sent by group members participating in the session in group i between 9:00-17:00, since the session identifiers x and y they carry respectively match the target session identifier, the server will only send them to user A's second terminal device (Android device and iOS device), and will not send them to the first terminal device (PC).

[0134] In order to ensure the continuity of session messages when the user uses the PC for instant messaging, after the target time period ends, the session messages that have not been sent to the PC of user A based on the session setting information of user A will be sent to the PC of user A.

[0135] For the above-mentioned hypothetical situation, in response to the end of the target time period, the server determines that there are private chat session messages sent by Zhang San and group session messages sent by group members participating in the session in group i that have not been sent to the PC within the target time period; then a prompt message is sent to the PC of user A, such as a push notification is sent to the PC of user A, reminding user A that there are session messages that have not been obtained on the PC within the target time period. User A sends a session pull request to the server based on the prompt message on the PC, such as clicking on the push notification to trigger the sending of the session pull request to the server. After receiving the session pull request, the server sends the private chat session messages sent by Zhang San and the group session messages sent by group members participating in the session in group i that have not been sent to the PC within the target time period from 9:00 to 17:00 to the PC according to the session pull request. Then, the PC of user A receives the private chat session messages sent by Zhang San and the group session messages sent by group members participating in the session in group i forwarded by the server, and updates the group chat session 2 corresponding to Zhang San's private chat session 1 and group i.

[0136] Optionally, in a specific implementation, after the server receives the session setting information sent by user A, the server may generate a scheduled task corresponding to the session setting information of user A, and the scheduled task is triggered when the target time period ends. Specifically, in response to the end of the target time period, the server calls the scheduled task and determines that there is a first session message that has not been sent to the PC within the target time period.

[0137] Figure 5 1 is a block diagram of a session processing device according to an exemplary embodiment, which is applied to a server. Figure 5 The block diagram of the session processing device 500 includes a receiving unit 501 and a processing unit 502.

[0138] The receiving unit 501 is configured to receive session setting information of a first user and receive a first session message sent by a second user to the first user, wherein the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to a first terminal device of the first user within a target time period.

[0139] The processing unit 502 is configured to execute, if it is determined that the session identifier corresponding to the first session message sent by the second user is consistent with the target session identifier, and the sending time of the first session message belongs to the target time period, then only send the first session message to the second terminal device of the first user; wherein the second terminal device is the remaining terminal device except the first terminal device among the multiple terminal devices simultaneously logged in by the first user.

[0140] Optionally, the receiving unit 501 is further configured to execute receiving a session pull request sent by the first terminal device, where the session pull request is used to obtain a session message that has not been obtained by a current pull time.

[0141] The processing unit 502 is further configured to execute, if it is determined according to the session setting information that the unobtained session message includes a second session message corresponding to the target session identifier generated within the target time period, and the pulling time belongs to the target time period, then send the remaining session messages in the unobtained session messages except the second session message to the first terminal device, where the second session message is a session message that is not sent to the first terminal device within the target time period.

[0142] Optionally, the processing unit 502 is further configured to execute, in response to the end of the target time period, determining that there is the first session message that has not been sent to the first terminal device within the target time period; sending a prompt message to the first terminal device; receiving a session pull request sent by the first terminal device based on the prompt message; and sending the first session message that has not been sent to the first terminal device to the first terminal device according to the session pull request.

[0143] Optionally, the processing unit 502 is further configured to execute and generate a timed task corresponding to the session setting information, wherein the timed task is triggered at the end of the target time period; and call the timed task to determine whether there is the first session message that has not been sent to the first terminal device within the target time period.

[0144] Regarding the device in the above embodiment, the specific manner in which each unit performs the operation has been described in detail in the embodiment of the method, and will not be elaborated here.

[0145] Figure 6 is a block diagram of another session processing device according to an exemplary embodiment, which is applied to a first terminal device and a second terminal device where a first user logs in at the same time. Figure 6 The block diagram of the session processing device 600 includes a sending unit 601 and a receiving unit 602.

[0146] The sending unit 601 is configured to execute the first terminal device or the second terminal device to send the session setting information of the first user to the server, where the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to the first terminal device within a target time period.

[0147] The receiving unit 602 is configured to execute the second terminal device to receive the first conversation message sent by the server, wherein, when the server receives the first conversation message sent by the second user to the first user, if it is determined that the session identifier corresponding to the first conversation message is consistent with the target conversation identifier, and the sending time of the first conversation message belongs to the target time period, the first conversation message is only sent to the second terminal device.

[0148] Optionally, the sending unit 601 is further configured to execute the first terminal device to send a session pull request to the server, where the session pull request is used to obtain a session message that has not been obtained by a current pull time.

[0149] The receiving unit 602 is further configured to execute the first terminal device to receive the remaining session messages except the second session message in the unacquired session messages sent by the server, wherein, when the server receives the session pull request, if it is determined according to the session setting information that the unacquired session messages include the second session message corresponding to the target session identifier generated within the target time period, and the pull time belongs to the target time period, then the remaining session messages except the second session message in the unacquired session messages are sent to the first terminal device, and the second session message is a session message that has not been sent to the first terminal device within the target time period.

[0150] Optionally, the receiving unit 602 is further configured to execute the first terminal device to receive a prompt message sent by the server, wherein the prompt message is sent in response to the end of the target time period and it is determined that there is the first session message that has not been sent to the first terminal device within the target time period; the first terminal device receives the first session message sent by the server that has not been sent to the first terminal device within the target time period.

[0151] The sending unit 601 is further configured to execute the first terminal device to send a session pull request to the server based on the prompt message.

[0152] Figure 7 is a block diagram of a communication system according to an exemplary embodiment. Figure 7 The communication system block diagram 700 includes a server 701, a first terminal device 702 and a second terminal device 703 of a first user.

[0153] The server 701 is configured to receive session setting information sent by the first user through the first terminal device 702 or the second terminal device 703, and receive a session message sent by the second user to the first user, wherein the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to the first terminal device 702 within a target time period; and, if it is determined that the session identifier corresponding to the session message sent by the second user is consistent with the target session identifier, and the sending time of the session message belongs to the target time period, then only send the session message to the second terminal device 703, wherein the second terminal device 703 is the remaining terminal device except the first terminal device 702 among the multiple terminal devices simultaneously logged in by the first user.

[0154] The second terminal device 703 is configured to receive the session message sent by the server 701 .

[0155] Optionally, the first terminal device 702 is further configured to execute sending a session pull request, where the session pull request is used to obtain a session message that has not been obtained by the current pull time.

[0156] The server 701 is further configured to execute and receive a session pull request sent by the first terminal device 702; if it is determined according to the session setting information that the unobtained session message includes a second session message corresponding to the target session identifier generated within the target time period, and the pull time belongs to the target time period, then the remaining session messages in the unobtained session message except the second session message are sent to the first terminal device 702, and the second session message is a session message that is not sent to the first terminal device 702 within the target time period.

[0157] The first terminal device 702 is further configured to receive the remaining session messages except the second session message in the unobtained session messages sent by the server 701.

[0158] Optionally, the server 701 is further configured to execute, in response to the end of the target time period, determining that there is the first session message that has not been sent to the first terminal device 702 within the target time period; sending a prompt message to the first terminal device 702; receiving a session pull request sent by the first terminal device 702 based on the prompt message; and sending the first session message that has not been sent to the first terminal device 702 to the first terminal device 702 according to the session pull request.

[0159] The first terminal device 702 is further configured to receive a prompt message sent by the server 701; send a session pull request to the server 701 based on the prompt message; and receive the first session message sent by the server 701 that has not been sent to the first terminal device 702 within the target time period.

[0160] Optionally, the server 701 is further configured to execute a scheduled task corresponding to the session setting information, wherein the scheduled task is triggered at the end of the target time period; and call the scheduled task to determine whether there is the first session message that has not been sent to the first terminal device 702 within the target time period.

[0161] Figure 8 is a block diagram of an electronic device according to an exemplary embodiment. Figure 8 , the electronic device block diagram 800 includes a processor 801 and a memory 802 for storing processor executable instructions.

[0162] The processor 801 is configured to execute the instructions to implement any one of the aforementioned session processing methods.

[0163] In an exemplary embodiment, a computer-readable storage medium is also provided, and when the instructions in the computer-readable storage medium are executed by a processor of a server, the server is enabled to perform any of the aforementioned session processing methods. Optionally, the 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, etc.

[0164] In an exemplary embodiment, a computer program product is also provided, including a computer program, wherein when the computer program is executed by a processor, any one of the aforementioned session processing methods is implemented.

[0165] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0166] It should be understood that the present disclosure is not limited to the exact structures that have been 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 present disclosure is limited only by the appended claims.

Claims

1. A session processing method, characterized in that: Applicable to servers, including: receiving session setting information of a first user, where the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to a first terminal device of the first user within a target time period; receiving a first conversation message sent by a second user to the first user; If it is determined that the session identifier corresponding to the first session message sent by the second user is consistent with the target session identifier, and the sending time of the first session message belongs to the target time period, the first session message is only sent to the second terminal device of the first user; wherein the second terminal device is the remaining terminal device except the first terminal device among the multiple terminal devices simultaneously logged in by the first user.

2. The method according to claim 1, characterized in that After receiving the session setting information of the first user, the method further includes: receiving a session pull request sent by the first terminal device, wherein the session pull request is used to obtain a session message that has not been obtained by a current pull time; If it is determined according to the session setting information that the unobtained session message includes a second session message corresponding to the target session identifier generated within the target time period, and the pulling time belongs to the target time period, the remaining session messages except the second session message in the unobtained session message are sent to the first terminal device, and the second session message is a session message that is not sent to the first terminal device within the target time period.

3. The method according to claim 1, characterized in that The determining that the session identifier corresponding to the first session message sent by the second user is consistent with the target session identifier, and the sending time of the first session message is after the target time period, the method further includes: In response to an end of the target time period, determining that there is the first session message that has not been sent to the first terminal device within the target time period; Sending a prompt message to the first terminal device; Receiving a session pull request sent by the first terminal device based on the prompt message; According to the session pull request, the first session message that has not been sent to the first terminal device is sent to the first terminal device.

4. The method according to claim 3, characterized in that After receiving the session setting information of the first user, the method further includes: Generate a scheduled task corresponding to the session setting information, wherein the scheduled task is triggered when the target time period ends; In response to the end of the target time period, determining that there is the first session message that has not been sent to the first terminal device within the target time period includes: The scheduled task is called to determine whether there is the first session message that has not been sent to the first terminal device within the target time period.

5. A session processing method, characterized in that: The first terminal device and the second terminal device used for the first user to log in simultaneously include: The first terminal device or the second terminal device sends the session setting information of the first user to the server, where the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to the first terminal device within a target time period; The second terminal device receives the first conversation message sent by the server, wherein, when the server receives the first conversation message sent by the second user to the first user, if it is determined that the session identifier corresponding to the first conversation message is consistent with the target conversation identifier, and the sending time of the first conversation message belongs to the target time period, the first conversation message is only sent to the second terminal device.

6. The method according to claim 5, characterized in that After the first terminal device or the second terminal device sends the session setting information of the first user to the server, the method further includes: The first terminal device sends a session pull request to the server, where the session pull request is used to obtain session messages that have not been obtained by the current pull time; The first terminal device receives the remaining session messages except the second session message in the unobtained session messages sent by the server, wherein, when the server receives the session pull request, if it is determined according to the session setting information that the unobtained session messages include the second session message corresponding to the target session identifier generated within the target time period, and the pull time belongs to the target time period, then the remaining session messages except the second session message in the unobtained session messages are sent to the first terminal device, and the second session message is a session message that has not been sent to the first terminal device within the target time period.

7. The method according to claim 5, characterized in that The determining that the session identifier corresponding to the first session message sent by the second user is consistent with the target session identifier, and the sending time of the first session message is after the target time period, the method further includes: The first terminal device receives the prompt information sent by the server, wherein the prompt information is sent in response to the end of the target time period when it is determined that there is the first conversation message that has not been sent to the first terminal device within the target time period; The first terminal device sends a session pull request to the server based on the prompt message; The first terminal device receives the first session message sent by the server and not sent to the first terminal device within the target time period.

8. A conversation processing device, characterized in that: Applicable to servers, including: a receiving unit, configured to receive session setting information of a first user, and receive a first session message sent by a second user to the first user, wherein the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to a first terminal device of the first user within a target time period; The processing unit is configured to execute, if it is determined that the session identifier corresponding to the first session message sent by the second user is consistent with the target session identifier, and the sending time of the first session message belongs to the target time period, then only send the first session message to the second terminal device of the first user; wherein the second terminal device is the remaining terminal device except the first terminal device among the multiple terminal devices logged in by the first user at the same time.

9. The device according to claim 8, characterized in that The receiving unit is further configured to receive a session pull request sent by the first terminal device, where the session pull request is used to obtain a session message that has not been obtained by the current pull time; The processing unit is further configured to execute, if it is determined according to the session setting information that the unobtained session message includes a second session message corresponding to the target session identifier generated within the target time period, and the pulling time belongs to the target time period, then send the remaining session messages in the unobtained session messages except the second session message to the first terminal device, where the second session message is a session message that is not sent to the first terminal device within the target time period.

10. The device according to claim 8, characterized in that The processing unit is further configured to, in response to an end of the target time period, determine that there is the first session message that has not been sent to the first terminal device within the target time period; Sending a prompt message to the first terminal device; receiving a session pull request sent by the first terminal device based on the prompt message; and sending the first session message that has not been sent to the first terminal device to the first terminal device according to the session pull request.

11. The device according to claim 10, characterized in that The processing unit is further configured to execute and generate a timed task corresponding to the session setting information, wherein the timed task is triggered at the end of the target time period; and call the timed task to determine whether there is the first session message that has not been sent to the first terminal device within the target time period.

12. A conversation processing device, characterized in that: The first terminal device and the second terminal device used for the first user to log in simultaneously include: A sending unit, configured to execute the first terminal device or the second terminal device to send the session setting information of the first user to the server, wherein the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to the first terminal device within a target time period; The receiving unit is configured to execute the second terminal device to receive the first conversation message sent by the server, wherein, when the server receives the first conversation message sent by the second user to the first user, if it is determined that the session identifier corresponding to the first conversation message is consistent with the target conversation identifier, and the sending time of the first conversation message belongs to the target time period, the first conversation message is only sent to the second terminal device.

13. The device according to claim 12, characterized in that The sending unit is further configured to execute the first terminal device to send a session pull request to the server, where the session pull request is used to obtain a session message that has not been obtained by the current pull time; The receiving unit is further configured to execute the first terminal device to receive the remaining session messages except the second session message in the unobtained session messages sent by the server, wherein, when the server receives the session pull request, if it is determined according to the session setting information that the unobtained session messages include the second session message corresponding to the target session identifier generated within the target time period, and the pull time belongs to the target time period, then the remaining session messages except the second session message in the unobtained session messages are sent to the first terminal device, and the second session message is a session message that is not sent to the first terminal device within the target time period.

14. The device according to claim 12, characterized in that The receiving unit is further configured to execute the first terminal device receiving a prompt message sent by the server, wherein the prompt message is sent in response to the end of the target time period when it is determined that there is the first session message that has not been sent to the first terminal device within the target time period; and the first terminal device receiving the first session message that has not been sent to the first terminal device within the target time period and is sent by the server; The sending unit is further configured to execute the first terminal device to send a session pull request to the server based on the prompt message.

15. A communication system, characterized in that: include: A server, a first terminal device and a second terminal device of a first user; The server is configured to receive session setting information sent by the first user through the first terminal device or the second terminal device, and receive a session message sent by the second user to the first user, wherein the session setting information is used to indicate that a session message corresponding to a target session identifier is prohibited from being sent to the first terminal device within a target time period; And, if it is determined that the session identifier corresponding to the session message sent by the second user is consistent with the target session identifier, and the sending time of the session message belongs to the target time period, the session message is sent only to the second terminal device, wherein the second terminal device is the remaining terminal device except the first terminal device among the multiple terminal devices simultaneously logged in by the first user; The second terminal device is configured to receive the session message sent by the server.

16. The communication system according to claim 15, characterized in that: The first terminal device is further configured to execute sending a session pull request, where the session pull request is used to obtain a session message that has not been obtained by the current pull time; The server is further configured to execute receiving a session pull request sent by the first terminal device; if it is determined according to the session setting information that the unobtained session message includes a second session message corresponding to the target session identifier generated within the target time period, and the pull time belongs to the target time period, then sending the remaining session messages except the second session message in the unobtained session message to the first terminal device, where the second session message is a session message that is not sent to the first terminal device within the target time period; The first terminal device is further configured to receive remaining session messages except the second session message among the unobtained session messages sent by the server.

17. The communication system according to claim 15, characterized in that: The server is further configured to, in response to an end of the target time period, determine that there is the first session message that has not been sent to the first terminal device within the target time period; Sending a prompt message to the first terminal device; receiving a session pull request sent by the first terminal device based on the prompt message; and sending the first session message that has not been sent to the first terminal device to the first terminal device according to the session pull request; The first terminal device is further configured to receive prompt information sent by the server; Sending a session pull request to the server based on the prompt message; The first session message sent by the server and not sent to the first terminal device within the target time period is received.

18. The communication system according to claim 17, characterized in that: The server is further configured to execute a timed task corresponding to the session setting information, wherein the timed task is triggered at the end of the target time period; and call the timed task to determine whether there is the first session message that has not been sent to the first terminal device within the target time period.

19. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the session processing method according to any one of claims 1 to 4, or the session processing method according to any one of claims 5 to 7.

20. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor of the server, the server is enabled to execute the session processing method according to any one of claims 1 to 4, or the session processing method according to any one of claims 5 to 7.

21. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the session processing method according to any one of claims 1 to 4 or the session processing method according to any one of claims 5 to 7 is implemented.

Images