Target object information processing method, device, computer equipment and storage medium

Abstract

The present application relates to a method, device, computer equipment, storage medium and computer program product for information processing of a target object. The method can be applied to communication scenarios and smart transportation scenarios, etc. The method comprises: displaying the information page of the target object through a first communication application; in response to the start operation triggered on the abnormal list moving control in the information page, moving the target communication account corresponding to the target object into the anti-interference abnormal list; the target communication account is an account in the account system corresponding to the second communication application, and is added to the address book of the first communication application; the first communication application and the second communication application are applications of different account systems; based on the target communication account, sending a first prompt message to the target object that it has been moved into the abnormal list; canceling the display of the object information of the target object in the address book of the first communication application. The use of this method can effectively process the target communication account and other information of each object.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, apparatus, computer equipment, and storage medium for processing information of a target object. Background Art

[0002] With the development of communication technology, the communication applications that have emerged are becoming more and more popular among the majority of people. Whether in life, work or study, people can communicate with each other in a timely and effective manner through communication applications anytime and anywhere. Even two parties using different communication applications can communicate effectively, such as person A using an enterprise communication application to communicate with person B using a personal communication application.

[0003] Target objects using different communication applications may send messages to the other party more frequently, such as frequently sending advertising messages, thereby affecting the normal life or work of the other party. However, there is a lack of effective means to handle the communication accounts and other information of each target object between communication applications with different account systems. Summary of the Invention

[0004] Based on this, it is necessary to provide a target object information processing method, device, computer equipment and storage medium to address the above technical problems, which can effectively process the target communication account and other information of each object.

[0005] In a first aspect, the present application provides a method for processing target object information. The method comprises:

[0006] displaying the target object's information page through the first communication application;

[0007] In response to an activation operation triggered on the exception list move control on the information page, a target communication account corresponding to the target object is moved to an exception list for interference prevention; the target communication account is an account in an account system corresponding to the second communication application and is added to the address book of the first communication application; the first communication application and the second communication application are applications in different account systems;

[0008] Based on the target communication account, sending a first prompt message to the target object that the target object has been moved into the abnormal list;

[0009] The object information of the target object is canceled from being displayed in the address book of the first communication application.

[0010] In a second aspect, the present application further provides a target object information processing device. The device comprises:

[0011] A first display module, configured to display an information page of a target object via a first communication application;

[0012] a moving module, configured to move a target communication account corresponding to the target object into an anti-interference exception list in response to an activation operation triggered on the exception list moving control on the information page; the target communication account is an account in the account system corresponding to the second communication application and is added to the address book of the first communication application; the first communication application and the second communication application are applications in different account systems;

[0013] A sending module, configured to send a first prompt message to the target object that the target object has been moved into the abnormal list based on the target communication account;

[0014] The second display module is configured to cancel display of the object information of the target object in the address book of the first communication application.

[0015] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are performed:

[0016] displaying the target object's information page through the first communication application;

[0017] In response to an activation operation triggered on the exception list move control on the information page, a target communication account corresponding to the target object is moved to an exception list for interference prevention; the target communication account is an account in an account system corresponding to the second communication application and is added to the address book of the first communication application; the first communication application and the second communication application are applications in different account systems;

[0018] Based on the target communication account, sending a first prompt message to the target object that the target object has been moved into the abnormal list;

[0019] The object information of the target object is canceled from being displayed in the address book of the first communication application.

[0020] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the following steps:

[0021] displaying the target object's information page through the first communication application;

[0022] In response to an activation operation triggered on the exception list move control on the information page, a target communication account corresponding to the target object is moved to an exception list for interference prevention; the target communication account is an account in an account system corresponding to the second communication application and is added to the address book of the first communication application; the first communication application and the second communication application are applications in different account systems;

[0023] Based on the target communication account, sending a first prompt message to the target object that the target object has been moved into the abnormal list;

[0024] The object information of the target object is canceled from being displayed in the address book of the first communication application.

[0025] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the following steps:

[0026] displaying the target object's information page through the first communication application;

[0027] In response to an activation operation triggered on the exception list move control on the information page, a target communication account corresponding to the target object is moved to an exception list for interference prevention; the target communication account is an account in an account system corresponding to the second communication application and is added to the address book of the first communication application; the first communication application and the second communication application are applications in different account systems;

[0028] Based on the target communication account, sending a first prompt message to the target object that the target object has been moved into the abnormal list;

[0029] The object information of the target object is canceled from being displayed in the address book of the first communication application.

[0030] The target object information processing method, apparatus, computer device, storage medium, and computer program product described above, for a first communication application and a second communication application in different account systems, displays the target object's information page through the first communication application, and performs an operation of moving the target communication account into the exception list on the information page, thereby moving the target communication account added to the first communication application's address book and belonging to the corresponding account system of the second communication application into the anti-interference exception list, thereby achieving management of communication accounts across account systems and effectively preventing the target communication account from pushing messages that interfere with the operator. In addition, a first prompt message indicating that the target communication account has been moved to the exception list is sent to the target communication account, thereby prompting the target communication account that has been moved to the exception list. Moreover, the target object's object information is removed from the first communication application's address book, thereby preventing messages from being sent to it, effectively achieving multi-dimensional and effective management of the target communication account and object information of the target object in different account systems.

[0031] In a sixth aspect, the present application provides a method for processing target object information. The method comprises:

[0032] receiving an exception list move-in request submitted by a first communication application; the exception list move-in request is generated by the first communication application in response to an activation operation of an exception list move-in control;

[0033] Moving the target communication account specified in the request to move the abnormal list into the anti-interference abnormal list; the target communication account is an account of the target object in the account system corresponding to the second communication application, and is added to the address book of the first communication application; the first communication application and the second communication application are applications in different account systems;

[0034] Sending a second prompt message to the first communication application that the target communication account has been successfully moved into the abnormal list;

[0035] The second prompt message is used to instruct the first communication application to cancel displaying the object information of the target object in the address book.

[0036] In a seventh aspect, the present application further provides a target object information processing device. The device comprises:

[0037] a receiving module configured to receive a request for moving into an exception list submitted by a first communication application; the request for moving into an exception list is generated by the first communication application in response to an activation operation of an exception list moving control;

[0038] a moving-in module, configured to move the target communication account specified in the moving-in request to the exception list into an anti-interference exception list; the target communication account is an account of the target object in the account system corresponding to the second communication application, and is added to the address book of the first communication application; the first communication application and the second communication application are applications in different account systems;

[0039] A sending module, configured to send a second prompt message to the first communication application indicating that the target communication account has been successfully moved to the abnormal list;

[0040] The second prompt message is used to instruct the first communication application to cancel displaying the object information of the target object in the address book.

[0041] In an eighth aspect, the present application further provides a computer device. The computer device includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0042] receiving an exception list move-in request submitted by a first communication application; the exception list move-in request is generated by the first communication application in response to an activation operation of an exception list move-in control;

[0043] Moving the target communication account specified in the request to move the abnormal list into the anti-interference abnormal list; the target communication account is an account of the target object in the account system corresponding to the second communication application, and is added to the address book of the first communication application; the first communication application and the second communication application are applications in different account systems;

[0044] Sending a second prompt message to the first communication application that the target communication account has been successfully moved into the abnormal list;

[0045] The second prompt message is used to instruct the first communication application to cancel displaying the object information of the target object in the address book.

[0046] In a ninth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the following steps:

[0047] receiving an exception list move-in request submitted by a first communication application; the exception list move-in request is generated by the first communication application in response to an activation operation of an exception list move-in control;

[0048] Moving the target communication account specified in the request to move the abnormal list into the anti-interference abnormal list; the target communication account is an account of the target object in the account system corresponding to the second communication application, and is added to the address book of the first communication application; the first communication application and the second communication application are applications in different account systems;

[0049] Sending a second prompt message to the first communication application that the target communication account has been successfully moved into the abnormal list;

[0050] The second prompt message is used to instruct the first communication application to cancel displaying the object information of the target object in the address book.

[0051] In a tenth aspect, the present application further provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the following steps:

[0052] receiving an exception list move-in request submitted by a first communication application; the exception list move-in request is generated by the first communication application in response to an activation operation of an exception list move-in control;

[0053] Moving the target communication account specified in the request to move the abnormal list into the anti-interference abnormal list; the target communication account is an account of the target object in the account system corresponding to the second communication application, and is added to the address book of the first communication application; the first communication application and the second communication application are applications in different account systems;

[0054] Sending a second prompt message to the first communication application that the target communication account has been successfully moved into the abnormal list;

[0055] The second prompt message is used to instruct the first communication application to cancel displaying the object information of the target object in the address book.

[0056] The target object information processing method, apparatus, computer device, storage medium, and computer program product described above, for a first communication application and a second communication application in different account systems, involves the first communication application displaying an information page for the target communication account, performing an operation to move the target communication account into the exception list within the information page, thereby moving the target communication account added to the first communication application's address book and belonging to the second communication application's corresponding account system into an anti-interference exception list, thereby achieving management of communication accounts across account systems and effectively preventing the target communication account from pushing messages that interfere with the operator. Furthermore, a second prompt message is sent to the first communication application indicating that the target communication account has been successfully moved to the exception list, thereby prompting the target communication account to have been moved into the exception list. The first communication application is also instructed to remove the target object's object information from the address book, thereby avoiding sending messages to it. This effectively achieves multi-dimensional and effective management of the target communication account and object information of the target object in different account systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 A diagram of an application environment of a method for processing information of a target object in one embodiment;

[0058] Figure 2 1 is a flow chart of a method for processing target object information in one embodiment;

[0059] Figure 3 A schematic diagram of an information page of a target object in one embodiment;

[0060] Figure 4 This is a schematic diagram of a first-level information page and a second-level information page of a target object in another embodiment;

[0061] Figure 5 A schematic diagram of displaying a prompt message on an information page of a target object in one embodiment;

[0062] Figure 6 A schematic diagram of displaying a prompt message on a conversation page in one embodiment;

[0063] Figure 7 An architectural environment diagram of an information processing method for a target object in one embodiment;

[0064] Figure 8 is a schematic diagram of an address book of a first communication application in one embodiment;

[0065] Figure 9 A flowchart of removing a target communication account from an abnormal list and redisplaying the object information in one embodiment is shown;

[0066] Figure 10A schematic diagram of a process for setting a label for a target object in one embodiment;

[0067] Figure 11 A schematic diagram of a page for setting a label for a target object and displaying the label in one embodiment;

[0068] Figure 12 is a flowchart of a method for processing target object information in another embodiment;

[0069] Figure 13 A schematic diagram of a process in which a sender that has been placed on an exception list fails to send a communication message in one embodiment;

[0070] Figure 14 A flowchart illustrating a case where an inviter that has been placed on an abnormal list fails to invite an operator to join a group in one embodiment;

[0071] Figure 15 A schematic diagram showing that the backend servers of an enterprise communication application and a personal communication application respectively store and maintain their respective data in one embodiment;

[0072] Figure 16 is a flowchart of a method for processing target object information in another embodiment;

[0073] Figure 17 is a structural block diagram of an information processing device for a target object in one embodiment;

[0074] Figure 18 is a structural block diagram of an information processing device for a target object in another embodiment;

[0075] Figure 19 is a structural block diagram of an information processing device for a target object in another embodiment;

[0076] Figure 20 is a diagram of the internal structure of a computer device in one embodiment;

[0077] Figure 21 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0078] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0079] The target object information processing method provided in the embodiment of the present application can be applied to Figure 1In the application environment shown. Among them, the terminal 102, the background server (referred to as the server) 104 corresponding to the first communication application, the server 106 corresponding to the second communication application and the terminal 108 communicate through the network. The data storage system, that is, the database, can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other servers. The first communication application is installed in the terminal 102, and the second communication application is installed in the terminal 108. The first communication application and the second communication application are applications of different account systems. For example, if the first communication application is an enterprise-level communication application (referred to as the enterprise communication application), the second communication application can be a personal-level communication application (referred to as the personal communication application).

[0080] For example, if the operator wants to move the target object into the exception list to prevent the target object from sending spam messages to it, specifically: the terminal 102 can display the information page of the target communication account of the target object through the first communication application, and the target communication account is an account in the account system corresponding to the second communication application, and is added to the address book of the first communication application; in response to the start operation triggered on the exception list move control in the information page, the target communication account is moved into the exception list; based on the target communication account, the server 104 sends a first prompt message to the target object that it has been moved into the exception list, so that the first prompt message is displayed through the terminal 108; in addition, the object information of the target object is cancelled from being displayed in the address book of the first communication application.

[0081] Among them, the terminal 102 and the terminal 108 can be, but are not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners and smart car devices. The portable wearable devices can be smart watches, smart bracelets and head-mounted devices.

[0082] Server 104 and server 106 can be independent physical servers or service nodes in a blockchain system. The service nodes in the blockchain system form a peer-to-peer (P2P) network. The P2P protocol is an application layer protocol running on top of the Transmission Control Protocol (TCP).

[0083] In addition, server 104 and server 106 can also be server clusters composed of multiple physical servers, and can be cloud servers that provide 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 (CDNs), and big data and artificial intelligence platforms.

[0084] In one embodiment, Figure 2 As shown, a method for processing target object information is provided, which is applied to Figure 1 The following steps are used as an example to illustrate the terminal in the figure:

[0085] S202: Displaying the target object's information page via the first communication application.

[0086] The first communication application may be an enterprise communication application or a personal communication application, such as a communication client installed on a terminal and used for instant communication.

[0087] Enterprise communication applications refer to enterprise-oriented communication software, which is mainly used to realize information exchange between enterprises or between enterprise members. In addition, it can also exchange information with objects that do not belong to the enterprise. Moreover, office matters can be performed through the enterprise communication application, such as handling leave and receiving card-style notification messages pushed by mini-programs through intelligent robots to process corresponding business based on the notification messages. The mini-program may refer to an application running in the system environment provided by the parent application (i.e., the enterprise communication application), such as a network disk application, a smart transportation application, an enterprise's to-do application, a screen projection application, a live broadcast application, a conference application, an email application, and other mobile applications. In addition, the notification message may be: a message for requesting the operator to grant file access rights, a message inviting the operator to join the target task group, a message prompting the operator to complete the to-do task, and a message prompting the operator that other objects have performed the first operation or the second operation on the target file. The first operation may be an operation such as editing, liking, collecting, or commenting on the target file. The second operation may be an operation of uploading the target file.

[0088] A personal communication application refers to personal communication software that is primarily used to enable information interaction between objects at different personal levels. The content of the information interaction includes text, interface, voice, video, and files. When a communication account of an object within the account system of a personal communication application is added to an enterprise communication application, the operator (i.e., the party that added the object) can use the enterprise communication application to interact with the object using the personal communication application; similarly, when a communication account of an object within the account system of an enterprise communication application is added to a personal communication application, the operator can use the personal communication application to interact with the object using the enterprise communication application. It should be noted that when the first communication application is an enterprise communication application, the operator is the enterprise object; when the first communication application is a personal communication application, the operator is the individual object.

[0089] The information page can be used to describe the details of the target communication account and configure the parameters of the target communication account. For example, in the information page, you can view the notes, description and target tags of the target communication account, configure the target tag, share the configured message and enable the exception list entry control for the target communication account. Figure 3 shown.

[0090] In one embodiment, before S202, the terminal obtains each notification message sent by the target communication account of the target object, determines whether there are sensitive keywords in the notification message, and then determines whether the target communication account of the target object is an abnormal account based on the sensitive keywords and the frequency of sending each notification message, thereby displaying a prompt message, or marking the target communication account in the address book. For example, when the notification message contains advertising language and the frequency of sending notification messages is high (such as greater than the set frequency threshold), it can be determined that the target object is an abnormal object and the corresponding target communication account is an abnormal account. At this time, a prompt message can be displayed to remind the operator that the target object is abnormal and can be moved to the abnormal list. The relationship between each object in the address book and the operator can be a friend or colleague.

[0091] In addition, the terminal can also extract features from each notification message received through a machine learning model to obtain feature information, and then predict whether the target communication account of the target object is an abnormal account based on the feature information, thereby displaying a prompt message or marking the target communication account in the address book.

[0092] In one embodiment, the terminal displays an address book through a first communication application; in response to an operation of displaying information of a target object in the address book, an information page of a target communication account is entered.

[0093] In another embodiment, the information page includes a first-level information page and a second-level information page, and the terminal displays the address book through the first communication application; in response to the information display operation of the target object in the address book, the first-level information page of the target communication account is entered, and when the details control in the first-level information page is triggered, the second-level information page of the target communication account is entered to trigger the start operation on the exception list move-in control of the second-level information page.

[0094] For example, when the operator triggers the list item of the target object in the address book of the first communication application, the first-level information page of the target object's target communication account is entered, such as Figure 4 As shown in Figure (a), the first-level information page displays the target object's avatar, object name (such as a virtual name), company, real name, source, and some functional controls. The functional controls may include controls for setting labels, notes, and descriptions. When you click the dot control in the upper right corner of the first-level information page, you can enter the second-level information page. The second-level information page can be used to describe the details of the target communication account and configure parameters for the target communication account. For example, in the second-level information page, you can view the notes, description, and target label of the target communication account, configure target labels for the target communication account, share configured messages, and enable controls for moving into the exception list, etc. Figure 4 As shown in Figure (b).

[0095] S204 , in response to a start operation triggered on the exception list move-in control in the information page, the target communication account corresponding to the target object is moved into the anti-interference exception list.

[0096] The target communication account is an account of the target subject within the account system corresponding to the second communication application and is added to the address book of the first communication application. For example, the target communication account is registered through a personal communication application and belongs to the account system corresponding to the personal communication application. The target communication account is also added as a contact account in the address book of the enterprise communication application. Because the target communication account of the target subject belongs to the account system corresponding to the second communication application, the target subject receives various messages through the second communication application.

[0097] The second communication application can be an enterprise communication application or a personal communication application, but the first communication application and the second communication application are applications with different account systems. Specifically, when the first communication application is an enterprise communication application, the second communication application is a personal communication application; or when the first communication application is a personal communication application, the second communication application is an enterprise communication application.

[0098] The "Move to Exception List" control has two states: on and off. When on, the target's communication account is moved to the interference prevention exception list. The target will be unable to send messages to the operator and will not be able to re-add the operator's communication account. When off, the target's communication account is not moved to the interference prevention exception list.

[0099] Target accounts placed on the exception list by the operator will no longer be able to send messages to the operator's account. Therefore, the exception list can be used to prevent spam from being sent to the operator, preventing them from disrupting the operator. Furthermore, a target account placed on the exception list will no longer be able to add the operator's account to a communication group.

[0100] In one embodiment, when an operator needs to move a target object to an exception list for preventing interference, an activation operation can be triggered on the exception list move control on the information page. In response to the activation operation triggered on the exception list move control on the information page, the terminal moves the target communication account corresponding to the target object to the exception list for preventing interference. Moving the target object to the exception list for preventing interference may refer to moving the target communication account of the target object to the exception list for preventing interference.

[0101] In another embodiment, the terminal can move the target communication account corresponding to the target object into the anti-interference exception list through the background server. The specific moving process is as follows: the terminal responds to the start operation triggered on the exception list moving control in the information page, and submits an exception list moving request to the background server of the first communication application, so that the background server moves the target communication account corresponding to the target object into the anti-interference exception list.

[0102] After the backend server moves the target communication account corresponding to the target object into the anti-interference exception list, it can return a second prompt message to the first communication application based on the communication account of the operator that the target communication account has been successfully moved into the exception list. The terminal receives the second prompt message returned by the backend server that the target communication account has been successfully moved into the exception list; displays the second prompt message returned by the backend server, such as displaying a pop-up window or floating layer on the information page of the target object, and displays the second prompt message in the pop-up window or floating layer, such as Figure 5 As shown, if the name of the target object is Xiao Ming, a second prompt message "Xiao Ming's communication account has been moved to the abnormal list" is displayed in a pop-up window on the information page.

[0103] In one embodiment, when the opening operation of the abnormal list moving-in control is triggered, the terminal can set the state flag of the abnormal list moving-in control to the opening state. Specifically, the terminal detects the opening operation triggered on the abnormal list moving-in control in the information page in real time, and in response to the opening operation triggered on the abnormal list moving-in control in the information page, sets the state flag of the abnormal list moving-in control to the opening state, such as Figure 5 shown.

[0104] In one embodiment, in addition to moving the target communication account corresponding to the target object into an exception list for interference prevention, the object information corresponding to the target object can also be deleted from the corresponding communication group. Specifically, in response to the start operation triggered on the exception list move control in the information page, the terminal displays a prompt sub-page, which displays whether the object information corresponding to the target object needs to be deleted from the corresponding communication group. If deletion is required, it is deleted from the communication group created by the operator or the communication group with the operator as the group owner.

[0105] S206: Based on the target communication account, a first prompt message is sent to the target object indicating that the target object has been moved into the abnormal list.

[0106] In one embodiment, the terminal obtains a first prompt message indicating that a target communication account has been added to an exception list; based on the target communication account, the terminal sends the first prompt message indicating that the target has been added to the exception list to the target object, and displays the first prompt message on a conversation page of a second communication application. The conversation page is a page for conducting a conversation with the operator, and messages between the operator and the target object can be displayed on the conversation page.

[0107] For example, if the operator is Xiao Ming and the target is Xiao Zhang, Xiao Ming moves Xiao Zhang's communication account into the abnormal list, then Xiao Zhang will receive a prompt message with the content "You have been moved into the abnormal list by Xiao Ming and will not be able to send messages to Xiao Ming", and then the prompt message will be displayed on the conversation page with Xiao Ming, such as Figure 6 shown.

[0108] If the target communication account is moved to the exception list by the terminal requesting the backend server, the backend server is instructed to send a first prompt message of being moved to the exception list to the target object based on the target communication account after moving the target communication account to the exception list.

[0109] Specifically, the terminal sends a first prompt message that the target communication account has been moved to the abnormal list to the background server of the first communication application through the first communication application, so that the background server of the first communication application forwards the first prompt message to the background server of the second communication application until the background server of the second communication application pushes the first prompt message to the second communication application of the target object based on the target communication account.

[0110] For example, after the operator moves the target object into the exception list through the enterprise communication application, the enterprise communication application will send an exception list move request to the corresponding backend server a, so that the backend server a moves the target communication account of the target object into the anti-interference exception list, and then the backend server a sends a first prompt message that the target communication account has been moved into the exception list to the backend server b, and the backend server b forwards the first prompt message to the personal communication application of the target object, so that the target object can view the first prompt message that the target communication account held by it has been moved into the exception list through the personal communication application. Figure 7 .

[0111] S208: Cancel displaying the object information of the target object in the address book of the first communication application.

[0112] The address book of the first communication application may refer to the address book of the operator in the first communication application. Canceling the display of the target object's object information includes hiding or deleting the target object's object information originally displayed in the address book so that it is no longer displayed. The object information includes at least one of the target object's profile picture, name, and target communication account.

[0113] For example, Figure 8 As shown in Figure (a), Jack's avatar and name are displayed in the address book of the first communication application. If the operator moves Jack to the abnormal list, Jack's avatar and name will be cancelled in the address book, such as Figure 8 As shown in Figure (b).

[0114] In one embodiment, in addition to canceling the display of the target object's object information in the operator's address book, the target object's object information can also be canceled in the group list of the communication group created by the operator, or in the group list of the communication group with the operator as the group owner.

[0115] In another embodiment, the target object's object information can be removed from the client list of another object. Specifically, the terminal sends a third prompt message to the other communication account in the address book, instructing the receiving device corresponding to the other communication account to remove the target object's object information from the client list; the client list is a list in the first communication application logged in by the other communication account.

[0116] In the above embodiment, for a first communication application and a second communication application in different account systems, the first communication application displays the target object's information page, and an operation is performed on this information page to move the target communication account, which is added to the first communication application's address book and belongs to the corresponding account system of the second communication application, into the anti-interference exception list. This enables management of communication accounts across account systems and effectively prevents the target communication account from pushing messages that interfere with the operator. In addition, a first prompt message is sent to the target communication account that has been moved to the exception list, thereby prompting the target communication account to have been moved to the exception list. Furthermore, the target object's object information is removed from the first communication application's address book, thereby preventing messages from being sent to it. This effectively achieves multi-dimensional and effective management of the target object's target communication account and object information in different account systems.

[0117] In one embodiment, before S204, the method also includes: the terminal moves the target communication account corresponding to the target object into the group management list in response to the anti-interference permission setting operation triggered in the information page; wherein, the target communication account moved into the group management list is prohibited from joining the customer communication group; based on the target communication account, a fourth prompt message is sent to the target object indicating that it has been moved into the group management list.

[0118] The group management list may also be called a group chat management list, which may be a list specifically used to prevent one or more objects from joining a client communication group to interfere with group members.

[0119] Optionally, in response to an anti-interference permission setting operation triggered on the information page, the terminal enters an anti-interference permission setting page. On this anti-interference permission setting page, the target object can be selected to prohibit the target object from joining the customer communication group, and all or part of the customer communication groups can be selected. After the confirmation control is triggered, the target communication account corresponding to the target object is moved to the group management list. In addition, the group identifier of the customer communication group that the target object is prohibited from joining can be associated with the target communication account and stored. Thus, when the target object requests to join the customer communication group, the backend server of the first communication application determines whether the target object's target communication account has been moved to the group management list. If it has been moved to the group management list, it can continue to check whether the customer communication group to be joined is a group that the target object is prohibited from joining. If it is a group that the target object is prohibited from joining, the target object is prohibited from joining the customer communication group; if it is not a group that the target object is prohibited from joining, the target object is allowed to join the customer communication group. Through the above solution, the target object can be specifically allowed or prohibited from joining the communication group of a specific department or a specific customer, or allowed or prohibited from joining the communication group created by the operator.

[0120] For example, Figure 3 As shown, when the operator triggers the "Set his anti-interference permissions" control on the information page, the anti-interference permissions setting page will be entered. Customer group chat a, customer group chat b and customer group chat c are displayed on the anti-interference permissions setting page. If customer group chat a and customer group chat b are selected, a prompt message will be sent to the target object that the target object is prohibited from joining customer group chat a and customer group chat b. If the target object requests to join customer group chat a, the background server will check whether the target object has been moved to the group chat management list. If it has been moved to the group chat management list, it will continue to check whether the customer group chat a to be joined is a group that the target object is prohibited from joining. If so, the target object will be prohibited from joining customer group chat a. Similarly, if the target object requests to join customer group chat c, since the target object is not prohibited from joining customer group chat c, the background server will allow the target object to join customer group chat c.

[0121] In addition, the terminal can also turn on a message reminder control in the information page in response to a message reminder operation triggered in the information page. After the message reminder control is turned on, the first communication application will emit a reminder sound when it receives a chat message or email sent by the target object, so that the operator can know that the target object has sent a message even if the operator is not viewing the first communication application or is not running the first communication application in the foreground, so that the chat message or email can be read in time.

[0122] In the above embodiment, by moving the target communication account of the target object to the group management list, the target object's joining of the customer communication group can be effectively controlled, thereby preventing the target object from joining the corresponding customer communication group and causing interference to group members. In addition, the target object can also be specifically prohibited from joining the customer communication group, thereby selectively allowing or prohibiting the target object from joining the customer communication group, effectively avoiding information security issues in the customer communication group.

[0123] In one embodiment, after S204, the method may further include: the terminal searches for media data from the target communication account locally or in the background server corresponding to the first communication application; the media data includes at least one of communication messages, audio data, image data and video data; the media data is marked in a state to obtain media data in a target state; when the duration in the target state meets the duration condition, the media data is deleted.

[0124] The target state can be a cold data state, indicating that the media data is cold data. If the frequency of access to the media data per unit time is greater than or equal to a preset threshold (e.g., accessed more than once a day, or more than twice a week), the state of the media data can be adjusted, such as from a cold data state to a hot data state. If the frequency of access to the media data per unit time is less than a preset threshold, it indicates that the media data has been in the cold data state for a long time and can be deleted. In addition, the aforementioned local area can be the terminal's own storage area or a local server.

[0125] Specifically, the terminal searches for media data from the target communication account in a folder within its own storage area that corresponds to the first communication application, or searches for media data from the target communication account on a local server, or searches for media data from the backend server of the first communication application. For example, for media data with a large amount of data, it may not be stored on the terminal, such as on a local server (such as the company's own server) or on a backend server corresponding to the company's communication application (i.e., the software developer's server). In this case, the media data from the target communication account can be searched on the local server or the software developer's server.

[0126] In the above embodiment, for target objects that have been moved to the exception list, the media data sent by them is deleted, effectively avoiding the use of memory resources. Furthermore, before deletion, a determination is made as to whether the duration of the media data in the target state meets the duration condition. Only media data that meets the duration condition is deleted, thereby preventing the problem of frequently used media data being mistakenly deleted and causing data loss.

[0127] In one embodiment, if the operator wants to remove the target communication account of the target object from the exception list, the state flag of the exception list move control can be set to the closed state, so that the target communication account can be removed from the exception list. Figure 9 As shown, the step of removing specifically includes:

[0128] S902: Display a message prompt page of the first communication application.

[0129] The message prompt page may include message prompt lines for multiple different objects, where the different objects are objects that have sent messages to the operator, and other applications (including mini-programs) that push notification messages.

[0130] The message prompt line displays the latest messages sent by different parties. If the message is long, it can display the first line of the message or message keywords, or display a prompt indicating that a certain party has sent a chat message. In addition, when the message prompt line for a certain party is triggered, the conversation page with that party is entered.

[0131] S904: If the message prompt page includes a message prompt line of the target object, in response to a triggering operation on the message prompt line, display a conversation page of the target object.

[0132] Among them, the conversation page can refer to the page where the two parties conduct the conversation. The conversation page can display various conversation messages (i.e., communication messages) sent by the two parties. For example, the conversation messages sent include text messages, pictures, voice, video and files.

[0133] When the target communication account of the target object is moved to the exception list, the message prompt line corresponding to the target object will usually be displayed on the message prompt page; if the message prompt line corresponding to the target object is deleted, the message prompt line corresponding to the target object will not be displayed on the message prompt page.

[0134] In one embodiment, S904 specifically includes: if the message prompt page includes a message prompt line for the target object, the terminal can detect in real time a trigger operation on the message prompt line for the target object. When the trigger operation is detected, the terminal enters the conversation page for the target object. After entering the conversation page for the target object, the terminal can respond to the operator's message sending operation and send a conversation message to the target object based on the target communication account. The target object can receive the conversation message through the second communication application, but cannot send a reply message to the operator.

[0135] S906: If the configuration button in the session page is triggered, the information page of the target object is displayed.

[0136] The configuration button may be a button for entering the target object's information page. Figure 6 The three vertical dots are the configuration button. When the configuration button is triggered, the information page of the target object is entered.

[0137] S908 , in response to a close operation triggered on the exception list move-in control in the information page, remove the target communication account from the exception list.

[0138] The "Exception List" control has two states: on and off. When off, the target user's communication account does not need to be added to the interference prevention exception list. If the target account is removed from the exception list, the target user can send conversation messages to the operator's communication account.

[0139] In one embodiment, after the target communication account is removed from the abnormal list, the terminal may further display a prompt message indicating that the target communication account has been removed from the abnormal list.

[0140] S910: Set the status flag of the abnormal list moving control to the closed state.

[0141] S912: Redisplay the object information of the target object in the address book of the first communication application.

[0142] In one embodiment, the terminal can also add the target communication account of the target object to the communication group created by the operator or the communication group with the operator as the group owner, so that the target object's object information can be displayed in the group list of the communication group. In addition, the target object's object information can be redisplayed in the customer lists of other objects.

[0143] In the above embodiment, the operator can remove the target communication account that has been moved into the abnormal list according to actual needs, so that the target object can send a conversation message to the operator, realizing normal communication between the two parties in the conversation.

[0144] In one embodiment, a label can be set for each object in the address book in the first communication application, for example, a label can be set for the target object that has not been moved into the exception list, such as Figure 10 As shown, the steps of setting the label may specifically include:

[0145] S1002, in response to a tag configuration operation triggered on the information page, candidate tags are displayed; the candidate tags include an enterprise tag corresponding to the operator's enterprise, a rule group tag corresponding to the enterprise role, and a personal tag customized by the operator.

[0146] The label setting operation refers to an operation triggered by the operator to set a label for the target object, including triggering operations such as click operation, slide operation, long press operation, and shake operation.

[0147] Enterprise tags are enterprise-level tags, and their usage permissions apply to all objects in the entire enterprise address book. For example, if a super administrator in an enterprise sets up an enterprise-level tag group called "Customer Level" for enterprise S and the subtags "Important Customers" and "General Customers" within that group, all objects in enterprise S's address book can use that enterprise-level tag group to set corresponding subtags for the customers they manage.

[0148] Enterprise roles refer to the role information of each object in the organizational structure of the enterprise to which it belongs. The organizational structure created by the backend server of the first communication application for each enterprise can be different, and each enterprise can include object data, enterprise customer data, and organizational structure data, etc. Role information can include multiple role types, such as department head, super administrator, second-level administrator, and other different role information. For example, in the user management center interface of a certain enterprise, the role information corresponding to the object Zhang San is displayed as a staff member of the Patent Electronics Department, the organizational structure to which he belongs is the Patent Department of a certain enterprise, and the label permission is the rule group label corresponding to the Patent Electronics Department.

[0149] Rule group tags are labels corresponding to different rules. Access to rule group tags can be limited to certain members of the enterprise address book. For example, if a super administrator sets the rule group tag "Branch" for enterprise S and its subtags "Branch in XX" and "Branch in YY," all members of enterprise S's address book can use the rule group tag "Branch" to set corresponding "Branch" subtags for their managed customers. Different enterprise roles have different and isolated rule group tags.

[0150] Personal tags refer to tags that are customized for each object. Personal tags can include personalized tags set for different objects.

[0151] Specifically, in response to the label setting operation triggered by the operator on the information page, the terminal displays the enterprise label corresponding to the operator's enterprise, the rule group label corresponding to the enterprise role, and the operator's customized personal label, wherein the rule group labels corresponding to different enterprise roles are different and isolated from each other.

[0152] S1004: Select at least one target tag from the candidate tags.

[0153] The target tag is the tag selected by the operator from the displayed candidate tags. For example, if the operator selects "Important Customers" from the displayed tags "Important Customers" and "General Customers", "Important Customers" will be the target tag selected by the operator.

[0154] Specifically, in response to the tag selection operation, the terminal selects at least one target tag from the candidate tags and displays a check mark at the location of the target tag. The check mark indicates that the selected tag is marked and displayed, and the mark display can be marked in different colors. For example, the selected tag is displayed in red, or the selected tag can be highlighted in other colors.

[0155] For example, in response to the label setting operation triggered by the operator on the information page, the terminal displays the enterprise label corresponding to the operator's enterprise, which includes the sub-labels "High" and "Medium" in the "Customer Level" label group; and displays the sub-labels "Location A", "Location B" and "Location C" in the rule group label "Patent Group 1" corresponding to the enterprise role, as well as the operator's customized personal label "Excellent" and other personal labels displayed in the personal label column. In response to the operator's label selection operation, the terminal displays a check mark at the position of the target label specified by the label selection operation, such as Figure 11 As shown in Figure (a), the selected target labels are “Place B”, “High”, “Friendly” and “Excellent”.

[0156] S1006: Display the target tag as a tag of the target object on the information page.

[0157] Specifically, in response to a confirmation operation on the target tag, the terminal displays the target tag as a tag of the target object on the information page. The confirmation operation refers to a confirmation operation on the target tag triggered by the operator, such as the operator clicking a confirmation control to complete the confirmation operation on the target tag.

[0158] For example, since the selected target tags are "Place B", "High", "Friendly" and "Excellent", the four tags "Place B", "High", "Friendly" and "Excellent" are displayed as tags of the target object on the target object's information page, such as Figure 11 As shown in Figure (b).

[0159] In one embodiment, the operator can share the label and description information of the target object with the target object so that the target object knows the label and description information set by the operator for it. The specific steps include: the terminal responds to the information sharing operation triggered on the information page, obtains the target label and description information configured by the operator for the target object; and shares the target label and description information with the target object.

[0160] In addition, the terminal may also obtain target tags and description information of other objects in the address book, and share the target tags and description information with the other objects.

[0161] In the above embodiment, the enterprise label corresponding to the enterprise to which the operator belongs, the rule group label corresponding to the enterprise role to which the operator belongs, and the personal label customized by the operator are displayed, and the target label is selected from the displayed candidate labels as the label of the target object and displayed on the information page. Since the rule group labels corresponding to different enterprise roles are different and isolated from each other, the operator can select a customized personal label to label the customer, or select a rule group label that his or her role has permission to use to label the customer, or select a configured enterprise-level label to label the customer, that is, support members of different management rules to use different enterprise customer labels, so that members belonging to different management rule groups in the enterprise can flexibly set different types of labels, and the management rule group labels corresponding to different enterprise roles are isolated from each other. Even when members of different business departments set labels for the same operator, since the management rule group labels corresponding to different departments or different enterprise roles are isolated from each other, it can effectively avoid the phenomenon of chaotic label configuration of enterprise customers, making the label configuration process of each enterprise customer in the address book efficient and flexible.

[0162] In one embodiment, Figure 12 As shown, a method for processing target object information is provided, which is applied to Figure 1 The following steps are used as an example to illustrate the server in the example:

[0163] S1202: Receive an exception list move-in request submitted by a first communication application; the exception list move-in request is generated by the first communication application in response to an activation operation of an exception list move-in control.

[0164] Among them, the exception list moving control is a control in the target object's information page that is used to manage the target communication account of the target object, such as moving the target communication account into the exception list or removing it from the exception list. The information page can be used to describe the detailed information of the target communication account and configure the parameters of the target communication account. For example, in the information page, you can view the notes, description, and target tags of the target communication account, configure the target tag for the target communication account, share the configured message, and enable the exception list moving control, etc. Figure 3 shown.

[0165] The first communication application can be an enterprise communication application or a personal communication application, such as a client installed on a terminal that can be used for instant messaging. An enterprise communication application refers to enterprise-oriented communication software that is primarily used to facilitate information exchange between enterprises or between enterprise members. It can also exchange information with objects that do not belong to the enterprise. Furthermore, the enterprise communication application can also be used to perform office tasks, such as handling leave and attendance, and receiving card-style notification messages pushed by mini-programs via intelligent robots to process corresponding business based on the notification messages. The mini-program can refer to an application that runs in the system environment provided by the parent application (i.e., the enterprise communication application), such as a network disk application, a smart transportation application, an enterprise's to-do application, a screen projection application, a live broadcast application, a conference application, and other mobile applications. Furthermore, the notification message can include: a message requesting the operator to grant file access rights, a message inviting the operator to join a target task group, a message prompting the operator to complete a to-do task, and a message prompting the operator that another object has performed a first operation or a second operation on the target file. The first operation can be an operation such as editing, liking, adding a favorite, or commenting on the target file. The second operation can be an operation of uploading the target file.

[0166] A personal communication application refers to personal communication software primarily used to facilitate information exchange between different individual-level entities. The content of this information exchange includes text, interfaces, voice, video, and files. When a communication account of an entity within the personal communication application's account system is added to an enterprise communication application, the operator (i.e., the party adding the entity) can use the enterprise communication application to exchange information with the entity using the personal communication application. Similarly, when a communication account of an entity within the enterprise communication application's account system is added to a personal communication application, the operator can use the personal communication application to exchange information with the entity using the enterprise communication application.

[0167] The "Move to Exception List" control has two states: on and off. When on, the target account is moved to the exception list for interference prevention. When off, the target account is not moved to the exception list for interference prevention.

[0168] Target accounts placed on the exception list by the operator will no longer be able to send messages to the operator's account. Therefore, the exception list can be used to prevent spam from being sent to the operator, preventing them from disrupting the operator. Furthermore, a target account placed on the exception list will no longer be able to add the operator's account to a communication group.

[0169] In one embodiment, before S1202, if the target object is moved into the group management list by the operator of the first communication application, when the target object sends a request to join the client communication group to the background server of the first communication application through the second communication application, the background server refuses the target object from joining the client communication group. Alternatively, the background server checks whether the client communication group to be joined is a client communication group that prohibits the target object from joining. If it is a client communication group that prohibits the target object from joining, the target object is refused from joining the client communication group; if it is not a client communication group that prohibits the target object from joining, the target object can be allowed to join the client communication group. Through the above scheme, the target object can be specifically allowed or prohibited from joining the communication group of a specific department or a specific customer, or the target object can be allowed or prohibited from joining the communication group created by the operator, effectively preventing the target object from joining the corresponding client communication group to interfere with group members, and avoiding information security issues in the client communication group.

[0170] S1204, moving the target communication account specified in the request into the exception list to prevent interference.

[0171] The target communication account is an account of the target object in the account system corresponding to the second communication application and is added to the address book of the first communication application. For example, the target communication account is registered through a personal communication application and belongs to the account system corresponding to the personal communication application. The target communication account is also added as a contact account in the address book of the enterprise communication application.

[0172] The first communication application and the second communication application are applications with different account systems. Since the target object's target communication account belongs to the account system corresponding to the second communication application, the target object needs to receive various messages through the second communication application, including messages sent by the operator through the first communication application.

[0173] The second communication application can be an enterprise communication application or a personal communication application, but the first communication application and the second communication application are applications with different account systems. Specifically, when the first communication application is an enterprise communication application, the second communication application is a personal communication application; or when the first communication application is a personal communication application, the second communication application is an enterprise communication application.

[0174] In one embodiment, after S1204, the method further includes: the server receives a communication message sent by the sender through the second communication application; when the communication account of the sender is the same as the target communication account in the exception list, a reminder message of the failure of the message sending is fed back to the sender through the background server of the second communication application.

[0175] For example, Figure 13As shown, a sender performs a message sending operation on a personal communication app. The personal communication app sends the message to its backend server, which then delivers a notification message to the server of the enterprise communication app. The server then queries the database to see if the sender has been placed on the exception list by the recipient. Specifically, it checks to see if the sender's account matches the target account on the exception list. If so, it retrieves the exception data. The server then returns the exception data to the personal communication app's corresponding backend server, which then returns the exception data to the personal communication app. Upon receiving the exception data, the personal communication app displays a message indicating that the message failed to be sent.

[0176] In one embodiment, after S1204, the method further includes: the server receiving a group joining request sent by the inviter through the second communication application; when the communication account of the inviter is the same as the target communication account in the exception list, a reminder message of invitation failure is fed back to the inviter through the background server of the second communication application.

[0177] For example, Figure 14 As shown, the inviter clicks the "Invite" button on the personal communication app to invite the user to join a communication group. The personal communication app then sends a group join request to its backend server, which forwards the request to the enterprise communication app's server. The server then queries the database to see if the inviter has been placed on an exception list by the recipient. This means the inviter's account matches the target account on the exception list. If so, the server retrieves the exception data. The server then returns the exception data to the personal communication app's corresponding backend server, which then returns the exception data to the personal communication app. Upon receiving the exception data, the personal communication app displays a message indicating that the invitation to join the group failed.

[0178] S1206: Send a second prompt message to the first communication application indicating that the target communication account has been successfully moved to the abnormal list.

[0179] The second prompt message is used to instruct the first communication application to cancel displaying the object information of the target object in the address book.

[0180] In one embodiment, the server obtains a second prompt message indicating that the target communication account has been successfully moved to the abnormal list, and sends the second prompt message to the first communication application of the operator.

[0181] In the above embodiment, for a first communication application and a second communication application in different account systems, the first communication application displays the information page of the target communication account and performs the operation of moving the target communication account into the exception list within this information page. This moves the target communication account added to the first communication application's address book and belonging to the second communication application's corresponding account system into the anti-interference exception list, thereby achieving management of communication accounts across account systems and effectively preventing the target communication account from pushing messages that interfere with the operator. In addition, a second prompt message is sent to the first communication application indicating that the target communication account has been successfully moved to the exception list, thereby prompting the target communication account to have been moved into the exception list. At the same time, the first communication application is instructed to remove the target object's object information from the address book, thereby preventing the sending of messages to the target object. This effectively achieves multi-dimensional and effective management of the target object's target communication account and object information in different account systems.

[0182] To better understand the above technical solution, we will now describe it in conjunction with personal communication applications, enterprise communication applications, and the corresponding backend servers. The specific details are as follows:

[0183] When enterprise objects use enterprise communication applications to communicate with other objects, their normal work is often disturbed by spam messages sent by others (such as the target objects mentioned above) using communication applications with different account systems (such as personal communication applications). Traditional solutions cannot effectively process the communication account and other information of the target object. However, by adopting the technical solution of this application, the enterprise object can act as the operator to add the target communication account of the target object to the abnormal list. After being added to the abnormal list, the target communication account is deleted from the address book, customer list, and group list of the enterprise communication application. At the same time, the personal communication application of the target object prompts that it has been added to the abnormal list. It should be pointed out that enterprise communication applications and personal communication applications are two different applications (APPs) with different accounts and friend systems.

[0184] Its main system architecture is as follows Figure 7 As shown, the system architecture is described below:

[0185] A. Enterprise objects on the enterprise communication application side exchange data with their backend servers (i.e., the servers mentioned above) through the enterprise communication application;

[0186] B. Individual objects (including target objects) on the personal communication application side interact with their backend servers through the personal communication application;

[0187] C. The backend server of the enterprise communication application and the backend server of the personal communication application realize data exchange between enterprise objects and individual objects through remote calls and other means.

[0188] It should be noted that the backend server of the enterprise communication application and the backend server of the personal communication application maintain their own friend data and exception lists respectively, such as Figure 15 As shown, the complexity of system design can be reduced.

[0189] The enterprise object acts as the operator to move the target objects that frequently send spam messages into the exception list, such as Figure 16 As shown, the steps to move into the exception list are as follows:

[0190] A. On the target object's information page in the enterprise communication application, the enterprise object switches the "Move into exception list" control from off to on. The enterprise communication application then submits a request to move into exception list to the backend server.

[0191] B. The enterprise communication application moves the target communication account of the target object to the abnormal list on the backend server and stores the abnormal list in the database;

[0192] C. The backend server of the enterprise communication application receives a prompt message indicating that the application has been successfully added to the exception list;

[0193] D. The backend server returns a prompt message to the enterprise communication application indicating that the application has been successfully moved to the exception list.

[0194] The target object that is moved to the exception list will not be able to send communication messages to the enterprise object, such as Figure 13 As shown, the specific process is as follows:

[0195] S1, the target object, as the sender, performs an operation of sending a communication message on the personal communication application;

[0196] S2, the personal communication application sends a communication message to its backend server;

[0197] S3, the background server of the personal communication application delivers a notification message to the background server of the enterprise communication application;

[0198] S4, the backend server of the enterprise communication application will query the database to see whether the sender has been added to the exception list by the receiver, that is, whether the communication account of the sender is the same as the target communication account in the exception list;

[0199] S5, if they are the same, obtain the abnormal data indicating that they are moved into the abnormal list.

[0200] S6 The backend server of the enterprise communication application may return the obtained abnormal data to the backend server corresponding to the personal communication application;

[0201] S7, the backend server corresponding to the personal communication application continues to return abnormal data to the personal communication application;

[0202] S8. After receiving the abnormal data, the personal communication application displays a prompt message indicating that the message sending has failed.

[0203] In addition, the target object that has been moved to the abnormal list cannot invite the enterprise object to join the group, such as Figure 14 As shown, the specific process is as follows:

[0204] S1, the target object, as the inviter, clicks on the personal communication application to invite the enterprise object to join the communication group;

[0205] S2, the personal communication application sends a group joining request to its backend server;

[0206] S3, the background server of the personal communication application forwards the group joining request to the background server of the enterprise communication application;

[0207] S4, the backend server of the enterprise communication application will query the database to see whether the inviter has been added to the exception list by the enterprise object, that is, whether the communication account of the inviter is the same as the target communication account in the exception list;

[0208] S5, if they are the same, obtain the abnormal data indicating that they are moved into the abnormal list.

[0209] S6, the backend server of the enterprise communication application may return the obtained abnormal data to the backend server corresponding to the personal communication application;

[0210] S7, the background server of the personal communication application continues to return abnormal data to the personal communication application;

[0211] S8. After receiving the abnormal data, the personal communication application displays a prompt message indicating that the invitation to the group has failed.

[0212] The technical solution of this application provides an implementation for processing communication accounts and related information across different communication applications in a heterogeneous account system. This allows users of both enterprise and personal communication applications to move exception lists between each other, avoiding interference. Furthermore, the data in each system is independent, reducing inter-system coupling and lowering development and maintenance costs.

[0213] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0214] Based on the same inventive concept, embodiments of the present application also provide a target object information processing device for implementing the target object information processing method described above. The implementation solution provided by this device is similar to the implementation solution described in the above method. Therefore, the specific limitations of the embodiments of the target object information processing device provided below can be found in the above-mentioned limitations of the target object information processing method, and will not be repeated here.

[0215] In one embodiment, Figure 17 As shown, a target object information processing device is provided, including: a first display module 1702, a moving module 1704, a sending module 1706, and a second display module 1708, wherein:

[0216] A first display module 1702 is configured to display the target object's information page via a first communication application;

[0217] Move module 1704 is configured to move a target communication account corresponding to a target object into an exception list for interference prevention in response to an activation operation triggered on an exception list move control on an information page; the target communication account is an account in an account system corresponding to a second communication application and is added to a contact list of a first communication application; and the first communication application and the second communication application are applications in different account systems;

[0218] A sending module 1706 is configured to send a first prompt message indicating that the target object has been moved into an abnormal list based on the target communication account;

[0219] The second display module 1708 is configured to cancel display of the target object's object information in the address book of the first communication application.

[0220] In one embodiment, the sending module 1706 is further used to send a third prompt message to other communication accounts in the address book to instruct the receiving device corresponding to the other communication account to cancel the display of the object information of the target object in the customer list; the customer list is a list in the first communication application based on the login of the other communication account.

[0221] In one embodiment, the move-in module 1704 is also used to submit an exception list move-in request to the background server of the first communication application in response to a start operation triggered on the exception list move-in control in the information page, so that the background server moves the target communication account corresponding to the target object into the anti-interference exception list.

[0222] In one embodiment, Figure 18 As shown, the device also includes:

[0223] The receiving module 1710 is configured to receive a second prompt message returned by the backend server indicating that the target communication account has been successfully moved into the abnormal list;

[0224] The first display module 1702 is further configured to display the second prompt message returned by the background server.

[0225] In one embodiment, Figure 18 As shown, the device also includes:

[0226] The first display module 1702 is further configured to, in response to an on operation triggered on the exception list move-in control on the information page, set the state flag of the exception list move-in control to an on state;

[0227] The acquisition module 1712 is configured to acquire a first prompt message indicating that the target communication account has been moved into the abnormal list, and execute the step of sending the first prompt message indicating that the target communication account has been moved into the abnormal list to the target object based on the target communication account.

[0228] In one embodiment, when the first communication application is an enterprise-level communication application, the second communication application is a personal-level communication application; or when the first communication application is a personal-level communication application, the second communication application is an enterprise-level communication application.

[0229] In the above embodiment, for a first communication application and a second communication application in different account systems, the first communication application displays the target object's information page, and an operation is performed on this information page to move the target communication account, which is added to the first communication application's address book and belongs to the corresponding account system of the second communication application, into the anti-interference exception list. This enables management of communication accounts across account systems and effectively prevents the target communication account from pushing messages that interfere with the operator. In addition, a first prompt message is sent to the target communication account that has been moved to the exception list, thereby prompting the target communication account to have been moved to the exception list. Furthermore, the target object's object information is removed from the first communication application's address book, thereby preventing messages from being sent to it. This effectively achieves multi-dimensional and effective management of the target object's target communication account and object information in different account systems.

[0230] In one embodiment, Figure 18 As shown, the device also includes:

[0231] The first display module 1702 is further configured to display a message prompt page of the first communication application; if the message prompt page contains a message prompt line of the target object, in response to a triggering operation on the message prompt line, display a conversation page of the target object; if the configuration button in the conversation page is triggered, display an information page of the target object;

[0232] The removal module 1714 is configured to remove the target communication account from the exception list in response to a close operation triggered on the exception list removal control in the information page.

[0233] In one embodiment, the first display module 1702 is further configured to, in response to a close operation triggered on the exception list move-in control on the information page, set the state flag of the exception list move-in control to a closed state;

[0234] The second display module 1708 is further configured to redisplay the object information of the target object in the address book of the first communication application.

[0235] In the above embodiment, the operator can remove the target communication account that has been moved into the abnormal list according to actual needs, so that the target object can send a conversation message to the operator, realizing normal communication between the two parties in the conversation.

[0236] In one embodiment, Figure 18 As shown, the device also includes:

[0237] The first display module 1702 is further configured to display candidate tags in response to a tag configuration operation triggered on the information page; the candidate tags include the enterprise tag corresponding to the operator's enterprise, the rule group tag corresponding to the enterprise role, and the operator's customized personal tag;

[0238] A selection module 1716 is configured to select at least one target tag from the candidate tags;

[0239] The first display module 1702 is further configured to display the target tag as a tag of the target object on the information page.

[0240] In one embodiment, Figure 18 As shown, the device also includes:

[0241] An acquisition module 1712 is configured to acquire a target tag and description information configured by the operator for a target object in response to an information sharing operation triggered on an information page;

[0242] The sharing module 1718 is used to share the target tag and description information with the target object.

[0243] In the above embodiment, the enterprise label corresponding to the enterprise to which the operator belongs, the rule group label corresponding to the enterprise role to which the operator belongs, and the personal label customized by the operator are displayed, and the target label is selected from the displayed candidate labels as the label of the target object and displayed on the information page. Since the rule group labels corresponding to different enterprise roles are different and isolated from each other, the operator can select a customized personal label to label the customer, or select a rule group label that his or her role has permission to use to label the customer, or select a configured enterprise-level label to label the customer, that is, support members of different management rules to use different enterprise customer labels, so that members belonging to different management rule groups in the enterprise can flexibly set different types of labels, and the management rule group labels corresponding to different enterprise roles are isolated from each other. Even when members of different business departments set labels for the same operator, since the management rule group labels corresponding to different departments or different enterprise roles are isolated from each other, it can effectively avoid the phenomenon of chaotic label configuration of enterprise customers, making the label configuration process of each enterprise customer in the address book efficient and flexible.

[0244] In one embodiment, the moving module 1704 is further configured to move the target communication account corresponding to the target object into a group management list in response to an anti-interference permission setting operation triggered in the information page; wherein the target communication account moved into the group management list is prohibited from joining the client communication group;

[0245] The sending module 1706 is further configured to send a fourth prompt message to the target object based on the target communication account, indicating that the target object has been moved into the group management list.

[0246] In the above embodiment, by moving the target communication account of the target object to the group management list, the target object's joining of the customer communication group can be effectively controlled, thereby preventing the target object from joining the corresponding customer communication group and causing interference to group members. In addition, the target object can also be specifically prohibited from joining the customer communication group, thereby selectively allowing or prohibiting the target object from joining the customer communication group, effectively avoiding information security issues in the customer communication group.

[0247] In one embodiment, Figure 18 As shown, the device also includes:

[0248] Search module 1720, configured to search for media data originating from the target communication account locally or in a backend server corresponding to the first communication application; the media data including at least one of communication messages, audio data, image data, and video data;

[0249] a marking module 1722, configured to mark the state of the media data to obtain media data in a target state;

[0250] The deleting module 1724 is configured to delete the media data when the duration of the target state satisfies a duration condition.

[0251] In the above embodiment, for target objects that have been moved to the exception list, the media data sent by them is deleted, effectively avoiding the use of memory resources. Furthermore, before deletion, a determination is made as to whether the duration of the media data in the target state meets the duration condition. Only media data that meets the duration condition is deleted, thereby preventing the problem of frequently used media data being mistakenly deleted and causing data loss.

[0252] In one embodiment, Figure 19 As shown, a target object information processing device is provided, including: a receiving module 1902, a moving module 1904 and a sending module 1906, wherein:

[0253] The receiving module 1902 is configured to receive an exception list move-in request submitted by the first communication application; the exception list move-in request is generated by the first communication application in response to an activation operation of an exception list move-in control;

[0254] A move-in module 1904 is configured to move a target communication account specified in the exception list move-in request into an exception list for interference prevention; the target communication account is an account of the target object in the account system corresponding to the second communication application and is added to the address book of the first communication application; the first communication application and the second communication application are applications in different account systems;

[0255] A sending module 1906 is configured to send a second prompt message to the first communication application indicating that the target communication account has been successfully moved to the abnormal list;

[0256] The second prompt message is used to instruct the first communication application to cancel displaying the object information of the target object in the address book.

[0257] In one embodiment, the receiving module 1902 is further configured to receive a communication message sent by the sender through the second communication application;

[0258] The sending module 1906 is further configured to, when the communication account of the sender is the same as the target communication account in the abnormal list, send a reminder message of the failure of the feedback message to the sender through the background server of the second communication application.

[0259] In one embodiment, the receiving module 1902 is further configured to receive a group joining request sent by the inviting party via the second communication application;

[0260] The sending module 1906 is further configured to, when the communication account of the inviting party is the same as the target communication account in the abnormal list, feed back a reminder message of invitation failure to the inviting party through the background server of the second communication application.

[0261] In the above embodiment, for a first communication application and a second communication application in different account systems, the first communication application displays the information page of the target communication account and performs the operation of moving the target communication account into the exception list within this information page. This moves the target communication account added to the first communication application's address book and belonging to the second communication application's corresponding account system into the anti-interference exception list, thereby achieving management of communication accounts across account systems and effectively preventing the target communication account from pushing messages that interfere with the operator. In addition, a second prompt message is sent to the first communication application indicating that the target communication account has been successfully moved to the exception list, thereby prompting the target communication account to have been moved into the exception list. At the same time, the first communication application is instructed to remove the target object's object information from the address book, thereby preventing the sending of messages to the target object. This effectively achieves multi-dimensional and effective management of the target object's target communication account and object information in different account systems.

[0262] Each module in the information processing device of the target object may be implemented in whole or in part through software, hardware, or a combination thereof. Each module may be embedded in or independent of a processor in a computer device in the form of hardware, or may be stored in a memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0263] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 20 As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected via a system bus, and the communication interface, the display unit and the input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a method for processing information of a target object is implemented. The display unit of the computer device is used to form a visually visible image, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device casing, or an external keyboard, touchpad or mouse, etc.

[0264] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 21 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O) and a communication interface. The processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store data such as friend data and exception lists. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for processing information of a target object is implemented.

[0265] Those skilled in the art will understand that Figure 20 and Figure 21The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0266] In one embodiment, a computer device is provided, comprising a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the following steps when executing the computer program: displaying an information page of a target object through a first communication application; in response to a start operation triggered on an exception list move-in control in the information page, moving a target communication account corresponding to the target object into an interference-proof exception list; the target communication account is an account in an account system corresponding to a second communication application, and is added to an address book of the first communication application; the first communication application and the second communication application are applications of different account systems; based on the target communication account, sending a first prompt message to the target object that the target object has been moved into the exception list; and canceling the display of the target object's object information in the address book of the first communication application.

[0267] In one embodiment, when the processor executes the computer program, it also implements the following steps: in response to the start operation triggered on the exception list move-in control in the information page, submitting an exception list move-in request to the background server of the first communication application, so that the background server moves the target communication account corresponding to the target object into the anti-interference exception list.

[0268] In one embodiment, when the processor executes the computer program, the following steps are further implemented: receiving a second prompt message returned by the background server indicating that the target communication account has been successfully moved to the abnormal list; and displaying the second prompt message returned by the background server.

[0269] In one embodiment, when the processor executes the computer program, it also implements the following steps: in response to the start operation triggered on the exception list moving control in the information page, the status flag of the exception list moving control is set to the open state; obtaining a first prompt message indicating that the target communication account has been moved into the exception list, and based on the target communication account, sending the first prompt message of being moved into the exception list to the target object.

[0270] In one embodiment, when the processor executes the computer program, it also implements the following steps: displaying a message prompt page of the first communication application; if the message prompt page contains a message prompt line of the target object, in response to a triggering operation on the message prompt line, displaying the conversation page of the target object; if the configuration button in the conversation page is triggered, displaying the information page of the target object; in response to a close operation triggered on the exception list move-in control in the information page, removing the target communication account from the exception list.

[0271] In one embodiment, when the processor executes the computer program, it also implements the following steps: in response to a close operation triggered on the exception list move-in control in the information page, setting the status flag of the exception list move-in control to a closed state; and redisplaying the object information of the target object in the address book of the first communication application.

[0272] In one embodiment, when the first communication application is an enterprise-level communication application, the second communication application is a personal-level communication application; or when the first communication application is a personal-level communication application, the second communication application is an enterprise-level communication application.

[0273] In one embodiment, when the processor executes the computer program, it also implements the following steps: in response to a tag configuration operation triggered on the information page, displaying candidate tags; the candidate tags include the enterprise tag corresponding to the enterprise to which the operator belongs, the rule group tag corresponding to the enterprise role to which the operator belongs, and the personal tag customized by the operator; selecting at least one target tag from the candidate tags; and displaying the target tag as the tag of the target object on the information page.

[0274] In one embodiment, when the processor executes the computer program, it further implements the following steps: in response to an information sharing operation triggered on the information page, obtaining the target tag and description information configured by the operator for the target object; and sharing the target tag and description information with the target object.

[0275] In one embodiment, when the processor executes the computer program, it also implements the following steps: sending a third prompt message to other communication accounts in the address book to instruct the receiving device corresponding to the other communication account to cancel the display of the object information of the target object in the customer list; the customer list is a list in the first communication application based on the login of the other communication account.

[0276] In one embodiment, when the processor executes the computer program, it also implements the following steps: in response to the anti-interference permission setting operation triggered in the information page, the target communication account corresponding to the target object is moved into the group management list; wherein, the target communication account moved into the group management list is prohibited from joining the customer communication group; based on the target communication account, a fourth prompt message is sent to the target object indicating that it has been moved into the group management list.

[0277] In one embodiment, when the processor executes the computer program, it also implements the following steps: searching for media data from the target communication account in the local or background server corresponding to the first communication application; the media data includes at least one of communication messages, audio data, image data and video data; marking the status of the media data to obtain media data in the target state; when the duration of the target state meets the duration condition, deleting the media data.

[0278] In another embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the following steps when executing the computer program: receiving an exception list move-in request submitted by a first communication application; the exception list move-in request is generated by the first communication application in response to the opening operation of the exception list move-in control; moving the target communication account specified in the exception list move-in request into an interference-proof exception list; the target communication account is an account of the target object in the account system corresponding to the second communication application, and is added to the address book of the first communication application; the first communication application and the second communication application are applications in different account systems; sending a second prompt message to the first communication application that the target communication account has been successfully moved to the exception list; wherein the second prompt message is used to instruct the first communication application to cancel the display of the object information of the target object in the address book.

[0279] In one embodiment, when the processor executes the computer program, it also implements the following steps: receiving a communication message sent by the sender through the second communication application; when the communication account of the sender is the same as the target communication account in the exception list, a reminder message of the failure of the message transmission is fed back to the sender through the background server of the second communication application.

[0280] In one embodiment, when the processor executes the computer program, it also implements the following steps: receiving a group joining request sent by an inviter through a second communication application; when the communication account of the inviter is the same as the target communication account in the exception list, a reminder message of invitation failure is fed back to the inviter through the background server of the second communication application.

[0281] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented: displaying an information page of a target object through a first communication application; in response to a start operation triggered on an exception list move-in control in the information page, moving a target communication account corresponding to the target object into an interference-proof exception list; the target communication account is an account in an account system corresponding to a second communication application, and is added to the address book of the first communication application; the first communication application and the second communication application are applications of different account systems; based on the target communication account, sending a first prompt message to the target object that it has been moved into the exception list; and canceling the display of the object information of the target object in the address book of the first communication application.

[0282] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: in response to the start operation triggered on the exception list move-in control in the information page, an exception list move-in request is submitted to the background server of the first communication application, so that the background server moves the target communication account corresponding to the target object into the anti-interference exception list.

[0283] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: receiving a second prompt message returned by the background server indicating that the target communication account has been successfully moved to the abnormal list; and displaying the second prompt message returned by the background server.

[0284] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: in response to an open operation triggered on the exception list moving control in the information page, the status flag of the exception list moving control is set to the open state; a first prompt message indicating that the target communication account has been moved into the exception list is obtained, and based on the target communication account, the first prompt message of being moved into the exception list is sent to the target object.

[0285] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: displaying a message prompt page of the first communication application; if the message prompt page contains a message prompt line of the target object, in response to a triggering operation on the message prompt line, displaying a conversation page of the target object; if the configuration button in the conversation page is triggered, displaying an information page of the target object; in response to a close operation triggered on the exception list move-in control in the information page, removing the target communication account from the exception list.

[0286] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: in response to a close operation triggered on the exception list move-in control in the information page, the status flag of the exception list move-in control is set to a closed state; and the object information of the target object is redisplayed in the address book of the first communication application.

[0287] In one embodiment, when the first communication application is an enterprise-level communication application, the second communication application is a personal-level communication application; or when the first communication application is a personal-level communication application, the second communication application is an enterprise-level communication application.

[0288] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: in response to a tag configuration operation triggered on the information page, candidate tags are displayed; the candidate tags include the enterprise tag corresponding to the enterprise to which the operator belongs, the rule group tag corresponding to the enterprise role to which the operator belongs, and the personal tag customized by the operator; at least one target tag is selected from the candidate tags; and the target tag is displayed on the information page as the tag of the target object.

[0289] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: in response to the information sharing operation triggered on the information page, obtaining the target tag and description information configured by the operator for the target object; and sharing the target tag and description information with the target object.

[0290] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: a third prompt message is sent to other communication accounts in the address book to instruct the receiving device corresponding to the other communication account to cancel the display of the object information of the target object in the customer list; the customer list is a list in the first communication application based on the login of the other communication account.

[0291] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: in response to the anti-interference permission setting operation triggered in the information page, the target communication account corresponding to the target object is moved into the group management list; wherein, the target communication account moved into the group management list is prohibited from joining the customer communication group; based on the target communication account, a fourth prompt message is sent to the target object indicating that it has been moved into the group management list.

[0292] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: searching for media data from the target communication account in the local or background server corresponding to the first communication application; the media data includes at least one of communication messages, audio data, image data and video data; the media data is marked in a state to obtain media data in a target state; when the duration in the target state meets the duration condition, the media data is deleted.

[0293] In another embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented: receiving an exception list move-in request submitted by a first communication application; the exception list move-in request is generated by the first communication application in response to the opening operation of the exception list move-in control; moving the target communication account specified in the exception list move-in request into an interference-proof exception list; the target communication account is an account of the target object in the account system corresponding to the second communication application, and is added to the address book of the first communication application; the first communication application and the second communication application are applications in different account systems; sending a second prompt message to the first communication application that the target communication account has been successfully moved to the exception list; wherein the second prompt message is used to instruct the first communication application to cancel the display of the object information of the target object in the address book.

[0294] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: receiving a communication message sent by the sender through the second communication application; when the communication account of the sender is the same as the target communication account in the exception list, a reminder message of the failure of the message sending is fed back to the sender through the background server of the second communication application.

[0295] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: receiving a group joining request sent by an inviter through a second communication application; when the communication account of the inviter is the same as the target communication account in the exception list, a reminder message of invitation failure is fed back to the inviter through the background server of the second communication application.

[0296] In one embodiment, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the following steps: displaying an information page of a target object through a first communication application; moving a target communication account corresponding to the target object into an interference-proof exception list in response to a start operation triggered on an exception list move-in control in the information page; the target communication account is an account within an account system corresponding to a second communication application and is added to an address book of the first communication application; the first communication application and the second communication application are applications of different account systems; based on the target communication account, sending a first prompt message to the target object indicating that the target object has been moved into the exception list; and canceling the display of the target object's object information in the address book of the first communication application.

[0297] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: in response to the start operation triggered on the exception list move-in control in the information page, an exception list move-in request is submitted to the background server of the first communication application, so that the background server moves the target communication account corresponding to the target object into the anti-interference exception list.

[0298] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: receiving a second prompt message returned by the background server indicating that the target communication account has been successfully moved to the abnormal list; and displaying the second prompt message returned by the background server.

[0299] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: in response to an open operation triggered on the exception list moving control in the information page, the status flag of the exception list moving control is set to the open state; a first prompt message indicating that the target communication account has been moved into the exception list is obtained, and based on the target communication account, the first prompt message of being moved into the exception list is sent to the target object.

[0300] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: displaying a message prompt page of the first communication application; if the message prompt page contains a message prompt line of the target object, in response to a triggering operation on the message prompt line, displaying a conversation page of the target object; if the configuration button in the conversation page is triggered, displaying an information page of the target object; in response to a close operation triggered on the exception list move-in control in the information page, removing the target communication account from the exception list.

[0301] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: in response to a close operation triggered on the exception list move-in control in the information page, the status flag of the exception list move-in control is set to a closed state; and the object information of the target object is redisplayed in the address book of the first communication application.

[0302] In one embodiment, when the first communication application is an enterprise-level communication application, the second communication application is a personal-level communication application; or when the first communication application is a personal-level communication application, the second communication application is an enterprise-level communication application.

[0303] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: in response to a tag configuration operation triggered on the information page, candidate tags are displayed; the candidate tags include the enterprise tag corresponding to the enterprise to which the operator belongs, the rule group tag corresponding to the enterprise role to which the operator belongs, and the personal tag customized by the operator; at least one target tag is selected from the candidate tags; and the target tag is displayed on the information page as the tag of the target object.

[0304] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: in response to the information sharing operation triggered on the information page, obtaining the target tag and description information configured by the operator for the target object; and sharing the target tag and description information with the target object.

[0305] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: a third prompt message is sent to other communication accounts in the address book to instruct the receiving device corresponding to the other communication account to cancel the display of the object information of the target object in the customer list; the customer list is a list in the first communication application based on the login of the other communication account.

[0306] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: in response to the anti-interference permission setting operation triggered in the information page, the target communication account corresponding to the target object is moved into the group management list; wherein, the target communication account moved into the group management list is prohibited from joining the customer communication group; based on the target communication account, a fourth prompt message is sent to the target object indicating that it has been moved into the group management list.

[0307] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: searching for media data from the target communication account in the local or background server corresponding to the first communication application; the media data includes at least one of communication messages, audio data, image data and video data; the media data is marked in a state to obtain media data in a target state; when the duration in the target state meets the duration condition, the media data is deleted.

[0308] In another embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps: receiving an exception list move-in request submitted by a first communication application; the exception list move-in request is generated by the first communication application in response to an activation operation of an exception list move-in control; moving a target communication account specified in the exception list move-in request into an interference-proof exception list; the target communication account is an account of the target object in the account system corresponding to the second communication application, and is added to the address book of the first communication application; the first communication application and the second communication application are applications in different account systems; sending a second prompt message to the first communication application indicating that the target communication account has been successfully moved to the exception list; wherein the second prompt message is used to instruct the first communication application to cancel displaying the object information of the target object in the address book.

[0309] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: receiving a communication message sent by the sender through the second communication application; when the communication account of the sender is the same as the target communication account in the exception list, a reminder message of the failure of the message sending is fed back to the sender through the background server of the second communication application.

[0310] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: receiving a group joining request sent by an inviter through a second communication application; when the communication account of the inviter is the same as the target communication account in the exception list, a reminder message of invitation failure is fed back to the inviter through the background server of the second communication application.

[0311] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions.

[0312] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processor involved in the various embodiments provided herein may be, but are not limited to, a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, and the like.

[0313] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0314] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A method for processing target object information, characterized in that: The method comprises: displaying the target object's information page through the first communication application; In response to an activation operation triggered on the exception list move control on the information page, a target communication account corresponding to the target object is moved to an exception list for interference prevention; the target communication account is an account in the account system corresponding to the second communication application and is added to the address book of the first communication application, and the target object receives various messages through the second communication application; the first communication application and the second communication application are applications in different account systems; the target communication account moved to the exception list by the operator will not be able to send messages to the communication account of the operator; Based on the target communication account, sending a first prompt message to the target object that the target object has been moved into the abnormal list; The object information of the target object is canceled from being displayed in the address book of the first communication application.

2. The method according to claim 1, characterized in that In response to the start operation triggered on the exception list move control in the information page, moving the target communication account corresponding to the target object into the anti-interference exception list includes: In response to the start operation triggered on the exception list move-in control in the information page, an exception list move-in request is submitted to the background server of the first communication application, so that the background server moves the target communication account corresponding to the target object into the anti-interference exception list.

3. The method according to claim 2, characterized in that The method further comprises: receiving a second prompt message returned by the backend server indicating that the target communication account has been successfully moved into the abnormal list; The second prompt message returned by the backend server is displayed.

4. The method according to claim 1, wherein The method further comprises: In response to an opening operation triggered on the abnormal list moving-in control in the information page, setting a state flag of the abnormal list moving-in control to an opening state; A first prompt message indicating that the target communication account is moved into the exception list is obtained, and the step of sending the first prompt message indicating that the target object is moved into the exception list based on the target communication account is executed.

5. The method according to claim 1, wherein After canceling the display of the target object's object information in the address book of the first communication application, the method further includes: Displaying a message prompt page of the first communication application; If the message prompt page includes a message prompt line of the target object, in response to a triggering operation on the message prompt line, displaying a conversation page of the target object; If the configuration button in the session page is triggered, the target object's information page is displayed; In response to a close operation triggered on the exception list move-in control in the information page, the target communication account is removed from the exception list.

6. The method according to claim 5, characterized in that The method further comprises: In response to a close operation triggered on the exception list move-in control in the information page, setting a state flag of the exception list move-in control to a closed state; The object information of the target object is redisplayed in the address book of the first communication application.

7. The method according to any one of claims 1 to 6, characterized in that When the first communication application is an enterprise-level communication application, the second communication application is a personal-level communication application; or, When the first communication application is a personal-level communication application, the second communication application is an enterprise-level communication application.

8. The method according to any one of claims 1 to 6, characterized in that In response to the start operation triggered on the exception list move control on the information page, before moving the target communication account corresponding to the target object into the anti-interference exception list, the method further includes: In response to a tag configuration operation triggered on the information page, candidate tags are displayed; the candidate tags include an enterprise tag corresponding to the enterprise to which the operator belongs, a rule group tag corresponding to the role of the enterprise to which the operator belongs, and a personal tag customized by the operator; Selecting at least one target tag from the candidate tags; The target tag is displayed on the information page as a tag of the target object.

9. The method according to claim 8, characterized in that The method further comprises: In response to an information sharing operation triggered on the information page, obtaining a target tag and description information configured by the operator for the target object; The target tag and the description information are shared with the target object.

10. The method according to any one of claims 1 to 6, characterized in that The method further comprises: A third prompt message is sent to other communication accounts in the address book to instruct the receiving device corresponding to the other communication account to cancel displaying the object information of the target object in the client list; the client list is a list in the first communication application logged in based on the other communication account.

11. The method according to any one of claims 1 to 6, characterized in that: In response to the start operation triggered on the exception list move control on the information page, before moving the target communication account corresponding to the target object into the anti-interference exception list, the method further includes: In response to an anti-interference permission setting operation triggered in the information page, a target communication account corresponding to the target object is moved into a group management list; wherein the target communication account moved into the group management list is prohibited from joining a customer communication group; Based on the target communication account, a fourth prompt message is sent to the target object, indicating that the target object has been moved into the group management list.

12. The method according to any one of claims 1 to 6, characterized in that After moving the target communication account corresponding to the target object into an exception list for preventing interference, the method further includes: Searching for media data from the target communication account locally or in a backend server corresponding to the first communication application; the media data includes at least one of communication messages, audio data, image data, and video data; Marking the state of the media data to obtain media data in a target state; When the duration of being in the target state meets a duration condition, the media data is deleted.

13. A method for processing target object information, characterized in that: The method comprises: receiving an exception list move-in request submitted by a first communication application; the exception list move-in request is generated by the first communication application in response to an activation operation of an exception list move-in control; The target communication account specified in the exception list move request is moved into an exception list for interference prevention; the target communication account is an account of the target object in the account system corresponding to the second communication application, and is added to the address book of the first communication application, and the target object receives various messages through the second communication application; the first communication application and the second communication application are applications in different account systems; the target communication account moved into the exception list by the operator will not be able to send messages to the communication account of the operator; Sending a second prompt message to the first communication application that the target communication account has been successfully moved into the abnormal list; The second prompt message is used to instruct the first communication application to cancel displaying the object information of the target object in the address book.

14. The method according to claim 13, characterized in that After moving the target communication account specified in the request to move the abnormal list into the anti-interference abnormal list, the method further includes: receiving a communication message sent by a sender through a second communication application; When the communication account of the sender is the same as the target communication account in the abnormal list, A reminder message of message sending failure is fed back to the sender through the background server of the second communication application.

15. The method according to claim 13, characterized in that After moving the target communication account specified in the request to move the abnormal list into the anti-interference abnormal list, the method further includes: receiving a group joining request sent by an inviter via a second communication application; When the communication account of the inviting party is the same as the target communication account in the abnormal list, Feedback a reminder message of invitation failure to the inviting party through the background server of the second communication application.

16. An information processing device for a target object, characterized in that: The device comprises: A first display module, configured to display an information page of a target object via a first communication application; a moving-in module, configured to move a target communication account corresponding to the target object into an anti-interference exception list in response to an activation operation triggered on an exception list moving-in control on the information page; the target communication account is an account within an account system corresponding to a second communication application and is added to an address book of the first communication application, and the target object receives various messages through the second communication application; the first communication application and the second communication application are applications of different account systems; the target communication account moved into the exception list by the operator will not be able to send messages to the operator's communication account; A sending module, configured to send a first prompt message to the target object that the target object has been moved into the abnormal list based on the target communication account; The second display module is configured to cancel display of the object information of the target object in the address book of the first communication application.

17. The device according to claim 16, characterized in that The move-in module is also used to submit an exception list move-in request to the background server of the first communication application in response to the start operation triggered on the exception list move-in control in the information page, so that the background server moves the target communication account corresponding to the target object into the anti-interference exception list.

18. The device according to claim 17, characterized in that The device further comprises: A receiving module, configured to receive a second prompt message returned by the backend server indicating that the target communication account has been successfully moved into the abnormal list; The first display module is further configured to display a second prompt message returned by the background server.

19. The device according to claim 16, characterized in that The device further comprises: The first display module is further configured to, in response to an opening operation triggered on the exception list moving-in control in the information page, set a state flag of the exception list moving-in control to an opening state; The acquisition module is used to acquire a first prompt message indicating that the target communication account is moved into the abnormal list, and execute the step of sending the first prompt message indicating that the target object is moved into the abnormal list based on the target communication account.

20. The device according to claim 16, wherein The device further comprises: The first display module is further configured to display a message prompt page of the first communication application; if the message prompt page contains a message prompt line of the target object, in response to a triggering operation on the message prompt line, display a conversation page of the target object; if a configuration button in the conversation page is triggered, display an information page of the target object; The removal module is configured to remove the target communication account from the exception list in response to a close operation triggered on the exception list removal control in the information page.

21. The device according to claim 20, characterized in that The first display module is further configured to, in response to a close operation triggered on the exception list move-in control in the information page, set a state flag of the exception list move-in control to a closed state; The second display module is further configured to redisplay the object information of the target object in the address book of the first communication application.

22. The device according to any one of claims 16 to 21, characterized in that When the first communication application is an enterprise-level communication application, the second communication application is a personal-level communication application; or, When the first communication application is a personal-level communication application, the second communication application is an enterprise-level communication application.

23. The device according to any one of claims 16 to 21, characterized in that The device further comprises: The first display module is further configured to display candidate tags in response to a tag configuration operation triggered on the information page; the candidate tags include an enterprise tag corresponding to the enterprise to which the operator belongs, a rule group tag corresponding to the role in the enterprise, and a personal tag customized by the operator; A selection module, configured to select at least one target tag from the candidate tags; The first display module is further configured to display the target tag as a tag of the target object on the information page.

24. The device according to claim 23, characterized in that The device further comprises: An acquisition module, configured to acquire, in response to an information sharing operation triggered on the information page, a target tag and description information configured by the operator for the target object; A sharing module is used to share the target tag and the description information with the target object.

25. The device according to any one of claims 16 to 21, characterized in that The sending module is further configured to send a third prompt message to other communication accounts in the address book to instruct the receiving device corresponding to the other communication account to cancel displaying the object information of the target object in the client list; the client list is a list in the first communication application based on logging in with the other communication account.

26. The device according to any one of claims 16 to 21, characterized in that The moving module is further configured to move the target communication account corresponding to the target object into a group management list in response to an anti-interference permission setting operation triggered in the information page; wherein the target communication account moved into the group management list is prohibited from joining the customer communication group; The sending module is further configured to send a fourth prompt message to the target object, indicating that the target object has been moved into the group management list, based on the target communication account.

27. The device according to any one of claims 16 to 21, characterized in that The device further comprises: A search module, configured to search for media data originating from the target communication account locally or in a backend server corresponding to the first communication application; the media data including at least one of communication messages, audio data, image data, and video data; a marking module, configured to mark the state of the media data to obtain media data in a target state; The deleting module is configured to delete the media data when the duration of the target state satisfies a duration condition.

28. An information processing device for a target object, characterized in that: The device comprises: a receiving module configured to receive a request for moving into an exception list submitted by a first communication application; the request for moving into an exception list is generated by the first communication application in response to an activation operation of an exception list moving control; a move-in module, configured to move the target communication account specified in the move-in request to the exception list into an anti-interference exception list; the target communication account is an account of the target object in the account system corresponding to the second communication application, and is added to the address book of the first communication application, and the target object receives various messages through the second communication application; the first communication application and the second communication application are applications of different account systems; the target communication account moved to the exception list by the operator will not be able to send messages to the communication account of the operator; A sending module, configured to send a second prompt message to the first communication application indicating that the target communication account has been successfully moved to the abnormal list; The second prompt message is used to instruct the first communication application to cancel displaying the object information of the target object in the address book.

29. The device according to claim 28, characterized in that The receiving module is further configured to receive a communication message sent by the sender via the second communication application; The sending module is further configured to, when the communication account of the sender is the same as the target communication account in the abnormal list, send a reminder message of a sending failure to the sender via the background server of the second communication application.

30. The device according to claim 28, wherein The receiving module is further configured to receive a group joining request sent by the inviting party via the second communication application; The sending module is further configured to, when the communication account of the inviting party is the same as the target communication account in the abnormal list, feed back a reminder message of invitation failure to the inviting party through the background server of the second communication application.

31. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 15 are implemented.

32. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 15 are implemented.

33. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 15 are implemented.

Images