Message duplicate removal method and device, computer equipment and computer readable storage medium
By comparing the messages currently displayed on the device screen with historical messages, and removing duplicate message entities, the problem of repeated messages occupies memory and increases processing pressure when message scrolling is solved, and message deduplication is achieved, reducing the load on the device and server.
Patent Information
- Application Number
- CN202410986810.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-19
- Publication Date
- 2024-11-29
AI Technical Summary
In the automatic reply scenario, when the message displayed on the device screen is scrolling, duplicate messages will appear when obtaining messages, occupying terminal memory and increasing processing pressure.
By obtaining the control attribute information and storage address of the target message currently displayed on the device screen, comparing the repetition of the historical message, removing the duplicate message entity, and generating a deduplication message record.
Reduce the number of messages obtained by the device, reduce message processing pressure, and reduce server parsing and storage pressure.
Smart Images

Figure CN119045714A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a message deduplication method, apparatus, computer equipment and computer-readable storage medium, wherein the storage medium is a computer-readable storage medium and the product is a computer program product. Background Art
[0002] In some scenarios, it is necessary to obtain the messages displayed on the device screen. For example, in the automatic reply scenario, it is necessary to obtain the messages displayed on the device screen and report them to the server. Currently, the terminal will obtain and save all the messages displayed on the device screen. When the device screen scrolls to display messages, the messages displayed on the screen may not slide out of the screen all at once. In this case, if all the messages are obtained, there will be many duplicate messages in the obtained messages, which will occupy the terminal's memory and put a lot of pressure on the terminal to process the messages later. Summary of the invention
[0003] The embodiments of the present application provide a message deduplication method, apparatus, computer device and computer-readable storage medium, which can remove the message entities of the to-be-deduplicated messages that are repeated in the historical messages in the target message currently displayed on the device screen, obtain the deduplicated message records, reduce the number of messages obtained by the device, and thereby reduce the device's processing pressure on the messages.
[0004] A message deduplication method provided in an embodiment of the present application includes:
[0005] Acquire first control attribute information of a message control associated with a target message currently displayed on a device screen, and acquire a first storage address corresponding to the target message, wherein a space corresponding to the first storage address is used to store the first control attribute information, and different target messages currently displayed on the device screen correspond to different first storage addresses;
[0006] Acquire the message type of the target message, and generate a first message entity corresponding to the target message based on the message type of the target message and at least part of the corresponding first control attribute information;
[0007] Acquire a second storage address and a second message entity corresponding to the historical message historically displayed on the device screen;
[0008] Determine, based on the first storage address and the first message entity, and the second storage address and the second message entity, messages to be deduplicated that are repeated with the historical messages in the target message;
[0009] The message entity of the message to be deduplicated is removed from the first message entity to obtain a deduplicated message record on the device screen.
[0010] Accordingly, an embodiment of the present application also provides a message deduplication device, including:
[0011] an information acquisition unit, used to acquire first control attribute information of a message control associated with a target message currently displayed on a device screen, and to acquire a first storage address corresponding to the target message, wherein a space corresponding to the first storage address is used to store the first control attribute information, and different target messages currently displayed on the device screen correspond to different first storage addresses;
[0012] A type acquisition unit, configured to acquire a message type of the target message, and generate a first message entity corresponding to the target message based on the message type of the target message and at least part of the corresponding first control attribute information;
[0013] An entity acquisition unit, configured to acquire a second storage address and a second message entity corresponding to the historical message historically displayed on the device screen;
[0014] A comparing unit, configured to determine, based on the first storage address and the first message entity, and the second storage address and the second message entity, messages to be deduplicated in the target message that are repeated with the historical message;
[0015] A deduplication unit is used to remove the message entity of the message to be deduplicated from the first message entity to obtain a deduplicated message record on the device screen.
[0016] Correspondingly, an embodiment of the present application also provides a computer device, including a memory and a processor; the memory stores a computer program, and the processor is used to run the computer program in the memory to execute any message deduplication method provided in the embodiment of the present application.
[0017] Correspondingly, an embodiment of the present application also provides a computer-readable storage medium, which is used to store a computer program, and the computer program is loaded by a processor to execute any message deduplication method provided in the embodiment of the present application.
[0018] The embodiment of the present application obtains the first control attribute information of the message control associated with the target message currently displayed on the device screen, and obtains the first storage address corresponding to the target message, the space corresponding to the first storage address is used to store the first control attribute information, and the first storage addresses corresponding to different target messages currently displayed on the device screen are different; obtains the message type of the target message, and generates a first message entity corresponding to the target message based on the message type of the target message and at least part of the information in the corresponding first control attribute information; obtains the second storage address and the second message entity corresponding to the historical messages historically displayed on the device screen; determines the to-be-deduplicated messages in the target message that are repeated with the historical messages based on the first storage address and the first message entity, and the second storage address and the second message entity; removes the message entity of the to-be-deduplicated messages from the first message entity, and obtains the deduplicated message record of the device screen.
[0019] The embodiment of the present application can remove the message entity of the target message currently displayed on the device screen that is repeated with the historical message, obtain the message record after deduplication, reduce the number of messages obtained by the device, and thus reduce the pressure on the device to process messages. In addition, if the device needs to upload the message entity to the server, the repeated reporting of the message can be reduced, thereby reducing the pressure on the server to parse the message and reducing the storage pressure on the server. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.
[0021] Figure 1 is a flow chart of a message deduplication method provided by an embodiment of the present application;
[0022] Figure 2 This is a schematic diagram of a message list before and after the device screen is scrolled provided in an embodiment of the present application;
[0023] Figure 3 This is a schematic diagram of a message list after deduplication provided in an embodiment of the present application;
[0024] Figure 4 It is a schematic diagram of a message deduplication device provided in an embodiment of the present application;
[0025] Figure 5 It is a schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0026] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.
[0027] The embodiment of the present application provides a message deduplication method, device, computer equipment and computer readable storage medium. The message deduplication device can be integrated in a computer equipment, which can be a server or a terminal.
[0028] The terminal may include a mobile phone, a wearable smart device, a tablet computer, a laptop computer, a personal computer (PC), and a vehicle-mounted computer.
[0029] Among them, the server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), as well as big data and artificial intelligence platforms.
[0030] It should be noted that the description order of the following embodiments is not intended to limit the preferred order of the embodiments.
[0031] This embodiment will be described from the perspective of a message deduplication device. The message deduplication device may be integrated into a computer device, which may be a server or a terminal.
[0032] The present application provides a message deduplication method, such as Figure 1 As shown, the specific process of the message deduplication method can be as follows:
[0033] 101. Obtain first control attribute information of a message control associated with a target message currently displayed on a device screen, and obtain a first storage address corresponding to the target message. The space corresponding to the first storage address is used to store the first control attribute information. Different target messages currently displayed on the device screen correspond to different first storage addresses.
[0034] Since the content displayed on the device screen can change with the operation on the device screen, for example, when a scrolling operation is performed on the device screen, the content displayed on the device screen scrolls, and the content displayed before and after the scrolling of the device screen may be completely the same, completely different, or partially the same.
[0035] For example, for a message list, the device screen can display part of the messages in the message list, and can scroll to display other messages in the message list, and the target message currently displayed on the device screen includes at least part of the message currently displayed on the device screen.
[0036] The message controls associated with the target message include controls for displaying information such as the message content of the target message on the device screen. The message controls may include interactive controls and non-interactive controls. Interactive controls can be used to display the information of the target message and can trigger the terminal (computer device) to respond to the user's operations. Non-interactive controls are used to display the information of the target message but do not support interactive interface elements.
[0037] For example, the target message includes the sender's nickname, avatar, message content, etc. The message controls associated with the target message may include a control for displaying the sender's nickname, a control for displaying the avatar, a control for the message content, etc. The message content may be text content, pictures, videos, or link cards, etc. The link card can be used to jump to the page indicated by the link, and the card content is displayed through the page.
[0038] The first control attribute information of the message control can describe the attributes of the message control. The first control attribute information may include the control ID of the target message control, the display position on the control device screen, the control type, the control description, the content displayed on the control, whether the control is operable and other information. The control type corresponds to the type of content displayed. For example, the control type for displaying text content is text type, and the control type for displaying picture content is picture type, etc.
[0039] A target message can be associated with one or more message controls.
[0040] The first storage address corresponding to the target message may be the address of a storage space for storing first control attribute information of a message control included in the target message.
[0041] The first control attribute information corresponding to different target messages displayed on the device screen is stored in different locations, so the first storage addresses corresponding to different target messages are different, and before the target message slides out of the device screen, the first storage address corresponding to the target message remains unchanged. Since the corresponding first storage address remains unchanged before the target message slides out of the device screen, it can be determined based on the first storage address whether the target message on the device screen is the same as the historically displayed message.
[0042] Optionally, after the target message slides out of the device screen, its first attribute information may be deleted from the storage space, and the vacated storage space may be used to store the first message attribute information of the target message newly displayed on the device screen.
[0043] For example, when updating the content displayed on the device screen, the device may store the control attribute information of each target message on the device screen in the storage space according to the updated content, and record the storage address.
[0044] The device can obtain the storage address, and obtain the first control attribute information according to the storage address.
[0045] In one embodiment, the target message currently displayed on the device screen and the historical messages displayed historically may be the messages displayed on the device screen before and after the scrolling operation, that is, before the step of "obtaining the first control attribute information of the message control associated with the target message currently displayed on the device screen", the message deduplication method provided in the embodiment of the present application may further include:
[0046] Receiving a scrolling event for the device screen, and updating the display of the device screen in response to the scrolling event;
[0047] The above-mentioned historical messages include a screen of messages displayed on the above-mentioned device screen before the above-mentioned scrolling event is responded to, and the above-mentioned target messages include a screen of messages displayed on the above-mentioned device screen after the above-mentioned scrolling event is responded to.
[0048] A scrolling event may be an event triggered by a scrolling operation detected by the device on the device screen. In response to the scrolling event, the device updates the display of the device screen. If the content of the graphical user interface displayed on the device screen has reached the bottom, the content displayed on the device screen remains unchanged after the display is updated. If the content of the graphical user interface displayed on the device screen has not reached the bottom, the content displayed on the device screen changes after the display is updated.
[0049] Optionally, the scrolling event indicates that the distance for scrolling the content displayed on the device screen is less than or equal to one screen.
[0050] A scrolling event for the device screen is received, and the device screen is updated in response to the scrolling event. At this time, the message displayed on the device screen is the first control attribute information corresponding to the target message.
[0051] The historical message may refer to a screen message displayed on the device screen before the scrolling event is responded to. Suppose the device screen displays message ABCD, receives a scrolling event, and updates the device screen in response to the scrolling event. After the display is updated, the device screen displays message CDFG. Then the target message is message CDFG, and the historical message is message ABCD.
[0052] In one embodiment, a message list image of the target message currently displayed on the device screen can be obtained, and the image area corresponding to each target message in the message list image can be determined through image recognition, and then the display area of each target message on the device screen can be determined. For each target message, the first control attribute information of the message control in the corresponding display area in the message list image is obtained.
[0053] In addition, the first control attribute information corresponding to the target message can also be obtained through the tree structure corresponding to the content currently displayed on the device screen. That is, in one embodiment, the step of "obtaining the first control attribute information of the message control associated with the target message currently displayed on the device screen" includes:
[0054] Determine a root node in a tree structure corresponding to the content currently displayed on the device screen, and perform node traversal based on the root node to determine child nodes belonging to the same message under the root node, wherein each control displayed on the device screen corresponds to a child node;
[0055] Based on the node information of the child node corresponding to the target message, the first control attribute information of the target message is obtained.
[0056] Among them, the tree structure corresponding to the content currently displayed on the device screen records the relationship between the controls displayed on the device screen and the control attribute information of the controls. Each control displayed on the device screen corresponds to a node in the tree structure. The node is an object used to describe the control information. Multiple target messages are displayed on the device screen. Each target message contains a message control, that is, the content displayed on the device screen, the target message, and the message control have a hierarchical relationship. The root node in the tree structure corresponds to the content displayed on the device screen. Each message can be considered as a large control, and the message control is a small control under the large control.
[0057] Determine the root node in the tree structure corresponding to the content currently displayed on the device screen, and perform node traversal based on the root node to determine the child nodes belonging to the same message. The child nodes belonging to the same message may include the node corresponding to the message itself, and the child nodes under the node (that is, the node corresponding to the message control associated with the message). The child node is an object used to describe the control information of the message control, so the node information includes the control information of the message control. For each target message, the first control attribute information of the message control can be obtained from the node information of the child node corresponding to the message control belonging to the same target message.
[0058] In one embodiment, all messages displayed on the device screen may be used as target messages, and messages meeting conditions may be screened out as target messages, for example, unread messages visible on the device screen are selected, that is, before the step of "obtaining first control attribute information of the target message based on the node information of the subnode corresponding to the target message", the message deduplication method provided in the embodiment of the present application may further include:
[0059] If the sub-node corresponding to the above message includes a target sub-node corresponding to a target message control indicating that the message is in an unread state, then the above message is determined to be a candidate message;
[0060] According to the node information of the sub-node corresponding to the candidate message, a target message that is visible on the device screen is determined.
[0061] If the message is in an unread state, the message control associated with the message will include a control indicating that the message is in an unread state, namely, the target control. If the message is in a read state, there is no target message control in the message control associated with the message. Therefore, the message can be determined as a candidate message based on whether the child node corresponding to each message contains a target child node (the target child node is the node corresponding to the target control) or not. If the message contains a target child node, the message will be determined as a candidate message.
[0062] The node information of the sub-node corresponding to the message also includes information indicating whether the message is visible on the device screen. For example, the node information of the node corresponding to the message itself may include information indicating whether the message is visible on the device screen. Based on the node information of the sub-node corresponding to the candidate message, the candidate message that is visible on the device screen can be determined, that is, the target message can be determined.
[0063] After the target message is determined, the first control attribute information corresponding to the target message may be obtained from the node information of the child node corresponding to the target message.
[0064] In one embodiment, the tree structure corresponding to the device screen can be implemented through an accessibility service. The accessibility service is a service provided by the device system to help people with disabilities obtain messages on the mobile phone screen and provide the ability to operate the device. The node corresponding to the control on the device screen can be an accessibility information node. The accessibility information node is an object used by the accessibility service to describe the attribute information of the control on the current device screen. Commonly used attributes include: control ID, screen position of the control, control type, control description, control text (if any), a list of sub-accessibility information nodes of the control, and whether the control is operable.
[0065] Third-party applications can develop upper-level applications based on the interfaces provided by the accessibility service, such as RPA applications. RPA refers to Robotic Process Automation (RPA). RPA can simulate manual operation tasks of computer equipment in a software automation manner, allowing software robots to automatically handle a large number of repetitive, highly standardized, and rule-based workflow tasks. In one embodiment, the message deduplication method provided in the embodiment of the present application can be implemented through RPA applications.
[0066] 102. Obtain a message type of the target message, and generate a first message entity corresponding to the target message based on the message type of the target message and at least part of the corresponding first control attribute information.
[0067] The message type may indicate the content type of the message content of the target message, such as a text message type, a picture message type, a video message type, a link message type, a mini-program message type, a voice message type, a location message type, and the like.
[0068] Different message contents can be displayed on the device screen through different types of controls, that is, the message controls associated with target messages of different message types are different. For example, the message control associated with a target message of a text message type may include a text control, and the message control associated with a target message of a picture message type may include a picture control, or include a text control and a picture control, etc. Therefore, the message type of the target message can be determined according to the control type in the first control attribute information corresponding to each target message and the control type contained in the target message.
[0069] Optionally, the content type of the target message can also be determined through image processing. For example, an image containing the target message currently displayed on the device screen (i.e., a message list image) can be obtained by taking a screenshot of the device screen, and the obtained message list image can be segmented. The image areas where different target messages are located in the message list image can be separated from the message image to obtain a message image corresponding to each target message.
[0070] Feature extraction is performed on each message image to obtain feature information of the message image, and based on the feature information of the image, it is determined whether the message content is text content, picture content or video content. Specifically, classification can be performed based on the feature information of the image according to a classification network to determine the type of the message content, and the message type can be determined based on the type of the message content.
[0071] Since the message structures of different message types are different, the message type can determine the control property information of the controls under the target message from which the required information is obtained. For example, for a target message of a text message type, the text content needs to be obtained from the text control. For a target message of a picture message type, the picture content needs to be obtained from the picture control. If there is a text control, the text content also needs to be obtained from the text control.
[0072] According to the message type, at least part of the information is obtained from the first control attribute information corresponding to the target message, such as the message content, etc., and a first message entity is generated according to the information obtained from the first control attribute information and the message type, that is, the first message entity corresponding to the target message is obtained.
[0073] Since if the content of the graphical user interface displayed on the device screen has reached the bottom, the content displayed on the device screen remains unchanged after the device screen is refreshed, and the target messages on the device screen are all repeated with the historical messages, if it is determined that the content of the graphical user interface has reached the bottom, there is no need to obtain the entity of the target message to determine whether there is a historical message duplication, that is, in one embodiment, before the step of "obtaining the message type of the above target message", the message deduplication method provided in the embodiment of the present application may also include:
[0074] Acquire the first display position information of the last target message currently displayed on the device screen, and the second display position information of the last historical message historically displayed on the device screen;
[0075] Based on the first display position information and the second display position information, determining whether the last target message and the last historical message are the same;
[0076] The step of “obtaining the message type of the target message” may include:
[0077] If the last target message is different from the last historical message, the message type of the target message is obtained.
[0078] If the content of the graphical user interface has reached the bottom, the content of the graphical user interface displayed on the device screen will not be updated. Therefore, whether the content of the graphical user interface has reached the bottom can be determined based on whether the content displayed on the device screen changes.
[0079] Specifically, it can be judged by whether the display position of the last message on the device screen has changed. If the content displayed on the device screen has changed, the display position of the last message will be different. If the content displayed on the device screen has not changed, the display position of the last message will remain unchanged.
[0080] Therefore, the first display position information of the last target message currently displayed on the device screen and the second display position information of the last historical message historically displayed on the device screen can be obtained.
[0081] Compare the first display position information and the second display position information. If the first display position information and the second display position information are the same, it is determined that the last target message and the last historical message are the same. If the first display position information and the second display position information are different, it is determined that the last target message and the last historical message are different, indicating that the content displayed on the graphical user interface has not yet reached the end, and the currently displayed target message is different from the historical message displayed historically. Therefore, if the last target message and the last historical message are different, the message type of the target message is obtained.
[0082] 103. Obtain a second storage address and a second message entity corresponding to the historical message historically displayed on the device screen.
[0083] Among them, the historical messages displayed on the device screen may include messages displayed before the target message currently displayed on the device screen. For example, the device screen can display some messages in the message list, and can scroll to display other messages in the message list. For the target message displayed on the device screen after scrolling, the message displayed on the device screen before scrolling is the historical message.
[0084] For example, the first storage address and the first message entity of the target message may be saved before the device screen is scrolled, and then the second storage address and the second message entity of the historical message may be obtained after the scrolling.
[0085] Optionally, the distance between the historical message and the target message is less than the height of a screen, and the distance between the historical message and the target message may refer to the distance scrolled from the historical message to the target message in a scrolling event.
[0086] 104. Determine the messages to be deduplicated that are duplicates of the historical messages in the target message based on the first storage address and the first message entity and the second storage address and the second message entity.
[0087] For example, the first storage address of the target message and the second storage address of the historical message can be compared. If the first storage address of each target message currently displayed on the device screen is different from the second storage address of any historical message, it is considered that the target message and the historical message are not duplicates, that is, the message to be deduplicated is empty.
[0088] If the first storage address of the target message currently displayed on the screen of the detection device is the same as the second storage address of the historical message, it can be further determined whether the message types of the target message and the historical message with the same first storage address and second storage address are the same. If the message types are the same, it is considered that the target message and the historical message are not repeated. If the message types are different, it is considered that the target message and the historical message are repeated, and the message to be deduplicated is obtained.
[0089] Optionally, if the message type and storage address of the target message are respectively the same as the message type and storage address of a historical message, it can be further determined whether the message contents of the target message and the historical message are the same to improve the accuracy of the determination.
[0090] In one embodiment, a mapping relationship may be established between a message entity and a storage address corresponding to each target message, or a mapping relationship may be established between a message type in a message entity and a storage address, so as to determine the message to be deduplicated based on the mapping relationship. Since it is necessary to compare with historical messages, in order to improve data search speed, the first storage address may be subjected to information mapping processing to obtain a message identifier of the target message, that is, the step of "determining the message to be deduplicated in the target message that is repeated with the historical message based on the first storage address and the first message entity, and the second storage address and the second message entity" may include:
[0091] Performing information mapping processing on the first storage address of the target message to obtain a message identifier of the target message;
[0092] Establishing a mapping relationship between the message identifier of the target message and the message type in the first message entity, and obtaining message mapping information corresponding to the content currently displayed on the device screen;
[0093] Based on the message mapping information corresponding to the target message and the historical message mapping information corresponding to the historical message, determine the messages to be deduplicated that are repeated with the historical message in the target message, and the historical message mapping information is obtained based on the second storage address and the second message entity.
[0094] For example, the first storage address of the target message can be mapped using a hash function to obtain the message identifier of the target message; a mapping relationship can be established between the message identifier of the target message and the message type in the first message entity to obtain message mapping information corresponding to the content currently displayed on the device screen.
[0095] The historical messages historically displayed on the device screen correspond to historical message mapping information. According to the message mapping information corresponding to the target message and the historical message mapping information corresponding to the historical message, the messages to be deduplicated that are repeated with the historical message in the target message are determined.
[0096] The messages displayed on the device screen slide out of the screen in the order in which they are displayed on the screen. The last message displayed on the device screen is the last to slide out of the device screen, so based on the last historical message, it can be determined whether it is a duplicate of the target message. If the last historical message is a duplicate of a target message, it can be considered that the target message on the device screen and other messages before the target message are duplicates of the historical messages. If the last historical message is not a duplicate of the target message, it can be considered that the target message is not a duplicate of the historical messages.
[0097] 105. Remove the message entity of the message to be deduplicated from the first message entity to obtain a deduplicated message record on the device screen.
[0098] After determining the messages to be deduplicated that are repeated in historical messages in the target message currently displayed on the device screen, the message entities to be deduplicated can be removed from the first message entity corresponding to the target message currently displayed on the device screen to obtain the deduplicated message record corresponding to the target message currently displayed on the device screen.
[0099] Optionally, removing the message entity of the message to be deduplicated from the first message entity may be by deleting the message entity of the message to be deduplicated in the storage space, or by adding the message entity of the target message other than the message to be deduplicated to the list of messages to be processed.
[0100] After obtaining the deduplicated message record of the target message currently displayed on the device screen, the device screen can continue to be scrolled to update the display of the device screen. That is, in one embodiment, after the step of "removing the message entity of the message to be deduplicated from the first message entity to obtain the deduplicated message record of the device screen", the message deduplication method provided in the embodiment of the present application may also include:
[0101] triggering a scrolling event for the device screen, and returning to execute the receiving of the scrolling event for the device screen, and updating the display of the device screen in response to the scrolling event, until the last target message is the same as the last historical message;
[0102] Report the above deduplicated message records to the server.
[0103] For example, a scrolling event for the device screen can be triggered by simulating a scrolling operation, and the execution step of "receiving a scrolling event for the device screen, and updating the display of the device screen in response to the scrolling event" can be returned until the last target message currently displayed on the device screen is the same as the last historical message.
[0104] When the last target message currently displayed on the device screen is the same as the last historical message, it is considered that the content displayed on the graphical user interface has reached the bottom, and the obtained deduplicated message record is reported to the server. It can be understood that each target message displayed on the device screen may correspond to a deduplicated message record, and the deduplicated message record reported to the server may include the deduplicated message record obtained in each cycle.
[0105] The obtained deduplicated message records can be applied to message reproduction scenarios. For example, a VR (virtual reality) device or an AR (augmented reality) device can obtain the deduplicated message records and reproduce the message list in the scene based on the deduplicated message records.
[0106] Optionally, it can also be applied to automatic reply scenarios. For example, the server can perform conversation intent recognition processing on the messages in the deduplicated message records to determine the conversation intent of the target message; and generate candidate reply messages based on the conversation intent so that the user can reply based on the candidate reply messages.
[0107] In one embodiment, the device may be a terminal, and the operating system on the terminal provides accessibility services, a PRA application developed based on the accessibility services, and a communication application, wherein the communication application allows users to communicate messages through the terminal. For example, the user can chat with contacts on the conversation interface of the communication application, and a message list between the user and the contact is displayed on the conversation interface. The device screen can display the conversation interface, and the terminal can scroll the message list on the device screen in response to a scrolling operation on the conversation interface. For example, when the user swipes up on the device screen, the messages displayed on the device screen will slide up, some messages will slide out of the screen, and new messages will be displayed on the device screen. During the message scrolling process, the messages displayed on the device screen may overlap. For example, the message of the Nth screen displayed on the device screen may overlap. Figure 2 As shown in (1), when the screen is scrolled down, the message of the N+1th screen displayed on the device screen is as follows Figure 2 As shown in (2), it can be seen that the message in the dotted box of the N+1th screen is repeated with the message in the dotted box of the Nth screen.
[0108] After the accessibility service of the PRA application is turned on in the terminal, the first control attribute information of the message control associated with the target message displayed on the device screen can be obtained through the accessibility service node, and the message type can be determined according to the first control attribute information, and a message entity can be generated based on the message type and the first control attribute information, and a mapping relationship corresponding to the target message currently displayed on the device screen, i.e., message type-storage address, can be constructed according to the message type and the storage address of the first control attribute information.
[0109] According to the mapping relationship corresponding to the target message and the mapping relationship corresponding to the historical message, the target message that is repeated in the historical message, that is, the message to be deduplicated, is determined, and the message entities other than the message to be deduplicated are added to the reporting list among the message entities corresponding to the target message currently displayed on the device screen, so as to eliminate the message entities of the message to be deduplicated and obtain the deduplicated message record of the target message currently displayed on the device screen.
[0110] And the mapping relationship of the message to be deduplicated is deleted, and the mapping relationship other than the message to be deduplicated is added to the cache list for comparison with the target message after the content of the device screen is updated.
[0111] by Figure 2 The historical messages and target messages shown in the figure are taken as an example to illustrate that the message of the Nth screen displayed on the device screen is as follows Figure 2 As shown in (1), when the screen is scrolled down, the message of the N+1th screen displayed on the device screen is as follows Figure 2 As shown in (2), it can be seen that the message in the dotted box on the N+1th screen is repeated with the message in the dotted box on the Nth screen. The message entities of the target message and the message to be deduplicated in the historical message are removed, which is equivalent to the message records of the Nth screen and the N+1th screen as shown in FIG. Figure 3 As shown, Figure 3 In the message record shown, the message in the dotted box is recorded only once without repeated recording, which can improve the problem of a large number of messages and a large amount of storage space occupied due to message duplication.
[0112] After obtaining the deduplicated message record of the target message currently displayed on the device screen, the content displayed on the device screen may be scrolled, with the scrolling distance being less than the height of the device screen.
[0113] After scrolling, obtain the first control attribute information corresponding to each target message displayed on the device screen after scrolling, obtain the message type of the last target message and the display position information on the device screen from the first control attribute information, and obtain the message type and display position information of the last historical message in the historical messages, and compare the message type and display position information. If the message type and display position information of the last target message are the same as the message type and display position information of the last historical message, it is considered that the message list has been scrolled to the end, and the message entity in the report list is reported to the server. If the message type and display position information of the last target message are different from at least one of the message type and display position information of the last historical message, it is considered that the message list has not been scrolled to the end, and obtain the deduplicated message record corresponding to the target message displayed after the device screen is scrolled, and so on, until the message list is scrolled to the end.
[0114] As can be seen from the above, the embodiment of the present application obtains the first control attribute information of the message control associated with the target message currently displayed on the device screen, and obtains the first storage address corresponding to the target message, the space corresponding to the first storage address is used to store the first control attribute information, and the first storage addresses corresponding to different target messages currently displayed on the device screen are different; obtains the message type of the target message, and based on the message type of the target message and at least part of the information in the corresponding first control attribute information, generates a first message entity corresponding to the target message; obtains the second storage address and the second message entity corresponding to the historical messages historically displayed on the device screen; determines the messages to be deduplicated in the target message that are repeated with the historical messages based on the first storage address and the first message entity, and the second storage address and the second message entity; removes the message entity of the message to be deduplicated from the first message entity, and obtains the deduplicated message record of the device screen.
[0115] The embodiment of the present application can remove the message entities of the target messages currently displayed on the device screen that are repeated with the historical messages, obtain the deduplicated message records, reduce the number of messages obtained by the device, and thus reduce the message processing pressure of the device. In addition, if the device needs to upload the message entity to the server, the repeated reporting of the message can be reduced, thereby reducing the server's parsing pressure and storage pressure on the message.
[0116] In order to better implement the message deduplication method provided in the embodiment of the present application, a message deduplication device is also provided in one embodiment. The meanings of the terms are the same as those in the above message deduplication method, and the specific implementation details can refer to the description in the method embodiment.
[0117] The message deduplication device can be integrated into a computer device, such as Figure 4 As shown, the message deduplication device may include: an information acquisition unit 301, a type acquisition unit 302, an entity acquisition unit 303, a comparison unit 304 and a deduplication unit 305, which are specifically as follows:
[0118] (1) An information acquisition unit 301 is used to acquire first control attribute information of a message control associated with a target message currently displayed on a device screen, and to acquire a first storage address corresponding to the target message. The space corresponding to the first storage address is used to store the first control attribute information. Different target messages currently displayed on the device screen have different first storage addresses.
[0119] In one embodiment, the information acquisition unit 301 may include:
[0120] A node traversal subunit, used to determine a root node in a tree structure corresponding to the content currently displayed on the device screen, and perform node traversal based on the root node to determine child nodes belonging to the same message under the root node, wherein each control displayed on the device screen corresponds to a child node;
[0121] The attribute acquisition subunit is used to acquire the first control attribute information of the above target message based on the node information of the subnode corresponding to the above target message.
[0122] In one embodiment, the message deduplication device may further include:
[0123] A first message determination unit, configured to determine that the message is a candidate message if the sub-node corresponding to the message includes a target sub-node corresponding to a target message control indicating that the message is in an unread state;
[0124] The second message determination unit is used to determine the target message that is visible on the device screen according to the node information of the sub-node corresponding to the above candidate message.
[0125] (2) A type acquisition unit 302, configured to acquire a message type of the target message, and generate a first message entity corresponding to the target message based on the message type of the target message and at least part of the corresponding first control attribute information.
[0126] In one embodiment, the message deduplication device may further include:
[0127] A response unit, configured to receive a scrolling event for the device screen, and update the display of the device screen in response to the scrolling event;
[0128] The above-mentioned historical messages include a screen of messages displayed on the above-mentioned device screen before the above-mentioned scrolling event is responded to, and the above-mentioned target messages include a screen of messages displayed on the above-mentioned device screen after the above-mentioned scrolling event is responded to.
[0129] In one embodiment, the message deduplication device may further include:
[0130] A position acquisition unit, used to acquire first display position information of the last target message currently displayed on the device screen, and second display position information of the last historical message historically displayed on the device screen;
[0131] a determination unit, configured to determine whether the last target message and the last historical message are the same based on the first display position information and the second display position information;
[0132] The type acquisition unit 302 may also be used for:
[0133] If the last target message is different from the last historical message, the message type of the target message is obtained.
[0134] (3) An entity acquisition unit 303 is used to acquire a second storage address and a second message entity corresponding to the historical message historically displayed on the device screen.
[0135] (4) A comparing unit 304, configured to determine, based on the first storage address and the first message entity, and the second storage address and the second message entity, the messages to be deduplicated in the target message that are duplicates of the historical message.
[0136] In one embodiment, the comparison unit 304 includes:
[0137] A mapping subunit, configured to perform information mapping processing on the first storage address of the target message to obtain a message identifier of the target message;
[0138] A relationship establishing subunit, used to establish a mapping relationship between the message identifier of the target message and the first message entity, and obtain message mapping information corresponding to the content currently displayed on the device screen;
[0139] A message comparison subunit is used to determine the messages to be deduplicated in the target message that are repeated with the above-mentioned historical messages based on the message mapping information corresponding to the above-mentioned target message and the historical message mapping information corresponding to the above-mentioned historical message, and the above-mentioned historical message mapping information is obtained based on the above-mentioned second storage address and the above-mentioned second message entity.
[0140] (5) A deduplication unit 305, configured to remove the message entity of the message to be deduplicated from the first message entity, and obtain a deduplicated message record on the device screen.
[0141] In one embodiment, the message deduplication device may further include:
[0142] a loop subunit, configured to trigger a scrolling event for the device screen, and return to execute the receiving of the scrolling event for the device screen, and update the display of the device screen in response to the scrolling event, until the last target message is the same as the last historical message;
[0143] The reporting subunit is used to report the above-mentioned deduplicated message records to the server.
[0144] As can be seen from the above, the message deduplication device of the embodiment of the present application obtains the first control attribute information of the message control associated with the target message currently displayed on the device screen, and obtains the first storage address corresponding to the target message through the information acquisition unit 301. The space corresponding to the first storage address is used to store the first control attribute information. The first storage addresses corresponding to different target messages currently displayed on the device screen are different; the type acquisition unit 302 obtains the message type of the target message, and generates a first message entity corresponding to the target message based on the message type of the target message and at least part of the information in the corresponding first control attribute information; the entity acquisition unit 303 obtains the second storage address and the second message entity corresponding to the historical message historically displayed on the device screen; the comparison unit 304 determines the to-be-deduplicated message in the target message that is repeated with the historical message based on the first storage address and the first message entity, and the second storage address and the second message entity; the deduplication unit 305 removes the message entity of the to-be-deduplicated message from the first message entity to obtain the deduplicated message record of the device screen.
[0145] The embodiment of the present application can remove the message entity of the target message currently displayed on the device screen that is repeated with the historical message, obtain the message record after deduplication, reduce the number of messages obtained by the device, and thus reduce the pressure on the device to process messages. In addition, if the device needs to upload the message entity to the server, the repeated reporting of the message can be reduced, thereby reducing the pressure on the server to parse the message and reducing the storage pressure on the server.
[0146] Accordingly, the embodiment of the present application also provides a computer device, which may be a terminal. Figure 5 As shown, Figure 5 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. The computer device 500 includes a processor 501 having one or more processing cores, a memory 502 having one or more computer-readable storage media, and a computer program stored in the memory 502 and executable on the processor. The processor 501 is electrically connected to the memory 502. It will be understood by those skilled in the art that the computer device structure shown in the figure does not constitute a limitation on the computer device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.
[0147] The processor 501 is the control center of the computer device 500. It uses various interfaces and lines to connect the various parts of the entire computer device 500, executes various functions of the computer device 500 and processes data by running or loading software programs and / or modules stored in the memory 502, and calling data stored in the memory 502, thereby monitoring the computer device 500 as a whole.
[0148] In the embodiment of the present application, the processor 501 in the computer device 500 will load instructions corresponding to the processes of one or more application programs into the memory 502 according to the following steps, and the processor 501 will run the application programs stored in the memory 502 to implement various functions:
[0149] Acquire first control attribute information of a message control associated with a target message currently displayed on the device screen, and acquire a first storage address corresponding to the target message, wherein the space corresponding to the first storage address is used to store the first control attribute information, and different target messages currently displayed on the device screen correspond to different first storage addresses;
[0150] Acquire a message type of a target message, and generate a first message entity corresponding to the target message based on the message type of the target message and at least part of the corresponding first control attribute information;
[0151] Acquire a second storage address and a second message entity corresponding to the historical message historically displayed on the device screen;
[0152] Determine, based on the first storage address and the first message entity, and the second storage address and the second message entity, the message to be deduplicated that is repeated with the historical message in the target message;
[0153] The message entity of the message to be deduplicated is removed from the first message entity to obtain a deduplicated message record on the device screen.
[0154] As can be seen from the above, the embodiment of the present application obtains the first control attribute information of the message control associated with the target message currently displayed on the device screen, and obtains the first storage address corresponding to the target message, the space corresponding to the first storage address is used to store the first control attribute information, and the first storage addresses corresponding to different target messages currently displayed on the device screen are different; obtains the message type of the target message, and based on the message type of the target message and at least part of the information in the corresponding first control attribute information, generates a first message entity corresponding to the target message; obtains the second storage address and the second message entity corresponding to the historical messages historically displayed on the device screen; determines the messages to be deduplicated in the target message that are repeated with the historical messages based on the first storage address and the first message entity, and the second storage address and the second message entity; removes the message entity of the message to be deduplicated from the first message entity, and obtains the deduplicated message record of the device screen.
[0155] The embodiment of the present application can remove the message entity of the target message currently displayed on the device screen that is repeated with the historical message, obtain the message record after deduplication, reduce the number of messages obtained by the device, and thus reduce the pressure on the device to process messages. In addition, if the device needs to upload the message entity to the server, the repeated reporting of the message can be reduced, thereby reducing the pressure on the server to parse the message and reducing the storage pressure on the server.
[0156] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.
[0157] Optional, such as Figure 5 As shown, the computer device 500 further includes: a touch screen 503, a radio frequency circuit 504, an audio circuit 505, an input unit 506, and a power supply 507. The processor 501 is electrically connected to the touch screen 503, the radio frequency circuit 504, the audio circuit 505, the input unit 506, and the power supply 507, respectively. Those skilled in the art can understand that Figure 5 The computer device structure shown in the figure does not constitute a limitation on the computer device, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.
[0158] The touch display screen 503 can be used to display a graphical user interface and receive operation instructions generated by the user acting on the graphical user interface. The touch display screen 503 may include a display panel and a touch panel. Among them, the display panel may be used to display information input by the user or information provided to the user and various graphical user interfaces of computer equipment, and these graphical user interfaces may be composed of graphics, text, icons, videos and any combination thereof. Optionally, the display panel may be configured in the form of a liquid crystal display (LCD, Liquid Crystal Display), an organic light emitting diode (OLED, Organic Light-Emitting Diode) and the like. The touch panel may be used to collect the user's touch operation on or near it (such as the user using any suitable object or attachment such as a finger, a stylus, etc. on the touch panel or near the touch panel), and generate corresponding operation instructions, and the operation instructions execute corresponding programs. Optionally, the touch panel may include two parts, a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into the touch point coordinates, and then sends it to the processor 501, and can receive the command sent by the processor 501 and execute it. The touch panel can cover the display panel. When the touch panel detects a touch operation on or near it, it is transmitted to the processor 501 to determine the type of touch event, and then the processor 501 provides a corresponding visual output on the display panel according to the type of touch event. In an embodiment of the present application, the touch panel and the display panel can be integrated into the touch display screen 503 to realize the input and output functions. However, in some embodiments, the touch panel and the touch panel can be used as two independent components to realize the input and output functions. That is, the touch display screen 503 can also be used as a part of the input unit 506 to realize the input function.
[0159] The radio frequency circuit 504 may be used to send and receive radio frequency signals, so as to establish wireless communication with a network device or other computer devices through wireless communication, and to send and receive signals between the network device or other computer devices.
[0160] The audio circuit 505 can be used to provide an audio interface between the user and the computer device through a speaker and a microphone. The audio circuit 505 can transmit the electrical signal converted from the received audio data to the speaker, which is converted into a sound signal for output; on the other hand, the microphone converts the collected sound signal into an electrical signal, which is received by the audio circuit 505 and converted into audio data, and then the audio data is output to the processor 501 for processing, and then sent to another computer device through the radio frequency circuit 504, or the audio data is output to the memory 502 for further processing. The audio circuit 505 may also include an earphone jack to provide communication between an external headset and the computer device.
[0161] The input unit 506 may be used to receive input numbers, character information or user feature information (such as fingerprint, iris, facial information, etc.), and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.
[0162] The power supply 507 is used to supply power to various components of the computer device 500. Optionally, the power supply 507 can be logically connected to the processor 501 through a power management system, so that the power management system can manage charging, discharging, and power consumption. The power supply 507 can also include one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, power status indicators, and other arbitrary components.
[0163] although Figure 5 Not shown, the computer device 500 may also include a camera, a sensor, a wireless fidelity module, a Bluetooth module, etc., which will not be described in detail here.
[0164] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0165] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.
[0166] To this end, an embodiment of the present application provides a computer-readable storage medium, in which multiple computer programs are stored, and the computer program can be loaded by a processor to execute the steps in any message deduplication method provided in the embodiment of the present application. For example, the computer program can execute the following steps:
[0167] Acquire first control attribute information of a message control associated with a target message currently displayed on the device screen, and acquire a first storage address corresponding to the target message, wherein the space corresponding to the first storage address is used to store the first control attribute information, and different target messages currently displayed on the device screen correspond to different first storage addresses;
[0168] Acquire a message type of a target message, and generate a first message entity corresponding to the target message based on the message type of the target message and at least part of the corresponding first control attribute information;
[0169] Acquire a second storage address and a second message entity corresponding to the historical message historically displayed on the device screen;
[0170] Determine, based on the first storage address and the first message entity, and the second storage address and the second message entity, the message to be deduplicated that is repeated with the historical message in the target message;
[0171] The message entity of the message to be deduplicated is removed from the first message entity to obtain a deduplicated message record on the device screen.
[0172] As can be seen from the above, the embodiment of the present application obtains the first control attribute information of the message control associated with the target message currently displayed on the device screen, and obtains the first storage address corresponding to the target message, the space corresponding to the first storage address is used to store the first control attribute information, and the first storage addresses corresponding to different target messages currently displayed on the device screen are different; obtains the message type of the target message, and based on the message type of the target message and at least part of the information in the corresponding first control attribute information, generates a first message entity corresponding to the target message; obtains the second storage address and the second message entity corresponding to the historical messages historically displayed on the device screen; determines the messages to be deduplicated in the target message that are repeated with the historical messages based on the first storage address and the first message entity, and the second storage address and the second message entity; removes the message entity of the message to be deduplicated from the first message entity, and obtains the deduplicated message record of the device screen.
[0173] The embodiment of the present application can remove the message entity of the target message currently displayed on the device screen that is repeated with the historical message, obtain the message record after deduplication, reduce the number of messages obtained by the device, and thus reduce the pressure on the device to process messages. In addition, if the device needs to upload the message entity to the server, the repeated reporting of the message can be reduced, thereby reducing the pressure on the server to parse the message and reducing the storage pressure on the server.
[0174] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.
[0175] The storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.
[0176] The above is a detailed introduction to a message deduplication method, device, computer equipment and computer storage medium provided in an embodiment of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A message deduplication method, characterized in that: include: Acquire first control attribute information of a message control associated with a target message currently displayed on a device screen, and acquire a first storage address corresponding to the target message, wherein a space corresponding to the first storage address is used to store the first control attribute information, and different target messages currently displayed on the device screen correspond to different first storage addresses; Acquire the message type of the target message, and generate a first message entity corresponding to the target message based on the message type of the target message and at least part of the corresponding first control attribute information; Acquire a second storage address and a second message entity corresponding to the historical message historically displayed on the device screen; Determine, based on the first storage address and the first message entity, and the second storage address and the second message entity, messages to be deduplicated that are repeated with the historical messages in the target message; The message entity of the message to be deduplicated is removed from the first message entity to obtain a deduplicated message record on the device screen.
2. The method according to claim 1, characterized in that The step of obtaining first control attribute information of a message control associated with a target message currently displayed on a device screen includes: Determine a root node in a tree structure corresponding to the content currently displayed on the device screen, and perform node traversal based on the root node to determine child nodes belonging to the same message under the root node, wherein each control displayed on the device screen corresponds to a child node; Based on the node information of the child node corresponding to the target message, first control attribute information of the target message is obtained.
3. The method according to claim 2, characterized in that Before acquiring the first control attribute information of the target message based on the node information of the sub-node corresponding to the target message, the method further includes: If the sub-node corresponding to the message includes a target sub-node corresponding to a target message control indicating that the message is in an unread state, determining that the message is a candidate message; According to the node information of the sub-node corresponding to the candidate message, a target message that is visible on the device screen is determined.
4. The method according to claim 1, characterized in that The determining, based on the first storage address and the first message entity, and the second storage address and the second message entity, the message to be deduplicated in the target message that is repeated with the historical message includes: Performing information mapping processing on the first storage address of the target message to obtain a message identifier of the target message; Establishing a mapping relationship between the message identifier of the target message and the first message entity, and obtaining message mapping information corresponding to the content currently displayed on the device screen; Based on the message mapping information corresponding to the target message and the historical message mapping information corresponding to the historical message, determine the messages to be deduplicated that are repeated with the historical message in the target message, and the historical message mapping information is obtained based on the second storage address and the second message entity.
5. The method according to any one of claims 1 to 4, characterized in that: Before obtaining the first control attribute information of the message control associated with the target message currently displayed on the device screen, the method further includes: receiving a scrolling event for the device screen, and updating the display of the device screen in response to the scrolling event; The historical messages include a screen of messages displayed on the device screen before the scrolling event is responded to, and the target messages include a screen of messages displayed on the device screen after the scrolling event is responded to.
6. The method according to claim 5, characterized in that Before obtaining the message type of the target message, the method further includes: Acquire the first display position information of the last target message currently displayed on the device screen, and the second display position information of the last historical message historically displayed on the device screen; Based on the first display position information and the second display position information, determining whether the last target message and the last historical message are the same; The acquiring the message type of the target message includes: If the last target message is different from the last historical message, the message type of the target message is acquired.
7. The method according to claim 6, characterized in that After removing the message entity of the to-be-deduplicated message from the first message entity to obtain the deduplicated message record on the device screen, the method further includes: triggering a scrolling event for the device screen, and returning to execute the receiving of the scrolling event for the device screen, and updating the display of the device screen in response to the scrolling event until the last target message is the same as the last historical message; The deduplicated message records are reported to the server.
8. A message deduplication device, characterized in that: include: an information acquisition unit, used to acquire first control attribute information of a message control associated with a target message currently displayed on a device screen, and to acquire a first storage address corresponding to the target message, wherein a space corresponding to the first storage address is used to store the first control attribute information, and different target messages currently displayed on the device screen correspond to different first storage addresses; A type acquisition unit, configured to acquire a message type of the target message, and generate a first message entity corresponding to the target message based on the message type of the target message and at least part of the corresponding first control attribute information; An entity acquisition unit, used to acquire a second storage address and a second message entity corresponding to the historical message historically displayed on the device screen; A comparing unit, configured to determine, based on the first storage address and the first message entity, and the second storage address and the second message entity, messages to be deduplicated in the target message that are repeated with the historical message; A deduplication unit is used to remove the message entity of the message to be deduplicated from the first message entity to obtain a deduplicated message record on the device screen.
9. A computer device, characterized in that: It comprises a memory and a processor; the memory stores a computer program, and the processor is used to run the computer program in the memory to execute the message deduplication method as described in any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store a computer program, and the computer program is loaded by a processor to execute the message deduplication method according to any one of claims 1 to 7.
