CN110430124B

CN110430124B - Unread mark processing method, unread mark processing device, unread mark processing system, unread mark storage medium and computer equipment

Info

Publication number: CN110430124B
Application number: CN201910718282.1A
Authority: CN
Inventors: 周罗武
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-08-05
Filing date: 2019-08-05
Publication date: 2022-08-19
Anticipated expiration: 2039-08-05
Also published as: CN110430124A

Abstract

The application relates to an unread mark processing method, an unread mark processing device, an unread mark processing system, a computer readable storage medium and computer equipment, wherein the method comprises the following steps: receiving an unread mark processing request of a client; the unread mark processing request is used for clearing a target unread mark in a session list interface of the client; determining a record table corresponding to the client; the record table is used for storing session identifications corresponding to all unread marks of the client; deleting the session identification corresponding to the target unread mark in the record table; and returning the deletion result to the client to clear the target unread mark of the client. The scheme provided by the application can improve the processing efficiency of the unread marks.

Description

Unread mark processing method, unread mark processing device, unread mark processing system, unread mark storage medium and computer equipment

Technical Field

The present application relates to the field of social application software technologies, and in particular, to a method, an apparatus, a system, a computer-readable storage medium, and a computer device for processing unread tags in social application software.

Background

With the development of mobile terminal technology, a great amount of social application software suitable for mobile terminals appears, and an important function provided by the application software is a chat function. Under the chat function, if a new conversation message is received, an unread mark, such as a red dot, is displayed on the corresponding conversation to prompt the user that the conversation of the corresponding friend has the unread message. When a user has a large number of friends or groups, if the user does not check the conversation messages in time, the accumulated unread messages will be more and more as time passes, so that a plurality of red dots appear in a conversation list interface, and the user cannot pay attention to the important unread messages.

The current method for processing unread marks in a session list interface is that a user initiates an unread mark processing request at a client, a chat server respectively inquires a chat database aiming at sessions corresponding to the unread marks after receiving the unread mark processing request of the client, and unread messages under corresponding sessions are marked as read. In this way, red dots on sessions in the client session list interface are eliminated. However, this processing method requires the chat server to frequently query the chat database, and also requires modifying unread messages in the chat database into read messages, so that there is a problem of low processing efficiency.

Disclosure of Invention

In view of the foregoing, it is necessary to provide an unread mark processing method, an unread mark processing apparatus, an unread mark processing system, a computer-readable storage medium, and a computer device, which are directed to the technical problem that the current unread mark processing method is inefficient.

One aspect of the present invention provides an unread mark processing method, including:

receiving an unread mark processing request of a client; the unread mark processing request is used for clearing a target unread mark in a session list interface of the client;

determining a record table corresponding to the client; the record table is used for storing session identifications corresponding to all unread marks of the client;

deleting the session identification corresponding to the target unread mark in the record table;

and returning the deletion result to the client to clear the target unread mark of the client.

The second aspect of the present invention provides an unread mark processing method, including:

displaying a session list interface of a client; the conversation list interface comprises an unread mark;

receiving operation information for clearing a target unread mark in the session list interface;

sending an unread mark processing request to a chat server;

receiving a response result returned by the chat server aiming at the unread mark processing request; the response result comprises a deletion result of the session identifier corresponding to the target unread mark in the record table; the record table is a record table corresponding to the client and is used for storing session identifications corresponding to all unread marks of the client;

and clearing the target unread marks in the session list interface.

A third aspect of the present invention provides an unread mark processing apparatus, the apparatus comprising:

the request receiving module is used for receiving an unread mark processing request of a client; the unread mark processing request is used for clearing a target unread mark in a session list interface of the client;

the table determining module is used for determining a record table corresponding to the client; the record table is used for storing session identifications corresponding to all unread marks of the client;

the table processing module is used for deleting the session identifier corresponding to the target unread mark in the record table;

and the result returning module is used for returning the deletion result to the client so as to clear the target unread mark of the client.

A fourth aspect of the present invention provides an unread mark processing apparatus, the apparatus comprising:

the display module is used for displaying a session list interface of the client; the conversation list interface comprises an unread mark;

the operation information receiving module is used for receiving operation information used for clearing the target unread marks in the session list interface;

the request sending module is used for sending an unread mark processing request to the chat server;

a response receiving module, configured to receive a response result returned by the chat server for the unread mark processing request; the response result comprises a deletion result of the session identification corresponding to the target unread mark in the record table; the record table is a record table corresponding to the client and is used for storing session identifications corresponding to all unread marks of the client;

and the mark clearing module is used for clearing the target unread mark in the session list interface.

A fifth aspect of the present invention provides an unread mark processing system, comprising: a client and a chat server;

the client is used for displaying a session list interface, and the session list interface comprises a session list and an unread mark; receiving operation information for clearing a target unread mark in the session list interface, and sending an unread mark processing request to the chat server; the unread mark processing request is used for clearing the target unread mark;

the chat server is used for receiving the unread tag processing request, determining a record table corresponding to the client, deleting the session identifier corresponding to the target unread tag in the record table, and returning the deletion result to the client; the record table is used for storing session identifications corresponding to all unread marks in a session list interface of the client;

the client is further configured to receive the deletion result and clear the target unread mark in the session list interface.

A sixth aspect of the present invention provides an unread mark processing system, including: a client, a chat server and a table server;

the client is used for displaying a session list interface, and the session list interface comprises a session list and an unread mark; receiving operation information for clearing a target unread mark in the session list interface, and sending an unread mark processing request to the chat server; the unread tag processing request is used for clearing the target unread tag;

the chat server is used for forwarding the unread mark processing request of the client to the table server;

the table server is used for determining a record table corresponding to the client, deleting the session identifier corresponding to the target unread mark in the record table, and returning the deletion result to the chat server; the record table is used for storing session identifications corresponding to all unread marks in a session list interface of the client;

the chat server is also used for returning the deletion result to the client;

A seventh aspect of the present invention provides a computer-readable storage medium storing a computer program which, when executed by a processor, causes the processor to perform the steps of any of the unread mark processing methods described above.

An eighth aspect of the present invention provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer program, when executed by the processor, causes the processor to execute the steps of the unread mark processing method as described in any of the above.

According to the unread mark processing method, the unread mark processing device, the unread mark processing system, the readable storage medium of the computer and the computer equipment, a corresponding record table is created for the client, and the record table is used for storing session identifications corresponding to all the unread marks of the client; when a user needs to clear a target unread mark in a session list interface, an unread mark processing request is sent to a chat server through a client, the chat server searches a record table corresponding to the client, quickly deletes a session identifier corresponding to the target unread mark in the record table, and returns a deletion result to the client, so that the client clears the target unread mark in the session list interface. In the process, the chat server does not need to inquire the chat database and modify unread messages in the chat database into read messages, so that the expense of the chat database is greatly reduced; and because the record table of the client is specially used for recording the session identification corresponding to the unread mark, the processing efficiency of the chat server for inquiring and deleting the record table is very high, so that the efficiency of processing the unread mark by the client is improved.

Drawings

FIG. 1 is a diagram of an exemplary embodiment of an unread tag processing method;

FIG. 2(a) is a schematic diagram of a client session interface in one embodiment;

FIG. 2(b) is a schematic diagram that illustrates a client session interface, in one embodiment;

FIG. 2(c) is a diagram that illustrates a client session interface, in one embodiment;

FIG. 3 is a schematic flow chart of a current unread tag handling method;

FIG. 4 is a diagram showing an application environment of an unread mark processing method in another embodiment;

FIG. 5 is a flowchart illustrating a method for processing unread tags, according to an embodiment;

FIG. 6 is a diagram illustrating a structure of a record table corresponding to a client in one embodiment;

FIG. 7 is a flowchart illustrating an update process of a record table corresponding to a client in an embodiment;

FIG. 8 is a flowchart illustrating a method for processing unread marks according to another embodiment;

FIG. 9 is a timing diagram of a method of unread marks processing, under an embodiment;

FIG. 10 is a flowchart illustrating a method for processing unread marks according to another embodiment;

FIG. 11 is a block diagram showing the structure of an unread flag processing apparatus according to an embodiment;

FIG. 12 is a block diagram showing the construction of an unread mark processing apparatus according to another embodiment;

FIG. 13 is a block diagram of a computer device in one embodiment;

fig. 14 is a block diagram showing a configuration of a computer device in another embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

FIG. 1 is a diagram of an exemplary embodiment of an unread mark processing method. Referring to fig. 1, the unread tag processing method is applied to a system of social application software. The system includes a terminal 100, a chat server 200 and a chat database 300. The terminal 100 and the chat server 200 are connected through a network. A client providing a chat function based on which a user can initiate a conversation message to other users is installed in the terminal 100. Chat server 200 is used to manage sessions between users and to manage buddy relationships, such as: based on the friend relationship, after receiving a session message sent by a user, the chat server 200 may determine a target user of the session message, and send the session message to a client corresponding to the target user. Among them, the chat database 300 is mainly used for storing and managing conversation messages.

The terminal 100 may specifically be a desktop terminal or a mobile terminal, and the mobile terminal may specifically be at least one of a mobile phone, a tablet computer, a notebook computer, and the like. Chat server 200 may be implemented as a stand-alone server or as a server cluster of multiple servers. Chat database 300 may be integrated in chat server 200, or may exist independently from chat server 200, and when it exists independently, chat server 200 and chat database 300 are connected through a network, and chat database 300 may be implemented by a separate server or a server cluster composed of a plurality of servers.

Optionally, the client may be an APP or a browser. When the client is a browser, it can provide a chat function through a web page. The form of the client is not limited.

When a user uses the chat function of the client, the user generally needs to log in first, for example, by using a user name and a login password. The chat server 200 typically stores login information for the user. It should be noted that the client may provide other functions besides the chat function, for example, a function of viewing the dynamic state of a friend or a function of viewing a friend list. After the user logs in through the client, the user can switch among all the functional interfaces of the client.

In the embodiment of the invention, the chat function provided by the client can comprise single chat and group chat, wherein the single chat is one-to-one conversation between one user and another user based on respective clients, the group chat is a group formed by a plurality of users, and a plurality of people in the group are multi-person conversations based on respective clients.

In one embodiment, the chat function interface (also referred to as "session list interface") of the client may refer to fig. 2(a), where "buddy 1", "buddy 2" and "buddy 3" in fig. 2(a) represent different sessions, specifically, "buddy 1", "buddy 2" and "buddy 3" correspond to session 10, session 20 and session 30, respectively. The

sessions

10, 20, and 30 may be single chat sessions or group chat sessions. For example, when session 10 is a single chat session, "friend 1" actually represents one user; when the session 20 is a group chat session, "friend 2" effectively represents a group. When any session (whether a single chat session or a group chat session) in the session list interface has unread messages, an unread mark is displayed at the corresponding position of the session to remind a user that the session contains the unread messages, and after the user clicks the session to view the unread messages, the unread mark corresponding to the session disappears. Specifically, the unread mark may be a small red dot, a small red heart, or other representation. For example, as shown in fig. 2(a), the unread flag is a red dot, and a number representing the number of unread messages in the current session may also be displayed in the red dot. Wherein, the unread mark 101 corresponding to the session 10 is a red dot with a number 3, which represents that there are 3 unread messages in the session 10; the unread flag 201 corresponding to the conversation 20 is a red dot with the number 1, which represents that there are 1 unread messages in the conversation 20. And

unread marks

101 and 201 are displayed on the right side of the

sessions

10 and 20, respectively, so as not to obscure the friend information of the sessions. Of course, the unread tags may also be displayed elsewhere in the conversation, such as to the left, etc. The embodiment of the invention does not limit the display position of the unread mark. When the user clicks the session 10 to view the unread message, the unread mark 101 disappears; when the user clicks on the conversation 20 to view the unread messages, the unread tags 201 disappear.

It should be understood that the above description is only illustrative of the expression of the unread marks, and the embodiment of the present invention does not limit the specific expression of the unread marks.

When there are many friends or groups of the user, if the user does not view the conversation messages in time, the number of accumulated unread messages increases, resulting in a plurality of unread marks, such as a plurality of red dots, appearing in the conversation list interface. These red dots affect the user's normal viewing of the conversation messages and some users may wish to clear them for obsessive compulsive reasons. The current process for the user to remove these red dots is illustrated with reference to fig. 3, which includes:

in step S301, the user sends an unread mark processing request to the chat server 200 through the client.

Step S302, after receiving the request, the chat server 200 may query the chat database 300 for all session identifiers of the client according to the login user of the client; wherein the session identification is used to distinguish different sessions, in particular the session identification may be a session ID.

In step S303, the chat database 300 returns a session identifier list to the chat server 200, where the session identifier list includes all session identifiers in the session list interface of the client, including the session identifier of the session with the unread message, and may also include the session identifier of the session without the unread message.

In step S304, based on the session identifier list of the client, the chat server 200 initiates a message processing request to the chat database 300 for the first session identifier in the session identifier list.

In step S305, the chat database 300 marks the unread message corresponding to the first session identifier as a read message, and returns a message processing result to the chat server 200.

In step S306, the chat server 200 polls the session identifier list, and initiates a message processing request to the chat database 300 for the next session identifier in the session identifier list, until all session identifiers in the session identifier list are polled.

S307, the message processing result returned from the chat database 300 is returned to the client.

S308, the client receives the message processing result returned by the chat server 200, and removes the red dots in the session list interface.

However, based on this processing method of unread marks, when a user wants to clear a plurality of unread marks in the session list interface, the chat server 200 needs to interact with the chat database 300 a plurality of times, and the chat database 300 needs to modify the unread messages corresponding to the corresponding session identifiers into read messages, which is inefficient and the overhead of the chat database 300 is large.

In the embodiment of the present invention, the chat server 200 is further configured to manage record tables corresponding to different clients besides managing sessions and friend relationships between users, and when a user performs a session through a client, the chat server 200 creates a corresponding record table for different users, where the record table is used to store session identifiers corresponding to all unread marks in a client session list interface of the user. After a user logs in a client, in a session list interface of the client, if a session A contains an unread message, a record list corresponding to the client contains a session identifier of the session A; if the chat server 200 finds that the session identifier of the session a exists in the record table corresponding to the client, an unread mark corresponding to the session a is displayed in a session list interface of the client.

Based on the created record table, when the user wishes to clear the target unread tag in the session list interface of the client, an unread tag processing operation is initiated at the client, and an unread tag processing request is sent to the chat server 200 through the terminal 100. After receiving the unread tag processing request, the chat server 200 queries the record table corresponding to the client, deletes the session identifier corresponding to the target unread tag in the record table, and returns a deletion result to the client, so that the target unread tag of the client can be removed. In the process of removing the unread identifiers, the chat server 200 does not need to query the chat database 300, and the chat database 300 does not need to process the stored session messages, so that the overhead of the chat database 300 is reduced, and the removal efficiency is improved.

Referring to fig. 2(a), the target unread marks may be the unread marks 101 and the unread marks 102, and the corresponding clearing effect is shown in fig. 2 (b); the target unread mark may also be any one of the unread marks 101 and 102, and when the target unread mark is the unread mark 102, the corresponding clearing effect is shown in fig. 2 (c).

It should be noted that, as shown in fig. 2(a), a menu bar 50 and an expansion operation item 40 may also be included in the session list interface of the client. A plurality of operation items for switching the client function may be included in the menu bar 50, and include, but are not limited to, "home page", "chat", "dynamic", "game", and "unread mark". When the user triggers the "chat" action in menu bar 50, the client switches to the session list interface; in the session list interface, when the user triggers the dynamic operation item, the client switches to the friend dynamic interface. The expansion operation item 40 is used to expand more operation items, such as user setting, client display theme setting, and the like.

In some embodiments, a preset operation item is included in the session list interface of the client, and the preset operation item is an operation item for clearing the unread mark. Specifically, the preset operation item may be an "unread mark" operation item in the menu bar 50, through which the user may initiate an operation of unread mark processing operation. In the session list interface, when a user triggers an 'unread mark' operation item, a client is enabled to initiate an unread mark processing request. In other embodiments, the "unread flag" operation item may also be set under the extended operation item 40, and when the user needs to clear the unread flag, the extended operation item 40 is triggered, and the "unread flag" operation item is selected from the expanded operation items, so that the client initiates an unread flag processing request.

In an alternative embodiment, an application environment diagram of the unread mark processing method according to an embodiment of the present invention can also refer to fig. 4, which includes the terminal 100, the chat server 200, the chat database 300, and the table server 400. Chat server 200 is also connected to table server 400 via a network. The table server 400 may be implemented by a stand-alone server or a server cluster composed of a plurality of servers.

The table server 400 is configured to manage a record table, that is, create a corresponding record table in the table server 400 for different clients, where the record table is configured to store session identifiers corresponding to all unread marks in a session list interface of the client. Chat server 200, upon receiving an unread tag processing request from a client to remove a target unread tag, forwards the unread tag processing request to table server 400. Table server 400 determines the record table corresponding to the client according to the unread tag processing request, deletes the session identifier corresponding to the target unread tag in the record table, and returns the deletion result to chat server 200, and chat server 200 returns the deletion result to the client, so that the target unread tag in the client session list interface can be cleared. The present embodiment decouples the management function of the log sheet from the chat server 200 by providing the sheet server 400, so that the chat server 200 is lighter and more easily expanded.

Based on the above description of the application environment, in one embodiment, as shown in fig. 5, an unread markup processing method is provided, and is exemplified by applying the method to the chat server 200 in fig. 1. It will be appreciated that the method may also be used with the table server 400 of fig. 4.

As shown in fig. 5, the unread mark processing method may include the steps of:

s401, an unread mark processing request of a client is received.

The client can be any application software which provides a chat function and adopts an unread mark (such as a small red dot) to remind the user of an unread message. Specifically, the client includes but is not limited to a QQ, a WeChat, a short message inbox, and the like.

The unread tag processing request can be understood as a request for clearing a target unread tag in a client session list interface. The target unread tags may be all unread tags in the client session list interface, and the corresponding unread tag processing request is used to clear all unread tags in the client session list interface. The target unread tag may also be a partial unread tag in the client session list interface, and the corresponding unread tag processing request is used to clear the partial unread tag in the client session list interface.

Specifically, when the user needs to remove a plurality of unread marks at a time, the plurality of unread marks may be selected as target unread marks, or all of the unread marks may be selected at a time by a set operation item, or a plurality of unread marks satisfying the removal condition may be set as target unread marks by setting the removal condition. The clearing condition may be set according to a time condition, and may be, for example, a time condition, or an unread message number condition.

In one embodiment, the unread tag processing request carries client identification information, and the client identification information is used for uniquely identifying a corresponding client. In particular, the client identification information may be a client login user identification, such as a client login user ID. Of course, the client login user identifier may also include description information of other users. After receiving the unread tag processing request from the client, chat server 200 may identify the client currently requesting according to the client identification information carried in the unread tag processing request.

Optionally, after receiving the request for processing the unread mark, chat server 200 may also perform identity verification on the client. The identity check may include validity check of the client login user ID, whether the client login user is a blacklist user, and the like. If the identity verification of the client fails, filtering the unread mark processing request, and sending a corresponding error report message to the client; if the identity check is passed. By checking the identity of the client, the operation safety can be improved, and malicious operation can be prevented.

S402, determining a record table corresponding to the client.

As described in the foregoing embodiment, the record table corresponding to the client stores session identifiers corresponding to all unread marks in the session list interface of the client. In order to facilitate the differentiated management, different clients may have a record table respectively. Therefore, after receiving the request for processing the unread mark from the client, the chat server 200 can determine the record table corresponding to the client according to the client identification information.

Note that the record table corresponding to the client may be provided in chat server 200, or may be provided in a place separate from chat server 200, for example, in table server 400.

And S403, deleting the session identifier corresponding to the target unread mark in the record table corresponding to the client.

As described in the foregoing embodiment, in a session list interface of a client, if a session a contains an unread message, a record table corresponding to the client contains a session identifier of the session a; if the record table corresponding to the client has the session identifier of the session a, an unread mark is displayed at the corresponding position of the session a in the session list interface of the client. Therefore, after the session identifier corresponding to the target unread mark in the record table corresponding to the client is deleted, the target unread mark is cleared in the session list interface of the client.

S404, returning the deletion result to the client to clear the target unread mark of the client.

Optionally, when the target unread tags are all unread tags in the session list interface of the client, step S403 correspondingly returns the deletion result to the client in order to empty all session identifiers in the record table corresponding to the client, and all unread tags in the session list interface of the client are cleared. Optionally, when the target unread flag is a partial unread flag in the session list interface of the client, step S403 correspondingly returns the deletion result to the client for deleting a partial session identifier in the record table corresponding to the client, and the partial unread flag in the session list interface of the client is cleared. The cleaning effect is shown with reference to fig. 2(b) and 2(c), respectively.

The unread mark processing method is characterized in that a corresponding record table is created for the client, and session identifications corresponding to all unread marks of the client are stored through the record table. In the process of clearing the unread marks in the session list interface, the chat server 200 does not need to query the chat database 300 or modify the unread messages in the chat database 300 into read messages, thereby reducing the overhead of the chat database 300. And because the record table of the client is dedicated to record the session identifier corresponding to the unread mark, the chat server 200 has high processing efficiency for inquiring and deleting the record table, and a user can remove a plurality of unread marks in the session list interface at one time or remove one unread mark in the session list interface at one time, and both can be realized through the record table corresponding to the client. Regardless of the number of the unread marks to be cleared, the processing efficiency can be improved compared with the current unread mark processing method.

In one embodiment, the record table may be a sequence table. The order table can be understood as a record table in which elements in the table are automatically ordered according to a set rule. The setting rule may be set according to actual conditions, for example, the setting rule may be automatically sorted according to respective time information. The time information corresponding to an element in the table can be understood as the creation time of the element, or the update time of the element, etc. When the above-described record table is an order table, the table structure can be referred to as shown in fig. 6. The session identifier may be understood as an element in the table, and the session time corresponding to the session identifier may be used as time information corresponding to the element in the table. The session time corresponding to the session identifier may be understood as: and in the session corresponding to the session identification, the receiving time of the last unread message. The session identifiers in the record table may be sorted according to the session time, for example: sorting according to descending order of session time, so as to sort the session identifier with the nearest session time at the forefront position.

Based on the sequence table, a user can conveniently and quickly clear the unread marks corresponding to the sessions in the session list interface when the unread messages are received last time within the set time. This is further explained below.

In the session list interface of the client, the time when the unread message is received last time by different sessions may be different. In particular, some sessions receive unread messages earlier for the last time, for example, one week or even one month ago; some sessions last received unread messages are closer in time, such as the last day. Because the unread messages received at an earlier time are not important for the user, the reminding value of the corresponding unread marks is low, and if the unread marks are displayed in the session list interface all the time, the user is influenced to pay attention to the latest unread messages. Therefore, users often want to selectively clear the unread tags according to their corresponding session times. The session time corresponding to the unread tag may be understood as the time when the session corresponding to the unread tag receives the unread message last time.

Optionally, when the client initiates the unread tag processing request, a clearing time may also be specified. By specifying the clearing time, the unread marks of the session time within the set time in the session list interface can be cleared in batches. For example: when a client side initiates an unread mark processing request, appointing the clearing time to be one week ago to clear all unread marks of which the session time is one week ago and keep the unread marks of which the session time is within one week; or when the client side initiates an unread mark processing request, the clearing time is appointed to be 1-10 numbers in the current month, all unread marks with the session time in the current month 1-10 numbers are cleared, and the unread marks with the session time in the current month 11 number and later are reserved.

Further, in some embodiments, the preset operation item for clearing the unread message includes a time setting item, and when the target unread message is cleared, the user can set a clearing time through the time setting item, so as to clear the unread message of the session in the session list interface, where the unread message is received within the clearing time. Correspondingly, in step S401, the unread tag processing request may also carry clearing time information. In step S403, chat server 200 may delete the session identifier of the session time in the clearing time in the record table according to the clearing time information. And finally, returning the deletion result of the record table to the client, thereby clearing the unread identification of the session in the session list interface of the client within the clearing time when the unread message is received for the last time. When the record table is the sequence table, the session identifications in the table are sequenced according to the session time, so that the session identifications of the session time in the sequence table within the clearing time can be quickly determined, and the clearing efficiency can be further improved compared with an unordered record table.

Optionally, at the client, a preset operation item for clearing the unread marks may be set as an operation item triggered by one key, and when the user triggers the operation item, the client initiates an unread mark processing request for clearing all the unread marks in the session list interface on behalf of the user wishing to clear all the unread marks in the session list interface. Optionally, a preset operation item for clearing the unread flag may also be set as an operation item for calling out a clearing setting window, when the user triggers the preset operation item, a clearing setting window pops up in the current interface, the clearing setting window may include a time setting item, and based on the clearing setting window, the user may set the clearing time. It should be noted that, in addition to the setting time setting item, the clearing setting window may further include a control for setting other clearing conditions, which is not limited in this regard. By setting the clearing time, the user can quickly clear the unread marks with earlier session time in the session list interface, so that the user operation is more diversified.

Further, when the above-mentioned recording table is an order table, after step S403, the method may further include the steps of: and reordering the session identifications in the record table according to the session time. That is, when the target unread tag that the client wishes to clear is a partial unread tag in the session list interface, for example, the unread tag of the session that receives the unread message within the set time, in step S403, only a partial session identifier in the record table corresponding to the client needs to be deleted, and for the remaining session identifiers in the record table, the session identifiers may be reordered according to their respective session times. The session time is the receiving time of the last unread message in the session corresponding to the session identifier. By reordering the session identifiers in the record table, subsequent clearing operations can be performed efficiently.

In one embodiment, the unread mark processing method of the present invention may further include a step of managing a record table corresponding to the client. Managing the record table corresponding to the client may include: and creating at least one of a record table corresponding to the client, updating the record table corresponding to the client and deleting the record table corresponding to the client.

Creating a record table corresponding to the client may include: when a client receives a first unread message, a record table is created for the client; or, when the user logs in through the client, a record table is created for the client; alternatively, a record table is created for a client when a user registers through the client.

Deleting the record table corresponding to the client may include: when the session identifier in the record table corresponding to the client is emptied, the record table can be deleted in time, and the storage space of the server is released in time; or after the user logs in through the client, the record table corresponding to the client is kept until the user of the client logs out, and the record table corresponding to the client is deleted.

And the updating record table comprises session time corresponding to the session addition identifier, the session deletion identifier and the session modification identifier. The following describes each case.

As shown in fig. 7, in an embodiment, the case that the new session identifier modifies the session time corresponding to the session identifier may include:

in step S601, the chat server 200 detects that a friend of the client initiates a session message.

The friends of the client can be personal friends or group friends. In the social application software, when a friend of a client initiates a new session message to the client, the chat server 200 detects the session message initiated by the friend of the client.

Step S602, the chat server 200 obtains the time when the client receives the session message.

The time when the client receives the session message may be the time when the client forwards the session message to the client, as the time when the client receives the session message. In other embodiments, the client terminal may report its receiving time to the chat server 200 when actually receiving the session message, thereby obtaining the time when the client terminal receives the session message.

Further, the specific situation that the chat server 200 updates the record table corresponding to the client according to the time when the friend receives the session message and the client specifically may include:

step S603, querying whether a session identifier corresponding to the friend already exists in a record table corresponding to the client. If yes, go to step S604, otherwise go to step S605.

Step S604, updating the session time of the session identifier corresponding to the friend in the record table corresponding to the client according to the time when the client receives the session message.

Step S605, adding the session identifier corresponding to the friend in the record table corresponding to the client, and using the time when the client receives the session message as the session time of the session identifier corresponding to the friend.

That is, when the chat server 200 detects that a friend of the client initiates a new session message to the client, the chat server 200 records time information of the client receiving the session message of the friend, and queries whether a session identifier corresponding to the friend already exists in a record table corresponding to the client, if so, it indicates that the session between the client and the friend already corresponds to an unread mark, and at this time, only the session time corresponding to the session identifier in the record table needs to be modified into the time information of the client receiving the current session message of the friend. If the record table is the sequence table, after the session time corresponding to the session identifier in the record table is updated, the session identifiers in the table are automatically reordered according to the new session time. If the session identifier corresponding to the friend does not exist in the record table corresponding to the client, it is indicated that the session between the client and the friend does not have the corresponding unread mark, at this time, in order to display the unread mark near the session corresponding to the friend of the client, the session identifier of the session between the client and the friend needs to be newly added in the record table, and at the same time, the session time corresponding to the session identifier is recorded as the time when the client receives the current session message of the friend. If the record list is a sequence list, after the session identifier is newly added in the record list, the session identifiers in the list can be automatically sequenced according to respective session time.

Further, after the session identifier corresponding to the friend is added to the record table corresponding to the client, the addition result information may be sent to the client, so that the client displays a new unread mark.

Wherein, the condition of deleting the session identifier comprises: the method comprises the steps that a user initiates a reading mark processing request through an 'unread mark' operation item of a client, and initiates the unread mark processing request when the user views unread messages in a session corresponding to a target unread mark in a session list interface. In the former case, reference may be made to the description of the above embodiments, which is not repeated. The following describes a procedure of deleting a session id in the latter request.

In an embodiment, with reference to fig. 8, when a user views an unread message in a session corresponding to a target unread tag in a session list interface, a process of removing the target unread tag is as follows:

step S701, when the user views the unread message in the session corresponding to a certain unread tag in the session list interface, the client sends an unread tag processing request to the chat server 200.

When the client detects that the user opens a session corresponding to an unread tag and reads an unread message therein, the client may send an unread tag processing request to the chat server 200. The unread flag processing request in step S701 may also be understood as a notification to read the unread message. And the unread mark processing request is used for clearing the unread mark corresponding to the viewed session in the session list interface of the client. That is, the target unread tag is an unread tag corresponding to the viewed session in the session list interface.

The unread tag processing request sent by the client to the chat server 200 may carry identification information of the client and a session identifier of the viewed session. In the embodiment of the present invention, the identification information of the client may be a login user ID of the client, and the session identification may be a session ID.

In step S702, chat server 200 receives an unread flag processing request sent by a client.

In step S703, the chat server 200 determines the session identifier of the session viewed by the client according to the unread flag processing request.

Step S704, the chat server 200 determines the record table corresponding to the client.

In the embodiment of the present invention, different client sides have different record tables, so that the chat server 200 can determine the record table corresponding to the client side according to the identification information of the client side carried in the unread mark processing request.

Step S705, the chat server 200 deletes the session identifier corresponding to the target unread flag in the record table.

I.e. the chat server 200 deletes the session identity of the session the client is being viewed from the log table.

Step S706, the chat server 200 returns record table processing result information to the client to remove the unread mark corresponding to the viewed session in the session list interface of the client.

Through the embodiment, when the user normally views the unread messages, the record table corresponding to the client is also updated synchronously, and the presentation result at the client is that the unread marks of the viewed sessions of the client disappear. At present, the user normally views the unread messages, and the implementation mechanism that the unread marks of the viewed sessions of the client disappear requires the chat server 200 to access the chat database 300, so that the unread messages in the viewed sessions are modified into read messages. In contrast, in the embodiment of the present invention, the unread flag of the viewed session of the client is cleared based on the corresponding record table of the client, so that the clearing efficiency is improved.

In order to better understand the unread tag processing method according to the embodiment of the present invention, the following describes a processing procedure of the unread tag in the client session list interface with reference to fig. 9. In this embodiment, the processing procedure of the unread mark includes:

in step S801, when the user at the client 1 logs in, the friend initiates a session message to the client 1 through the client 2.

Step S802, the chat server 200 detects a session message initiated from the client 2 to the client 1, and performs identity verification on the client 2, and may also perform verification on the content of the session message.

When the identity of the client 2 is verified, validity of the user ID of the client 2 is verified, whether the user ID of the client 2 is in the blacklist is determined, and if the user ID of the client 2 is in the blacklist, the identity verification of the client 2 is not passed. If the identity verification of the client 2 fails, the forwarding of the session message of the client 2 is refused, and an error reminding message can be returned to the client 2.

The step of checking the content of the session message includes judging whether the session message contains a set sensitive word, and if the session message contains the set sensitive word, the content of the session message of the client 2 is not checked. If the content of the session message initiated by the client 2 is not verified, the session message of the client 2 is refused to be forwarded, and an error reminding message can be returned to the client 2.

When the identity check of the client 2 is passed and the content check of the session message is passed, the next step is executed.

At step S803, the chat server 200 may also send the session message of the client 2 to the chat database 300. Chat database 300 stores the session information and returns the processing result to chat server 200.

Step S804, the chat server 200 obtains the time when the client 1 receives the session message as the session time.

In some embodiments, the time when the session message is forwarded to the client 1 may be taken as the time when the client 1 receives the session message. In other embodiments, when client 1 actually receives the session message, it may report its receiving time to chat server 200, thereby obtaining the time when client 1 receives the session message.

In step S805, the chat server 200 transmits the session ID and the session time to the table server 400.

In this embodiment, the record table corresponding to the client is a sequence table, and the sequence table is managed by the table server 400.

Step S806, after receiving the session ID and the session time, the table server 400 determines whether a session identifier corresponding to the client 2 exists in the record table corresponding to the client 1; and if so, updating the session time of the session identifier of the client 2 in the record table corresponding to the client 1 according to the session time. If not, adding the session identifier corresponding to the client 2 in the record table corresponding to the client 1, and taking the time of the client 1 receiving the session message as the session time of the session identifier corresponding to the client 2. The table operation result is then returned to chat server 200.

In step S807, chat server 200 returns the table operation result to client 1.

Step S808, displaying the session corresponding to the client 2 and displaying the corresponding unread mark near the session in the session list interface of the client 1.

In the session list interface of the client 1, other sessions and unread marks corresponding to other sessions may also be displayed, for example, as shown in fig. 2, including session 10, session 20, and session 30, where the unread mark 101 corresponds to session 10 and the unread mark 201 corresponds to session 20. For the purpose of combining the above embodiments, the session 20 may be understood as a session corresponding to the client 2.

Step S809, the client 1 receives the operation information for clearing the target unread tag in the session list interface, and sends an unread tag processing request to the chat server 200.

The target unread marks may be all unread marks included in the session list interface of the client 1, or may be partial unread marks in the session list interface of the client 1.

Optionally, the unread flag processing request may carry clearing time information, which is used to clear the unread flag of the session in the session list interface, where the unread message is received within the clearing time. In other embodiments, the unread tags may not have a clearing time in the processing request, and is used to clear all the unread tags in the session list interface.

Specifically, a preset operation item for clearing the unread flag may be included in the session list interface of the client 1 (refer to the above-described embodiment). The receiving operation information for clearing the target unread mark in the session list interface and sending an unread mark processing request to the chat server 200 may include: receiving clearing operation information initiated by the preset operation item; acquiring the time set in the time setting item as clearing time; if the clearing time is a null value, sending a first unread tag processing request to the chat server 200; if the clearing time is not null, sending a second unread mark processing request to the chat server 200; the first unread tag processing request is used for clearing all unread tags in the session list interface; and the second unread tag processing request is used for clearing the unread tag of the session in the session list interface, in which the unread message is received within the clearing time, so that the second unread tag processing request is required to carry the information of the clearing time.

In step S810, after receiving the unread flag processing request, the chat server 200 first performs identity verification and parameter verification for the client 1.

The identity verification process of the client 1 is similar to that of the client 2, and is not described in detail. The parameter checking may include checking a clearing time parameter carried in the unread tag processing request, for example, detecting whether the clearing time is greater than the current time, or the clearing time is earlier than the set historical time.

And when any check result in the identity check and the parameter check of the client 1 is failed, filtering the unread mark processing request at the time, and returning a corresponding error prompt to the client 1. And when the identity verification result and the parameter verification result of the client 1 both pass, executing the next step.

In step S811, chat server 200 forwards the unread flag processing request to table server 400.

In step S812, the table server 400 determines the record table corresponding to the client 1, and deletes the session identifier corresponding to the target unread flag in the record table.

In the table server 400, a corresponding record table is created for the client 1, and the record table is used for storing session identifiers corresponding to all unread marks of the client 1.

In step S813, table server 400 returns the table processing result to chat server 200.

In step S814, chat server 200 returns the table processing result to client 1.

Step S815, the client 1 receives the table processing result, and clears the target unread flag in the session list interface.

In the unread tag processing method of the foregoing embodiment, the table server 400 creates a corresponding record table for the client, where the record table is used to store session identifiers corresponding to all the unread tags of the client; when a user initiates a session message, the table server 400 updates the record table corresponding to the client in real time, so as to maintain the session identifier containing the unread message in the record table. When a user needs to clear a target unread mark in a session list interface, an unread mark processing request is sent to the chat server 200 through a client, the chat server 200 sends the unread mark processing request to the table server 400, the table server 400 quickly deletes a session mark corresponding to the target unread mark in the table by inquiring a record table corresponding to the client, and returns a deletion result to the chat server 200, and the chat server 200 returns the deletion result to the client, so that the client clears the target unread mark in the session list interface. In the process, the chat server 200 does not need to query the chat database 300 or modify unread messages in the chat database 300 into read messages, so that the overhead of the chat database 300 is greatly reduced; and because the record table of the client is specially used for recording the session identification corresponding to the unread mark, the processing efficiency of inquiring and deleting the record table is very high, so that the efficiency of processing the unread mark by the client is improved.

In an embodiment, as shown in fig. 10, an embodiment of the present invention further provides an unread flag processing method, and the method is described as an example where the method is applied to the terminal 100. The method comprises the following steps:

step S901, displaying a session list interface of the client; the conversation list interface comprises a conversation list and an unread mark.

A menu bar and an expansion operation item can be contained in the session list interface of the client. Specifically, reference may be made to fig. 2(a) and the above-mentioned embodiments, which are not repeated herein.

Step S902, receiving operation information for clearing the target unread flag in the session list interface.

The operation of clearing the target unread tag in the session list interface may be initiated through a preset operation item in the session list interface, or initiated when the user views the session corresponding to the unread tag, which may be specifically referred to in the above embodiments and is not described in detail.

Step S903, sends an unread mark processing request to chat server 200.

And creating a corresponding record table for the client, and storing the session identification corresponding to all unread marks of the client through the record table. The log may be stored in chat server 200. Sending an unread tag processing request to the chat server 200, for triggering the chat server 200 to determine the record table corresponding to the client, and deleting the session identifier corresponding to the target unread tag in the record table.

Of course, the log table may be stored in table server 400 separately from chat server 200. Sending an unread tag processing request to the chat server 200, sending the unread tag processing request to the table server 400 through the chat server 200, determining a record table corresponding to the client by the table server 400, and deleting the session identifier corresponding to the target unread tag in the record table. And optionally the record table may be a sequential table. For the record table corresponding to the client, reference may be specifically made to the above-mentioned embodiment, which is not described in detail.

Step S904, receiving the deletion result returned by the chat server 200.

The response result returned by chat server 200 includes the deletion result of the session identifier corresponding to the target unread tag in the record table.

Step S905, clear the target unread flag in the session list interface.

Because a corresponding record table is created for the client, session identifiers corresponding to all unread marks of the client are stored through the record table, once, when a user needs to clear a target unread mark in a session list interface of the client, the chat server 200 quickly deletes the session identifier corresponding to the target unread mark in the record table by inquiring the record table corresponding to the client, and returns a deletion result to the client, so that the client clears the target unread mark in the session list interface. In the process, the chat server 200 does not need to query the chat database 300 or modify unread messages in the chat database 300 into read messages, so that the overhead of the chat database 300 is greatly reduced; moreover, because the record table of the client is dedicated to record the session identifier corresponding to the unread mark, the efficiency of processing query and deletion of the record table by the chat server 200 is high, so that the efficiency of processing the unread mark by the client is improved.

In an embodiment, when the session list interface includes a preset operation item for clearing an unread flag, for example, an "unread flag" operation item, in the step S901, receiving operation information for clearing a target unread flag in the session list interface may specifically include: and receiving the operation information of the preset operation item to obtain the operation information for clearing the target unread mark in the session list interface.

Since the corresponding unread mark is also cleared when the user normally views the unread message, in another embodiment, in the step S901, the receiving the operation information for clearing the target unread mark in the session list interface may further include: and receiving operation information for viewing the unread messages in the conversation corresponding to the target unread marks in the conversation list interface, and obtaining the operation information for clearing the target unread marks in the conversation list interface.

In one embodiment, the client may also clear the unread id in the session list by session time. Correspondingly, after receiving the operation information of the preset operation item of the client, acquiring the time set in the user passing time setting item as the clearing time, and if the clearing time is a null value, sending a first unread mark processing request to the chat server 200; and if the clearing time is not null, sending a second unread mark processing request to the chat server 200. The first unread mark processing request is used for clearing all unread marks in the session list interface; the second unread tag processing request is used for clearing the unread tag of the session in the session list interface, in which the unread message is received within the clearing time, so that the second unread tag processing request carries the information of the clearing time.

Through the embodiment, the user can autonomously set the clearing time based on the client, and the user can quickly clear the unread mark with the earlier session time in the session list interface, so that the user operation is more diversified.

It should be understood that, in the flowchart of the unread flag processing method in the above embodiments, the respective steps are sequentially displayed as indicated by arrows, but the steps are not necessarily sequentially executed in the order indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flow diagram of the unread mark processing method in the above embodiments may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or the stages is not necessarily sequential, but may be performed alternately or alternatingly with other steps or at least a part of the sub-steps or stages of other steps.

Based on the same idea as the unread mark processing method in the above-described embodiments, an unread mark processing apparatus is also provided herein.

In one embodiment, as shown in fig. 11, an unread tag processing device 001 of this embodiment may be applied to the chat server 200 or the table server 400, where the unread tag processing device 001 includes: a request receiving module 110, a table determining module 120, a table processing module 130, and a result returning module 140, each of which is detailed as follows:

a request receiving module 110, configured to receive an unread tag processing request of a client; and the unread mark processing request is used for clearing the target unread mark in the session list interface of the client.

A table determining module 120, configured to determine a record table corresponding to the client; and the record table is used for storing the session identifications corresponding to all the unread marks of the client.

A table processing module 130, configured to delete the session identifier corresponding to the target unread flag in the record table.

A result returning module 140, configured to return the deletion result to the client, so as to clear the target unread flag of the client.

Through the unread tag processing apparatus 001 of the above embodiment, when a user needs to remove a target unread tag in a session list interface of a client, the session identifier corresponding to the target unread tag in the record table is quickly deleted by querying the record table corresponding to the client, and the deletion result is returned to the client, so that the client removes the target unread tag in the session list interface. In the process, the chat database 300 does not need to be inquired, and unread messages in the chat database 300 do not need to be modified into read messages, so that the expense of the chat database 300 is reduced; and because the record table of the client is specially used for recording the session identification corresponding to the unread mark, the processing efficiency of inquiring and deleting the record table is very high, so that the efficiency of processing the unread mark by the client is improved.

In one embodiment, the record table is a sequential table; the session identifiers in the record table are sorted according to session time; and the session time is the receiving time of the last unread message in the session corresponding to the session identifier.

In one embodiment, the target unread tag includes: all unread marks in a session list interface of the client; the table processing module 130 is specifically configured to: and clearing the session identification in the record table.

In one embodiment, the target unread tag includes: a part of unread marks in a session list interface of the client; the table processing module 130 is specifically configured to: clearing part of session identifications in the record table; and the part of session identification is the session identification corresponding to the target unread mark.

In one embodiment, the target unread tag includes: an unread mark of a conversation of an unread message is received in a conversation list interface of the client within a set time; the table processing module 130 is specifically configured to: and deleting the session identification of the session time in the set time in the record table.

In an embodiment, the table processing module 130 may be further configured to reorder the session identifiers in the record table according to the session time.

In one embodiment, the unread mark processing device 001 further includes:

the message detection module is used for detecting a friend initiating session message of the client;

a session time obtaining module, configured to obtain time for the client to receive the session message;

and the table updating module is used for updating the record table corresponding to the client according to the time when the friend and the client receive the session message.

In one embodiment, the table update module has a module comprising:

a table query unit, configured to determine whether a session identifier corresponding to the friend exists in a record table corresponding to the client;

a first updating unit, configured to update, according to the time when the client receives the session message, the session time of the session identifier corresponding to the friend in the record table corresponding to the client if the query result of the table querying unit is yes;

and the second updating unit is used for increasing the session identifier corresponding to the friend in the record table corresponding to the client if the query result of the table query unit is negative, and taking the time of the client receiving the session message as the session time of the session identifier corresponding to the friend.

In one embodiment, the unread mark processing device 001 further includes:

and the message storage module is used for sending the adding result information to the client after the session identification corresponding to the friend is added in the record table corresponding to the client so as to enable the client to display a new unread mark.

In one embodiment, as shown in fig. 12, the unread mark processing device 002 of the present embodiment may be applied to the terminal 100, and the unread mark processing device 002 includes:

a display module 210, configured to display a session list interface of a client; the conversation list interface comprises a conversation list and an unread mark.

An operation information receiving module 220, configured to receive operation information for clearing the target unread tag in the session list interface.

Request sending module 230, configured to send an unread markup processing request to chat server 200.

A response receiving module 240, configured to receive a response result returned by the chat server 200 for the unread mark processing request; the response result comprises a deletion result of the session identification corresponding to the target unread mark in the record table; the record table is a record table corresponding to the client and is used for storing session identifications corresponding to all unread marks of the client;

a mark clearing module 250, configured to clear the target unread mark in the session list interface.

With the unread tag processing apparatus 002 of the above embodiment, when the user needs to remove the target unread tag in the session list interface of the client, the unread tag processing request is sent to the chat server 200, and the chat server 200 quickly deletes the session identifier corresponding to the target unread tag in the record table by querying the record table corresponding to the client, and returns the deletion result to the client, so that the client removes the target unread tag in the session list interface. In the process, the chat server 200 does not need to query the chat database 300 or modify unread messages in the chat database 300 into read messages, so that the overhead of the chat database 300 is reduced; and because the record table of the client is specially used for recording the session identification corresponding to the unread mark, the processing efficiency of inquiring and deleting the record table is very high, so that the efficiency of processing the unread mark by the client is improved.

In one embodiment, the session list interface includes preset operation items; the preset operation item is an operation item for clearing an unread mark; the operation information receiving module 220 includes:

the first receiving unit is used for receiving the operation information of the preset operation item to obtain the operation information for clearing the target unread mark in the session list interface;

and/or the presence of a gas in the gas,

and the second receiving unit is used for receiving and viewing the operation information of the unread messages in the session corresponding to the target unread marks in the session list interface, and obtaining the operation information for clearing the target unread marks in the session list interface.

In one embodiment, the preset operation item comprises a time setting item. The first receiving unit is further configured to acquire the time set in the time setting item as the clearing time.

The request sending module 230 includes: a first sending unit, configured to send a first unread tag processing request to the chat server 200 if the clearing time is null; a second sending unit, configured to send a second unread tag processing request to the chat server 200 if the clearing time is not null.

The first unread mark processing request is used for clearing all unread marks in the session list interface; and the second unread message processing request is used for clearing the unread message of the session which receives the unread message within the clearing time in the session list interface.

The present invention also provides an embodiment of an unread indicia processing system, the unread indicia processing system comprising: a client and a chat server 200.

The client is used for displaying a session list interface, and the session list interface comprises a session list and an unread mark; receiving operation information for clearing the target unread mark in the session list interface, and sending an unread mark processing request to the chat server 200; the unread tag processing request is used for clearing the target unread tag;

the chat server 200 is configured to receive the unread tag processing request, determine a record table corresponding to the client, delete the session identifier corresponding to the target unread tag in the record table, and return the deletion result to the client; the record table is used for storing session identifications corresponding to all unread marks in a session list interface of the client;

The present invention also provides an embodiment of an unread indicia processing system, the unread indicia processing system comprising: the method comprises the following steps: client, chat server 200, and table server 400;

the client is used for displaying a session list interface, and the session list interface comprises an unread mark; receiving operation information for clearing the target unread mark in the session list interface, and sending an unread mark processing request to the chat server 200; the unread tag processing request is used for clearing the target unread tag;

the chat server 200 is configured to forward the unread mark processing request of the client to the table server 400;

the table server 400 is configured to determine a record table corresponding to the client, delete the session identifier corresponding to the target unread tag in the record table, and return the deletion result to the chat server 200; the record table is used for storing session identifications corresponding to all unread marks in a session list interface of the client;

the chat server 200 is further configured to return the deletion result to the client;

FIG. 13 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer device may specifically be chat server 200 (or table server 400) in fig. 4. As shown in fig. 13, the computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may further store a computer program that, when executed by the processor, causes the processor to implement the unread mark processing method. The internal memory may also have a computer program stored therein, which when executed by the processor, causes the processor to perform the unread mark processing method.

Fig. 14 is a diagram showing an internal structure of a computer device in another embodiment. The computer device may specifically be the terminal 100 in fig. 4. As shown in fig. 14, the computer apparatus includes a processor, a memory, a network interface, a display screen, and an input device, which are connected through a system bus. Wherein the processor is configured to provide computing and control capabilities; the memory comprises a nonvolatile storage medium and an internal memory, wherein the nonvolatile storage medium stores an operating system and a computer program, and the internal memory provides an environment for the operation of the operating system and the computer program in the nonvolatile storage medium; the network interface is used for communicating with an external terminal 100 through network connection; the computer program is executed by a processor to implement an unread markup handling method; the display screen can be a liquid crystal display screen or an electronic ink display screen; the input device may be a touch layer covered on a display screen, or may be a key, a track ball or a touch pad arranged on a casing of the computer device, or may be an external keyboard, a touch pad or a mouse, etc.

Those skilled in the art will appreciate that the configurations shown in fig. 13 and 14 are block diagrams of only some configurations relevant to the present disclosure, and do not constitute a limitation on the computing devices to which the present disclosure may be applied, and that a particular computing device may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, the unread mark processing apparatus provided by the present application may be implemented in the form of a computer program, and the computer program may be run on a computer device as shown in fig. 13 and fig. 14. The memory of the computer device may store various program modules constituting the unread mark processing apparatus, such as the request receiving module 110, the table determining module 120, the table processing module 130, and the result returning module 140 shown in fig. 11. The computer program constituted by the respective program modules causes the processor to execute the steps in the unread mark processing method of the corresponding embodiment of the present application described in the present specification.

In one embodiment, a computer device is provided, comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform the steps of the above-described unread mark processing method. The steps of the unread mark processing methods herein may be steps in the unread mark processing methods of the respective embodiments described above.

In one embodiment, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, causes the processor to perform the steps of the above-described unread mark processing method. The steps of the unread mark processing methods herein may be steps in the unread mark processing methods of the respective embodiments described above.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent application shall be subject to the appended claims.

Claims

1. An unread tag processing method, comprising:

and returning a deletion result to the client to clear the target unread mark of the client.

2. The method of claim 1,

the record table is a sequence table;

the session identifiers in the record table are sorted according to session time;

and the session time is the receiving time of the last unread message in the session corresponding to the session identifier.

3. The method of claim 1,

the target unread mark includes: all unread marks in a session list interface of the client;

the deleting the session identifier corresponding to the target unread mark in the record table includes: and clearing the session identification in the record table.

4. The method of claim 2,

the target unread tag includes: receiving an unread mark of a session of an unread message within a set time in a session list interface of the client;

the deleting the session identifier corresponding to the target unread mark in the record table includes: and deleting the session identification of the session time in the set time in the record table.

5. The method according to any one of claims 2 to 4, further comprising:

detecting that a friend of the client initiates a session message;

acquiring the time for the client to receive the session message;

and updating a record table corresponding to the client according to the time when the friend and the client receive the session message.

6. The method according to claim 5, wherein said updating the record table corresponding to the client according to the time when the buddy and the client receive the session message comprises:

determining whether a session identifier corresponding to the friend exists in a record table corresponding to the client;

if so, updating the session time of the session identifier corresponding to the friend in the record table corresponding to the client according to the time for receiving the session message by the client;

if not, adding the session identifier corresponding to the friend in the record table corresponding to the client, and taking the time when the client receives the session message as the session time of the session identifier corresponding to the friend.

7. An unread mark processing method, comprising:

sending an unread tag processing request aiming at the target unread tag to a chat server;

receiving a response result returned by the chat server aiming at the unread mark processing request; the response result comprises a deletion result of the session identification corresponding to the target unread mark in the record table; the record table is a record table corresponding to the client and is used for storing session identifications corresponding to all unread marks of the client;

and clearing the target unread marks in the session list interface.

8. The method according to claim 7, wherein the session list interface comprises preset operation items; the preset operation item is an operation item for clearing an unread mark;

the receiving operation information for clearing the target unread mark in the session list interface includes:

and receiving the operation information of the preset operation item to obtain the operation information for clearing the target unread mark in the session list interface.

9. The method according to claim 8, wherein the preset operation item comprises a time setting item;

after receiving the operation information of the preset operation item of the client, the method further includes:

acquiring the time set in the time setting item as clearing time;

if the clearing time is a null value, sending a first unread mark processing request to the chat server;

if the clearing time is not null, sending a second unread mark processing request to the chat server;

10. An unread indicia processing apparatus, the apparatus comprising:

and the result returning module is used for returning a deletion result to the client so as to clear the target unread mark of the client.

11. The apparatus of claim 10,

the recording table is a sequence table;

12. The apparatus of claim 10,

the target unread tag includes: all unread marks in a session list interface of the client;

the table processing module is specifically configured to: and clearing the session identification in the record table.

13. The apparatus of claim 11, wherein the target unread tag comprises: an unread mark of a conversation of an unread message is received in a conversation list interface of the client within a set time;

the table processing module is specifically configured to: and deleting the session identification of the session time in the set time in the record table.

14. The apparatus according to any one of claims 11-13, further comprising in the unread mark processing means:

15. The apparatus of claim 14, wherein the table update module comprises:

a first updating unit, configured to update, if the query result of the table querying unit is yes, the session time of the session identifier corresponding to the friend in the record table corresponding to the client according to the time when the client receives the session message;

and the second updating unit is used for increasing the session identification corresponding to the friend in the record table corresponding to the client if the query result of the table query unit is negative, and taking the time of the client for receiving the session message as the session time of the session identification corresponding to the friend.

16. An unread mark processing apparatus, characterized in that said apparatus comprises:

a request sending module, configured to send an unread tag processing request for the target unread tag to a chat server;

a response receiving module, configured to receive a response result returned by the chat server for the unread mark processing request; the response result comprises a deletion result of the session identifier corresponding to the target unread mark in the record table; the record table is a record table corresponding to the client and is used for storing session identifications corresponding to all unread marks of the client;

17. The apparatus according to claim 16, wherein the session list interface includes preset operation items; the preset operation item is an operation item for clearing an unread mark;

the operation information receiving module includes:

and the first receiving unit is used for receiving the operation information of the preset operation item to obtain the operation information for clearing the target unread mark in the session list interface.

18. The apparatus according to claim 17, wherein the preset operation item comprises a time setting item; the first receiving unit is further configured to:

acquiring the time set in the time setting item as clearing time;

the request sending module comprises:

a first sending unit, configured to send a first unread tag processing request to the chat server if the clearing time is a null value;

a second sending unit, configured to send a second unread tag processing request to the chat server if the clearing time is not null;

the first unread tag processing request is used for clearing all unread tags in the session list interface; and the second unread message processing request is used for clearing the unread message of the session which receives the unread message within the clearing time in the session list interface.

19. An unread tag processing system, comprising: a client and a chat server;

the client is used for displaying a session list interface, and the session list interface comprises an unread mark; receiving operation information for clearing a target unread mark in the session list interface, and sending an unread mark processing request aiming at the target unread mark to the chat server;

the chat server is used for receiving the unread mark processing request, determining a record table corresponding to the client, deleting the session identifier corresponding to the target unread mark in the record table, and returning a deletion result to the client; the record table is used for storing session identifications corresponding to all unread marks in a session list interface of the client;

20. An unread tag processing system, comprising: a client, a chat server and a table server;

the table server is used for determining a record table corresponding to the client, deleting the session identifier corresponding to the target unread mark in the record table, and returning a deletion result to the chat server; the record table is used for storing session identifications corresponding to all unread marks in a session list interface of the client;

the chat server is also used for returning the deletion result to the client;

the client is further configured to receive the deletion result, and clear the target unread mark in the session list interface.

21. A computer-readable storage medium, storing a computer program which, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 9.

22. A computer device comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 9.