Information display method and device, electronic equipment, computer readable storage medium and computer program product

By displaying tags added by historical service recipients and tags automatically generated based on behavior in the social interface, the problem of users not being able to see feature tags is solved, improving service efficiency and user experience.

CN122346342APending Publication Date: 2026-07-07TENCENT TECHNOLOGY (SHENZHEN) CO LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
TENCENT TECHNOLOGY (SHENZHEN) CO LTD
Filing Date
2025-01-06
Publication Date
2026-07-07

AI Technical Summary

Technical Problem

In social applications, users cannot see the feature tags that other users have set for customers, which leads to reduced service efficiency and the inability to provide personalized services.

Method used

Display the information entry point for the second object in the social interface, showcasing the first feature tags added by historical service objects and the second feature tags automatically generated based on behavior, thereby improving the richness and visibility of the tags.

Benefits of technology

By displaying rich tag information, the efficiency of the service recipient in providing services to the second recipient is improved, thus enhancing the user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122346342A_ABST
    Figure CN122346342A_ABST
Patent Text Reader

Abstract

The application provides an information display method and device, electronic equipment, computer readable storage medium and computer program product; the method comprises the following steps: in the social interface of a first object, display a first information entrance of a second object, the first information entrance is used for viewing the characteristic label of the second object, the first object is a service object providing service for the second object, and there is at least one historical service object for the second object for the service, in response to the trigger operation for the first information entrance, display at least one first characteristic label of the second object, and display at least one second characteristic label of the second object, the first characteristic label is a label added by at least one historical service object, and the second characteristic label is a label automatically generated based on the behavior of the second object, and the behavior has an association relationship with the historical service object. Through the application, the richness of the displayed label can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to an information display method, device, electronic device, computer-readable storage medium, and computer program product. Background Technology

[0002] In related technologies, users can provide services to customers through social applications. For different customers, users can set corresponding feature tags for customers in the social application, which can improve the efficiency of providing services to customers. However, when a user needs to transfer a customer to another user, that is, after another user adds the customer, the other user cannot see the feature tags set by the user for the customer, which reduces the efficiency of the other user in providing services to customers. Summary of the Invention

[0003] This application provides an information display method, apparatus, electronic device, computer-readable storage medium, and computer program product, which can improve the richness of displayed labels, improve the service efficiency of providing services, and thus improve the user experience.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] This application provides an information display method, the method comprising:

[0006] In the social interface of the first object, the first information entry of the second object is displayed, and the first information entry is used to view the feature tags of the second object;

[0007] Wherein, the first object is a service object that provides services to the second object, and for the service, the second object has at least one historical service object;

[0008] In response to a trigger operation on the first information entry, at least one first feature label of the second object is displayed, and at least one second feature label of the second object is displayed;

[0009] Wherein, the first feature tag is a tag added to at least one of the historical service objects, and the second feature tag is a tag automatically generated based on the behavior of the second object, wherein the behavior is associated with the historical service object.

[0010] This application provides an information display device, the device comprising:

[0011] The display module is used to display the first information entry of the second object in the social interface of the first object, and the first information entry is used to view the feature tags of the second object;

[0012] Wherein, the first object is a service object that provides services to the second object, and for the service, the second object has at least one historical service object;

[0013] A response module is configured to, in response to a trigger operation on the first information entry, display at least one first feature label of the second object, and display at least one second feature label of the second object;

[0014] Wherein, the first feature tag is a tag added to at least one of the historical service objects, and the second feature tag is a tag automatically generated based on the behavior of the second object, wherein the behavior is associated with the historical service object.

[0015] In the above scheme, the response module is further configured to respond to a trigger operation for the first information entry and display the details page of the second object; in the first display area of ​​the details page, display at least one first tag group of the second object and display at least one first feature tag in the first tag group; in the second display area of ​​the details page, display at least one second tag group of the second object and display at least one second feature tag in the second tag group; wherein, the at least one first tag group belongs to a first tag type, and the at least one second tag group belongs to a second tag type.

[0016] In the above scheme, the number of second feature tags in the second tag group is multiple; the response module is also used to display multiple second feature tags in the second tag group in the order of their generation time.

[0017] In the above scheme, the number of second feature tags in the second tag group is multiple; the response module is further configured to, in response to the number of target second feature tags in the second tag group reaching a target number, display corresponding first prompt information in the associated area of ​​the second tag group; wherein, the first prompt information is used to prompt at least one of the following: perform corresponding processing on the second object, or the score corresponding to the second tag group.

[0018] In the above scheme, the number of first feature tags in the first tag group is multiple; the display module is further configured to display multiple first feature tags in the first tag group according to the priority of each first feature tag; or, according to the addition time of each first feature tag, display multiple first feature tags in the first tag group.

[0019] In the above scheme, the response module is further configured to execute at least one of the following: in response to a first deletion instruction triggered for the first tag group, delete the first tag group indicated by the first deletion instruction, and the first feature tag in the first tag group indicated by the first deletion instruction; in response to a second deletion instruction triggered for the first feature tag, delete the first feature tag indicated by the second deletion instruction; in response to a third deletion instruction triggered for the second tag group, display a second prompt message, the second prompt message being used to indicate that the second tag group cannot be deleted.

[0020] In the above scheme, the response module is further configured to display a first deletion control after displaying at least one first feature label of the second object, the first deletion control being used to delete the first feature label added to the historical service object; in response to a trigger operation on the first deletion control, display at least one of the historical service objects for selection; and in response to a selection operation on the at least one of the historical service objects, delete the first feature label added to the selected historical service object.

[0021] In the above scheme, the response module is further configured to display a second deletion control, which is used to delete the first feature tag added before the target time point of the historical service object; in response to the trigger operation of the second deletion control, a time point setting interface is displayed; and in response to the target time point set in the time point setting interface, the first feature tag added before the target time point is deleted.

[0022] In the above scheme, there are multiple first feature tags, and there are different first feature tags among the multiple first feature tags; the response module is also used to display a statistical control for the multiple first feature tags, the statistical control is used to count the number of different first feature tags; in response to the trigger operation of the statistical control, the number of different first feature tags is displayed.

[0023] In the above scheme, the response module is further configured to, in response to a trigger operation on the first information entry, display an object entry, wherein the object entry is configured to, display historical service objects that provide services to the second object;, in response to a trigger operation on the object entry, display at least one of the historical service objects;, in response to a selection operation on the historical service object, display a synchronization control corresponding to the selected historical service object; and, in response to a trigger operation on the synchronization control, display a first feature tag added by the selected historical service object to the second object.

[0024] In the above scheme, the response module is further configured to, in response to a trigger operation for the first information entry, display a first add control for adding the first feature tag; in response to a trigger operation for the first add control, display at least one candidate first feature tag added by the historical service object for the second object; in response to a selection instruction for the candidate first feature tag, control the selected first feature tag to be in a selected state; and in response to a confirmation instruction triggered for the first feature tag in the selected state, display the first feature tag in the selected state.

[0025] In the above scheme, the response module is further configured to display a second add control, which is used for the first object to add a third feature label for the second object; in response to a trigger operation on the second add control, a label editing area is displayed, and the edited label is displayed in the label editing area; in response to a confirmation instruction on the edited label, the third feature label added by the first object for the second object is displayed.

[0026] In the above scheme, the first feature tag belongs to the first tag group; the response module is also used to respond to the determination instruction for the edited tag, and when the third feature tag added by the first object to the second object belongs to the first tag group, and the number of first feature tags in the first tag group displayed reaches the number threshold, cancel the display of the first feature tag with the earliest addition time, and highlight the third feature tag.

[0027] In the above scheme, the first feature tag belongs to the first tag group, and the first feature tag is displayed in the first display area of ​​the details page of the second object; the response module is further configured to, when the third feature tag belongs to the first tag group, display the third feature tag added by the first object for the second object in the first display area; when the third feature tag does not belong to the first tag group, display the third feature tag in the third display area of ​​the details page, wherein the third tag group is parallel to the first tag group.

[0028] In the above scheme, the at least one first feature tag belongs to a first tag group; the response module is further configured to display a third add control, which is used to add a third tag group for the second object, the third tag group being parallel to the first tag group; in response to a trigger operation on the third add control, a tag group editing area is displayed, and the edited third tag group is displayed in the tag group editing area; in response to a viewing instruction triggered on the added third tag group, a fourth add control is displayed, which is used for the first object to add feature tags belonging to the third tag group for the second object.

[0029] In the above scheme, the response module is further configured to display a third prompt message and a second information entry in the social interface; wherein, the third prompt message is configured to indicate the number of third objects with updated second feature tags among the objects associated with the first object within a preset time period, and the second information entry is configured to view the updated second feature tags of the third objects; in response to a trigger operation on the second information entry, the third objects are displayed, and the updated second feature tags of the third objects are displayed accordingly.

[0030] In the above scheme, the response module is further configured to display an analysis control after displaying the third object and correspondingly displaying the updated second feature label of the third object. The analysis control is configured to analyze the change of the second feature label corresponding to the third object. In response to the trigger operation of the analysis control, the module displays the change result of the second feature label corresponding to the third object within a preset time period, and displays a fourth prompt message generated based on the change result. The fourth prompt message is configured to prompt the reason information corresponding to the change result.

[0031] This application provides an electronic device, the electronic device comprising:

[0032] Memory is used to store executable instructions or computer programs.

[0033] The processor, when executing computer-executable instructions or computer programs stored in the memory, implements the information display method provided in the embodiments of this application.

[0034] This application provides a computer-readable storage medium storing a computer program or computer-executable instructions, which, when executed by a processor, implements the information display method provided in this application.

[0035] This application provides a computer program product, including a computer program or computer executable instructions. When the computer program or computer executable instructions are executed by a processor, they implement the information display method provided in this application.

[0036] The embodiments of this application have the following beneficial effects:

[0037] In an information display method provided in this application embodiment, a first information entry of a second object is displayed in the social interface of a first object. The first information entry is used to view the feature tags of the second object. The first object is a service object that provides services to the second object. For the service, the second object has at least one historical service object. In response to the trigger operation of the first information entry, at least one first feature tag of the second object and at least one second feature tag of the second object are displayed. The first feature tag is a tag added by at least one historical service object. The second feature tag is a tag automatically generated based on the behavior of the second object, and the behavior is associated with the historical service object.

[0038] This application allows for the display of first feature tags added by historical service objects to second objects, as well as second feature tags automatically generated based on the behavior of the second object. This enhances the richness of the displayed tags. When the first feature tags added by historical service objects to second objects are displayed, the first object can learn about the first feature tags added by historical service objects to second objects, thereby improving the efficiency of the first object in providing services to the second object and enhancing the user experience (i.e., the first object, the second object, and the historical service objects). Attached Figure Description

[0039] Figure 1 This is a schematic diagram of the structure of the information display system provided in the embodiments of this application;

[0040] Figure 2 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application;

[0041] Figure 3 This is a flowchart illustrating the information display method provided in the embodiments of this application. Figure 1 ;

[0042] Figure 4 This is a schematic diagram of the object information page provided in the embodiments of this application. Figure 1 ;

[0043] Figure 5 This is a flowchart illustrating the information display method provided in the embodiments of this application. Figure 2 ;

[0044] Figure 6 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 1 ;

[0045] Figure 7 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 2 ;

[0046] Figure 8 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 3 ;

[0047] Figure 9 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 4 ;

[0048] Figure 10 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 6 ;

[0049] Figure 11 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 7 ;

[0050] Figure 12 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 8 ;

[0051] Figure 13 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 9 ;

[0052] Figure 14 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 ;

[0053] Figure 15 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 one;

[0054] Figure 16 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 two;

[0055] Figure 17 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 three;

[0056] Figure 18 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 Four;

[0057] Figure 19 This is a schematic diagram of the time point setting interface provided in the embodiments of this application;

[0058] Figure 20 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 five;

[0059] Figure 21 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 six;

[0060] Figure 22This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 seven;

[0061] Figure 23 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 eight;

[0062] Figure 24 This is a schematic diagram of the label details page provided in an embodiment of this application;

[0063] Figure 25 This is a schematic diagram of the tag selection page provided in the embodiments of this application. Figure 1 ;

[0064] Figure 26 This is a schematic diagram of the tag selection page provided in the embodiments of this application. Figure 2 ;

[0065] Figure 27 This is a schematic diagram of the label editing area provided in an embodiment of this application;

[0066] Figure 28 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 Nine;

[0067] Figure 29 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 2 ten;

[0068] Figure 30 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 2 eleven;

[0069] Figure 31 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 2 twelve;

[0070] Figure 32 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 2 Thirteen;

[0071] Figure 33 This is a schematic diagram of the editing page provided in the embodiments of this application. Figure 1 ;

[0072] Figure 34 This is a schematic diagram of the editing page provided in the embodiments of this application. Figure 2 ;

[0073] Figure 35 This is a schematic diagram of the social interface provided in the embodiments of this application. Figure 1 ;

[0074] Figure 36 This is a schematic diagram of the social interface provided in the embodiments of this application. Figure 2 ;

[0075] Figure 37 This is a schematic diagram of the object information page provided in the embodiments of this application. Figure 2 ;

[0076] Figure 38 This is a schematic diagram of an object information page in related technologies;

[0077] Figure 39 This is a schematic diagram of the relationship chain provided in the embodiments of this application;

[0078] Figure 40 This is a schematic diagram of the first structure provided in the embodiments of this application. Figure 1 ;

[0079] Figure 41 This is a schematic diagram of the first structure provided in the embodiments of this application. Figure 2 . Detailed Implementation

[0080] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0081] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0082] In the following description, the terms "first, second, third" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first, second, third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0083] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0084] Unless otherwise defined, all technical and scientific terms used in the embodiments of this application have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in the embodiments of this application is for the purpose of describing the embodiments of this application only and is not intended to limit this application.

[0085] In the implementation of this application, the collection and processing of relevant data should strictly comply with the requirements of relevant laws and regulations, obtain the informed consent or separate consent of the personal information subject, and carry out subsequent data use and processing within the scope of laws and regulations and the authorization of the personal information subject.

[0086] Before providing a further detailed description of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained, and the nouns and terms involved in the embodiments of this application shall be interpreted as follows.

[0087] 1) Responding to: used to indicate the conditions or states on which the operation is performed depends. When the conditions or states on which it depends are met, one or more operations can be performed in real time or with a set delay. Unless otherwise specified, there is no restriction on the order in which the multiple operations are performed.

[0088] 2) Human-Computer Interaction Interface (HCI): An interface that provides human-computer interaction functions or displays feature labels. Examples include Graphical User Interface (GUI) displays, such as Augmented Reality (AR) interfaces, Virtual Reality (VR) interfaces, Voice User Interface (VUI) interfaces, Interactive Projection Interfaces (using projection technology to display information on a flat surface), Eye-tracking interfaces (interfaces controlled by detecting the user's gaze), Holographic Interfaces (three-dimensional holograms formed by projecting images using holographic projection technology, allowing users to see stereoscopic images without special glasses), Multimodal Interfaces (interfaces combining multiple interaction methods, such as tactile, visual, and auditory interaction), and Brain-Machine Interfaces (BMI) interfaces.

[0089] 3) In-service succession refers to a resource allocation method in which a current employee of an enterprise (i.e., the historical service recipient) needs to reassign customers (i.e., the second customer) or customer groups (the group of objects composed of the second customer) to other current employees (i.e., the first customer) to continue providing services due to job changes or other reasons.

[0090] 4) Succession upon leaving the company refers to a resource allocation method in which, after a member (i.e., a former client) leaves the company, the client(i.e., the second client) or the client group(s consisting of the second client) corresponding to the member(i.e., the former client) is assigned to other current members(i.e., the first client) to continue providing services.

[0091] 5) Client, also known as user terminal, refers to the program that provides local services to users in contrast to the server. Except for some applications that can only run locally, it is generally installed on ordinary client machines and needs to work in conjunction with the server. That is, there needs to be a corresponding server and service program on the network to provide the corresponding services. Thus, a specific communication connection needs to be established between the client and the server to ensure the normal operation of the application. For example, a game client is a tool client that can display the game in the form of a desktop background.

[0092] During the research process, the inventors discovered the following technical problems in the relevant technology:

[0093] Technical Issue 1: In related technologies, users can provide services to customers through social applications. For different customers, users can set corresponding feature tags for customers in the social application, which can improve the efficiency of providing services to customers. However, when a user needs to transfer a customer to another user, that is, after another user adds the customer, the other user cannot see the feature tags set by the user for the customer. In other words, other users cannot see the feature tags, which reduces the efficiency of other users in providing services to customers and prevents other users from providing personalized services to customers.

[0094] This application provides an information display method, an information display device, an electronic device, a computer-readable storage medium, and a computer program product, which can improve the richness of displayed labels, improve the service efficiency of providing services, and thus improve the user experience.

[0095] See Figure 1 , Figure 1 This is a schematic diagram of the structure of the information display system provided in the embodiments of this application. Figure 1 The information display system 100 shown supports an information display application. Terminals (terminals 400-1, 400-2, and 400-3 are shown as examples) are connected to server 200 through network 300. Network 300 can be a wide area network, a local area network, or a combination of both.

[0096] Terminal 400-1 corresponds to the first object, terminal 400-2 corresponds to the second object, and terminal 400-3 corresponds to the historical service object. There can be multiple historical service objects. Figure 1The example shown is only one terminal corresponding to a historical service object (i.e., terminal 400-3).

[0097] Terminal 400-1 is used to display the social interface of the first object in the graphical interface 410-1, and in the social interface of the first object, display the first information entry of the second object, which is used to view the feature tags of the second object.

[0098] The first object can provide services to the second object through terminal 400-1, and the second object can be provided with services by the first object through terminal 400-2. That is, the first object provides services to the second object. For the service, the second object has at least one historical service object. The historical service object can provide services to the second object through terminal 400-3, and the second object can be provided with services by the historical service object through terminal 400-2.

[0099] In response to a trigger operation targeting the first information entry, terminal 400-1 can send an information acquisition request to server 200. Based on the information acquisition request, server 400-1 can send at least one first feature tag of the second object and at least one second feature tag of the second object to terminal 400-1.

[0100] Terminal 400-1 can display at least one first feature label of the second object, and display at least one second feature label of the second object, wherein the first feature label is a label added to at least one historical service object, and the second feature label is a label automatically generated based on the behavior of the second object, and the behavior is associated with the historical service object.

[0101] In response to a tag addition instruction triggered by terminal 400-3, terminal 400-3 can send the tag added based on the tag addition instruction to server 200. The tag added based on the tag addition instruction is the first feature tag.

[0102] For the second feature tag, a behavior acquisition prompt can be displayed on terminal 400-2. When terminal 400-2 receives a confirmation instruction for the behavior acquisition prompt, it indicates that the second object agrees to have its behavior acquired. In response to the confirmation instruction triggered by the behavior acquisition prompt, terminal 400-2 can upload the second object's behavior to server 200, so that server 200 can generate a second feature tag based on the second object's behavior. The behavior acquisition prompt serves to indicate whether the second object agrees to have its behavior acquired, and the confirmation instruction triggered by the behavior acquisition prompt indicates that the second object, through terminal 400-2, agrees to have its behavior uploaded to server 200.

[0103] This application allows for the display of first feature tags added by historical service objects to second objects, as well as second feature tags automatically generated based on the behavior of the second object. This enhances the richness of the displayed tags. When displaying the first feature tags added by historical service objects to second objects, the first object can learn about the first feature tags added by historical service objects to second objects. This improves the efficiency of the first object in providing services to the second object and enhances the user experience (i.e., the first object, the second object, and the historical service objects).

[0104] The following describes an electronic device that implements the information display method provided in the embodiments of this application. The electronic device that implements the information display method in the embodiments of this application can be a terminal, a server, or a combination of the two.

[0105] In some embodiments, the terminal can be implemented as various types of terminals such as laptops, tablets, desktop computers, set-top boxes, smartphones, smart speakers, smartwatches, smart TVs, and in-vehicle terminals.

[0106] In some embodiments, the server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. The terminal and server can be connected directly or indirectly via wired or wireless communication, which is not limited in this embodiment.

[0107] See Figure 2 , Figure 2 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Figure 2 The illustrated electronic device includes at least one processor 410, a memory 450, at least one network interface 420, and a user interface 430. The various components of the electronic device are coupled together via a bus system 440. It is understood that the bus system 440 is used to implement communication between these components. In addition to a data bus, the bus system 440 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in… Figure 2 The general labeled all buses as Bus System 440.

[0108] The processor 410 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0109] User interface 430 includes one or more output devices 431 that enable the presentation of media content, including one or more speakers and / or one or more visual displays. User interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0110] The memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state storage, hard disk drives, optical disk drives, etc. The memory 450 may optionally include one or more storage devices physically located away from the processor 410.

[0111] The memory 450 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), and the volatile memory may be random access memory (RAM). The memory 450 described in this application embodiment is intended to include any suitable type of memory.

[0112] In some embodiments, memory 450 is capable of storing data to support various operations, examples of which include programs, modules, and data structures or subsets or supersets thereof, as illustrated below.

[0113] Operating system 451 includes system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, driver layer, etc., for implementing various basic business functions and handling hardware-based tasks;

[0114] The network communication module 452 is used to reach other electronic devices via one or more (wired or wireless) network interfaces 420, exemplary network interfaces 420 including: Bluetooth, WiFi, and Universal Serial Bus (USB), etc.

[0115] Presentation module 453 is configured to enable the presentation of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more output devices 431 (e.g., a display screen, a speaker, etc.) associated with user interface 430;

[0116] The input processing module 454 is used to detect and translate one or more user inputs or interactions from one or more input devices 432.

[0117] In some embodiments, the information display device provided in this application can be implemented in software. Figure 2 An information display device 455 stored in memory 450 is shown. This device can be software in the form of programs and plug-ins, and includes the following software modules: a display module 4551 and a response module 4552. These modules are logically linked and can therefore be arbitrarily combined or further separated according to the functions they implement. The functions of each module will be described below.

[0118] In other embodiments, the information display device provided in this application can be implemented in hardware. As an example, the information display device provided in this application can be a processor in the form of a hardware decoding processor, which is programmed to execute the information display method provided in this application. For example, the processor in the form of a hardware decoding processor can be one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0119] In some embodiments, the terminal or server can implement the information display method provided in this application by running various computer-executable instructions or computer programs. For example, computer-executable instructions can be microprogram-level commands, machine instructions, or software instructions. Computer programs can be native programs or software modules in an operating system; they can be native applications (APPs), i.e., programs that need to be installed in the operating system to run, such as instant messaging APPs or office collaboration APPs; or they can be applets that can be embedded in any APP, i.e., programs that only need to be downloaded to a browser environment to run. In summary, the aforementioned computer-executable instructions can be any form of instruction, and the aforementioned computer programs can be any form of application, module, or plugin.

[0120] The following describes the information display method provided in the embodiments of this application. As mentioned above, the electronic device implementing the information display method of the embodiments of this application can be a terminal, a server, or a combination of both. Therefore, the executing entity of each step will not be described again below.

[0121] See Figure 3 , Figure 3 This is a flowchart illustrating the information display method provided in the embodiments of this application. Figure 1 The following is combined with Figure 3 The steps shown are illustrated using a terminal as an example to explain the information display method provided in the embodiments of this application.

[0122] In step 101, the first information entry of the second object is displayed in the social interface of the first object.

[0123] In practical applications, the terminal can have one or more of the following installed: instant messaging applications, office collaboration applications, and social networking applications. In response to a trigger operation on any of these applications, the social interface of the first target can be displayed. Each of these applications has an account corresponding to the first target logged in.

[0124] In the social interface of the first object, you can see the accounts of other objects added by the account corresponding to the first object. There can be one or more other objects. In response to a trigger operation on any of the accounts of other objects, the object information page of the selected other object's account can be displayed.

[0125] The selected "other objects" are the second objects, meaning that the object information page for the second object's account can be displayed. The second object's account is the account added by the first object, meaning that the second object's account and the first object's account are friends. The first object can send service-related information to the second object's account through its own account, thus enabling the first object to provide services to the second object.

[0126] The first object is the service object that provides services to the second object. There can be one or more service objects providing services to the second object, which can be configured according to actual usage needs. For each service, the second object can also have at least one historical service object; that is, the number of historical service objects can be one or more. Correspondingly, historical service objects can send service-related information to the second object's account through their accounts, thereby enabling historical service objects to provide services to the second object. The conversion of the object providing services to the second object from the initial service object to the first object can be achieved through either in-service inheritance or out-of-service inheritance.

[0127] The object information page displays information about the second object, information added by the first object to the second object's account, the first information entry point, and a conversation control. The information about the second object can include the name of the second object, the nickname of the second object's account, the avatar of the second object's account, the account of the second object, and the organization to which the second object belongs. The organization can be a school, a company, etc., and can be set according to actual usage needs.

[0128] The information added by the first object to the account of the second object can include notes added by the first object to the account of the second object, descriptive information added by the first object to the second object, and feature tags (i.e., third feature tags) added by the first object to the second object. The feature tags can also be the first feature tag and / or the second feature tag; that is, the feature tags can be at least one (or more) of the first feature tag, the second feature tag, and the third feature tag. The first feature tag, the second feature tag, and the third feature tag will be explained later.

[0129] The first information entry is used to view the feature tags of the second object. The conversation control is used to have a conversation with the second object. In response to the trigger operation of the conversation control, a conversation page can be displayed to show the conversation between the account of the first object and the account of the second object, thus enabling the first object to have a conversation with the second object. No specific limitations are made here.

[0130] For example, see Figure 4 , Figure 4 This is a schematic diagram of the object information page provided in the embodiments of this application. Figure 1The object information page 401 can display the nickname 403 of the second object's account, the name of the company to which the second object belongs (i.e., company name 402), the avatar 408 of the second object's account, the description information added by the first object for the second object (i.e., description 404), the feature tags (i.e., tags 405) corresponding to the second object, the name (i.e., real name 406) of the second object, the first information entry 407, and the conversation control 409.

[0131] Here, label 405 can be one or more of the first feature label, second feature label, and third feature label, which will be explained later. Real name 406 is the real name of the second object. The first object entry is used to view the feature labels of the second object. The description information corresponding to the conversation control 409 is "send message". Description 404 can be set according to the actual usage needs of the first object; for example, description 404 can be the second object's birthday.

[0132] See also Figure 3 In step 102, in response to a trigger operation for the first information entry, at least one first feature label of the second object is displayed, and at least one second feature label of the second object is displayed.

[0133] The first feature label is a label added to at least one historical service object; that is, the first feature label can be a label added to one historical service object or a label added to multiple historical service objects. The second feature label is a label automatically generated based on the behavior of the second object, and the behavior is associated with the historical service object and / or the first object.

[0134] The following explains the method for automatically generating the second feature tag. First, in order to generate the second feature tag, the consent of the user (i.e., the second object) can be obtained. For the second object's terminal, a behavior acquisition prompt can be displayed on the second object's terminal. In response to the refusal instruction triggered by the behavior acquisition prompt, the behavior of the second object can be not acquired. Accordingly, the second feature tag of the second object that refuses to acquire the prompt will not be updated.

[0135] In response to a confirmation command triggered by a prompt message regarding behavior acquisition, the behavior of the second object can be acquired, which is equivalent to the second object authorizing the acquisition of its behavior. The behavior of the second object can include login account behavior, conversation behavior with the first object or a previous service object, and transaction behavior with the first object or a previous service object, etc., and can be specifically configured according to actual usage requirements.

[0136] The login account behavior can include one or more of the following: login time, login frequency, and online duration of the second object. When the behavior is associated with the first object, the behavior of conversing with the first object can include one or more of the following: duration of conversation with the first object, frequency of conversation with the first object, and conversation method with the first object. The conversation method can be one or more of the following: conversation via text, conversation via audio, and conversation via video.

[0137] Accordingly, when there is a relationship between the behavior and the historical service object, the behavior of having a conversation with the historical service object may include one or more of the following: the duration of the conversation with the historical service object, the frequency of the conversation with the historical service object, and the conversation method of the conversation with the historical service object.

[0138] When an action is related to a first object, the action of transacting with the first object may include one or more of the following: the time of transacting with the first object, the frequency of transacting with the first object, and the transacting method with the first object.

[0139] Accordingly, when there is a relationship between the behavior and the historical service object, the behavior of transacting with the historical service object may include one or more of the following: the time point of transacting with the historical service object, the frequency of transacting with the historical service object, and the transacting method.

[0140] After acquiring the behavior of the second object, a second feature label can be automatically generated based on the behavior at preset time intervals. If the behavior of the second object includes one type, the relationship between the behavior of the second object and a preset threshold of that behavior object can be determined. Based on the behavior of the second object and the correspondence between the preset threshold and candidate labels, candidate labels corresponding to the behavior of the second object can be determined, and the candidate labels corresponding to the behavior of the second object can be used as the second feature labels.

[0141] In some embodiments, during the communication between the first object and the second object, in order to facilitate the first object to better serve the second object, if a voice call is used, the first object can ask the second object whether it can obtain the behavior of the second object. If the second object agrees, the terminal of the first object can obtain the behavior of the second object and generate a second feature tag based on the behavior of the second object.

[0142] For example, the first object can be a customer service representative who provides services to customers, and the second object can be the customer. The customer service representative can ask the customer if they can obtain the behavior of the second object in order to provide more personalized services to customers. With the consent of the second object, the behavior of the second object can be obtained, and a second feature label can be generated based on the behavior of the second object.

[0143] If a text-based conversation is used, the first object can send a behavior acquisition prompt to the second object through its terminal. In response to the confirmation command triggered by the behavior acquisition prompt, the second object's terminal can send a confirmation request to the first object's terminal or server. Thus, the first object's terminal or server can acquire the second object's behavior and generate a second feature tag based on the second object's behavior.

[0144] To facilitate understanding, the method for generating the second feature label is explained below with specific examples. For instance, the number of historical conversation days between the second object and the first object within the past 7 days can be obtained. If the number of historical conversation days is greater than or equal to 3 days (i.e., a preset threshold), the second feature label of the second object can be determined to be active. If the number of historical conversation days is greater than 1 day (i.e., a preset threshold) but less than 3 days (i.e., a preset threshold), the second feature label of the second object can be determined to be silent. If the number of historical conversation days is less than or equal to 1 day (i.e., a preset threshold), the second feature label of the second object can be determined to be dormant.

[0145] In some embodiments, see Figure 5 , Figure 5 This is a flowchart illustrating the information display method provided in the embodiments of this application. Figure 2 The following is combined with Figure 5 The steps shown are for Figure 3 Step 102 is illustrated below.

[0146] In step 1021, in response to the trigger operation for the first information entry, the details page of the second object is displayed.

[0147] In some embodiments, the first information entry is displayed on the object information page. In response to a trigger operation on the first information entry, the details page of the second object can be displayed, effectively allowing switching from the object information page to the details page. For example, inheriting... Figure 4 In response to Figure 4 The triggering operation of the first information entry 407 shown is described in the following example. Figure 6 , Figure 6 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 1 This can display the details page 601 of the second object.

[0148] In step 1022, at least one first tag group of the second object is displayed in the first display area of ​​the details page, and at least one first feature tag in the first tag group is displayed.

[0149] In step 1023, at least one second tag group of the second object is displayed in the second display area of ​​the details page, and at least one second feature tag in the second tag group is displayed.

[0150] The details page includes at least two display areas. In some embodiments, the details page may include a first display area and a second display area. The first display area may be the display area corresponding to a first tag type, and the second display area may be the display area corresponding to a second tag type object.

[0151] The first tag type is the object tag type, and the first display area corresponding to the first tag type is used to display the tag groups and / or feature tags added by the object providing services to the second object. The second tag type is the system tag type, and the second display area corresponding to the second tag type is used to display the tag groups and / or feature tags generated based on the behavior of the second object. At least one first tag group belongs to the first tag type, at least one third tag group belongs to the first tag type, and at least one second tag group belongs to the second tag type.

[0152] For cases where the details page only includes a first display area and a second display area, the first display area of ​​the details page can display at least one first tag group added by the historical service object for the second object, and at least one first feature tag in the first tag group. The first display area of ​​the details page can also display at least one third tag group added by the first object for the second object, and at least one third feature tag in the third tag group. The second display area of ​​the details page can display at least one second tag group for the second object, and at least one second feature tag in the second tag group.

[0153] The second tag group can be pre-set, or it can be determined based on the type of behavior of the second object. For example, for login account behavior and conversation behavior with the first object or historical service object, the second tag group can be determined as object activity. Or, for transaction behavior with the first object or historical service object, the second tag group can be determined as payment behavior.

[0154] For example, see Figure 6The details page 601 may include a first display area and a second display area. The first display area is a display area for displaying system tag type 602, object activity 603, payment behavior 604, feature tags corresponding to object activity 603, and feature tags corresponding to payment behavior 604. The second display area is a display area for displaying object tag type 605, object information 606, object hobbies 607, object following 608, feature tags corresponding to object information 606, feature tags corresponding to object hobbies 607, and feature tags corresponding to object following 608.

[0155] In some embodiments, two second tag groups for the second object can be displayed in the display area corresponding to the display system tag type 602 (i.e., the second display area). The second tag groups are object activity 603 and payment behavior 604. In the display area corresponding to the display object tag type 605 (i.e., the first display area), a first tag group added by the historical service object for the second object can be displayed. The first tag group is object information 606. Two third tag groups added by the first object for the second object can also be displayed. The third tag groups are object interests 607 and object following 608.

[0156] In some embodiments, at least one first tag group of the second object may be displayed in the first display area of ​​the details page. In response to a viewing instruction for the first tag group, at least one first feature tag in the first tag group corresponding to the viewing instruction may be displayed. The number of first tag groups corresponding to the viewing instruction may be one or more. The viewing instruction may be triggered by controls, voice, body movements, etc., and no specific limitation is made here.

[0157] Accordingly, in the first display area of ​​the details page, at least one third tab group of the second object is displayed. In response to a view command for the third tab group, at least one third feature tag in the third tab group corresponding to the view command can be displayed. In the second display area of ​​the details page, at least one second tab group of the second object is displayed. In response to a view command for the second tab group, at least one second feature tag in the second tab group corresponding to the view command can be displayed.

[0158] In some embodiments, for each tag group (corresponding to a first tag group, a second tag group, or a third tag group), a viewing control corresponding to each tag group can be displayed. In response to a trigger operation on the viewing control, at least one feature tag in the tag group corresponding to the viewing control can be displayed.

[0159] For example, see Figure 6 ,exist Figure 6 The image only shows the viewing control 609 for object information 606 (first tab group). In response to a triggering operation targeting the viewing control 609, see [link to relevant documentation]. Figure 7 , Figure 7 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 2 This allows the display of a first feature tag 610 within object information 606 (first tag group). This method enables users to view the corresponding feature tags based on their specific needs, thus improving the user experience.

[0160] against Figure 7 The first feature label 610 can be any label that can represent information about the second object added by the historical service object for the second object. For example, the first feature label 610 can be the second object's birthday, gender, education level, etc., without specific limitations.

[0161] In some embodiments, the details page may display a tag viewing control for viewing feature tags in all tag groups. In response to a trigger operation on the tag viewing control, the feature tags corresponding to all tag groups may be displayed. In some embodiments, in response to a trigger operation on the first information entry point, at least one first tag group of the second object and at least one first feature tag in the first tag group may be displayed directly in the first display area of ​​the details page. In the second display area of ​​the details page, at least one second tag group of the second object and at least one second feature tag in the second tag group may be displayed.

[0162] For example, see Figure 8 , Figure 8 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 3 In response to a trigger operation on the tag viewing control (or a trigger operation on the first information entry point), the system can display the second feature tag 801 of object activity 603 (second tag group), the second feature tag 802 of payment behavior 604 (second tag group), the first feature tag 803 of object information 606 (first tag group), the third feature tag 804 of object interests 607 (third tag group), and the third feature tag 805 of object following 608 (third tag group). This allows for the display of different feature tags, enhancing the richness of the displayed feature tags.

[0163] against Figure 8 The second feature label 801 can be any feature label automatically generated based on the behavior of the second object that can characterize the activity level of the second object. For example, the second feature label 801 can be active, silent, dormant, etc. The second feature label 802 can be any feature label automatically generated based on the behavior of the second object that can characterize the payment behavior of the second object.

[0164] The third feature label 804 is a feature label added by any first object to the second object that can characterize the second object's interests. For example, the third feature label 804 can be mountain climbing, swimming, reading, etc. The third feature label 805 is a feature label added by any first object to the second object that can characterize the information that the second object is interested in. For example, the third feature label 805 can be meeting A. The specific settings can be configured according to actual usage needs and are not specifically limited here.

[0165] The details page may also include a first display area, a second display area, and a third display area. The first display area may be the display area corresponding to the third tag type, the second display area may be the display area corresponding to the second tag type object, and the third display area may be the display area corresponding to the fourth tag type.

[0166] The first tag type includes a third tag type and a fourth tag type. The third tag type is a historical tag type, and the first display area corresponding to the third tag type is used to display the tag groups and / or feature tags added by the historical service objects for the second object. The fourth tag type is the current object tag type, and the third display area corresponding to the fourth tag type is used to display the tag groups and / or feature tags added by the first object for the second object.

[0167] For a details page that includes a first display area, a second display area, and a third display area, at least one first tag group of the second object and at least one first feature tag from the first tag group can be displayed in the first display area of ​​the details page. At least one second tag group of the second object and at least one second feature tag from the second tag group can be displayed in the second display area of ​​the details page. At least one third tag group of the second object and at least one third feature tag from the third tag group can be displayed in the third display area of ​​the details page.

[0168] For example, to undertake Figure 4 In response to Figure 4 The triggering operation of the first information entry 407 shown is described in the following example. Figure 9 , Figure 9 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 4In the first display area of ​​the details page 901 (i.e., the display area corresponding to historical tag type 905), a first tag group (i.e., interests 906) of the second object can be displayed, along with a first feature tag (i.e., exercise 910) within that first tag group. In the second display area of ​​the details page (i.e., the display area corresponding to system tag type 902), a second tag group (i.e., object activity 903) of the second object can be displayed, along with a second feature tag (i.e., activity 909) within that second tag group. In the third display area of ​​the details page (i.e., the display area corresponding to current object tag type 907), a third tag group (i.e., consumption habits 908) of the second object can be displayed, along with a third feature tag (saving 904) within that third tag group. This method allows for the display of tag groups from different sources and their corresponding feature tags in different display areas, thereby increasing the richness of the displayed feature tags.

[0169] In some embodiments, the number of second label features in the second label group is multiple. The above-mentioned display of at least one second feature label in the second group can be achieved by displaying multiple second feature labels in the second label group in the order of their generation time.

[0170] In some embodiments, the number of second feature tags to be displayed can be determined based on the area of ​​the display area corresponding to the second tag group (i.e., the second display area) and the area occupied by the second feature tag. In this way, the number of second feature tags to be displayed can be automatically adjusted.

[0171] The font size of the second feature labels can be adjusted, and / or the area of ​​the display area corresponding to the second label group (i.e., the second display area) can be adjusted, based on the preset number of second feature labels to be displayed. Specific settings can be configured according to actual usage requirements. In this way, the font size of the second feature labels and / or the area of ​​the second display area can be automatically adjusted, thus enabling clearer display of the second feature labels.

[0172] In some embodiments, when displaying the second feature label, a first identifier can be added to the second feature label with the smallest difference between the generation time and the current time. The first identifier is used to identify that the corresponding second feature label is the most recently generated. In this way, the user can intuitively know the most recently generated second feature label.

[0173] In some embodiments, the display of the second feature label may correspond to the display of the generation time of the second feature label. For example, see... Figure 10 , Figure 10This is a schematic diagram of the details page provided in the embodiments of this application. Figure 6 On the details page 1001, multiple second feature tags in the object activity 1003 (i.e., second feature tags) included in the system tag type 1002 are displayed in chronological order of their generation time, and the generation time of the second feature tags is also displayed accordingly.

[0174] exist Figure 10 The diagram shows Active 1004 (second feature label) and its generation time 1006, Silent 1005 (second feature label) and its generation time 1007, Active 1008 (second feature label) and its generation time 1009, where generation time 1006 is later than generation time 1007, and generation time 1007 is later than generation time 1009. That is, in... Figure 10 In this approach, multiple second feature labels within a second label group are displayed in ascending order of their generation time. This enhances the richness of the displayed second feature labels and demonstrates the evolution of these labels based on the behavior of the second object.

[0175] In some embodiments, the number of second feature tags in the second tag group is multiple. After at least one second tag group of the second object is displayed in the second display area of ​​the details page, in response to the target number of target second feature tags in the second tag group reaching a target number, a corresponding first prompt message is displayed in the associated area of ​​the second tag group.

[0176] The first prompt message is used to prompt at least one of the following: to perform corresponding processing on the second object, or to provide a score for the second tag group. The associated area of ​​the second tag group belongs to the second display area, which is the area formed by a preset distance interval from the second tag group.

[0177] In some embodiments, when the second label group indicates that the object is active, that is, when the second label group is used to characterize the activity level of the second object, the second feature label can be a label characterizing different levels of activity. For example, the second feature label can be active, silent, and dormant. Accordingly, the target second feature label can be any one of active, silent, and dormant, and of course, it can be specifically divided according to actual usage requirements, which is not specifically limited here.

[0178] The processing performed on the second object can be configured according to actual usage needs. For example, if the target's second feature tag is "active," the processing performed on the second object could be to recommend other services to the second object; that is, the first prompt message could include recommending service A to the second object. In this way, the user experience of the first object can be improved, and it can be ensured that the first object can provide more personalized services to the second object.

[0179] For example, if the target's second feature label is "silent," the corresponding processing for the second object could be to periodically send greeting messages to the second object. That is, the first prompt message could include "Please send greeting messages to the second object periodically, with the next message to be sent on day X." This approach improves the user experience for the first object and ensures that the first object can provide more personalized services to the second object.

[0180] The score corresponding to the second label group can be calculated based on the second feature label in the second label group, or it can be calculated based on the second feature label in the second label group whose difference from the current time is less than the first difference. For example, "active" can be converted into the first parameter, "silent" into the second parameter, and "dormant" into the third parameter. Then, the first parameter is multiplied by the first weight to obtain the first product, the second parameter is multiplied by the second weight to obtain the second product, and the third parameter is multiplied by the third weight to obtain the third product. The sum of the first product, the second product, and the third product is then used as the score corresponding to the second label group.

[0181] See Figure 11 , Figure 11 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 7 The following is combined with Figure 11 The first prompt information provided in this application embodiment is explained as follows: System tag type 1102 can be displayed on the details page 1101. A second tag group can be displayed for system tag type 1102. The second tag group is object activity 1103. The associated area of ​​the second tag group displays the corresponding rating, which is 83. The rating is based on the condition that the activity tag in object activity 1103 reaches 5 (the target number). Figure 11 The values ​​of 1104 (Active), 1105 (Silent), 1106 (Active), 1107 (Active), 1108 (Active), and 1109 (Active) displayed in the image are calculated to obtain the results. Figure 11 The text also shows that corresponding processing is performed on the second object, specifically "Recommend Service B to the second object". The first prompt information can include a rating of 83 and the recommendation of Service B to the second object. The associated area of ​​the second tag group is the area that displays the rating of 83 and the recommendation of Service B to the second object.

[0182] The scoring process is as follows: Determine the percentage of "active" among all the secondary feature tags (i.e., Active 1104, Silent 1105, Active 1106, Active 1107, Active 1108, and Active 1109), multiply this percentage by 100, and round down to obtain a score of 83. This method increases the diversity of content displayed on the details page, making it easier for users to obtain the initial information and improving the user experience.

[0183] In some embodiments, the number of first feature tags in the first tag group is multiple. The above-mentioned display of at least one first feature tag in the first tag group can be achieved in the following ways: In the first implementation, multiple first feature tags in the first tag group can be displayed according to the priority of each first feature tag.

[0184] The following describes how the priority of each first feature tag is determined. In some embodiments, the priority of the first feature tag can be determined based on at least one of the following: the number of historical service objects to which the first feature tag was added, the interaction information for the first feature tag, and the pre-set weight of the first feature tag.

[0185] The number of historical service objects with the first feature tag is positively correlated with the priority of the first feature tag. In other words, the more historical service objects with the first feature tag, the higher the priority of the first feature tag. The number of historical service objects with the first feature tag can be converted into the first priority parameter. If the priority is determined solely by the number of historical service objects with the first feature tag, then the first priority parameter is the priority of the first feature tag.

[0186] The interaction information for the first feature tag can include one or more of positive and negative interaction counts. The number of positive interactions is positively correlated with the priority of the first feature tag; that is, the higher the number of positive interactions, the higher the priority of the first feature tag. Positive interaction counts can be converted into positive interaction parameters, and negative interaction counts into negative interaction parameters. Then, a second priority parameter can be determined based on these parameters. For example, the positive and negative interaction parameters can be added together to obtain the second priority parameter. The specific settings can be configured according to actual usage requirements. If priority is determined solely by the interaction information of the first feature tag, then the second priority parameter is the priority of the first feature tag.

[0187] If the priority is determined by the number of historical service objects with the first feature tag and the interaction information of the first feature tag, then the first priority parameter can be multiplied by the fourth weight to obtain the fourth product, the second priority parameter can be multiplied by the fifth weight to obtain the fifth product, and the sum of the fourth product and the fifth product can be used as the priority of the first feature tag.

[0188] The pre-set weight of the first feature label can be used as the third priority parameter. If the priority is determined by the number of historical service objects with the first feature label and the pre-set weight of the first feature label, the sum of the fourth product and the third priority parameter can be used as the priority of the first feature label. If the priority is determined by the interaction information of the first feature label and the pre-set weight of the first feature label, the sum of the fifth product and the third priority parameter can be used as the priority of the first feature label.

[0189] If the priority is determined by the number of historical service objects to which the first feature label is added, the pre-set weight of the first feature label, and the interaction information of the first feature label, then the sum of the fourth product, the fifth product, and the third priority parameter can be used as the priority of the first feature label.

[0190] In some embodiments, priorities can be divided into high, medium, and low. Of course, multiple priorities can also be defined according to actual usage needs, such as first priority, second priority, ..., seventh priority, etc. To make it easier for users to intuitively understand the priorities, the priority of the first feature label can be displayed when the first feature label is shown.

[0191] For example, see Figure 12 , Figure 12 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 8 On the details page 1201, historical tag type 1202 (i.e., the first tag type) can be displayed. Historical tag type 1202 includes hobbies 1203 (i.e., the first tag group), and hobbies 1203 includes three first feature tags: running 1204 (first feature tag), reading 1205 (first feature tag), and hiking 1206 (first feature tag). Running 1204 has a high priority, reading 1205 has a high priority, and hiking 1206 has a medium priority. This approach increases the diversity of content displayed on the details page and allows users to more intuitively understand the priority of the first feature tags, thereby improving the user experience.

[0192] The second implementation method displays multiple first feature tags in the first tag group according to the addition time of each first feature tag. The addition time of the first feature tag can be the time when the first feature tag was added to the corresponding historical service object, or the time when the first object added the first feature tag to the details page. The specific settings can be configured according to actual usage requirements.

[0193] In some embodiments, the addition time of the first feature tag can be displayed when the first feature tag is displayed. This can improve the diversity of the content displayed on the details page and make it easier for users to intuitively know the addition time of the first feature tag, thereby improving the user experience.

[0194] The information display method provided in this application can display both first feature tags added by historical service objects to a second object and second feature tags automatically generated based on the behavior of the second object. This improves the richness of the displayed tags. When displaying the first feature tags added by historical service objects to a second object, the first object can know the first feature tags added by historical service objects to the second object, which can improve the efficiency of the first object in providing services to the second object and enhance the user experience (i.e., the first object, the second object, and the historical service objects).

[0195] When the first object knows the feature tags (i.e., the first feature tag, the second feature tag, and the third feature tag) corresponding to the second object, it can easily provide personalized services for the second object, thereby solving the above-mentioned technical problem 1.

[0196] The following describes the methods for deleting feature tags. In the first deletion method, after displaying at least one first tag group of the second object and at least one first feature tag within the first tag group, in response to a first deletion instruction triggered against the first tag group, the first tag group and the first feature tag within the first tag group are deleted.

[0197] In some embodiments, a third delete control for a first tab group can be displayed. In response to a trigger operation on the third delete control, which is equivalent to a first delete command triggered on the first tab group, the first tab group indicated by the first delete command and the first feature tag in the first tab group indicated by the first delete command can be deleted. This is equivalent to canceling the display of the first tab group corresponding to the first delete command and the first feature tag in the first tab group in the first display area of ​​the details page.

[0198] For example, see Figure 13 , Figure 13 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 9The first object can long press on the object information 606 (first tag group) to display the third delete control 1301 of the object information 606 in the details page 601. In response to the trigger operation of the third delete control 1301 (equivalent to the first delete command triggered on the object information 606), the object information 606 and the first feature tag 803 in the object information 606 can be deleted.

[0199] See Figure 14 , Figure 14 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 After deleting object information 606 and the first feature tag 803, it can be displayed. Figure 14 The corresponding page, compared to Figure 13 , Figure 14 The display of object information 606 and the first feature tag 803 is cancelled. In this way, the first tag group and the first feature tag within it can be deleted according to actual usage needs, improving the efficiency of deleting the first feature tag.

[0200] The second deletion method, to further meet the actual deletion needs of the first object, deletes the first feature tag indicated by the second deletion instruction in response to a second deletion instruction triggered on the first feature tag. In some embodiments, a fourth deletion control corresponding to each first feature tag can be displayed. Responding to a triggering operation on the third deletion control is equivalent to responding to a second deletion instruction triggered on the first feature tag and deleting the first feature tag indicated by the second deletion instruction.

[0201] For example, see Figure 15 , Figure 15 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 First, users can swipe left on the first feature tag 803, which will display a delete control 1501 for the first feature tag 803 on the details page 601. Responding to a trigger operation on the delete control 1501 (equivalent to a second delete command triggered on the first feature tag 803), the first feature tag 803 can be deleted. This method allows for the deletion of the first feature tag according to actual usage needs, thus improving the user experience.

[0202] In some embodiments, after deleting one or more first feature tags in the first tag group, if there are other first feature tags in the first tag group, the first feature tags belonging to the first tag group and not deleted can be displayed after the first feature tags indicated by the second deletion instruction are deselected.

[0203] For example, see Figure 16 , Figure 16This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 Second, after deleting the first feature tag 803, the display of the first feature tag 803 can be canceled, and the first feature tag 1502 belonging to the object information 606 that has not been deleted can be displayed. In this way, after deleting the first feature tag, the first feature tags belonging to the first tag group that have not been deleted can be displayed, so that users can intuitively know the first feature tags that have not been deleted.

[0204] In some embodiments, after deleting one or more first feature tags in the first tag group, if there are no other first feature tags in the first tag group, the first feature tags indicated by the second deletion instruction can be de-displayed, and no feature tags or other content can be displayed in the associated area of ​​the first tag group, so that users can easily and intuitively know whether there are any remaining first feature tags in the first tag group.

[0205] For the first and second deletion methods mentioned above, a fifth deletion control can be displayed on the details page. In response to a trigger operation on the fifth deletion control, both the first tag group and the first feature tag on the details page can be made selectable. In response to a selection operation on at least one of the first tag group and the first feature tag, the selected first tag group and / or first feature tag is made selected. In response to a confirmation command triggered on the selected first tag group and / or first feature tag, the selected first tag group and / or first feature tag can be deleted. In this way, one or more of the first tag group and first feature tag to be deleted can be selected, thereby improving deletion efficiency.

[0206] The third deletion method, in response to a fourth deletion instruction triggered for the third tag group, deletes the third tag group indicated by the fourth deletion instruction, as well as the third feature tag in the third tag group indicated by the fourth deletion instruction.

[0207] The fourth deletion method responds to a fifth deletion command triggered by the third feature tag, deleting the third feature tag indicated by the fifth deletion command. The deletion method for the third feature tag is the same as the deletion method for the first feature tag, and the deletion method for the third tag group is the same as the deletion method for the first tag group. The first deletion method can be equivalently replaced by the third deletion method, and the second deletion method can be equivalently replaced by the fourth deletion method. These details will not be elaborated further here.

[0208] The fifth deletion method, in response to the third deletion command triggered on the second tab group, displays a second prompt message. This second prompt message indicates that the second tab group cannot be deleted. The second prompt message can be displayed in the associated area of ​​the second tab group, or it can be displayed as a pop-up window or a floating layer.

[0209] For example, see Figure 17 , Figure 17 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 Third, in response to a third deletion command triggered on the second tab group, a pop-up window 1701 can be displayed, showing a second prompt message: "Unable to delete active object 603". A confirmation control 1702 is also displayed in the pop-up window 1701. In response to a triggering operation on the confirmation control 1702, the pop-up window 1701 can be canceled. In this application, the second tab group is undeletable. In this way, the first object can be informed that the second tab group is undeletable, thereby improving the user experience of the first object.

[0210] The sixth deletion method, in response to a sixth deletion command triggered on the second feature tag, displays a fourth prompt message. This fourth prompt message indicates that the second feature tag cannot be deleted. The fourth prompt message can be displayed in the associated area of ​​the second tag group, or it can be displayed as a pop-up window or a floating layer. In this application, the second feature tag is undeletable. Through this method, the first object can be informed that the second feature tag cannot be deleted, thereby improving the user experience for the first object.

[0211] The seventh deletion method involves displaying at least one first feature tag of the second object, and then displaying one or more historical service objects corresponding to the first feature tag on the details page. To further improve the efficiency of deleting feature tags, a first deletion control can be displayed on the details page, wherein the first deletion control is used to delete the first feature tag added to the historical service object.

[0212] In response to a trigger operation on the first delete control, at least one historical service object is displayed for selection (i.e., one or more historical service objects can be displayed). All displayed historical service objects are in an optional state and can display one or more of the following: name, nickname, account, and avatar.

[0213] For example, see Figure 18 , Figure 18 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 Fourth, in response to the triggered operation of the first delete control, two historical service objects can be displayed on the details page 1801. Figure 18The document shows historical service objects 1802 and 1803, and also shows selection controls for historical service object 1802 and historical service object 1803.

[0214] In response to a selection operation targeting at least one historical service object, the first feature tag added to the selected historical service object is deleted. In some embodiments, in response to a selection operation targeting at least one historical service object, the first feature tag added to the selected historical service object can be deleted in real time. This method enables rapid deletion of the first feature tag corresponding to the historical service object, thereby improving the efficiency of deleting the first feature tag.

[0215] In some embodiments, each historical service object has a corresponding selection control. In response to the triggering operation of the selection control for at least one historical service object, the historical service object is controlled to be in a selected state. In response to the confirmation instruction triggered for the historical service object in the selected state, the first feature tag added to the selected historical service object can be deleted.

[0216] For example, see Figure 18 , Figure 18 The selection controls for historical service object 1802, historical service object 1803, and confirmation control 1804 shown can control historical service object 1802 to be selected in response to a trigger operation on the selection control for historical service object 1802. Figure 18 (Unmarked in the text) In response to a trigger operation on the confirmation control 1804, or a confirmation command triggered on a selected historical service object, the first feature tag added to the historical service object 1802 can be deleted. This method allows for the rapid deletion of the first feature tag corresponding to the historical service object, thereby improving the efficiency of deleting the first feature tag.

[0217] The eighth deletion method involves displaying the sixth deletion control. This control is used to delete the third feature tag added to the first object. In response to a trigger operation on the sixth deletion control, the third feature tag added to the first object is deleted. This method allows for one-click deletion of the third feature tag added to the first object, thus improving the efficiency of deleting third feature tags.

[0218] The ninth deletion method involves displaying a second deletion control after showing at least one first feature label of the second object. The second deletion control is used to delete the first feature labels of the historical service object before the target time point in which they were added. Each first feature label has a corresponding historical addition time, which is the time when the first feature label of the historical service object was added.

[0219] In response to a trigger operation on the second delete control, a time point setting interface is displayed. This interface is used to set a target time point. In some embodiments, a time point selection area may also be displayed within the interface, allowing the first object to select the target time point. In some embodiments, a time point input area may be displayed within the interface, allowing the first object to input the target time point. The unit corresponding to the target time point may include one or more of year, month, day, hour, minute, and second, and can be specifically set according to actual usage requirements.

[0220] For example, see Figure 19 , Figure 19 This is a schematic diagram of the time point setting interface provided in the embodiment of this application. In response to the trigger operation of the second delete control, the time point setting interface 1901 can be displayed. The time point setting interface 1901 can display the time point input area 1902, and the input prompt information is displayed in the time point input area 1902. The input prompt information is "Please enter the time point".

[0221] In response to the target time point set in the time point setting interface, the first feature label added before the target time point is deleted. In some embodiments, for a time point selection area, in response to a trigger operation for the time point selection area, multiple candidate time points can be displayed. In response to a trigger operation for the candidate time points, a target time point set based on the time point selection area can be determined. Therefore, in response to the target time point set based on the time point selection area, the first feature label added before the target time point can be deleted.

[0222] In some embodiments, for a time point input area, in response to an input operation for the time point input area, the input target time point can be obtained, which is equivalent to obtaining the target time point set based on the time point selection area. In response to the target time point set based on the time point selection area, the first feature label added before the target time point can be deleted.

[0223] For example, see Figure 19 In response to an input operation to the time input area 1902, the target time point can be obtained and displayed in the time input area 1902. Figure 19 (Not shown in the image), in response to a trigger operation on the determination control 1903, which is equivalent to responding to a target time point set based on the time point selection area, the first feature tag added before the target time point can be deleted. In this way, the first feature tag before the target time point can be deleted, thereby improving the efficiency of coral first feature tag removal.

[0224] In some embodiments, there may be multiple first feature labels, and there may be different first feature labels among the multiple first feature labels. That is, any two first feature labels among the multiple first feature labels may be the same or different.

[0225] After displaying at least one first feature label of the second object, a statistical control for multiple first feature labels is displayed. The statistical control is used to count the number of different first feature labels and, in response to a trigger operation on the statistical control, to display the number of different first feature labels.

[0226] In some embodiments, in response to a trigger operation on the statistics control, the first feature labels can be grouped, and the first feature labels with a similarity greater than a first similarity threshold can be divided into a group. For each group, the number of first feature labels in the group can be counted, thereby displaying the number of different first feature labels.

[0227] In some embodiments, since the display area of ​​the details page is limited, only the first feature tags whose occurrence frequency is greater than the first quantity threshold can be displayed, so that the first object can know the number of the first feature tags with a high occurrence frequency.

[0228] For example, see Figure 20 , Figure 20 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 Fifth, the statistics control 2002 can be displayed on the details page 2001. This is in response to... Figure 20 The triggering operation of the statistical control 2002 shown can display the quantity of each first feature tag in the form of a pop-up window or a floating layer. For example, the quantity of first feature tag a can be displayed as quantity a, the quantity of first feature tag b as quantity b, and the quantity of first feature tag c as quantity c, where quantity a is greater than quantity b, and quantity b is greater than quantity c. In this way, the richness of the content displayed on the details page can be improved, and users can easily and intuitively know the quantity of each first feature tag.

[0229] To further facilitate users' intuitive understanding of the quantity of different primary feature labels, bar charts, line charts, pie charts, etc., can be used to display the quantity of different primary feature labels. For example, see... Figure 21 , Figure 21 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 Sixth, in response to Figure 20The triggering operation of the statistical control 2002 shown can display a pop-up window 2104, which includes a bar chart, specifically the bar corresponding to the first feature label 2101, the bar corresponding to the first feature label 2102, and the bar corresponding to the first feature label 2103.

[0230] In this configuration, the bar corresponding to the first feature label 2101 is associated with the number 7, meaning there are 7 first feature labels 2101; the bar corresponding to the first feature label 2102 is associated with the number 6, meaning there are 6 first feature labels 2102; and the bar corresponding to the first feature label 2103 is associated with the number 4, meaning there are 4 first feature labels 2103. All three first feature labels 2101, 2102, and 2103 are different. This method enhances the richness of the content displayed on the details page and allows users to intuitively understand the quantity of each different first feature label.

[0231] In some embodiments, after displaying the number of each first feature tag, a first analysis control may be displayed. In response to an analysis command triggered by the first analysis control, the analysis result corresponding to the analysis command may be displayed. In some embodiments, the analysis command may be an analysis command for the first feature tag with the largest number. Accordingly, the analysis result may be an analysis result generated based on the first feature tag with the largest number. The analysis result may include one or more of the following: suggestion information, service recommendation information, and session guidance information to facilitate the first object to provide services to the second object. The suggestion information may be information that the first object is advised to learn or understand. The service recommendation information is used to recommend other services to the second object. The session guidance information is used to guide the first object and the second object to have a session.

[0232] For example, the most frequent primary feature tag is "sports," indicating that the second user likes sports. Suggested information could suggest that the first user learn more about sports-related content. Service recommendation information could suggest that the first user recommend sports-related services and / or products to the second user. Conversation guidance information could guide the first user to engage in a conversation with the second user through sports-related content. This approach further facilitates the first user in providing personalized services to the second user, thereby improving the user experience.

[0233] In some embodiments, the analysis instruction can analyze a first feature label whose quantity is greater than a second quantity threshold, and then display the analysis results generated for the first feature label whose quantity is greater than the second quantity threshold. For the description of the analysis results, please refer to the above description of the analysis results and make equivalent substitutions, which will not be repeated here.

[0234] Below are the methods for adding feature tags. The first method, in response to a trigger operation on the first information entry point, displays a details page. The fourth display area of ​​the details page can show object entries, where object entries are used to display historical service objects that provided services to the second object. Object entries can also be called historical object entries. For example, see... Figure 22 , Figure 22 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 7. The object entry 2202 can be displayed in the fourth display area of ​​the details page 2201.

[0235] In response to a trigger operation targeting an object entry, at least one historical service object is displayed. In some embodiments, when the number of historical service objects providing services to the second object is one, one historical service object can be displayed in response to a trigger operation targeting the object entry. When the number of historical service objects providing services to the second object is multiple, multiple historical service objects can be displayed in response to a trigger operation targeting the object entry. That is, in response to a trigger operation targeting the object entry, all historical service objects providing services to the second object can be displayed.

[0236] In response to a selection operation for a historical service object, the synchronization control corresponding to the selected historical service object is displayed. In some embodiments, in response to a selection operation for a historical service object, the synchronization control corresponding to the selected historical service object can be displayed in the associated area of ​​the historical service object. The associated area can be found in the description of the associated area for the second tab group, and the corresponding content is replaced accordingly, which will not be repeated here.

[0237] For example, see Figure 23 , Figure 23 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 10 eight, Figure 23 The document shows historical service objects 2301, 2302, 2303, and 2304. In response to a trigger operation on historical service object 2301, historical service object 2301 can be selected. Figure 23 The historical service object 2301 is selected (i.e., displayed in bold) and its synchronization control 2305 can be displayed in the associated area of ​​the historical service object 2301.

[0238] In some embodiments, multiple historical service objects can be selected simultaneously, and a synchronization control can be displayed for each historical service object. In some embodiments, in response to a viewing instruction for a historical service object, a tag details page for the historical service object can be displayed. The tag details page can display one or more first feature tags added by the historical service object for a second object, and the synchronization control for the historical service object can also be displayed on the tag details page.

[0239] For example, see Figure 24 , Figure 24 This is a schematic diagram of the tag details page provided in the embodiments of this application. In response to a viewing command for a historical service object 2301, a tag details page 2401 for the historical service object 2301 can be displayed. The tag details page 2401 displays multiple first feature tags added by the historical service object 2301 for the second object. Figure 24 The image shows first feature label 2402, first feature label 2403, and first feature label 2404, and... Figure 24 The document also shows a synchronization control 2405 for historical service objects.

[0240] In response to a trigger operation on the synchronization control, the first feature tag added by the selected historical service object for the second object is displayed. In some embodiments, the above steps correspond to... Figure 3 In the case of step 102 shown, in response to a trigger operation on the synchronization control, a first feature tag added by the selected historical service object for the second object can be displayed in the first display area of ​​the details page. For example, in response to a trigger operation on the synchronization control... Figure 23 The triggering operation of the synchronization control 2305 shown can display the first feature tag added by the historical service object 2301 for the second object in the first display area of ​​the details page.

[0241] For example, in response to... Figure 24 The triggering operation of the synchronization control 2405 shown can display the first feature tags 2402, 2403, and 2404 added by the historical service object 2301 for the second object in the first display area of ​​the first details page. In this way, the corresponding first feature tags can be displayed by selecting a historical service object, which can improve the richness of the content displayed on the details page. Furthermore, the first object can know the first feature tags added by the historical service object for the second object, which can improve the efficiency of the first object in providing services to the second object and enhance the user experience (i.e., the first object, the second object, and the historical service object).

[0242] The above steps do not correspond Figure 3In the case of step 102 shown, in response to a trigger operation on the synchronization control, a synchronization result can be displayed. This synchronization result indicates that the first feature tag added by the historical service object to the second object has been synchronized to the details page of the second object. Where the above steps do not correspond... Figure 3 In the case of step 102 shown, it is possible to Figure 3 If step 102 is performed before the first object clicks the first information entry again, in response to the trigger operation for the first information entry, at least one first feature tag added by the pre-synchronized historical service object for the second object can be displayed, and at least one second feature tag of the second object can be displayed.

[0243] In the above steps Figure 3 If the action is performed after step 102, then in response to a triggering operation on the first information entry, at least one first feature tag of the second object and at least one second feature tag of the second object can be displayed. After a new first feature tag (i.e., a first feature tag, new only for differentiation) is added to the second object by the synchronization history service object, in response to a triggering operation on the first information entry, at least one first feature tag and at least one new first feature tag of the second object can be displayed, as well as at least one second feature tag of the second object.

[0244] In other words, users can choose to add the first method at any time based on their actual needs, and Figure 3 Step 102 shown can be repeated multiple times, and the specific settings can be configured according to actual usage needs. In this way, the first feature tag added by the historical service object for the second object can be added, thereby improving the user experience.

[0245] The second method of adding features, in response to a trigger operation on the first information entry, displays a first add control for adding a first feature tag. In response to a trigger operation on the first add control, at least one candidate first feature tag added by a historical service object for the second object can be displayed. The number of candidate first feature tags can be one or more.

[0246] In some embodiments, in response to a triggering operation on the first add control, a tag selection page can be displayed. If there are multiple candidate first feature tags, the tag selection page can display multiple candidate first feature tags in one or more of the following order: the order of the number of historical service objects corresponding to the candidate first feature tags (i.e., sorting criteria), the order of the weights of the candidate first feature tags (i.e., sorting criteria) set in advance, and the order of the number of interaction information for the candidate first feature tags (i.e., sorting criteria). To facilitate the user's understanding of the sorting method, a fifth prompt message corresponding to the sorting criteria can be displayed. The fifth prompt message is used to indicate the sorting criteria of the multiple candidate first feature tags.

[0247] For example, see Figure 25 , Figure 25 This is a schematic diagram of the tag selection page provided in the embodiments of this application. Figure 1 The fifth prompt message can be displayed on the tag selection page 2501. This fifth prompt message reads "The number of historical service recipients, from largest to smallest." Figure 25 The image shows first feature label 2502 (candidate first feature label), first feature label 2503 (candidate first feature label), and first feature label 2504 (candidate first feature label). First feature labels 2502, 2503, and 2504 are arranged in descending order of the number of historical service objects. First feature labels 2502, 2503, and 2504 are all candidate first feature labels.

[0248] In some embodiments, when there are multiple first feature tags, the correspondence between the first feature tags and historical service objects can be displayed on the tag selection page. Specifically, this can be done in various ways, such as adding identifiers, lists, or links of historical service objects. This approach enhances the richness of the displayed correspondence between the first feature tags and historical service objects, making it easier for the first object to intuitively understand this relationship.

[0249] In response to a selection instruction for a candidate first feature label, the selected first feature label is controlled to be in a selected state. In response to a confirmation instruction triggered for the first feature label in the selected state, the first feature label in the selected state is displayed.

[0250] For example, in response to Figure 25 The selection operation of the first feature label 2502 and the first feature label 2503 can control whether the first feature label 2502 and the first feature label 2503 are selected. See [link to documentation]. Figure 26 , Figure 26 This is a schematic diagram of the tag selection page provided in the embodiments of this application. Figure 2 ,exist Figure 26 The first feature label 2502 and the first feature label 2503 can be marked with solid lines to indicate that they are selected. In response to a confirmation command triggered for the selected first feature label, the selected first feature label is displayed. In this way, the selected first feature label can be displayed according to the usage requirements of the first object, thus enabling customized display of feature labels for the second object.

[0251] In some embodiments, the second method of addition can correspond to Figure 3 Step 102 shown can also be performed in Figure 3 Before or before step 102 shown Figure 3 The process is executed after step 102 shown. Specifically, the content corresponding to the first addition method can be replaced with an equivalent one, which will not be elaborated here.

[0252] The third method involves displaying a second add control on the details page. This second add control allows the first object to add a third feature tag specific to the second object. In response to a trigger action on the second add control, a tag editing area is displayed, showing the edited tag. In response to a confirmation command for the edited tag, the third feature tag added by the first object to the second object is displayed.

[0253] In some embodiments, in response to a triggering operation on the second added control, a label editing area can be displayed, and in response to a triggering operation on the label editing area, a candidate third feature label can be displayed. The candidate third feature label can be a feature label added by the first object to an object of another service, or a feature label generated based on the session content between the first object and the second object. The specific settings can be configured according to actual usage requirements.

[0254] In response to a selection operation on a candidate third feature label, the selected label can be displayed in the label editing area. For example, see... Figure 27 , Figure 27 This is a schematic diagram of the label editing area provided in an embodiment of this application. Figure 27The label editing area 2701 shown is displayed, and a candidate label display control 2705 is displayed in the label editing area 2701. In response to a trigger operation on the candidate label display control 2705, multiple candidate third feature labels can be displayed, including third feature label 2702, third feature label 2703, and third feature label 2704. Correspondingly, in response to a selection operation on third feature label 2704, third feature label 2704 can be displayed in the label editing area 2701. Figure 27 (Not shown in the image).

[0255] In some embodiments, in response to a triggering operation on a second additional control, a label editing area can be displayed, and in response to an input operation on the label editing area, a label can be entered in the label editing area.

[0256] In response to a confirmation command for the edited label, a third feature label added by the first object to the second object is displayed. In some embodiments, a confirmation control and a cancellation control may be displayed correspondingly in the label editing area. In response to a triggering operation of the cancellation control, which is equivalent to a cancellation command for the edited label, the label editing area can be de-displayed.

[0257] In response to a trigger operation on a selected control, which is equivalent to a confirmation command on an edited label, the system can display a third feature label added by the first object to the second object. This means displaying either the selected third feature label or the entered third feature label. This method allows for the addition of third feature labels, thereby increasing the richness of the displayed feature labels.

[0258] In some embodiments, the first feature label belongs to a first label group. In response to a determination instruction for the edited label, if the third feature label added by the first object to the second object belongs to the first label group, and the number of first feature labels in the displayed first label group reaches a threshold, it indicates that the associated area corresponding to the first label group does not have a position for displaying the third feature label. To allow users to more intuitively understand the added third feature label, the display of the earliest added first feature label can be canceled, and the third feature label can be highlighted. The highlighting method can be to bold the font of the third feature label, use a pre-set identifier to mark the third feature label, or display the third feature label in a color different from other feature labels. The specific method can be set according to actual usage needs and is not specifically limited here.

[0259] For example, see Figure 28 , Figure 28 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 109. The first tag group 2802 can be displayed on the details page 2801, and multiple first feature tags in the first tag group 2802 can be displayed. The first feature tags may include first feature tag 2803, first feature tag 2804 and first feature tag 2805.

[0260] In response to the instruction to determine the tags obtained from the editing, if the third feature tag 2901 added by the first object to the second object belongs to the first tag group, and the number of first feature tags in the displayed first tag group reaches 3 (a number threshold), see [link to relevant documentation]. Figure 29 , Figure 29 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 2 10. Among the first feature tags 2803, 2804, and 2805, the first feature tag 2805 was added earliest. The first feature tag 2805 can be hidden, and the third feature tag 2901 can be displayed in bold.

[0261] In some embodiments, the area occupied by the first feature label is different from the area occupied by the third feature label. In order to fully display the added third feature label, multiple first feature labels that were added earlier than the preset addition time can be canceled and the third feature label can be highlighted. In this way, the completeness of the display of the third feature label can be improved, thereby improving the user experience.

[0262] In some embodiments, the first feature tag belongs to the first tag group, and the first feature tag is displayed in the first display area of ​​the details page of the second object. The display of the third feature tag added by the first object for the second object can also be achieved by the following method: when the third feature tag belongs to the first tag group, the third feature tag added by the first object for the second object is displayed in the first display area.

[0263] In some embodiments, it can be first determined whether the associated area of ​​the first tag group in the first display area can fully display the third feature tag. If it can be fully displayed, the third feature tag can be displayed in the associated area of ​​the first tag group in the first display area. If there is an arrangement order between the first feature tag and the third feature tag belonging to the first tag group, the third feature tag can also be displayed at the position corresponding to the arrangement order. The specific settings can be configured according to the actual usage. If it cannot be fully displayed, the first feature tag with the earliest addition time can be hidden, and the third feature tag can be highlighted. The third feature tag displayed in the associated area of ​​the first tag group in the first display area is in a fully displayed state, meaning that the third feature tag is not obscured by other content.

[0264] If the third feature tag does not belong to the first tag group, the third feature tag will be displayed in the third display area of ​​the details page. In this case, the third tag group to which the third feature tag belongs can be determined, and then the third feature tag will be displayed in the associated area of ​​the third tag group in the third display area. The third feature tag displayed in the associated area of ​​the third tag group in the third display area is in a complete display state. Specifically, it can be equivalently replaced by the third feature tag displayed in the associated area of ​​the first tag group in the first display area, without specific limitations here.

[0265] The fourth way to add tags is to have at least one first feature tag belonging to the first tag group. A third add control can be displayed on the details page. The third add control is used to add a third tag group for the second object. The third tag group is parallel to the first tag group.

[0266] For example, see Figure 30 , Figure 30 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 2 11. On the details page 3001, there are first tab group 3003, first tab group 3004, second tab group 3002, and third add control 3005.

[0267] In response to a triggering operation on a third add control, a tag group editing area is displayed, and the edited third tag group is displayed in the tag group editing area. In some embodiments, in response to an input operation on the tag group editing area, tags can be entered in the tag editing area.

[0268] For example, see Figure 31 , Figure 31 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 2 Twelve, in Figure 31 The system allows the creation of new tag groups and displays the tag group editing area 3102. Tag group guidance information, such as "Please enter the tag group name," can be displayed in the tag group editing area 3102. In response to input operations in the tag group editing area 3102, tags can be entered in the tag editing area; the entered tag is the third tag group 3101.

[0269] In some embodiments, in response to a trigger operation on the tag group editing area, candidate third tag groups can be displayed. These candidate third tag groups can be tag groups added by the first object for other services, or they can be tag groups generated based on the session content between the first and second objects. The specific configuration can be tailored to actual usage requirements. In response to a selection operation on a candidate third tag group, the selected third tag group can be displayed in the tag group editing area.

[0270] In some embodiments, a third tab group may be added and displayed on the details page, for example, a continuation tab. Figure 30 and Figure 31 In response to Figure 31 The trigger operation of the cancel control shown can display Figure 30 That is, without adding a third tag group, in response to targeting Figure 31 The trigger action of the confirmation control shown can display Figure 32 , Figure 32 This is a schematic diagram of the details page provided in the embodiments of this application. Figure 2 Thirteen, the third tab group 3101 can be displayed on the details page 3001. This method can improve the richness of the displayed tab groups.

[0271] In response to a view command triggered by the added third tag group, a fourth add control is displayed. This fourth add control allows the first object to add feature tags belonging to the third tag group to the second object. In response to a trigger operation on the fourth add control, a tag editing area can be displayed, and the edited tags can be shown in the tag editing area. In response to a confirmation command for the edited tags, the third feature tag belonging to the third tag group added by the first object to the second object is displayed.

[0272] For example, to undertake Figure 32 In response to a viewing command triggered for the third tag group 3101, the editing page of the third tag group can be displayed, and a fourth add control can be shown on the editing page. In some embodiments, other third feature tags belonging to the third tag group can also be displayed on the editing page of the third tag group. In this case, pre-added third feature tags can be used.

[0273] For example, see Figure 33 , Figure 33 This is a schematic diagram of the editing page provided in the embodiments of this application. Figure 1 The third feature tag can be displayed on the editing page 3301. The third feature tag can include "likes to make repeated purchases", "high purchase frequency", and "small single transaction amount". "likes to make repeated purchases" means that the number of times the same product is purchased is greater than a preset number threshold. "high purchase frequency" means that the frequency of purchasing products is greater than a preset frequency threshold. "small single transaction amount" means that the amount of a single transaction is less than a preset amount threshold.

[0274] In response to a trigger operation on the fourth added control, the label editing area can be displayed, and the edited label can be shown in the label editing area. In response to a confirmation command on the edited label, the third feature label belonging to the third label group added by the first object to the second object can be displayed, for example, see [link to relevant documentation]. Figure 34 , Figure 34This is a schematic diagram of the editing page provided in the embodiments of this application. Figure 2 The third feature tag added by the first object to the second object, belonging to the third tag group, is "no bargaining". "No bargaining" means not communicating with the merchant to adjust the price of the product. "No bargaining" can be displayed on the editing page 3301. In this way, the third feature tag can be added, thereby improving the richness of the displayed feature tags.

[0275] In some embodiments, a third prompt message and a second information entry can be displayed in the social interface. The third prompt message is used to indicate the number of third objects with updated second feature tags among the objects associated with the first object within a preset time period. The second information entry is used to view the updated second feature tags of the third objects.

[0276] For example, see Figure 35 , Figure 35 This is a schematic diagram of the social interface provided in the embodiments of this application. Figure 1 In the social interface 3501, accounts of other individuals who are friends with the first individual's account can be displayed; that is, accounts of other individuals who provide services to the first individual can be displayed. Figure 35 The diagram shows other objects that provide services to the first object, namely objects 3503, 3504, and 3505, where objects 3503, 3504, and 3505 can all serve as second objects.

[0277] Figure 35 The document also shows a third prompt message 3506 and a second information entry 3502. The third prompt message is “Two objects updated their second feature tags this week”. “This week” corresponds to a preset duration, and “2” corresponds to the number of third objects that updated their second feature tags. The objects are those associated with the first object, i.e., the third objects.

[0278] In response to a trigger operation targeting the second information entry, a third object is displayed, along with the updated second feature tag of the third object and the second tag group to which the updated second feature tag belongs. For example, see... Figure 36 , Figure 36 This is a schematic diagram of the social interface provided in the embodiments of this application. Figure 2 Since objects 3503 and 3504 have updated second feature labels, objects 3503 and 3504 are third objects, in response to the... Figure 35The triggering operation of the second information entry 3502 shown can display objects 3503 and 3504. For object 3503, it can display: "Active" added under Customer Activity. Customer Activity corresponds to the second tag group, and Activity corresponds to the second feature tag. For object 3504, it can display: "Silent (Second Feature Tag)" added under Customer Activity (Second Tag Group). Customer Activity corresponds to the second tag group, and Silent corresponds to the second feature tag. In this way, the updated second feature tag can be displayed intuitively.

[0279] In some embodiments, after displaying a third object and correspondingly displaying the updated second feature label of the third object, an analysis control can be displayed. The analysis control is used to analyze the changes in the second feature label corresponding to the third object. In response to a trigger operation on the analysis control, the analysis control displays the change results of the second feature label corresponding to the third object within a preset time period and displays a fourth prompt message generated based on the change results. The fourth prompt message is used to prompt the reason information corresponding to the change results.

[0280] In some embodiments, in response to a trigger operation on the analysis control, the number of different second feature tags within a first time period (i.e., a preset time period) can be counted. Based on the number of the most numerous second feature tags, a change result for the second feature tags corresponding to the third object in the content of the first time period can be generated. For example, if the number of active objects is the highest within the first time period, the change result could be that the second object is active.

[0281] Furthermore, based on the change result and the conversation content between the first object or historical object and the second object, a fourth prompt message can be generated. For example, if the change result is that the second object is active, the fourth prompt message can be that the first object is active due to the positive interaction of the first object.

[0282] In some embodiments, a line graph can be generated based on the second feature labels within a second time period (preset time period). The change result of the second object can then be determined based on the line graph. For example, if all the second feature labels within the second time period are the same, the change result can be determined to be stable. Conversely, if any two second feature labels generated at adjacent times within the second time period are different, the change result can be determined to be unstable. Specific settings can be configured according to actual usage requirements. Furthermore, a fourth prompt message can be generated based on the change result and the conversation content between the first object or historical object and the second object.

[0283] In some embodiments, the first feature tag, the second feature tag, and the third feature tag displayed on the details page can be set to be displayed on the object information page, thereby improving the richness of the content displayed on the object information page.

[0284] Regarding the information display method provided in this application embodiment, when the service object providing services to the second object changes from a historical service object to a first object, the first object, in response to an information viewing instruction for the second object, can display the object information page of the second object. For a description of the second object information page, please refer to... Figure 3 The description of the object information page in step 101 shown will not be repeated here.

[0285] See Figure 37 , Figure 37 This is a schematic diagram of the object information page provided in the embodiments of this application. Figure 2 When the service object providing services to the second object is changed from a historical service object to the first object, it is possible to Figure 37 The display area corresponding to label 3702 in the object information page 3701 shows the first feature label 3703 added by the historical service object for the second object, and can also display the second feature label 3704 automatically generated based on the behavior of the second object.

[0286] See Figure 38 , Figure 38 This is a schematic diagram of an object information page in related technologies. When the service object providing services to the second object is changed from a historical service object to the first object, in... Figure 38 The display area corresponding to label 3802 in the object information page 3801 does not display the feature label.

[0287] Compared to related technologies, for scenarios such as job resignation succession and online succession, that is, for situations where a historical service object of a service second object needs to be converted into a first object, this application can display the first feature tag added by the historical service object for the second object, and can also display the second feature tag automatically generated based on the behavior of the second object. This can improve the richness of the displayed tags. When the first feature tag added by the historical service object for the second object is displayed, the first object can know the first feature tag added by the historical service object for the second object, which can improve the efficiency of the first object in providing services to the second object, and can also improve the user experience (i.e., the first object, the second object, and the historical service object).

[0288] In this embodiment of the application, feature labels can be classified, with a first label type and a second label type. The first label type can include multiple first label groups (equivalent to first label subtypes) and multiple third label groups (equivalent to first label subtypes), and the second label type can include multiple second label groups (equivalent to first label subtypes).

[0289] The first tag group includes multiple first feature tags, which are feature tags added by historical service objects to the second object. The number of historical service objects can be one or more. The third tag group includes multiple third feature tags, which are feature tags added by the first object to the second object.

[0290] The second tag group can include customer activity and payment behavior. The second tag group cannot be deleted. The second tag group includes multiple second feature tags. The second feature tags are automatically generated based on the behavior of the second object (i.e., the customer). The second feature tags have an automatic generation cycle. For example, the second feature tags can be updated once a week.

[0291] No new label will be generated if the behavior of the second object does not trigger the generation of a new second feature label. When the behavior of the second object triggers the generation of a new second feature label, the already generated second feature labels are retained. Each second feature label has a corresponding generation time. When displaying second feature labels, the generation time of the second feature labels can be shown, allowing the first object to more quickly understand the historical behavior and behavioral changes of the second object based on second feature labels generated at different times.

[0292] The customer activity (second tag group) includes three second feature tags: active, silent, and dormant. In some embodiments, the second feature tags can be determined based on the object providing services to the second object (the first object or the historical service object) and the second object's conversational behavior. In some embodiments, the active judgment is based on the second object actively contacting the object providing services to the second object for 3 or more days within a week; the silent judgment is based on the object actively contacting the object providing services to the second object for 1-3 days within a week; and the dormant judgment is based on the second object not actively contacting the object providing services to the second object within a week.

[0293] Payment behavior can be determined based on the transaction behavior between the object providing services to the second object and the second object. Payment behavior (second tag group) includes three types of second feature tags: key, potential, and yet to be explored. Among them, key is used to identify the first object that the object currently needs to provide services to the second object spends the main effort on. The judgment method is to determine whether the number of transactions attributed to the object providing services to the second object exceeds 3 times per week or the transaction amount reaches a first preset amount threshold. The first preset amount threshold can be set according to actual usage needs.

[0294] The "Potential" metric identifies a second object that requires time to develop from the object providing services to that second object. It's determined by whether the number of transactions attributed to the object providing services to that second object each week is greater than 0 but less than 3, or whether the transaction amount reaches a second preset threshold. This second preset threshold can be set according to actual usage needs, and it must be less than a first preset threshold. The "To be Discovered" metric identifies a second object that requires less time to develop from the object providing services to that second object. It's determined by whether there are any transactions attributed to that member this week. Of course, the specific settings can be customized according to actual usage needs.

[0295] In some embodiments, after updating the second feature tag (i.e., after generating a new second feature tag), an update notification can be pushed to the first object, and a third notification message and a second information entry can be displayed in the social interface. The third notification message is "x customers automatically updated their second feature tags this week." See also the section on [specific details regarding the second feature tag]. Figure 35-Figure 35 The explanation will not be repeated here.

[0296] For example, in response to a triggering action targeting the second information entry point, it can display that Sister Wang (the second target) has improved her activity and consumption behavior through the active operation of the first target, while Lao Li (the second target) has negative payment behavior due to the passive operation of the first target or other reasons, prompting the user to be potentially churned.

[0297] In this application, the first object can also create a third tab group. The details page can display a third add control. In response to the trigger operation of the third add control, "Please enter the tab group name" can be displayed. After the tab group name is entered, in response to the confirmation instruction triggered by the entered tab group name, the created third tab group can be displayed.

[0298] Of course, you can also delete the third tab group created by the first object. The first object can swipe left on the third tab group. In response to the swipe command on the third tab group, the delete control for the third tab group can be displayed. In response to the trigger operation of the delete control, the third tab group can be deleted.

[0299] After creating the third tag group, a tag addition control (i.e., the fourth addition control) can be displayed on the details page of the third tag group. In response to the trigger operation of the tag addition control, "Please enter the feature tag name" can be displayed. After entering the feature tag name, in response to the confirmation instruction triggered by the entered feature tag name, the created third feature tag can be displayed.

[0300] Of course, it is also possible to delete the third feature label created by the first object. The first object can swipe left on the third feature label. In response to the left swipe command on the third feature label, the delete control for the third feature label can be displayed. In response to the trigger operation of the delete control, the third feature label can be deleted.

[0301] The details page can also display a history tag entry. In response to a trigger operation on the history tag entry, multiple historical service objects can be displayed. In response to a selection operation on a historical service object, the first feature tag added by the selected historical service object to the second object can be displayed, and a synchronization control (i.e., an overlay control) can be displayed. In response to a trigger operation on the synchronization control, the first feature tag added by the selected historical service object to the second object can be synchronized to the details page for display, thereby enabling the first object to view the first feature tag added by the historical service object to the second object.

[0302] In this application, the first object and the second object, or the historical service object and the second object, can be determined by a pre-created relationship chain (ContactRelation). Through the relationship chain, the first object or the historical service object can provide services to the second object.

[0303] For example, see Figure 39 , Figure 39 This is a schematic diagram of the relationship chain provided in the embodiments of this application. In the case of needing to carry out inheritance while employed or after leaving the company, the historical service object A in the relationship chain between the historical service object A and the second object A can be replaced with the first object A. That is, the first object identifier 1 of the historical service object A that provides services to the second object A in the relationship chain can be replaced with the second object identifier 2 of the first object A. The relationship chain also includes the second object identifier, which is the second object A.

[0304] The feature tags of the second object can be stored as a first structure (UserProfile). The first structure contains a first structure identifier (user_profile_id) and a tag group identifier (category_id). The tag group identifier corresponds to a tag group.

[0305] For example, see Figure 40 , Figure 40 This is a schematic diagram of the first structure provided in the embodiments of this application. Figure 1 The first structure 4002 corresponds to the relationship chain 4001. The first structure 4002 has a corresponding first structure identifier. The first structure 4002 includes multiple tag group identifiers. Figure 40The document shows tag group identifiers 4003, 4004, and 4005. Tag group identifier 4003 corresponds to interests (i.e., the first tag group), tag group identifier 4004 corresponds to object information (i.e., the first tag group), and tag group identifier 4005 corresponds to consumption habits (i.e., the third tag group).

[0306] The first structure includes a first feature label, a second feature label, and a third feature label. The deletion field (enable_delete) for the second feature label and the second label group can be set to non-deletable (false), while the deletion field (enable_delete) for the first feature label, the first label group, the third feature label, and the third label group can be set to deletable (true).

[0307] The first, second, and third label groups can be associated with the first structure using label group identifiers. Each of the first, second, and third feature labels has a corresponding label identifier (label_id). To delete a label group, the corresponding label group identifier can be deleted; similarly, to delete a feature label, the corresponding label identifier can be deleted. This allows for the deletion of either a label group or a label identifier.

[0308] A label group can include multiple feature labels, for example, see Figure 41 , Figure 41 This is a schematic diagram of the first structure provided in the embodiments of this application. Figure 2 The first label group 4101 can use label identifiers to associate multiple feature labels. The first label group 4101 includes label identifiers 4102, 4103 and 4104. Label identifier 4102 corresponds to the first feature label 4105, label identifier 4103 corresponds to the first feature label 4106 and label identifier 4104 corresponds to the first feature label 4107.

[0309] The first feature tag can be synchronized by overwriting the name of the first structure with the name of the second structure of the historical image. This method can achieve fast synchronization and save storage space.

[0310] The synchronization of the first feature label can also be achieved by copying the second structure. First, the label group in the first structure can be cleared, the label group in the second structure can be copied and copied to the first structure. For each label group, the feature label under each label group in the first structure can be cleared, the feature label under each label group in the second structure can be copied and copied to the corresponding label group in the first structure, thereby completing the synchronization of the first feature label.

[0311] In some embodiments, based on the first object, all tag groups corresponding to the first object can be deleted, a second tag group can be obtained, and each second tag group can be used as a temporary scalar. Each second tag group is traversed to determine whether the second tag group has a corresponding value, that is, to determine whether the second tag group has a corresponding second feature tag. If it exists, the first object can be inserted into the second tag group, that is, to create a correspondence between the first object and the second tag group. If it does not exist, it means that each second tag group is associated with the first object, that is, the second feature tag included in the second tag group is associated with the first object. Therefore, complete synchronization can be achieved.

[0312] The following description continues to illustrate the exemplary structure of the information display device 455 provided in the embodiments of this application as a software module. In some embodiments, such as Figure 2 As shown, the software module stored in the information display device 455 in the memory 450 may include:

[0313] Display module 4551 is used to display the first information entry of the second object in the social interface of the first object, and the first information entry is used to view the feature tags of the second object;

[0314] Wherein, the first object is a service object that provides services to the second object, and for the service, the second object has at least one historical service object;

[0315] The response module 4552 is configured to, in response to a trigger operation on the first information entry, display at least one first feature label of the second object, and display at least one second feature label of the second object;

[0316] Wherein, the first feature tag is a tag added to at least one of the historical service objects, and the second feature tag is a tag automatically generated based on the behavior of the second object, wherein the behavior is associated with the historical service object.

[0317] In some embodiments, the response module 4552 is further configured to, in response to a trigger operation for the first information entry, display a details page of the second object; in a first display area of ​​the details page, display at least one first tag group of the second object, and display at least one first feature tag in the first tag group; in a second display area of ​​the details page, display at least one second tag group of the second object, and display at least one second feature tag in the second tag group; wherein the at least one first tag group belongs to a first tag type, and the at least one second tag group belongs to a second tag type.

[0318] In some embodiments, the number of second feature tags in the second tag group is multiple; the response module 4552 is further configured to display multiple second feature tags in the second tag group in chronological order of their generation time.

[0319] In some embodiments, the number of second feature tags in the second tag group is multiple; the response module 4552 is further configured to, in response to the number of target second feature tags in the second tag group reaching a target number, display corresponding first prompt information in the associated area of ​​the second tag group; wherein, the first prompt information is used to prompt at least one of the following: performing corresponding processing on the second object, or the score corresponding to the second tag group.

[0320] In some embodiments, the number of first feature tags in the first tag group is multiple; the display module 4551 is further configured to display multiple first feature tags in the first tag group according to the priority of each first feature tag; or, to display multiple first feature tags in the first tag group according to the addition time of each first feature tag.

[0321] In some embodiments, the response module 4552 is further configured to perform at least one of the following: in response to a first deletion instruction triggered for the first tag group, delete the first tag group indicated by the first deletion instruction and the first feature tag in the first tag group indicated by the first deletion instruction; in response to a second deletion instruction triggered for the first feature tag, delete the first feature tag indicated by the second deletion instruction; and in response to a third deletion instruction triggered for the second tag group, display a second prompt message, the second prompt message being used to indicate that the second tag group cannot be deleted.

[0322] In some embodiments, the response module 4552 is further configured to: display a first delete control after displaying at least one first feature label of the second object, the first delete control being configured to delete the first feature label added to the historical service object; display at least one of the historical service objects for selection in response to a triggering operation of the first delete control; and delete the first feature label added to the selected historical service object in response to a selection operation of the at least one of the historical service objects.

[0323] In some embodiments, the response module 4552 is further configured to display a second deletion control, the second deletion control being configured to delete the first feature tag added before the target time point added by the historical service object; in response to a trigger operation on the second deletion control, display a time point setting interface; and in response to the target time point set in the time point setting interface, delete the first feature tag added before the target time point.

[0324] In some embodiments, the number of the first feature tags is multiple, and there are different first feature tags among the multiple first feature tags; the response module 4552 is further configured to display a statistical control for the multiple first feature tags, the statistical control being used to count the number of different first feature tags; in response to a trigger operation on the statistical control, the number of different first feature tags is displayed.

[0325] In some embodiments, the response module 4552 is further configured to, in response to a trigger operation on the first information entry, display an object entry, wherein the object entry is configured to: display historical service objects that provide services to the second object; display at least one of the historical service objects in response to a trigger operation on the object entry; display a synchronization control corresponding to the selected historical service object in response to a selection operation on the historical service object; and display a first feature tag added by the selected historical service object for the second object in response to a trigger operation on the synchronization control.

[0326] In some embodiments, the response module 4552 is further configured to, in response to a trigger operation for the first information entry, display a first add control for adding the first feature tag; in response to a trigger operation for the first add control, display at least one candidate first feature tag added by the historical service object for the second object; in response to a selection instruction for the candidate first feature tag, control the selected first feature tag to be in a selected state; and in response to a confirmation instruction triggered for the first feature tag in the selected state, display the first feature tag in the selected state.

[0327] In some embodiments, the response module 4552 is further configured to display a second add control, the second add control being configured to allow the first object to add a third feature label for the second object; in response to a trigger operation on the second add control, display a label editing area and display the edited label in the label editing area; in response to a confirmation instruction on the edited label, display the third feature label added by the first object for the second object.

[0328] In some embodiments, the first feature tag belongs to a first tag group; the response module 4552 is further configured to, in response to a determination instruction for the edited tag, cancel the display of the first feature tag with the earliest addition time and highlight the third feature tag when the third feature tag added by the first object to the second object belongs to the first tag group and the number of first feature tags in the displayed first tag group reaches a number threshold.

[0329] In some embodiments, the first feature tag belongs to a first tag group, and the first feature tag is displayed in a first display area of ​​the details page of the second object; the response module 4552 is further configured to, when the third feature tag belongs to the first tag group, display a third feature tag added by the first object for the second object in the first display area; when the third feature tag does not belong to the first tag group, display the third feature tag in a third display area of ​​the details page, wherein the third tag group is parallel to the first tag group.

[0330] In some embodiments, the at least one first feature tag belongs to a first tag group; the response module 4552 is further configured to display a third add control, the third add control being used to add a third tag group for the second object, the third tag group being parallel to the first tag group; in response to a trigger operation on the third add control, a tag group editing area is displayed, and the edited third tag group is displayed in the tag group editing area; in response to a viewing instruction triggered on the added third tag group, a fourth add control is displayed, the fourth add control being used for the first object to add feature tags belonging to the third tag group for the second object.

[0331] In some embodiments, the response module 4552 is further configured to display a third prompt message and a second information entry in the social interface; wherein the third prompt message is configured to indicate the number of third objects with updated second feature tags among the objects associated with the first object within a preset time period, and the second information entry is configured to view the updated second feature tags of the third objects; in response to a trigger operation on the second information entry, the third objects are displayed, and the updated second feature tags of the third objects are displayed accordingly.

[0332] In some embodiments, the response module 4552 is further configured to display an analysis control after displaying the third object and correspondingly displaying the updated second feature label of the third object, the analysis control being configured to analyze the change of the second feature label corresponding to the third object; in response to a trigger operation on the analysis control, display the change result of the second feature label corresponding to the third object within a preset time period, and display a fourth prompt message generated based on the change result, the fourth prompt message being configured to prompt the reason information corresponding to the change result.

[0333] This application provides a computer program product, which includes a computer program or computer-executable instructions stored in a computer-readable storage medium. The processor of an electronic device reads the computer-executable instructions from the computer-readable storage medium and executes the computer-executable instructions, causing the electronic device to perform the information display method described in this application.

[0334] This application provides a computer-readable storage medium storing computer-executable instructions or a computer program. When the computer-executable instructions or the computer program are executed by a processor, the processor will execute the information display method provided in this application. For example, ... Figure 3 The method for displaying information is shown.

[0335] In some embodiments, the computer-readable storage medium may be a memory such as RAM, ROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or it may be a variety of devices including one or any combination of the above-mentioned memories.

[0336] In some embodiments, computer-executable instructions may take the form of programs, software, software modules, scripts, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as stand-alone programs or as modules, components, subroutines, or other units suitable for use in a computing environment.

[0337] As an example, computer-executable instructions may, but do not necessarily, correspond to files in a file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple co-located files (e.g., files that store one or more modules, subroutines, or code sections).

[0338] As an example, computer-executable instructions can be deployed to execute on a single electronic device, or on multiple electronic devices located at one location, or on multiple electronic devices distributed across multiple locations and interconnected via a communication network.

[0339] The information display method provided in this application can display both first feature tags added by historical service objects to a second object and second feature tags automatically generated based on the behavior of the second object. This improves the richness of the displayed tags. When displaying the first feature tags added by historical service objects to a second object, the first object can know the first feature tags added by historical service objects to the second object, which can improve the efficiency of the first object in providing services to the second object and enhance the user experience (i.e., the first object, the second object, and the historical service objects).

[0340] When the first object knows the feature tags (i.e., the first feature tag, the second feature tag, and the third feature tag) corresponding to the second object, it can easily provide personalized services for the second object, thereby solving the above-mentioned technical problem 1.

[0341] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of this application are included within the scope of protection of this application.

Claims

1. An information display method, characterized in that, The method includes: In the social interface of the first object, the first information entry of the second object is displayed, and the first information entry is used to view the feature tags of the second object; Wherein, the first object is a service object that provides services to the second object, and for the service, the second object has at least one historical service object; In response to a trigger operation on the first information entry, at least one first feature label of the second object is displayed, and at least one second feature label of the second object is displayed; Wherein, the first feature tag is a tag added to at least one of the historical service objects, and the second feature tag is a tag automatically generated based on the behavior of the second object, wherein the behavior is associated with the historical service object.

2. The method according to claim 1, characterized in that, The step of displaying at least one first feature label of the second object and displaying at least one second feature label of the second object in response to a trigger operation on the first information entry includes: In response to a trigger operation targeting the first information entry point, the details page of the second object is displayed; In the first display area of ​​the details page, at least one first tag group of the second object is displayed, and at least one first feature tag in the first tag group is displayed; In the second display area of ​​the details page, at least one second tag group of the second object is displayed, and at least one second feature tag in the second tag group is displayed; Wherein, the at least one first tag group belongs to the first tag type, and the at least one second tag group belongs to the second tag type.

3. The method according to claim 2, characterized in that, The number of second feature tags in the second tag group is multiple; The step of displaying at least one second feature label in the second label group includes: Multiple second feature tags in the second tag group are displayed in chronological order of their generation time.

4. The method according to claim 2, characterized in that, The number of second feature tags in the second tag group is multiple; After displaying at least one second tab group of the second object in the second display area of ​​the details page, the method further includes: In response to the number of target second feature tags in the second tag group reaching the target number, the corresponding first prompt information is displayed in the associated area of ​​the second tag group; The first prompt information is used to prompt at least one of the following: to perform corresponding processing on the second object, or to provide a rating for the second tag group.

5. The method according to claim 2, characterized in that, The number of first feature tags in the first tag group is multiple; The step of displaying at least one first feature label in the first label group includes: Display multiple first feature labels in the first label group according to the priority of each first feature label; Alternatively, multiple first feature tags in the first tag group can be displayed according to the addition time of each first feature tag.

6. The method according to claim 2, characterized in that, After displaying at least one first feature label of the second object and at least one second feature label of the second object, the method further includes at least one of the following: In response to a first deletion command triggered for the first tag group, delete the first tag group indicated by the first deletion command, and the first feature tag in the first tag group indicated by the first deletion command; In response to a second deletion command triggered on the first feature tag, the first feature tag indicated by the second deletion command is deleted; In response to a third deletion command triggered for the second tag group, a second prompt message is displayed, indicating that the second tag group cannot be deleted.

7. The method according to claim 1, characterized in that, After displaying at least one first feature label of the second object, the method further includes: Display a first delete control, which is used to delete the first feature tag added to the historical service object; In response to a trigger operation on the first delete control, at least one of the historical service objects is displayed for selection; In response to a selection operation for at least one of the historical service objects, the first feature tag added to the selected historical service object is deleted.

8. The method according to claim 1, characterized in that, After displaying at least one first feature label of the second object, the method further includes: Display a second delete control, which is used to delete the first feature tag added to the historical service object before the target time point; In response to a trigger operation on the second delete control, the time point setting interface is displayed; In response to the target time point set in the time point setting interface, the first feature tag added before the target time point is deleted.

9. The method according to claim 1, characterized in that, The number of the first feature labels is multiple, and there are different first feature labels among the multiple first feature labels; After displaying at least one first feature label of the second object, the method further includes: Display a statistical control for multiple first feature labels, the statistical control being used to count the number of different first feature labels; In response to a trigger operation on the statistics control, the number of each of the first feature labels is displayed.

10. The method according to claim 1, characterized in that, The step of displaying at least one first feature label of the second object in response to a trigger operation on the first information entry includes: In response to a trigger operation on the first information entry, an object entry is displayed, which is used to display historical service objects that provide services to the second object; In response to a trigger operation targeting the object entry, at least one of the historical service objects is displayed; In response to the selection operation for the historical service object, the synchronization control corresponding to the selected historical service object is displayed; In response to a trigger operation on the synchronization control, the first feature tag added by the selected historical service object for the second object is displayed.

11. The method according to claim 1, characterized in that, The step of displaying at least one first feature label of the second object in response to a trigger operation on the first information entry includes: In response to a trigger operation on the first information entry point, a first add control for adding the first feature tag is displayed; In response to a trigger operation on the first added control, at least one candidate first feature label added by the historical service object for the second object is displayed; In response to a selection instruction for the first feature label of a candidate, the selected first feature label is kept in a selected state. In response to a confirmation command triggered for the first feature label that is selected, the first feature label that is selected is displayed.

12. The method according to claim 1, characterized in that, The method further includes: A second add control is displayed, which is used to allow the first object to add a third feature label for the second object; In response to a trigger operation on the second added control, a label editing area is displayed, and the edited label is displayed in the label editing area; In response to a confirmation instruction for the edited tag, the third feature tag added by the first object to the second object is displayed.

13. The method according to claim 12, characterized in that, The first feature label belongs to the first label group; In response to a determination instruction for the edited tag, displaying the third feature tag added by the first object for the second object includes: In response to the determination instruction for the edited tag, if the third feature tag added by the first object to the second object belongs to the first tag group, and the number of first feature tags in the displayed first tag group reaches the number threshold, the first feature tag with the earliest addition time is canceled and the third feature tag is highlighted.

14. The method according to claim 12, characterized in that, The first feature tag belongs to the first tag group, and the first feature tag is displayed in the first display area of ​​the details page of the second object; The display of the third feature label added by the first object for the second object includes: When the third feature label belongs to the first label group, the third feature label added by the first object for the second object is displayed in the first display area; If the third feature tag does not belong to the first tag group, the third feature tag is displayed in the third display area of ​​the details page, wherein the third tag group is parallel to the first tag group.

15. The method according to claim 1, characterized in that, The at least one first feature label belongs to a first label group; the method further includes: A third add control is displayed, which is used to add a third tag group for the second object, and the third tag group is placed side by side with the first tag group; In response to a trigger operation on the third added control, the tag group editing area is displayed, and the edited third tag group is displayed in the tag group editing area; In response to a viewing command triggered for the added third tag group, a fourth add control is displayed, which is used by the first object to add feature tags belonging to the third tag group to the second object.

16. The method according to claim 1, characterized in that, The method further includes: The social interface displays a third prompt message and a second information entry point; The third prompt information is used to prompt the number of third objects with updated second feature tags among the objects associated with the first object within a preset time period. The second information entry is used to view the updated second feature tags of the third objects. In response to a trigger operation on the second information entry, the third object is displayed, and the updated second feature tag of the third object is displayed accordingly.

17. The method according to claim 16, characterized in that, After displaying the third object and correspondingly displaying the updated second feature label of the third object, the method further includes: The display analysis control is used to analyze the changes in the second feature label corresponding to the third object; In response to a trigger operation on the analysis control, the change result of the second feature label corresponding to the third object within a preset time period is displayed, and a fourth prompt message generated based on the change result is displayed. The fourth prompt message is used to prompt the reason information corresponding to the change result.

18. An information display device, characterized in that, The device includes: The display module is used to display the first information entry of the second object in the social interface of the first object, and the first information entry is used to view the feature tags of the second object; Wherein, the first object is a service object that provides services to the second object, and for the service, the second object has at least one historical service object; A response module is configured to, in response to a trigger operation on the first information entry, display at least one first feature label of the second object, and display at least one second feature label of the second object; Wherein, the first feature tag is a tag added to at least one of the historical service objects, and the second feature tag is a tag automatically generated based on the behavior of the second object, wherein the behavior is associated with the historical service object.

19. An electronic device, characterized in that, The electronic device includes: Memory is used to store executable instructions or computer programs. A processor, when executing computer-executable instructions or computer programs stored in the memory, implements the information display method according to any one of claims 1 to 17.

20. A computer-readable storage medium storing computer-executable instructions or a computer program, characterized in that, When the computer-executable instructions or computer program are executed by a processor, the information display method according to any one of claims 1 to 17 is implemented.

21. A computer program product comprising computer-executable instructions or a computer program, characterized in that, When the computer-executable instructions or computer program are executed by a processor, the information display method according to any one of claims 1 to 17 is implemented.