Session list display method and device, equipment and storage medium

Abstract

The invention provides a session list display method and device, equipment and a storage medium, and the method comprises the steps: reading a first user token corresponding to a target user from a local disk of the target user if the cold start of the target application program by the target user is detected; and if a first login token corresponding to the instant messaging module in the target application program is successfully obtained based on the first user token, logging in the instant messaging module based on the first login token. And receiving first session list data pushed by the instant messaging module, and storing the first session list data in a local memory of the target user. And in response to an operation triggered by the target user for the message control in the home page of the target application program, reading the first session list data from a local memory of the target user. According to the first session list data, the first session list is generated, so that the first session list is displayed in the target application program of the target user, the session list is rapidly displayed, and then the user experience is improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a conversation list display method, device, equipment and storage medium. Background Art

[0002] Quickly displaying the session list after a cold start of an application is an important user experience optimization measure. Quickly displaying the session list can help users quickly enter the core functions of the application, reduce waiting time, and thus improve user experience and user satisfaction. Therefore, how to quickly display the session list after a cold start of an application has become an urgent problem to be solved. Summary of the invention

[0003] The embodiments of the present invention provide a method, apparatus, device and storage medium for displaying a conversation list, which are used to quickly display a conversation list after a cold start of an application program, thereby improving user experience.

[0004] In a first aspect, an embodiment of the present invention provides a method for displaying a conversation list, the method comprising:

[0005] If it is detected that the target user cold-starts the target application, reading a first user token corresponding to the target user from the local disk of the target user;

[0006] If a first login token corresponding to the instant messaging module in the target application is successfully acquired based on the first user token, then logging into the instant messaging module based on the first login token;

[0007] Receiving first conversation list data pushed by the instant messaging module, and storing the first conversation list data in the local memory of the target user, wherein the first conversation list data is part of the conversation list data in the original conversation list data set corresponding to the target user;

[0008] In response to an operation triggered by the target user on a message control in a homepage of a target application, reading the first conversation list data from a local memory of the target user;

[0009] A first conversation list is generated according to the first conversation list data, so as to display the first conversation list in a target application of the target user.

[0010] In a second aspect, an embodiment of the present invention provides a conversation list display device, the device comprising:

[0011] A detection module, configured to read a first user token corresponding to the target user from a local disk of the target user if it is detected that the target user cold-starts the target application;

[0012] A login module, configured to log in to the instant messaging module based on the first login token if a first login token corresponding to the instant messaging module in the target application is successfully acquired based on the first user token;

[0013] A storage module, configured to receive first conversation list data pushed by the instant messaging module, and store the first conversation list data in a local memory of the target user, wherein the first conversation list data is part of conversation list data in an original conversation list data set corresponding to the target user;

[0014] a reading module, configured to read the first conversation list data from the local memory of the target user in response to an operation triggered by the target user on a message control in the homepage of a target application;

[0015] A generating module is used to generate a first conversation list according to the first conversation list data, so as to display the first conversation list in a target application of the target user.

[0016] In a third aspect, an embodiment of the present invention provides an electronic device, comprising: a memory, a processor, and a communication interface; wherein the memory stores an executable code, and when the executable code is executed by the processor, the processor executes the conversation list display method as described in the first aspect.

[0017] In a fourth aspect, an embodiment of the present invention provides a non-transitory machine-readable storage medium, on which executable code is stored. When the executable code is executed by a processor of an electronic device, the processor can at least implement the conversation list display method described in the first aspect.

[0018] In the conversation list display scheme provided by the embodiment of the present invention, it is detected whether the target user starts the target application. If it is detected that the target user cold-starts the target application, the first user token corresponding to the target user is read from the local disk of the target user. Then, based on the first user token, the first login token corresponding to the instant messaging module in the target application is obtained. If the first login token is successfully obtained, the instant messaging module is logged in based on the first login token. Then, the first conversation list data pushed by the instant messaging module is received, and the first conversation list data is stored in the local memory of the target user. Among them, the first conversation list data is part of the conversation list data set corresponding to the target user. In response to the operation triggered by the target user on the message control in the homepage of the target application, the first conversation list data is read from the local memory of the target user, and the first conversation list is generated according to the first conversation list data to display the first conversation list in the target application of the target user.

[0019] In the above scheme, when it is detected that the target user cold-starts the target application, the previously cached first user token is read from the local disk of the target user in advance, and based on the cached first user token, the first login token corresponding to the instant messaging module is obtained, so as to log in to the instant messaging module in advance based on the first login token. In this way, when the target application is started, when the message control is quickly clicked, it is no longer necessary to wait for the instant messaging module to log in, and the first conversation list data can be directly pulled up from the local memory, and the first conversation list can be generated based on the first conversation list data, so as to avoid long waiting after the application is cold-started, and the conversation list can be quickly displayed, thereby improving the user experience. In addition, when the conversation list is displayed after the target application is cold-started, part of the conversation list data can be directly loaded from the local memory to display part of the conversation list, and the loading time is short, and it is no longer necessary to wait for all the original conversation list data sets to be loaded, and the first conversation list can be quickly generated and displayed. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0021] Figure 1 A schematic diagram of a traditional method for displaying a conversation list provided by an embodiment of the present invention;

[0022] Figure 2 A schematic diagram of a new method for displaying a conversation list provided by an embodiment of the present invention;

[0023] Figure 3 A schematic diagram of an application of a method for displaying a conversation list provided by an embodiment of the present invention;

[0024] Figure 4 A flowchart of a method for displaying a conversation list provided by an embodiment of the present invention;

[0025] Figure 5 A flowchart of another method for displaying a conversation list provided by an embodiment of the present invention;

[0026] Figure 6 A schematic diagram of the structure of a conversation list display device provided by an embodiment of the present invention;

[0027] Figure 7 A schematic diagram of the structure of an electronic device provided in this embodiment. DETAILED DESCRIPTION

[0028] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention. In addition, the step timing in the following method embodiments is only an example, not a strict limitation.

[0029] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in the embodiments of the present invention are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0030] At present, when a user opens a target application by clicking on a mobile desktop application icon (icon), the target application is cold started. When the target application is started, the application homepage is displayed. After entering the target application homepage, the user quickly switches to the message interface. When responding to the user's switching operation to display the message interface, it is necessary to first determine whether the instant messaging module in the target application has been successfully logged in. If it has been successfully logged in, the user's corresponding session list can be pulled to be displayed in the message interface.

[0031] Among them, the cold start process of the target application, such as Figure 1 As shown. During the cold start process of the target application, the process will be loaded. During the process startup, the passport user authentication module will be initialized first, and the user authentication module will be logged in. The passport checkPPU user token check operation will be executed. After the check, a valid user token PPU will be returned. Based on the valid user token, the login token will be obtained and the login token will be used to log in to the IM instant messaging module.

[0032] Among them, the user token checking process is relatively time-consuming. Therefore, after the cold start process of the target application, it may have entered the home page display stage, and the instant messaging module has not been successfully logged in. If the user has quickly triggered the message control in the home page at this time, it is necessary to wait for the initialization and login of the instant messaging module first, and display the transitional interface first. When it is detected that the instant messaging module has been successfully logged in, the user's corresponding session list is pulled to display it in the corresponding message interface. In this way, the user waiting time is long, which affects the user experience and may cause user loss during the loading process.

[0033] In order to solve the above technical problems, the embodiment of the present invention provides a new conversation list display solution. For example, Figure 2 As shown, the IM instant messaging module login is advanced to the process startup phase of the target application APP. In the process startup phase, the IM module is initialized and logged in. That is, the login of the IM module can be completed before the passport checkPPU user token check operation is completed. Since the login timing of the IM module is advanced, the login of the IM module can be completed before the target program enters the opening screen phase. In this way, after the target application homepage is displayed, when the target user quickly triggers the message control in the target application homepage, the operation of the target user can be quickly responded to to quickly display the conversation list, so that the conversation list can be quickly displayed after the target application is cold started.

[0034] Specifically, when the target application is cold-started, the user token cached by the user authentication module is first read from the user's local disk, and the login token is obtained based on the cached user token to log in to the instant messaging module in advance. In this way, when the user quickly switches to the message interface, the session list data can be quickly pulled to quickly generate a session list and display the session list in the message interface. In addition, after the instant messaging module successfully logs in, part of the pushed session list data is cached in the local memory. In this way, when pulling data, the part of the session list data can be quickly read from the local memory, and the session list corresponding to the part of the session list data can be displayed, which can improve loading efficiency, quickly display the session list, and thus improve the user experience to avoid user loss.

[0035] In the following, some embodiments of the present invention are described in detail in conjunction with the accompanying drawings. In the case where there is no conflict between the embodiments, the following embodiments and features in the embodiments can be combined with each other.

[0036] Figure 3 An application diagram of a conversation list display method provided by an embodiment of the present invention; wherein the method can be executed by a conversation list display device, and the device is communicatively connected to a user device and can display a user conversation list in a target application in the user device.

[0037] The user device is an electronic device installed with a target application. In specific implementation, the user device / client may be a mobile phone, a personal computer PC, a tablet computer, etc.

[0038] The session list display device refers to a device that can provide session list display services for user devices. In physical implementation, the application wake-up device can be a terminal device such as a PC, a laptop, a smart phone, or a server.

[0039] In the embodiment of the present invention, the conversation list display device can advance the instant messaging module initialization and login timing in the target application to the process startup stage, and use the user token cached in the local disk of the user device by the user identity authentication module in the target application to log in to the instant messaging module. At the same time, the partial conversation list data pushed by the instant messaging module cached in the local memory of the user device is used to display the partial conversation list.

[0040] Specifically, when it is detected that the user device starts the target application, the startup method corresponding to the target application corresponding to the user device is detected. If it is detected that the target application in the user device is cold started, the first user token corresponding to the target device is read from the local disk of the user device. Among them, the first user token PPU can be a parameter that identifies the user's identity. In some applications, the first user token is used to record the user's login status, so that when the user accesses the target application or a service, the user's identity can be identified according to the first user token.

[0041] Then, based on the first user token, a first login token corresponding to the instant messaging module in the target application is obtained. The instant messaging module is a form of electronic communication that allows users to communicate in real time via text, audio or video over the Internet. The login token is usually a temporary credential generated by the server and issued to the user's device after the user successfully logs in, which is used to prove that the user has passed the identity authentication and has the right to access the protected resources.

[0042] In actual applications, user tokens usually have a validity period. If the first user token obtained from the local disk of the user device is still within the validity period, the first login token can be obtained through the first user token. If the first user token obtained from the local disk of the user device is not within the validity period, the first login token cannot be obtained through the first user token.

[0043] In the specific implementation, if the first login token corresponding to the instant messaging module in the target application is successfully obtained based on the first user token, the instant messaging module can be logged in based on the first login token. After the instant messaging module is logged in, the conversation list data is actively pushed. The conversation list display device receives the first conversation list data pushed by the instant messaging module, and stores the first conversation list data in the local memory of the user device, so that the first conversation list data can be quickly read from the local memory of the user device later. Among them, the first conversation list data is part of the conversation list data in the original list data set corresponding to the user device.

[0044] When the target application is cold started, the target application homepage will be displayed on the user device. The target application homepage includes a message control, and the user can quickly display the session list corresponding to the target device by triggering the message control.

[0045] Specifically, in response to a selection operation on a message control sent by a user device, first conversation list data is read from a local memory of the user device, and a first conversation list is generated according to the first conversation list data to display the first conversation list in a target application of the user device.

[0046] From the above description, it can be seen that: when the target application is cold started, the first user token cached by the user authentication module is read from the local disk of the user device, and the login token is obtained based on the cached user token to log in to the instant messaging module in advance, and some session list data pushed by the instant messaging module is cached in the local memory. In this way, when the user quickly switches the message interface after the target application is cold started, some session list data can be directly pulled from the local memory of the user device to quickly generate and display the session list corresponding to the part of the session list data, so that the session list can be quickly displayed after the target application is cold started, the waiting time is reduced, and the user experience is improved to avoid user loss.

[0047] In addition, in order to ensure that the conversation list corresponding to the user device can be displayed in the message interface after the user switches the message interface, the embodiment of the present invention also includes a user token invalidation fault tolerance mechanism. That is, when the first user token obtained from the local disk of the user device has expired and the first login token cannot be successfully obtained based on the first user token, the valid second user token returned after the user identity authentication module completes the user token check can be used to obtain the second login token corresponding to the instant messaging module, and the instant messaging module can be logged in based on the second login token. The second conversation list data pushed by the instant messaging module is received, and the second conversation list data is stored in the local memory of the user device. When the user device triggers the message control selection operation, the second conversation list data can be read from the local memory of the user device in response to the selection operation for the message control sent by the user device, and the second conversation list can be generated according to the second conversation list data to display the second conversation list in the target application of the user device.

[0048] It should be noted that the second conversation list data and the first conversation list data may be the same conversation list data.

[0049] The specific implementation process of quickly displaying the conversation list is described in detail below in conjunction with the following embodiments.

[0050] Figure 4 A flowchart of a method for displaying a conversation list provided by an embodiment of the present invention is shown in FIG. Figure 4 As shown, the method comprises the following steps:

[0051] 401. If it is detected that the target user cold-starts the target application, a first user token corresponding to the target user is read from a local disk of the target user.

[0052] 402. If a first login token corresponding to the instant messaging module in the target application is successfully acquired based on the first user token, the instant messaging module is logged in based on the first login token.

[0053] 403. Receive first conversation list data pushed by the instant messaging module, and store the first conversation list data in the local memory of the target user, where the first conversation list data is part of the conversation list data in the original conversation list data set corresponding to the target user.

[0054] 404. In response to an operation triggered by the target user on a message control in the homepage of the target application, first conversation list data is read from the local memory of the target user.

[0055] 405. Generate a first conversation list according to the first conversation list data, so as to display the first conversation list in a target application of the target user.

[0056] The conversation list display solution provided by the embodiment of the present invention can be applied to various applications. When a user cold-starts an application, the user can log in to the instant messaging module in the application in advance, and cache part of the conversation list data pushed by the instant messaging module into the local memory, so that the conversation list corresponding to the user can be quickly displayed after the application is cold-started. The application can be recruitment software, audio and video playback software, office software, image processing software, etc.

[0057] In specific implementation, when it is detected that the target user starts the target application, the startup method of the current target application is determined. If it is detected that the current startup method of the target application is a cold start, the first user token corresponding to the target user is obtained from the local disk of the target user.

[0058] The target application includes a user identity authentication module. The user identity authentication module is mainly used to authenticate the user's identity information. When the authentication is passed, the first user token corresponding to the target user can be stored in the local disk of the target user. Then, when it is detected that the target user cold-starts the target application, the first user token corresponding to the target user stored in the user identity authentication module can be read from the local disk of the target user.

[0059] In actual application, it is necessary to first log in to the user identity authentication module, authenticate the identity information of the target user, and then read the first user token stored in the user identity authentication module from the local disk of the target user. Specifically, in an optional embodiment, the user identity authentication module in the target application can be initialized in advance, and the user identity authentication module can be logged in based on the authentication information of the target user. If the user identity authentication module is successfully logged in, the first user token corresponding to the target user can be read from the local disk of the target user.

[0060] Among them, the user identity authentication module can be initialized by calling a specific interface, and the login information of the target user can be obtained to log in to the user identity authentication module. At the same time, the instant messaging module can also be initialized by calling a specific interface. In other words, the initialization operation of the instant messaging module is placed first.

[0061] Next, based on the first user token, the first login token corresponding to the instant messaging module in the target application is obtained. The user token has a validity period, for example, a user token has a validity period of two months. If the user device has not started the target application for more than two months, the first user token obtained from the local disk of the target user is invalid, and the first login token corresponding to the instant messaging module cannot be successfully obtained.

[0062] That is to say, the first user token read from the local disk of the target user may be invalid. If the first user token is invalid, then based on the first user token, it is impossible to successfully obtain the first login token corresponding to the instant messaging module in the target application. At this time, it is also impossible to use the first user token corresponding to the target user stored in the local disk of the target user to log in to the instant messaging module.

[0063] Therefore, in specific implementation, it is possible to first determine whether the first login token corresponding to the instant messaging module in the target application can be obtained based on the locally stored first user token. If the first login token corresponding to the instant messaging module in the target application is successfully obtained, the instant messaging module can be logged in based on the first login token, so that the login operation of the instant messaging module can be completed in advance during the cold start process of the target application. In this way, when the target application is cold started, when the target user quickly switches the session list, the session list data can be quickly pulled to display the session list in the target application of the target user.

[0064] After the instant messaging module successfully logs in, the instant messaging module can actively push the first conversation list data to the conversation list display device. The first conversation list data is part of the conversation list data in the original conversation list data set corresponding to the target user. For example, the original conversation list data set includes 80 conversation records, and the latest 20 conversation records are obtained from the original conversation list data set, and the latest 20 conversation records are determined as the first conversation list data, and the instant messaging module pushes the first conversation list data to the conversation list display device.

[0065] Then, the first conversation list data pushed by the instant messaging module is received, and the first conversation list data is stored in the local memory of the target user, so as to quickly respond to the conversation list display operation triggered by the target user later, and the first conversation list data is read from the local memory to speed up the loading speed.

[0066] Specifically, after the target application is cold-started, the target application homepage is displayed in the target application. The target application homepage includes a message control. When the target user wants to quickly display the conversation list, the message control in the target application homepage can be triggered. After the conversation list display device receives the operation triggered by the user, in response to the operation triggered by the target user on the message control in the target application homepage, the first conversation list data is read from the local memory of the target user, and the first conversation list is generated according to the first conversation list data, so as to display the first conversation list in the target application of the target user.

[0067] Since the first login token has been obtained based on the first user token cached in the local disk during the cold start process of the target application, the login operation of the instant messaging module can be quickly completed before the home page of the target application is displayed. In this way, when the target user wants to quickly switch to the message interface after the home page of the target application is displayed, he has successfully logged into the instant messaging module in advance. In this way, the first conversation list data can be quickly read from the local memory of the target user, and the first conversation list can be generated based on the first conversation list data to quickly display the first conversation list in the target application of the target user. This achieves that after the cold start of the target application, there is no need to wait for the user identity authentication module to complete the user token check operation before completing the login of the instant messaging module, and the first conversation list can be quickly displayed, thereby reducing the user waiting time and improving the user experience.

[0068] In order to ensure that the conversation list corresponding to the target user can be displayed in the target application, before reading the first conversation list data, it can be determined whether the instant communication module has logged in successfully. Specifically, in an optional embodiment, in response to the message control triggered by the target user, it is determined whether the instant communication module in the current target application has logged in successfully; if the login is successful, the first conversation list data is read from the local memory of the target user; if the login is unsuccessful, a preset animation page is displayed, and it is monitored whether the instant communication module has logged in successfully. When it is monitored that the instant communication module has logged in successfully, the first conversation list data is read from the local memory of the target user.

[0069] In addition, the first conversation list data is only a small part of the conversation list data set corresponding to the target user. Therefore, when displaying the conversation list, the data loading can be completed quickly to quickly generate the first conversation list, thereby speeding up the display speed of the conversation list.

[0070] In summary, in the embodiment of the present invention, when it is detected that the target user cold-starts the target application, the previously cached first user token is read from the local disk of the target user in advance, and based on the cached first user token, the first login token corresponding to the instant messaging module is obtained, so as to log in to the instant messaging module in advance based on the first login token. In this way, when the target application is started, when the message control is quickly clicked, it is no longer necessary to wait for the login of the instant messaging module, and the first conversation list data can be directly pulled up from the local memory, and the first conversation list can be generated based on the first conversation list data, so as to avoid long waiting after the application is cold-started, and the conversation list can be quickly displayed, thereby improving the user experience. Moreover, when the conversation list is displayed after the target application is cold-started, part of the conversation list data can be directly loaded from the local memory to display part of the conversation list, and the loading time is short, and it is no longer necessary to wait for all the original conversation list data sets to be loaded, and the first conversation list can be quickly generated and displayed.

[0071] The above embodiment describes that during the cold start process of the target application, if the first login token corresponding to the instant messaging module in the target application can be successfully obtained based on the first user token in the local disk, the login operation of the instant messaging module can be quickly completed based on the obtained first login token, and there is no need to wait for the user token check operation of the user identity authentication module, which can save a lot of waiting time and can quickly display the first conversation list. In actual applications, the target user may not start the target application for a long time, that is, the first user token stored in the local disk has expired. In this case, the first login token corresponding to the instant messaging module cannot be obtained based on the first user token, and the login operation of the instant messaging module cannot be completed in advance, which in turn affects the display of the first conversation list.

[0072] In order to ensure that the first conversation list can be displayed in the target application of the target user, after reading the first user token corresponding to the target user from the local disk of the target user, the user token check operation corresponding to the user identity authentication module can also be completed at the same time. When I cannot obtain the first login token corresponding to the instant communication module based on the first user token, I can obtain the corresponding login token based on the valid user token returned by the user identity authentication module after completing the check operation on the first user token to complete the login operation of the instant communication module.

[0073] Specifically, in an optional embodiment, the first user token can be decrypted to obtain the expiration time corresponding to the first user token; according to the expiration time, check whether the first user token is valid. If the first user token is valid, the first user token corresponding to the target user stored in the local disk of the target user is no longer updated. If the first user token is invalid, request the user token corresponding to the target user from the server of the target application; receive the second user token corresponding to the target user sent by the server, and update the second user token to the local disk of the target user.

[0074] After the checking operation and the updating operation are completed, it can be determined whether the first login token corresponding to the instant messaging module has been successfully obtained. If the first login token corresponding to the instant messaging module has been successfully obtained, the operation of obtaining the login token corresponding to the instant messaging module is no longer performed. If the first login token corresponding to the instant messaging module has not been successfully obtained, the second login token corresponding to the instant messaging module is obtained based on the second user token returned by the user identity authentication module. And based on the second login token, the instant messaging module is logged in.

[0075] Among them, in an optional embodiment, based on the second user token, the specific implementation process of obtaining the second login token corresponding to the instant messaging module may include: sending the second user token to the server of the target application through the server interface of the target application, so that the server verifies the second user token, and after the verification is passed, generates a second login token corresponding to the instant messaging module; receiving the second login token sent by the server.

[0076] Similarly, when the instant communication module logs in successfully, the instant communication module can actively push the first conversation list data corresponding to the target user, receive the first conversation list data pushed by the instant communication module, and store the first conversation list data in the local memory of the target user.

[0077] In this way, after receiving the message control selection operation triggered by the target user, it is possible to quickly respond to the target user's selection operation on the message control and determine whether the instant messaging module in the current target application has been successfully logged in. If the instant messaging module has been successfully logged in, the first conversation list data is read from the local memory of the target user, and the first conversation list is generated according to the first conversation list data. This ensures that when the target user triggers the message control, the first conversation list data can be directly read from the local memory, and part of the conversation list data can be read from the local memory. Compared with pulling all the original conversation list data sets corresponding to the target user from the server, the reading speed is faster and the reading cost is lower, and the first conversation list data can be quickly displayed.

[0078] From the above description, it can be seen that: in the specific implementation process of displaying the session list, a user token time-limited fault-tolerant mechanism is added. If the first user token stored in the local disk of the target user expires, you can wait for the user identity authentication module to complete the user token check operation to obtain the second user token returned by the user identity authentication module, use the second user token to obtain the second login token corresponding to the instant messaging module, and log in to the instant messaging module based on the second login token.

[0079] The above embodiments describe in detail that after receiving a selection operation of a message control triggered by a target user, the first conversation list data is read from the local memory of the target user, that is, a part of the conversation list data is quickly loaded, and a part of the conversation list is generated, so as to quickly display the part of the conversation list in the target application, reduce the user waiting time, and quickly display the conversation list.

[0080] In addition, in order to fully display all conversation lists corresponding to the target user and ensure the display efficiency of the conversation lists, when it is determined that the instant messaging module in the current target application has successfully logged in, while reading the first conversation list from the local memory of the target user, the original conversation list data set corresponding to the target user can also be pulled, and the second conversation list is generated based on the original conversation list data set. The second conversation list is then displayed in the target application corresponding to the target user.

[0081] The specific execution process and technical effects of the above steps in this embodiment are similar to the specific execution process and technical effects in the above embodiments. Please refer to the above statements for details, and no further details will be given here.

[0082] In order to facilitate understanding of the specific implementation process and implementation principle of this solution, this solution is illustrated in combination with a specific application scenario. Figure 5 As shown, the display process of the session list is explained. In specific implementation, first, when a cold start of the recruitment app is detected, the passport module (user identity authentication module) in the recruitment app can be initialized, and the user identity authentication module can be logged in. Next, the user token ppu corresponding to the target user cached by the user identity authentication module is read from the local disk of the target user, and based on the user token ppu, the IMtoken login token corresponding to the instant messaging module in the recruitment app is obtained. At the same time, the passport checkppu (user token check operation) corresponding to the user identity authentication module can also be executed. When the user token check is completed, a valid user token is returned. It should be noted that the returned valid user token may be the same as the first user token read from the local disk, or it may be a different user token.

[0083] Among them, the user token may become invalid. In order to ensure that the login token corresponding to the IM module (instant messaging module) can be successfully obtained, after obtaining the login token based on the user token, it can be determined whether the IMtoken login token corresponding to the instant messaging module is successfully obtained. If the login token is successfully obtained, the instant messaging module is logged in based on the login token.

[0084] In addition, in order to avoid obtaining the login token corresponding to the instant messaging module multiple times, after receiving the valid user token returned by the user identity authentication, it is determined whether the login token corresponding to the instant messaging module has been successfully obtained. If the login token corresponding to the instant messaging module is successfully obtained, the login token acquisition operation is no longer performed. If the login token corresponding to the instant messaging module fails to be obtained, the login token corresponding to the instant messaging module is obtained based on the returned valid user token, and the instant messaging module is logged in based on the login token.

[0085] When the instant messaging module successfully logs in, the first conversation list data is actively pushed, the first conversation list data pushed by the instant messaging module is received, and the first conversation list data is stored in the local memory. The first conversation list data is part of the conversation list data in the original conversation list data set, for example, the first conversation list data includes 20 conversation records.

[0086] While executing the login operation of the instant messaging module, the recruitment app performs a cold start operation. When the recruitment app completes the cold start, the instant messaging module can be successfully logged in according to the user token in the local disk.

[0087] When the recruitment app completes the cold start, it enters the splash screen stage, at which time the splash screen interface can be displayed. After the splash screen ends, the home page corresponding to the recruitment app begins to be displayed. The home page includes a message control, which responds to the target user's operation triggered by the message control in the home page of the target application, and determines whether the instant messaging module has been successfully logged in. If the login is successful, the first session list data is read from the local memory of the target user, and the first session list is generated according to the first session list data to display the first session list in the recruitment app of the target user, so that the session list can be quickly displayed after the recruitment app is cold started.

[0088] While reading the first conversation list data from the local memory of the target user, the original conversation list data set corresponding to the target user can be pulled from the server, and a second conversation list is generated based on the original conversation list data set, and the second conversation list is displayed in the recruitment APP corresponding to the target user.

[0089] In the embodiment of the present invention, the cache ppu of the Passport module is used to obtain the IMToken, and the IM module is logged in based on the obtained IMToken. At the same time, a ppu failure tolerance mechanism is added, so that the IM module is logged in in advance. When the user quickly clicks the message control after a cold start, the complete IM session data can be directly obtained while loading part of the session data first. There is no need to wait and the session list can be displayed immediately.

[0090] In addition, the conversation list display method provided in the embodiment of the present invention can be executed in the cloud, and several computing nodes (cloud servers) can be deployed in the cloud, and each computing node has processing resources such as computing and storage. In the cloud, multiple computing nodes can be organized to provide the conversation list display service, and of course, one computing node can also provide the service.

[0091] The conversation list display device of one or more embodiments of the present invention will be described in detail below. Those skilled in the art will appreciate that these devices can be configured using commercially available hardware components through the steps taught in this solution.

[0092] Figure 6 A structural diagram of a conversation list display device provided by an embodiment of the present invention, such as Figure 6 As shown, the device includes: a detection module 11, a login module 12, a storage module 13, a reading module 14, and a generation module 15.

[0093] The detection module 11 is configured to read a first user token corresponding to the target user from a local disk of the target user if it is detected that the target user cold-starts the target application.

[0094] The login module 12 is used to log in to the instant messaging module based on the first login token if a first login token corresponding to the instant messaging module in the target application is successfully acquired based on the first user token.

[0095] The storage module 13 is used to receive the first conversation list data pushed by the instant messaging module and store the first conversation list data in the local memory of the target user, wherein the first conversation list data is part of the conversation list data in the original conversation list data set corresponding to the target user.

[0096] The reading module 14 is configured to read the first conversation list data from the local memory of the target user in response to an operation triggered by the target user on a message control in the homepage of the target application.

[0097] The generating module 15 is configured to generate a first conversation list according to the first conversation list data, so as to display the first conversation list in the target application of the target user.

[0098] Optionally, the detection module 11 is also used to: decrypt the first user token to obtain the expiration time corresponding to the first user token; check whether the first user token is valid based on the expiration time; if the first user token is invalid, request the user token corresponding to the target user from the server of the target application; receive the second user token corresponding to the target user sent by the server, and update the second user token to the local disk of the target user.

[0099] Optionally, the login module 12 is also used to: determine whether the first login token corresponding to the instant messaging module in the target application has been successfully obtained; if the first login token corresponding to the instant messaging module has not been successfully obtained, then based on the second user token, obtain the second login token corresponding to the instant messaging module; based on the second login token, log in to the instant messaging module.

[0100] Optionally, the login module 12 is specifically used to: send the second user token to the server of the target application through the server interface of the target application, so that the server verifies the second user token, and after the verification is passed, generates a second login token corresponding to the instant messaging module; receive the second login token sent by the server.

[0101] Optionally, the reading module 14 is specifically used to: in response to the message control triggered by the target user, determine whether the instant messaging module in the current target application has logged in successfully; if the login is successful, read the first conversation list data from the local memory of the target user; if the login is unsuccessful, display a preset animation page, and monitor whether the instant messaging module has logged in successfully.

[0102] Optionally, the generating module 15 is further configured to: pull an original conversation list data set corresponding to the target user; generate a second conversation list based on the original conversation list data set; and display the second conversation list in a target application corresponding to the target user.

[0103] Optionally, the detection module 11 is specifically used to: initialize the user identity authentication module within the target application; log in to the user identity authentication module based on the authentication information of the target user; if the user identity authentication module logs in successfully, read the first user token corresponding to the target user from the local disk of the target user.

[0104] Figure 6 The device shown can execute the steps in the conversation list display method in the aforementioned embodiment. The detailed execution process and technical effects are described in the aforementioned embodiment and will not be repeated here.

[0105] The embodiment of the present invention also provides an electronic device, such as Figure 7 As shown, the electronic device may include: a processor 21, a memory 22, and a communication interface 23. The memory 22 stores executable codes, and when the executable codes are executed by the processor 21, the processor 21 implements the conversation list display method in the above-mentioned embodiment.

[0106] In addition, an embodiment of the present invention provides a non-transitory machine-readable storage medium, on which executable code is stored. When the executable code is executed by a processor of an electronic device, the processor can at least implement the conversation list display method provided in the aforementioned embodiment.

[0107] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment. Those of ordinary skill in the art may understand and implement the present invention without creative effort.

[0108] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by adding a necessary general hardware platform, and of course can also be implemented by combining hardware and software. Based on such an understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a computer product, and the present invention can be in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0109] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for displaying a conversation list, characterized in that: include: If it is detected that the target user cold-starts the target application, reading a first user token corresponding to the target user from the local disk of the target user; If a first login token corresponding to the instant messaging module in the target application is successfully acquired based on the first user token, then logging into the instant messaging module based on the first login token; Receiving first conversation list data pushed by the instant messaging module, and storing the first conversation list data in the local memory of the target user, wherein the first conversation list data is part of the conversation list data in the original conversation list data set corresponding to the target user; In response to an operation triggered by the target user on a message control in a homepage of a target application, reading the first conversation list data from a local memory of the target user; A first conversation list is generated according to the first conversation list data, so as to display the first conversation list in a target application of the target user.

2. The method according to claim 1, characterized in that After reading the first user token corresponding to the target user from the local disk of the target user, the method further includes: Decrypting the first user token to obtain an expiration time corresponding to the first user token; According to the expiration time, checking whether the first user token is valid; If the first user token is invalid, requesting a user token corresponding to the target user from the server of the target application; Receive a second user token corresponding to the target user sent by the server, and update the second user token to the local disk of the target user.

3. The method according to claim 2, characterized in that The method further comprises: Determining whether a first login token corresponding to the instant messaging module in the target application has been successfully acquired; If the first login token corresponding to the instant messaging module is not successfully acquired, acquiring the second login token corresponding to the instant messaging module based on the second user token; Log in to the instant messaging module based on the second login token.

4. The method according to claim 3, characterized in that The acquiring, based on the second user token, a second login token corresponding to the instant messaging module includes: Sending the second user token to the server of the target application through the server interface of the target application, so that the server verifies the second user token, and after the verification is passed, generates a second login token corresponding to the instant messaging module; Receive the second login token sent by the server.

5. The method according to claim 1, characterized in that The step of reading the first conversation list data from the local memory of the target user in response to the message control triggered by the target user includes: In response to the message control triggered by the target user, determining whether the instant messaging module in the current target application program has logged in successfully; If the login is successful, reading the first session list data from the local memory of the target user; If the login is unsuccessful, a preset animation page is displayed, and the instant messaging module is monitored to see whether the login is successful.

6. The method according to claim 1, characterized in that After generating the first conversation list according to the first conversation list data, the method further includes: Pulling the original conversation list data set corresponding to the target user; Based on the original conversation list data set, generating a second conversation list; The second conversation list is displayed in a target application corresponding to the target user.

7. The method according to claim 1, characterized in that The step of reading the first user token corresponding to the target user from the local disk of the target user includes: Initializing a user identity authentication module within the target application; Based on the authentication information of the target user, log in to the user identity authentication module; If the user identity authentication module logs in successfully, the first user token corresponding to the target user is read from the local disk of the target user.

8. A conversation list display device, characterized in that: include: A detection module, configured to read a first user token corresponding to the target user from a local disk of the target user if it is detected that the target user cold-starts the target application; A login module, configured to log in to the instant messaging module based on the first login token if a first login token corresponding to the instant messaging module in the target application is successfully acquired based on the first user token; A storage module, configured to receive first conversation list data pushed by the instant messaging module, and store the first conversation list data in a local memory of the target user, wherein the first conversation list data is part of conversation list data in an original conversation list data set corresponding to the target user; a reading module, configured to read the first conversation list data from the local memory of the target user in response to an operation triggered by the target user on a message control in the homepage of a target application; A generating module is used to generate a first conversation list according to the first conversation list data, so as to display the first conversation list in a target application of the target user.

9. An electronic device, characterized in that: include: A memory, a processor, and a communication interface; wherein the memory stores executable code, and when the executable code is executed by the processor, the processor executes the conversation list display method according to any one of claims 1 to 7.

10. A non-transitory machine-readable storage medium, characterized in that: The non-transitory machine-readable storage medium stores executable code, and when the executable code is executed by a processor of an electronic device, the processor executes the conversation list display method according to any one of claims 1 to 7.

Images