A data processing method, device, apparatus, and readable storage medium

Abstract

The application discloses a data processing method, device and equipment and a readable storage medium. The method comprises the following steps: in a first application, in response to a data query operation for a first sub-object, displaying target plug-in media data in the first application; the target plug-in media data is generated based on a target plug-in service file associated with the first sub-object; the target plug-in media data comprises a main content abstract in the target plug-in service file; if the main content in the target plug-in service file contains query data input by the data query operation, the main content abstract is obtained by screening the main content based on the query data, and the main content abstract comprises the query data; and the query data contained in the target plug-in media data is highlighted. According to the application, the presentation form of the query result can be enriched, and the display effect can be optimized in the query service of the application.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a data processing method, apparatus, device, and readable storage medium. Background Technology

[0002] Currently, some applications (such as social applications for enterprises) offer email search functionality, allowing users to search for emails that match their input by entering information such as keywords or images.

[0003] However, the existing email search function only supports simple title search, and the email search results only show the email title information, which is a single presentation format and has a poor display effect. Summary of the Invention

[0004] This application provides a data processing method, apparatus, device, and readable storage medium, which can enrich the presentation of query results and optimize their display effect in the query business of the application.

[0005] One embodiment of this application provides a data processing method, including:

[0006] In the first application, a data query operation targeting the first sub-object is responded to, and the target plugin media data is displayed in the first application. The target plugin media data is generated based on the target plugin business files associated with the first sub-object. The target plugin business files are obtained by requesting the network server through the plugin query interface when the terminal database is traversed through the plugin query interface and no set of associated plugin business files that meet the file display requirements is found in the terminal database. The file display requirements refer to the display requirements indicated by the plugin data display area. The plugin data display area refers to the area in the first application used to display the target plugin media data. The terminal database refers to the database corresponding to the second application. The plugin query interface is provided by the second application. The network server refers to the server that provides query services for the second application. The first application is different from the second application. The target plugin media data includes a summary of the main content of the target plugin business file. If the main content of the target plugin business file contains the query data input by the data query operation, then the summary of the main content is obtained by filtering the main content based on the query data, and the summary of the main content includes the query data.

[0007] Highlight the query data contained in the target plugin's media data.

[0008] One embodiment of this application provides a data processing apparatus, including:

[0009] The media data display module is used in the first application to respond to data query operations on the first sub-object and display target plugin media data in the first application. The target plugin media data is generated based on the target plugin business files associated with the first sub-object. The target plugin business files are obtained by requesting the network server through the plugin query interface when the terminal database is traversed through the plugin query interface and no set of associated plugin business files that meet the file display requirements is found in the terminal database. The file display requirements refer to the display requirements indicated by the plugin data display area. The plugin data display area refers to the area in the first application used to display the target plugin media data. The terminal database refers to the database corresponding to the second application. The plugin query interface is provided by the second application. The network server refers to the server that provides query services for the second application. The first application is different from the second application. The target plugin media data includes a summary of the main content of the target plugin business file. If the main content of the target plugin business file contains the query data input by the data query operation, the summary of the main content is obtained by filtering the main content based on the query data, and the summary of the main content includes the query data.

[0010] The highlighting module is used to highlight query data contained in the target plugin media data.

[0011] In one embodiment, the target plugin media data displayed in the first application consists of object information of the second sub-object, the title content of the target plugin business file, and a summary of the main content; the second sub-object refers to the object that performs plugin business through the target plugin business file and the first sub-object.

[0012] In one embodiment, the media data display module includes:

[0013] The query interface display unit is used to respond to data query operations for the first sub-object in the first application and to display a comprehensive query interface in the first application.

[0014] The plugin data display unit is used to display the plugin data display area in the comprehensive query interface, and to display the target plugin media data in the plugin data display area.

[0015] In one embodiment, the target plugin media data is displayed in the plugin data display area of ​​the first application;

[0016] The data processing device also includes:

[0017] The extended query module is used to respond to extended query operations targeting the plugin data display area and display an extended query interface containing one or more plugin media data; one or more plugin media data are associated with the first sub-object, and one or more plugin media data contain the target plugin media data.

[0018] In one embodiment, the extended query interface includes auxiliary filtering function controls;

[0019] The data processing device also includes:

[0020] The auxiliary filtering module is used to respond to the trigger operation of the auxiliary filtering function control, and to obtain a portion of the plug-in media data indicated by the auxiliary filtering function control from one or more plug-in media data; the filtering dimension content of the portion of plug-in media data includes the query data, and the filtering dimension content refers to the content corresponding to the target business dimension in the portion of plug-in media data, and the target business dimension is the dimension indicated by the auxiliary filtering function control;

[0021] The auxiliary filtering module is also used to display some plugin media data in the extended query interface.

[0022] In one embodiment, the data processing apparatus further includes:

[0023] The details display module is used to respond to triggered operations on the media data of the target plugin and display the file details display interface;

[0024] The details display module is also used to display the full file details of the target plugin business file in the file details display interface.

[0025] In one embodiment, the extended query module includes:

[0026] The interface call unit is used to respond to extended query operations targeting the plugin data display area and call the plugin query interface; the plugin query interface is provided by the second application.

[0027] The interface retrieval unit is used to retrieve the query result interface of the second application through the plugin query interface; the query result interface includes one or more plugin media data provided by the second application;

[0028] The interface retrieval unit is also used to determine the query results interface as an extended query interface and display the extended query interface.

[0029] In one embodiment, the media data display module includes:

[0030] The integrated interface display unit is used to respond to data query operations for the first sub-object in the first application and to display an integrated query interface including a plugin file viewing control in the first application.

[0031] The plugin interface display unit is used to respond to the trigger operation of the plugin file viewing control and display the plugin data display interface;

[0032] The plugin interface display unit is also used to display the target plugin media data in the plugin data display interface.

[0033] In one embodiment, the media data display module further includes:

[0034] The preview area display unit is used to respond to triggered operations on the target plugin media data and display the plugin data preview area in the plugin data display interface;

[0035] The preview information display unit is used to display the file preview information of the target plugin business file in the plugin data preview area; the file preview information of the target plugin business file is a part of the full file details information of the target plugin business file; the amount of file information in the file preview information is greater than the amount of file information in the target plugin media data.

[0036] In one embodiment, the plugin data preview area also includes a file details viewing control;

[0037] The media data display module also includes:

[0038] The file details display unit is used to respond to the trigger operation of the file details viewing control and display the file details display interface;

[0039] The file details display unit is also used to display the full file details information of the target plugin business file in the file details display interface.

[0040] In one embodiment, the plugin data display interface also includes an auxiliary filtering function control; the number of target plugin media data is at least two.

[0041] The media data display module also includes:

[0042] The input box display unit is used to respond to the trigger operation of the auxiliary filtering function control and display the filtering dimension and the corresponding input box of the filtering dimension;

[0043] The dimensional media data display unit is used to respond to input operations on the input box and retrieve the target plugin media data containing the dimensional query data from at least two target plugin media data sets, as the dimensional plugin media data; the dimensional query data refers to the data associated with the filter dimension entered in the input operation.

[0044] Update the display unit to update the display of at least two target plugin media data in the plugin data display interface as dimensional plugin media data.

[0045] In one embodiment, the data processing apparatus further includes:

[0046] The plugin interface call module is used to obtain the number of files displayed as indicated by the plugin data display area, and call the plugin query interface based on the number of files displayed;

[0047] The traversal module is used to traverse the terminal database through the plugin query interface; the terminal database refers to the database corresponding to the second application.

[0048] The target file determination module is used to determine the target plugin business file based on the number of files displayed and the set of associated plugin business files if a set of associated plugin business files related to the first sub-object exists in the terminal database.

[0049] The step execution module is used to generate target plugin media data based on the target plugin business file and execute the steps to display the target plugin media data in the plugin data display area.

[0050] In one embodiment, the traversal module includes:

[0051] The content traversal unit is used to traverse the object information, title content, and main content of the second sub-object contained in the plugin business file in the terminal database through the plugin query interface; the second sub-object refers to the object that performs plugin business through the plugin business file and the first sub-object in the terminal database.

[0052] The collection generation unit is used to determine the plugin business file as the associated plugin business file associated with the first sub-object if the file traversal content contains query data, and to form a set of associated plugin business files based on the associated plugin business files; the file traversal content refers to at least one of the following: object information, title content, and body content.

[0053] In one embodiment, the target file determination module is further specifically used to obtain the total number of associated plugin business files in the associated plugin business file set;

[0054] The target file determination module is also specifically used to determine if the total number is greater than or equal to the number of files to be displayed, and to determine if the set of associated plugin business files meets the number of files to be displayed. Based on the number of files to be displayed and the file transfer time corresponding to each associated plugin business file in the set of associated plugin business files, the target plugin business file is obtained from the set of associated plugin business files.

[0055] The target file determination module is further specifically used to determine that if the total number is less than or equal to the number of files displayed, the set of associated plugin business files does not meet the file display requirement. It then generates a first data query request containing query data and the number of files displayed through the plugin query interface, sends the first data query request to the network server, and determines one or more first network plugin business files returned by the network server based on the query data and the number of files displayed as target plugin business files. The total number of files in the one or more first network plugin business files is the same as the number of files displayed; the one or more first network plugin business files include a set of associated plugin business files; the one or more first network plugin business files are plugin business files associated with the first sub-object that the network server retrieves from the network database based on the query data; the network database refers to the database corresponding to the network server.

[0056] In one embodiment, the target file determination module includes:

[0057] The file sorting unit is used to sort the associated plugin business files in the associated plugin business file set according to the file transfer time corresponding to each associated plugin business file, so as to obtain the plugin file sequence.

[0058] The target file determination unit is used to sequentially obtain K associated plugin business files in the plugin file sequence and determine the K plugin business files as target plugin business files; K is equal to the number of files displayed.

[0059] In one embodiment, the extended query module includes:

[0060] The terminal traversal module is used to respond to extended query operations targeting the plugin data display area, call the plugin query interface, and traverse the terminal database through the plugin query interface;

[0061] The first interface display unit is used to generate terminal plug-in media data based on the terminal plug-in service file if a terminal plug-in service file associated with the first sub-object exists in the terminal database, and to form one or more plug-in media data based on the terminal plug-in media data and the target plug-in media data, and to display an extended query interface containing one or more plug-in media data; the terminal plug-in service file does not contain the target plug-in service file;

[0062] The request sending unit is used to generate a second data query request containing query data through the plugin query interface if the terminal plugin business file associated with the first sub-object does not exist in the terminal database, and then send the second data query request to the network server.

[0063] The plugin data determination unit is used to determine one or more plugin media data based on the feedback data returned by the web server based on the query data.

[0064] The second interface display unit is used to display an extended query interface containing media data for one or more plugins.

[0065] In one embodiment, the plug-in data determining unit is further configured to, if the feedback data includes a second network plug-in service file, generate network plug-in media data based on the second network plug-in service file, and determine the network plug-in media data and the target plug-in media data as one or more plug-in media data; the second network plug-in service file is a plug-in service file that the network server retrieves from the network database based on the query data; the network database refers to the database corresponding to the network server; the second network plug-in service file does not contain the target plug-in service file;

[0066] The plug-in data determination unit is also specifically used to determine the target plug-in media data as one or more plug-in media data if the feedback data does not include the second network plug-in service file.

[0067] In one embodiment, the extended query module further includes:

[0068] The database update unit is used to update the terminal database based on the second network plug-in service file when the feedback data includes the second network plug-in service file, so as to obtain the updated terminal database; the updated database includes the second network plug-in service file.

[0069] In one embodiment, the data processing apparatus further includes:

[0070] The main content traversal module is used to obtain the query data input by the data query operation and traverse the main content of the target plugin business file based on the query data;

[0071] The surrounding content acquisition module is used to acquire the surrounding content of the query data in the main content if the main content contains the query data; in the main content, the data interval distance between the surrounding content and the query data is less than or equal to the interval distance threshold.

[0072] The content summary generation module is used to generate a summary of the main content based on the surrounding content and the query data.

[0073] In one embodiment, the traversal module further includes:

[0074] If the terminal database does not contain a set of associated plugin business files related to the first sub-object, the similar file determination unit retrieves the similar plugin business files related to the first sub-object from the terminal database based on the query data.

[0075] The prompt information display unit is used to generate similar plugin media data based on similar plugin business files, display the similar plugin media data in the first application, and provide a detailed viewing prompt for the similar plugin media data; the detailed viewing prompt is used to instruct the first sub-object to view the full file details of the similar plugin business files through the similar plugin media data.

[0076] In one embodiment, the similar file determination unit is further specifically used to obtain the plug-in service file in the terminal database, as well as the file content contained in the plug-in service file.

[0077] The similar file determination unit is also specifically used to determine the plugin business file as a similar plugin business file associated with the first sub-object if the file content contained in the plugin business file contains similar data that has a similar relationship with the query data.

[0078] One embodiment of this application provides a computer device, including: a processor and a memory;

[0079] The memory stores a computer program, which, when executed by a processor, causes the processor to perform the methods described in the embodiments of this application.

[0080] One aspect of this application provides a computer-readable storage medium storing a computer program, which includes program instructions. When executed by a processor, the program instructions perform the methods described in this application.

[0081] One aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the method provided in one aspect of the embodiments of this application.

[0082] In this embodiment, after the first sub-object performs a data query operation in an application (such as a first application), the terminal can respond to this data query operation and display target plugin media data. This target plugin media data is generated based on a target plugin business file associated with the first sub-object. The target plugin media data includes a summary of the main content of the target plugin business file. When the main content of the target plugin business file contains the query data input in the data query operation, the summary of the main content is obtained by filtering the main content based on the query data, and the summary of the main content includes the query data. When displaying the target plugin media data, the terminal can highlight the query data contained within the target plugin media data. It should be understood that in the query business of the application, when a certain sub-object (such as the first sub-object) enters query data in the application to query the plugin business file related to the query data, this application can determine the target plugin business file in the terminal database or network server based on the query data, and generate target plugin media data based on the target plugin business file. Subsequently, when the target plugin media data is displayed in the application, a summary of the main content of the target plugin business file can be displayed at the same time. By synchronously displaying the summary of the main content, the specific content contained in the target plugin business file can be clearly reflected, which can greatly enrich the presentation form of the plugin media data and optimize its display effect. Furthermore, when the main content of the target plugin business file contains query data, the main content summary displayed in this application is determined based on the query data within the main content. In other words, the presented main content summary dynamically changes based on the position of the query data within the main content. When displaying the main content summary, the query data within it can be highlighted simultaneously. This not only enriches the presentation format but also allows for quick location of the query data within the target plugin business file through the highlighted query data, improving query efficiency. In summary, this application can enrich the presentation format of query results (such as target plugin media data) and optimize their display effect in the application's query business. Attached Figure Description

[0083] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0084] Figure 1 This is a network architecture diagram provided in an embodiment of this application;

[0085] Figure 2 This is a schematic diagram illustrating a data query scenario provided in an embodiment of this application;

[0086] Figure 3 This is a schematic flowchart of a data processing method provided in an embodiment of this application;

[0087] Figure 4 This is a schematic diagram of a process for displaying target plugin media data provided in an embodiment of this application;

[0088] Figure 5 This is a schematic diagram of a comprehensive query interface provided in an embodiment of this application;

[0089] Figure 6 This is a schematic diagram of a process for displaying similar plug-in media data provided in an embodiment of this application;

[0090] Figure 7 This is a schematic diagram of a scenario for displaying similar plug-in media data provided in an embodiment of this application;

[0091] Figure 8 This is a schematic diagram illustrating an extended query scenario provided in an embodiment of this application;

[0092] Figure 9 This is a schematic diagram of a process for displaying target plugin media data provided in an embodiment of this application;

[0093] Figures 10a-10b This is a schematic diagram of a scenario for displaying target plugin media data provided in an embodiment of this application;

[0094] Figure 11 This is a schematic diagram of a scenario for previewing a plugin service file provided in an embodiment of this application;

[0095] Figure 12 This is a schematic diagram of a data filtering scenario provided in an embodiment of this application;

[0096] Figure 13 This is a schematic diagram of an interactive process provided in an embodiment of this application;

[0097] Figure 14 This is a system logic flowchart provided in an embodiment of this application;

[0098] Figure 15 This is a schematic diagram of the structure of a data processing device provided in an embodiment of this application;

[0099] Figure 16 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0100] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0101] Please see Figure 1 , Figure 1 This is a network architecture diagram provided in an embodiment of this application. For example... Figure 1 As shown, this network architecture may include a service server 1000 and a terminal device cluster. The terminal device cluster may include one or more terminal devices; the number of terminal devices is not limited here. Figure 1 As shown, multiple terminal devices may include terminal device 100a, terminal device 100b, terminal device 100c, ..., terminal device 100n; as Figure 1 As shown, terminal devices 100a, 100b, 100c, ..., 100n can each connect to the business server 1000 via a network, so that each terminal device can interact with the business server 1000 through the network connection.

[0102] It is understandable that, such as Figure 1 Each terminal device shown can have the target application installed. When the target application runs on each terminal device, it can interact with... Figure 1 The business servers 1000 shown interact with each other, enabling them to receive business data from each terminal device. The target application can include applications capable of displaying text, images, audio, and video data, such as social applications (e.g., instant messaging applications), browsers, video applications, entertainment applications (e.g., game applications), novel applications, etc., without further examples. The application can be a standalone application or an embedded sub-application integrated into an application (e.g., social applications, educational applications, multimedia applications, etc.), without limitation. Taking a social application as an example, the business server 1000 can be a collection of multiple servers, including a backend server and a data processing server corresponding to the social application. Therefore, each terminal device can transmit data with the business server 1000 through the social application. For example, each terminal device can upload its local images, videos, etc., to the business server 1000 through the social application, and the business server 1000 can then distribute the images, videos, etc., to other terminal devices or transmit them to a cloud server.

[0103] This application embodiment can select one terminal device from multiple terminal devices as the target terminal device. This terminal device may include: smartphones, tablets, laptops, desktop computers, smart TVs, smart speakers, desktop computers, smartwatches, smart in-vehicle systems, and other smart terminals with multimedia data processing functions (e.g., video playback, music playback, text playback), but is not limited to these. For example, this application embodiment can... Figure 1 The terminal device 100a shown serves as the target terminal device, which may integrate the aforementioned target application. In this case, the target terminal device can interact with the business server 1000 through the target application. The business server 1000 in this application can obtain business data based on these applications. For example, the business server 1000 can obtain business data through the bound account of a sub-object. The bound account can refer to the account bound to the sub-object in the application; the sub-object can log in to the application, upload data, retrieve data, etc., through its corresponding bound account, and the business server can also obtain the sub-object's login status, uploaded data, send data to the sub-object, etc., through its bound account.

[0104] It should be understood that in the target application, this application can provide a data query function. Sub-objects of the target application can perform data queries within the target application. For example, when a sub-object inputs certain information (which can be called query data) to query data related to that information, the sub-object can view the data related to the query data. For instance, taking a communication application for an enterprise (which can be called an enterprise communication application) as an example, the sub-object can refer to an enterprise member. This enterprise communication application can have a data query function, and enterprise members can perform data queries through this function. For example, after an enterprise member inputs the query text "design," this query text can be called query data. With the authorization and permission of the enterprise member, the target terminal device corresponding to the enterprise member can traverse the interaction records between the enterprise member and other enterprise members, and determine the enterprise member whose interaction records contain the query text "design" (which can be called the target interaction sub-object). The target terminal device corresponding to the enterprise member can display a comprehensive query interface, and display the object information of the target interaction sub-object in the comprehensive query interface, which is used to represent that the interaction with the target interaction sub-object contains the query text "design."

[0105] It is understood that in this application, the target application (such as the enterprise communication application mentioned above) may also integrate functional plugins (such as email plugins, communication plugins (such as SMS plugins, address book plugins, etc.), etc.), and the query function of the target application may also provide query services for plugin business files (such as emails, SMS messages, etc.). For example, for the enterprise communication application mentioned above, an email plugin may be integrated into the enterprise communication application. After an enterprise member enters the query text "design", the query text can be called query data. With the authorization and permission of the enterprise member, the target terminal device corresponding to the enterprise member can also call the email plugin to query emails containing the query text "design". The target terminal device can display these emails at the same time as displaying the target interactive sub-object in the comprehensive query interface (or, the target terminal device can display these emails in an interface independent of the comprehensive query interface).

[0106] It is understood that, in order to optimize the presentation of plug-in business files, this application allows a sub-object (which may be referred to as the first sub-object) to input query data in the target application. After the target terminal device determines the target plug-in business file based on the query data, it can generate target plug-in media data based on the target plug-in business file and then display the target plug-in media data. Furthermore, in this application, when displaying the target plug-in media data, a content summary of the main content contained in the target plug-in business file (which may be referred to as the main content summary; for example, when the target plug-in business file is an email, the main content may refer to the body of the email, and the main content summary may refer to the body summary) can be displayed. Simultaneously, when the query data is included in the main content, this application can filter out the main content summary to be displayed based on the query data, and highlight the query data contained in the main content summary when displaying the summary.

[0107] It should be understood that the embodiments of this application integrate additional function plugins (such as email plugins, SMS plugins, etc.) into the target application (such as communication applications for enterprises). By integrating these additional function plugins, the target application provides a query function for plugin business files (such as emails and SMS messages), and adds a new presentation format for the query results of plugin business files. By simultaneously displaying a summary of the main content of the plugin business file when displaying the plugin media data (generated based on the plugin business file), the presentation format can be enriched, and a portion of the main content of the business file can be clearly presented, optimizing the display effect. At the same time, when the main content contains query data, the query data contained in the summary of the main content can also be highlighted, making it easy to quickly locate the position of the query data in the main content, thus improving the viewing experience of sub-objects.

[0108] It is understood that the methods provided in this application embodiment can be executed by computer devices, including but not limited to terminal devices or business servers. The business server can be an independent 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, CDN, and big data and artificial intelligence platforms.

[0109] The terminal equipment and the business server can be connected directly or indirectly through wired or wireless communication, and this application does not impose any restrictions on this.

[0110] Optionally, and understandably, the aforementioned computer devices (such as the aforementioned business server 1000, terminal device 100a, terminal device 100b, etc.) can be nodes in a distributed system. This distributed system can be a blockchain system, formed by connecting multiple nodes through network communication. The nodes can form a peer-to-peer (P2P) network, where the P2P protocol is an application layer protocol running on top of the Transmission Control Protocol (TCP). In this distributed system, any type of computer device, such as a business server or terminal device, can become a node in the blockchain system by joining this peer-to-peer network. For ease of understanding, the concept of blockchain is explained below: Blockchain is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. It is mainly used to organize data in chronological order and encrypt it into a ledger, making it tamper-proof and forgery-proof, while also enabling data verification, storage, and updating. When a computer device is a blockchain node, the immutability and anti-counterfeiting characteristics of the blockchain ensure that the data in this application (such as query data, target plugin business files determined based on query data, etc.) are authentic and secure, thereby making the results obtained after processing the data more reliable.

[0111] It should be noted that, in the specific embodiments of this application, object-related data such as sub-object information and sub-object data (e.g., the bound account of the aforementioned object, the data uploaded by the object, and the object information of the sub-objects mentioned below) are only acquired and processed after obtaining the permissions granted by the corresponding sub-object. In other words, when the embodiments of this application are applied to specific products or technologies, permission or consent from the object is required, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions.

[0112] For ease of understanding, please refer to the following: Figure 2 , Figure 2 This is a schematic diagram illustrating a data query scenario provided in an embodiment of this application. Wherein, as... Figure 2 The terminal device 100a shown can be used in the above-mentioned Figure 1 Terminal device 100a in the terminal device cluster of the corresponding embodiment.

[0113] like Figure 2 As shown, terminal device 100a can be the terminal device corresponding to sub-object a. When the target application is installed on terminal device 100a, sub-object a can start and run the target application. Taking the target application as a communication application for an enterprise (hereinafter referred to as the enterprise communication application) as an example, sub-object a can refer to a member of an enterprise S. Sub-object a can start and run the enterprise communication application for enterprise S through terminal device 100a. After sub-object a starts and runs the enterprise communication application, it can log in to the enterprise communication application through its bound account in the enterprise communication application. After logging in to the enterprise communication application, it first enters the homepage of the enterprise communication application. That is to say, the bound account of sub-object a can also be used to refer to sub-object a.

[0114] like Figure 2 As shown, the homepage 2001 may contain a search box 20a. Sub-object a can input query data through this search box 20a to retrieve results related to that query data. For example... Figure 2As shown, when sub-object a enters the text "mobile phone" in search box 20a and triggers the search control, the text "mobile phone" entered by sub-object a can be called query data, and the triggering operation of sub-object a on the search control can be called a data query operation. Terminal device 100a can respond to this data query operation and query the terminal database for emails containing the query data "mobile phone". Here, the enterprise communication application can integrate an email plugin corresponding to the email application. When an email plugin is integrated, the enterprise communication application and the email application can call and access each other's data through corresponding interfaces (such as Application Program Interfaces (APIs)). Therefore, the terminal database here can actually refer to the application database corresponding to the email application. The terminal device can call the corresponding interface to access the application database corresponding to the email application and traverse the emails associated with sub-object a stored in the application database. Here, emails associated with sub-object a can refer to emails where sub-object a is the sender, recipient, or CC recipient.

[0115] Furthermore, by traversing the emails associated with sub-object a, it is possible to find emails whose sender, recipient, subject, body, or attachment (which can be called email attachments) contain the queried data "mobile phone". This includes emails whose sender name, recipient name, email subject, email body, and email attachment name all contain "mobile phone". The emails retrieved can be used as email query results (which can be called target plugin business files). Terminal device 100a can generate corresponding target plugin media data for each target plugin business file. This target plugin media data package contains object information (such as object avatar, object name, etc.) of the sub-object communicating with sub-object a via email, the email subject, and a summary of the email body (which can be called the body summary).

[0116] In other words, when an email containing the query data "mobile phone" is found, if the email is addressed to sub-object a, the terminal device 100a can display the sender's account avatar, account name, and other object information in the enterprise communication application, the email's title, and a summary of the main content. If the email is addressed to sub-object a, the terminal device 100a can display the recipient's (or, if there are multiple recipients, one can be selected) account information in the enterprise communication application, the email's title, and a summary of the main content. If the email's main content contains the query data "mobile phone," the summary of the main content displayed by the terminal device 100a can be determined based on the query data. The main content summary determined based on the query data contains the query data "mobile phone," and when displaying the main content summary, the terminal device 100a can highlight the query data "mobile phone" contained within it. Here, "highlighting" can refer to highlighting, color-changing, enlarging, shrinking, etc.

[0117] For example, when terminal device 100a traverses the terminal database, the retrieved emails include email 1 and email 2. Email 1 contains the queried data "mobile phone" in its main content, and email 2 also contains the queried data "mobile phone" in its main content. Terminal device 100a can display a comprehensive query interface 2002, and within this interface 2002, display a media data display area M for showing plug-in media data. Taking an email sent from child object "Zhao Ke'ai" to child object a as an example, terminal device 100a filters the main content summary of email 1 based on the query data "mobile phone" and obtains "mobile phone preview design content". Terminal device 100a can generate plug-in media data 1 based on email 1. This plug-in media data 1 can be composed of the avatar and name of child object "Zhao Ke'ai", the title content of email 1 "model design planning", and the main content summary "mobile phone preview design content". Terminal device 100a can display this plug-in media data 1 in the media data display sub-area M1 of the media data display area M. When displaying plug-in media data 1, terminal device 100a can highlight the query data "mobile phone" in the main content summary "mobile phone preview design content" (e.g., by bolding and enlarging it).

[0118] Similarly, taking email 2, which is sent by child object "Yangyangyang" to child object a, as an example, terminal device 100a obtains the main content summary "watch online on mobile phone" by filtering the main content of email 2 based on the query data "mobile phone". Terminal device 100a can generate plug-in media data 2 based on email 2. This plug-in media data 2 can be composed of the avatar and name of child object "Zhao Ke'ai", the title content of email 2 "January Design Weekly", and the main content summary "watch online on mobile phone". Terminal device 100a can display this plug-in media data 2 in the media data display sub-area M2 of the media data display area M. When displaying plug-in media data 2, terminal device 100a can highlight the query data "mobile phone" in the main content summary "watch online on mobile phone" (e.g., by bolding and enlarging it).

[0119] It should be noted that the input operations or triggering operations for each control in this application may refer to contact operations such as clicking or long-pressing, or non-contact operations such as voice or gestures; there is no limitation on this.

[0120] It should be understood that, in enterprise communication applications, this embodiment, by integrating an email plugin, can provide email query services within the data query business of enterprise communication applications, thus enriching the diversity of query results. Simultaneously, when displaying email query results, it can show object information, title content, and a summary of the main content. Furthermore, when the main content contains the query data entered by the object, this embodiment can flexibly determine the summary of the main content based on the query data and highlight the query data when displaying the summary. This enriches the presentation of email query results, optimizes their display effect, and makes it easier for the object to quickly locate the query data within the main content through the summary and highlighted query data, thereby improving the object's experience.

[0121] Further, please see Figure 3 , Figure 3 This is a schematic flowchart of a data processing method provided in an embodiment of this application. The method can be performed by a terminal device (e.g., the one described above). Figure 1 Any terminal device in the terminal device cluster 100 shown) or a service server (e.g., the one mentioned above) Figure 1 The data processing method can be executed by the business server 1000 shown, or it can be jointly executed by the terminal device and the business server. For ease of understanding, this embodiment uses the execution of the method by the aforementioned terminal device as an example. The data processing method may include at least the following steps S101-S102:

[0122] Step S101: In the first application, respond to the data query operation for the first sub-object and display the target plugin media data in the first application. The target plugin media data is generated based on the target plugin business file associated with the first sub-object. The target plugin business file is obtained by requesting the network server through the plugin query interface when the terminal database is traversed through the plugin query interface and no set of associated plugin business files that meet the file display requirements is found in the terminal database. The file display requirements refer to the display requirements indicated by the plugin data display area. The plugin data display area refers to the area in the first application used to display the target plugin media data. The terminal database refers to the database corresponding to the second application. The plugin query interface is provided by the second application. The network server refers to the server that provides query services for the second application. The first application is different from the second application. The target plugin media data includes a summary of the main content in the target plugin business file. If the main content in the target plugin business file contains the query data input by the data query operation, the summary of the main content is obtained by filtering the main content based on the query data, and the summary of the main content includes the query data.

[0123] In this application, the "first application" can refer to any application with social communication functions, also known as the "target application," which can be an instant messaging application. The target application can be a standalone application or an embedded sub-application within a video application, entertainment application, shopping application, etc., without limitation. Sub-objects can log in to the target application using a bound account. After logging in, sub-objects can communicate with other logged-in sub-objects using their bound account. A sub-object can be an object subordinate to a main object, which can be any object with an organizational structure. For example, the main object can be an enterprise, a group (such as a multi-person study group, assessment group, etc.), a department (such as a multi-person electrical engineering department, mechanical engineering department, etc.), etc., without further examples. For instance, if the main object is an enterprise, and enterprise members are employees of that enterprise, then the sub-object can refer to an enterprise member. It is understood that the "first sub-object" in this application can refer to any sub-object.

[0124] It is understood that, within the target application (such as an enterprise communication application), the embodiments of this application may integrate functional plugins for additional functional applications (which may be referred to as second applications). These additional functional applications can refer to applications independent of the target application, such as email applications, SMS applications, etc. The plugin business files in this application may refer to the business files corresponding to the second application. For example, if the second application is an email application, and the corresponding business file is "email," then the plugin business file may refer to "email." Similarly, if the second application is an SMS application, and the corresponding business file is "SMS," then the plugin business file may refer to "SMS."

[0125] It should be understood that when a target application integrating functional plugins provides data query services, it can determine the plugin business file containing the query data (which may include text data, image data, etc.) in the plugin business file associated with the first sub-object based on the query data input by the sub-object (such as the first sub-object). The terminal device can then generate and display target plugin media data based on this target plugin business file. It can be understood that the plugin business file associated with the first sub-object can refer to the plugin business file corresponding to the second application, where the first sub-object is a participating object (i.e., the first sub-object is a participant in the plugin business). For example, taking the second application as an email application with the plugin business file for email as an example, the plugin business file associated with the first sub-object could refer to an email where the first sub-object is the sender, recipient, or CC recipient.

[0126] Understandably, after the first sub-object performs a data query operation, the terminal device can determine the target plugin business file through the functional plugin. For example, the terminal device can traverse the terminal database through the plugin query interface provided by the second application. If the terminal database does not find a set of associated plugin business files that meet the file display requirement, it can request the target plugin business file from the network server through the plugin query interface. Here, the file display requirement can refer to the display quantity indicated by the plugin data display area (which can be the area in the first application used to display the target plugin media data), the terminal database can refer to the database corresponding to the second application (which can be understood as the local database of the second application), and the network server can refer to the server (such as a cloud server) that provides the query server for the second application. It should be understood that the terminal database can store a small number of plugin business files to alleviate storage pressure, while the network server can store the full set of plugin business files. Only when the terminal database does not find a set of plugin business files that meet the requirement can a query be requested from the network server. This reduces the storage pressure on the terminal database while ensuring the accuracy and comprehensiveness of the query results. For the specific implementation method of the terminal device determining the target plugin business file through the functional plugin, please refer to the following sections. Figure 5 The description of the target plugin business file is determined based on the query data in the corresponding embodiment.

[0127] Furthermore, the terminal device can generate target plugin media data based on the target plugin business file and display the target plugin media data in the first application. The target plugin media data can consist of object information of a second sub-object, the title content of the target plugin business file, and a body summary. The second sub-object can refer to an object that performs plugin business with the first sub-object through the target plugin business file. In other words, the target plugin business file can be used for business interaction (performing plugin business) between the first and second sub-objects. For example, taking an email as the target plugin business file, the first and second sub-objects can act as senders or recipients, and they can communicate via email (performing communication business). Therefore, the terminal device can generate the target plugin media data based on the object information, title content, and body summary of the second sub-object contained in the target plugin business file; that is, the target plugin media data contains the object information of the second sub-object, the title content of the target plugin business file, and the body summary.

[0128] Among them, the summary of the main content in the target plug-in media data can refer to the summary of the main content (i.e., part of the content). For example, taking the target plug-in business file as an email, the main content can refer to the body content, and the summary of the main content can refer to the summary of the body content. The summary of the theme content can be determined based on the query data input by the first sub-object. The specific implementation method can be as follows: The query data input by the data query operation can be obtained, and the main content of the target plug-in business file can be traversed based on the query data; if the main content contains the query data, the surrounding content of the query data can be obtained in the main content; among them, in the main content, the data interval distance between the surrounding content and the query data is less than or equal to the interval distance threshold; subsequently, the summary of the main content can be generated according to the surrounding content and the query data. If the main content does not contain the query data, the content at the specified position in the main content (such as the first sentence or the first image of the main content) can be used as the summary of the main content. Among them, the data interval distance can refer to the number of data separated from the query data, such as the number of characters or images separated, etc. For example, taking the main content as the text content "The vegetable market actually opens very early. You can go shopping at 5 o'clock in the morning" and the query data as the text data "5 o'clock", the data interval distance can refer to the number of interval characters, and the interval distance threshold can refer to the character number threshold. Assuming the interval distance threshold is 3 characters, the word "in" before the query data "5 o'clock" has an interval character number of 0 (actually the interval character number with the word "5"), and this interval character number 0 is less than the interval distance threshold 3, so the word "in" can be used as the surrounding word of the query data "5 o'clock"; the word "can" before the query data "5 o'clock" has an interval character number of 0 (actually the interval character number with the word "o'clock"), and this interval character number 0 is less than the interval distance threshold 3, so the word "can" can be used as the surrounding word of the query data "5 o'clock". Similarly, it can be determined that the interval character number between the word "early" in "early 5 o'clock" and the query data "5 o'clock" is 1 (separating 1 word "in"), and it can be determined that the interval character number between the word "can" in "5 o'clock can" and the query data "5 o'clock" is 1 (separating 1 word "can"). The interval character number 1 is less than the interval distance threshold 3, so the words "early", "in", "can", and "go" can also be used as the surrounding words of the query data "5 o'clock". Subsequently, according to the order of the corresponding presentation positions of these surrounding words and the query data in the main content, the surrounding words and the query data can be spliced in order to form the summary of the main content "You can go shopping at 5 o'clock in the morning". That is to say, according to the query data, part of the content containing the query data can be intercepted in the main content to be used as the summary of the main content. When the main content contains the query data, the summary of the main content changes dynamically and flexibly.

[0129] Optionally, when query data is contained in multiple locations within the main content, the most coherent or complete main content summary can be selected based on sentence coherence or completeness to be used as the final main content summary for generating the target plugin media data. This application can employ an artificial intelligence model (such as a statistical language model) to determine sentence coherence or completeness. For example, using a statistical language model to determine sentence coherence, if query data is contained in positions 1 and 2 of the main content, and main content summary 1 for position 1 and main content summary 2 for position 2 are generated based on surrounding words of the query data, these main content summaries 1 and 2 can be input into the statistical language model. The statistical language model can then evaluate the coherence of main content summary 1 and main content summary 2, and based on the evaluation results, the more coherent one can be selected as the final main content summary for display.

[0130] Step S102: Highlight the query data contained in the target plugin media data.

[0131] In this application, when displaying target plugin media data, query data contained within the target plugin media data can be highlighted. For example, if the object information of the second sub-object in the target plugin media data contains query data, then the query data in that object information can be highlighted; similarly, if the main content summary in the target plugin media data contains query data, then the query data in that main content summary can be highlighted. It should be understood that by highlighting query data, the location of the query data in the target plugin business file can be intuitively presented, facilitating quick location of query results and improving query efficiency.

[0132] It is understandable that the target plugin media data is generated from the object information, title content, and main content summary of the second sub-object in the target plugin business file. Therefore, this target plugin media data can be understood as a portion of the file content of the target plugin business file. The first sub-object can view the file details of the target plugin business file by accessing the target plugin media data. Specifically, when the first sub-object executes a trigger operation on the target plugin media data, the terminal device can respond to the trigger operation and display the file details display interface. Subsequently, the full file details information of the target plugin business file can be displayed in the file details display interface. When displaying the target plugin media data, the terminal device can simultaneously display the details viewing control for the target plugin business file; in this case, the trigger operation on the target plugin media data can refer to the trigger operation on the details viewing control. Conversely, when the terminal device does not display the details viewing control, the trigger operation on the target plugin media data can still refer to the trigger operation on the target plugin media data itself.

[0133] In this application embodiment, during the query business of the application, when a sub-object (such as the first sub-object) inputs query data in the application to query the plugin business file related to the query data, this application can determine the target plugin business file based on the query data and generate target plugin media data based on the target plugin business file. Subsequently, when the target plugin media data is displayed in the application, a summary of the main content of the target plugin business file can be displayed simultaneously. By synchronously displaying the summary of the main content, the specific content contained in the target plugin business file can be clearly reflected, which can greatly enrich the presentation form of the plugin media data and optimize its display effect. Furthermore, when the main content of the target plugin business file contains query data, the main content summary displayed in this application is determined based on the query data within the main content. In other words, the presented main content summary dynamically changes based on the position of the query data within the main content. When displaying the main content summary, the query data within it can be highlighted simultaneously. This not only enriches the presentation format but also allows for quick location of the query data within the target plugin business file through the highlighted query data, improving query efficiency. In summary, this application can enrich the presentation format of query results (such as target plugin media data) and optimize their display effect in the application's query business.

[0134] Further, please see Figure 4 , Figure 4 This is a schematic diagram of a process for displaying target plugin media data provided in an embodiment of this application. This process can correspond to the above. Figure 3In the corresponding embodiment, the process of displaying target plugin media data in the first application in response to a data query operation targeting the first sub-object is described. For example... Figure 4 As shown, the process may include at least the following steps S201-S202:

[0135] Step S201: Respond to the data query operation for the first sub-object in the first application and display the comprehensive query interface in the first application.

[0136] Specifically, after the first sub-object performs a data query operation in the first application, the terminal device can display a comprehensive query interface in the first application. This comprehensive query interface can refer to an interface provided by the first application for displaying comprehensive query results. The comprehensive query results can refer to a list of objects including target interactive sub-objects, target interactive groups, and target application files within the first application. Specifically, a target interactive sub-object can refer to a sub-object whose interaction records (such as session records) contain query data within an interaction (such as a conversation) between the target application and the first sub-object; a target interactive group can refer to a group (composed of the first sub-object and other sub-objects) whose interaction records (such as session records) contain query data within an interaction (such as a conversation) between the target application and the first sub-object; and a target application file can refer to an application file within the application file corresponding to the first application that contains the query data.

[0137] Step S202: Display the plugin data display area in the comprehensive query interface, and display the target plugin media data in the plugin data display area.

[0138] Specifically, the terminal device can display a plugin data display area in the comprehensive query interface, and display the target plugin media data in the plugin data display area. As can be seen from the above, the target plugin media data can be composed of the object information, title content, and main content summary of the second sub-object. The target plugin media data can be presented in the form of cards, images, etc., and can be used to reflect part of the information in the target plugin business file.

[0139] For ease of understanding, please refer to the following: Figure 5 , Figure 5 This is a schematic diagram of a comprehensive query interface provided in an embodiment of this application. For example... Figure 5As shown, in the comprehensive query interface 2001, the sub-object "Little Rabbit" and group X can refer to the comprehensive query results. When displaying the object information of the sub-object "Little Rabbit," the number of records in the interaction log that match the query data (e.g., 4 records) can be displayed simultaneously. When displaying group X, the number of records in the interaction log that match the query data (e.g., 10 records) can be displayed simultaneously. Furthermore, when displaying the comprehensive query results of the first application, the comprehensive query interface 2001 can display the plugin data display area M, and the target plugin media data can be displayed in the plugin data display area M (this corresponds to the above). Figure 2 In the corresponding embodiment, the target plug-in media data may include plug-in media data 1 and plug-in media data 2, and then plug-in media data 1 and plug-in media data 2 can be displayed in the plug-in data display sub-area M1.

[0140] It is understood that before displaying the target plugin media data, the terminal device needs to determine the target plugin business file based on query data, and then generate the target plugin media data based on the target plugin business file (such as extracting the object information of the second sub-object in the target plugin business file, the file title content, and the main content summary to form the target plugin media data), and then display the target plugin media data. In this application, the specific implementation method for determining the target plugin business file based on query data can be as follows: the number of files displayed as indicated by the plugin data display area can be obtained, and the plugin query interface can be called according to the number of files displayed; wherein, the plugin query interface is provided by the second application; subsequently, the terminal database can be traversed through the plugin query interface; wherein, the terminal database can refer to the database corresponding to the second application; if there is a set of associated plugin business files related to the first sub-object in the terminal database, the target plugin business file can be determined according to the number of files displayed and the set of associated plugin business files, the target plugin media data can be generated according to the target plugin business file, and then the step of displaying the target plugin media data in the plugin data display area can be executed.

[0141] The specific implementation method for traversing the terminal database through the plugin query interface can be as follows: Through the plugin query interface, the object information, title content, and body content of the second sub-object contained in the plugin business file in the terminal database can be traversed; where the second sub-object refers to the object that executes the plugin business through the plugin business file and the first sub-object in the terminal database; if the file traversal content contains query data, the plugin business file can be identified as an associated plugin business file related to the first sub-object, and an associated plugin business file set can be formed based on the associated plugin business files; where the file traversal content refers to at least one of the object information, title content, and body content.

[0142] The specific implementation method for determining the target plugin business file based on the number of files displayed and the set of associated plugin business files can be as follows: The total number of associated plugin business files in the set of associated plugin business files can be obtained. If the total number is greater than or equal to the number of files displayed, it can be determined that the set of associated plugin business files meets the file display requirement. The target plugin business file can be obtained from the set of associated plugin business files based on the file display requirement and the file transfer time corresponding to each associated plugin business file. If the total number is less than the number of files displayed, it can be determined that the set of associated plugin business files does not meet the file display requirement. A first data query request containing query data and the number of files displayed is generated through the plugin query interface. The first data query request is sent to the network server. One or more first network plugin business files returned by the network server based on the query data and the number of files displayed are determined as the target plugin business files. The total number of files in the one or more first network plugin business files is the same as the number of files displayed. The one or more first network plugin business files include the set of associated plugin business files. The one or more first network plugin business files are plugin business files associated with the first sub-object that the network server retrieves from the network database based on the query data. The network database refers to the database corresponding to the network server.

[0143] The specific implementation method for obtaining the target plugin business file from the associated plugin business file set based on the number of files displayed and the file transfer time corresponding to each associated plugin business file in the associated plugin business file set can be as follows: The associated plugin business files in the associated plugin business file set can be sorted according to the file transfer time corresponding to each associated plugin business file to obtain a plugin file sequence; then, K associated plugin business files can be obtained sequentially from the plugin file sequence, and the K plugin business files can be determined as the target plugin business files; where K is equal to the number of files displayed.

[0144] It is understood that this application can delineate a portion of the comprehensive query interface of the first application as a plugin data display area. In other words, this plugin data display area can refer to a defined area within the comprehensive query interface. Alternatively, the plugin data display area can be a sizable floating window presented as a mask or semi-transparent layer, which can be overlaid on the comprehensive query interface. The plugin data display area can also refer to an interface whose size can be adjusted by dragging, overlaid on the comprehensive query interface, and whose area is smaller than the comprehensive query interface. This application can define the number of target plugin media data (i.e., target plugin business files) to be displayed in the comprehensive query interface (which can be referred to as the file display count, e.g., 3 files). The terminal device can then call the plugin query interface based on this file display count. This plugin query interface can be provided by the second application (e.g., an API interface provided by an email application). This interface can be integrated into the target application, allowing the target application to access data in the second application through this interface.

[0145] Furthermore, through this plugin query interface, the terminal database can be traversed. Here, the terminal database can refer to the application's local database. Since the target application integrates the plugin query interface, it is equivalent to integrating the second application. Therefore, the application's local database can also be called the terminal database of the terminal corresponding to the first application. This terminal database stores at least two plugin business files. The terminal device can traverse the object information, title content, and body content of the second sub-object contained in each plugin business file. If at least one of the object information, title content, and body content of a plugin business file contains the query data, then that plugin business file can be identified as an associated plugin business file related to the first sub-object. Through traversal, one or more associated plugin business files related to the first sub-object can be identified, and these one or more associated plugin business files can form a set of associated plugin business files.

[0146] Furthermore, the total number of associated plugin business files in the associated plugin business file set can be obtained. If this total number is greater than or equal to the number of files displayed, the associated plugin business files in the associated plugin business file set can be sorted according to the file transfer time corresponding to each associated plugin business file to obtain a plugin file sequence. Subsequently, K associated plugin business files (K corresponding to the aforementioned number of files displayed) can be sequentially obtained from the plugin file sequence, and these K associated plugin business files can be identified as target plugin business files. Here, the file transfer time can refer to the time when the first sub-object sends the plugin business file to the second sub-object, or the time when the second sub-object sends the plugin business file to the first sub-object.

[0147] Optionally, it is understood that, as described above, when there is a set of associated plugin business files related to the first sub-object in the terminal database, the target plugin business file can be determined based on the number of files displayed and the set of associated plugin business files. When the total number is less than the number of files displayed, each associated plugin business file in the set of associated plugin business files can be directly determined as the target plugin business file. In a feasible embodiment, when the total number is less than the number of files displayed, the difference can be determined based on the total number and the number of files displayed. A data query request containing query data and the difference can be generated and sent to the network server corresponding to the second application. The network server then queries the set of plugin business files containing the query data based on the query data and obtains the plugin business file corresponding to the difference in the set of plugin business files (the plugin business file here does not include the aforementioned set of associated plugin business files). The terminal device can determine the plugin business file determined by the network server together with the aforementioned set of associated plugin business files as the target plugin business file. Alternatively, when the total number is less than the number of files to be displayed, a data query request (which can be called the first data query request) containing query data and the number of files to be displayed can be generated through the plugin query interface. This first data query request can be sent to the network server, and the network server can then query the first network plugin business file containing the query data (the first network plugin business file here includes the aforementioned set of associated plugin business files). Subsequently, the first network plugin business file can be directly identified as the target plugin business file.

[0148] It should be understood that the number of business files stored in the terminal database is small, while the database of the network server (which can be called the network database) can store all the business files. Therefore, when the number of business files queried in the terminal database is small, they can be obtained from the network server.

[0149] Optionally, it is understood that, as described above, when a set of associated plugin business files related to the first sub-object exists in the terminal database, the target plugin business file can be determined based on the number of files displayed and the set of associated plugin business files. However, when a set of associated plugin business files related to the first sub-object does not exist in the terminal database, a query request containing query data can be generated and sent to the network server corresponding to the second application. The network server then queries the set of plugin business files containing the query data based on the query data, and obtains the plugin business file corresponding to the number of files displayed in the set of plugin business files. The terminal device can determine the plugin business file determined by the network server together with the aforementioned set of associated plugin business files as the target plugin business file.

[0150] In this application embodiment, when displaying query results in the application's query business, the presentation format can be enriched and the display effect optimized by displaying a summary of the main content of the target plugin business file. At the same time, by highlighting the query data in the summary of the main content, the presentation format can be further enriched, and the location of the query data in the plugin business file can be quickly located, which can help improve query efficiency.

[0151] As described above, when the terminal database does not contain a set of associated plugin business files related to the first sub-object, a query can be performed from the network server. In one feasible embodiment, when the terminal database does not contain a set of associated plugin business files related to the first sub-object, similar plugin business files (which can be understood as business files containing similar data with similar relationships to the queried data) can be searched in the terminal database. The terminal device can then generate similar plugin media data based on these similar plugin business files and display the similar plugin media data. Alternatively, when the terminal database does not contain a set of associated plugin business files related to the first sub-object, a query can be performed first from the network server. If the network server also does not contain any associated plugin business files related to the first sub-object, then similar plugin business files can be obtained from both the terminal database and the network server. For ease of understanding, please refer to [further details omitted]. Figure 6 , Figure 6 This is a schematic diagram of a process for displaying similar plug-in media data provided in an embodiment of this application, such as... Figure 6 As shown, the process may include at least the following steps S301-S302:

[0152] Step S301: If there is no set of associated plugin business files related to the first sub-object in the terminal database, then based on the query data, obtain the similar plugin business files related to the first sub-object in the terminal database.

[0153] Specifically, through the above Figure 4As can be seen in the corresponding embodiments, the specific implementation method for determining the target plugin business file based on query data can be as follows: the number of files displayed as indicated by the plugin data display area can be obtained, and the plugin query interface can be called based on the number of files displayed; wherein, the plugin query interface is provided by the second application; subsequently, the terminal database can be traversed through the plugin query interface; wherein, the terminal database can refer to the database corresponding to the second application; if there is a set of associated plugin business files related to the first sub-object in the terminal database, the target plugin business file can be determined based on the number of files displayed and the set of associated plugin business files, the target plugin media data can be generated based on the target plugin business file, and then the step of displaying the target plugin media data in the plugin data display area can be executed. Alternatively, if there is a set of associated plugin business files related to the first sub-object in the terminal database, similar plugin business files associated with the first sub-object can be obtained from the terminal database based on the query data. The specific implementation method for retrieving similar plugin business files associated with the first sub-object from the terminal database based on query data can be as follows: The plugin business files in the terminal database, along with their contents, can be retrieved. If the contents of the plugin business files contain similar data that has a similar relationship with the query data, then the plugin business file can be identified as a similar plugin business file associated with the first sub-object. Here, the file content can include the object information, title content, and body content of the second sub-object. Similar data can refer to data in at least one of the object information, title content, and body content that has a similar relationship with the query data. In this application, the method for determining whether a similar relationship exists between data can be any method capable of similarity matching. For example, taking text data as the query data, the method for confirming similar data can be as follows: The vector representation features corresponding to the query data and the data to be matched (contained in the file content) can be determined, and then the vector distance between the two vector representation features can be calculated. This vector distance can be used as the similarity between the query data and the data to be matched. When the similarity is greater than a similarity threshold, the data to be matched can be determined as similar data to the query data, and the plugin business file containing the data to be matched can be determined as a similar plugin business file. As another example, when the query data is image data, the data to be matched in the file content can refer to image data. The image similarity between images can be calculated, and this image similarity can be used as the similarity between the query data and the data to be matched.

[0154] Step S302: Generate similar plugin media data based on similar plugin business files, display the similar plugin media data and a details viewing prompt for the similar plugin media data in the first application; the details viewing prompt is used to instruct the first sub-object to view the full details of the similar plugin business files through the similar plugin media data.

[0155] Specifically, when similar plugin business files are identified, similar plugin media data can be generated based on the object information, title content, and main content summary (if the main content contains similar data, the main content summary also contains similar data) of the second sub-object within the similar plugin business files. This similar plugin media data, along with detailed viewing prompts, can be displayed in the first application. This similar plugin media data and detailed viewing prompts can be used to indicate to the first sub-object: if no plugin business file containing the query data was found, but a similar plugin business file containing similar data was found, the first sub-object can view the similar plugin business file and access its full file details.

[0156] For ease of understanding, please refer to the following: Figure 7 , Figure 7 This is a schematic diagram illustrating a scenario for displaying similar plug-in media data, provided in an embodiment of this application. For example... Figure 7 As shown, terminal device 100a can display search box 20a on the homepage 2001 of the enterprise communication application. After entering the query data "mobile phone" in sub-object a and clicking the search control, if terminal device 100a does not find any email containing the query data "mobile phone" in the terminal database, then terminal device 100a can traverse each email in the terminal database to check if there is a similar email with a similar relationship to the query data "mobile phone". Assuming that email 3 contains the data "tablet" in both its title and body, and there is a similar relationship between the data "tablet" and the query data "mobile phone", then email 3 can be determined to be a similar email (i.e., a similar plug-in business file). Similar plug-in media data 3 can be generated based on the object information, title content, and body content summary of the second sub-object contained in email 3, and displayed in the plug-in data display sub-area Q1 of the plug-in data display area Q of the comprehensive query interface 2002. Figure 7 As shown, the similar plugin media data 3 contains the avatar information, name, title "Tablets Can Also Play Games," and main content summary "How to Set Up Tablets for Playing Games." The similar data "Tablet" contained in the title "Tablets Can Also Play Games" and the similar data "Tablet" contained in the main content summary "How to Set Up Tablets for Playing Games" can be highlighted. Simultaneously, when displaying similar plugin media data 3, a detailed viewing prompt can be displayed for that similar plugin media data 3, as shown in the following example. Figure 7The text message "No emails related to mobile phones found. The following are emails related to tablets. Please check if you wish to view them" can be used to indicate to sub-object a that no emails related to "mobile phone" have been found, but emails related to "tablet" have been found, and sub-object a can view them.

[0157] In this application embodiment, in the query business of the application, if no plugin business file associated with the query data is found, similar plugin business files can be determined based on the query data and displayed, which can make the presented query results more diversified, enrich the presentation form of the query results, and improve the user experience.

[0158] Furthermore, it can be understood that, as described above, the target plugin media data is displayed in the plugin data display area of ​​the first application, and the quantity of the target plugin media data is one or more (the number corresponding to the number of files displayed). However, in the plugin business files associated with the first sub-object, it is not only the target plugin business files that are related to the query data; the target plugin media data is merely generated by selecting a portion of the plugin business files and then displaying them. Therefore, this application can also provide an extended query function. If the first sub-object needs to query more plugin business files besides the target plugin business files, the terminal device can display an extended query interface containing one or more plugin media data. Here, the one or more plugin media data are associated with the first sub-object, and the one or more plugin media data contain the target plugin media data. That is to say, the total quantity of the one or more plugin media data is greater than or equal to the quantity of the target plugin media data.

[0159] For ease of understanding, please refer to the following: Figure 8 , Figure 8 This is a schematic diagram illustrating an extended query scenario provided in an embodiment of this application. For example... Figure 8 As shown, in the comprehensive query interface 2002, terminal device 100a can display the plug-in data display area M, and display the target plug-in media data U1 and target plug-in media data U2 containing the query data in the plug-in data display area M. Sub-object a can view the full file details (email details) of the corresponding plug-in business file (corresponding email) by triggering the operation on the target plug-in media data U1 or the target plug-in media data U2. Figure 8 As shown, the plugin data display area M may also include a control for viewing more corporate email notifications. This control can be understood as an extended query control. The child object a can perform extended queries by triggering the extended query control. In other words, the triggering operation for the extended query control can be an extended query operation that points to the plugin data display area M.

[0160] like Figure 8 As shown, when child object a triggers an operation on the extended query control, terminal device 100a can execute the following: Figure 8 Step 41, as shown, involves responding to an extended query operation targeting the plug-in data display area and displaying an extended query interface containing one or more plug-in media data. Terminal device 100a can respond to an extended query operation targeting the plug-in data display area M and display an extended query interface 2003 containing target plug-in media data U1, target plug-in media data U2, plug-in media data U3, and plug-in media data U4. Specifically, the implementation of displaying the extended query interface containing one or more plug-in media data can be as follows: When sub-object a performs an extended query operation targeting the plug-in data display area, the terminal device can respond to the extended query operation by calling the plug-in query interface; wherein the plug-in query interface is provided by the second application (e.g., it can be the API interface of the second application); the query result interface of the second application can be retrieved through the plug-in query interface; wherein the query result interface includes one or more plug-in media data provided by the second application; subsequently, the query result interface can be determined as the extended query interface and displayed. Understandably, when a sub-object performs an extended query operation targeting the plugin data display area, the terminal device 100a can call the plugin query interface to send the query data to the functional plugin (email plugin). The email plugin can then traverse the local database (also known as the terminal database) corresponding to the second application (i.e., the email application) based on this query data. Based on the terminal database, it can identify one or more plugin media data sets containing the target plugin media data. The email plugin can then generate a query result interface containing these one or more plugin media data sets. The terminal device 100a can directly retrieve this query result interface and use it as the extended query interface for display. In other words, by integrating the functional plugin of the second application into the target application, the target application and the second application can provide corresponding API interfaces for mutual access and data retrieval. The terminal device 100a can also directly retrieve the query result interface of the second application and use it as the extended query interface to be displayed, thus achieving interface reuse. Interface reuse reduces development effort and facilitates data interaction between products, improving the user experience.

[0161] In this context, it's understandable that the process of an email plugin determining one or more plugin media data containing target plugin media data based on the terminal database and generating a query result interface containing that one or more plugin media data can be understood as the process being executed by the terminal device corresponding to the target application, since the email plugin is integrated into the target application. The specific implementation of the terminal device determining one or more plugin media data containing target plugin media data based on the terminal database, generating a query result interface containing that one or more plugin media data, and then displaying it as an extended query interface can be as follows: When a sub-object performs an extended query operation on the plugin data display area, the terminal device can respond to the extended query operation on the plugin data display area by calling the plugin query interface and traversing the terminal database through the plugin query interface. Here, the plugin query interface is provided by the second application; the terminal database refers to the database accessed by the second application. The database should be configured accordingly. If a terminal plugin business file associated with the first sub-object exists in the terminal database, terminal plugin media data can be generated based on the terminal plugin business file. Then, one or more plugin media data can be formed by combining the terminal plugin media data with the target plugin media data, and an extended query interface containing one or more plugin media data can be displayed. The terminal plugin business file does not contain the target plugin business file. If no terminal plugin business file associated with the first sub-object exists in the terminal database, a data query request containing query data can be generated through the plugin query interface. This data query request can be sent to the network server. Based on the feedback data returned by the network server based on the query data, one or more plugin media data can be determined, and an extended query interface containing one or more plugin media data can be displayed. The network server refers to the server that provides query services for the second application (which can be understood as the backend server or cloud server corresponding to the second application, etc.).

[0162] The specific implementation method for determining one or more plug-in media data based on the feedback data returned by the network server based on the query data can be as follows: If the feedback data includes network plug-in business files, network plug-in media data can be generated based on the network plug-in business files, and the network plug-in media data and the target plug-in media data can be determined as one or more plug-in media data; wherein, the network plug-in business files are the plug-in business files associated with the first sub-object that the network server finds in the network database based on the query data; the network database refers to the database corresponding to the network server; the network plug-in business files do not contain the target plug-in business files; and if the feedback data does not include the network plug-in business files, the target plug-in media data can be directly determined as the one or more plug-in media data (that is, after performing the extended query operation, the one or more plug-in media data displayed in the extended query interface still only contains the target plug-in media data).

[0163] Understandably, after the first sub-object (e.g., sub-object a) performs an extended query operation, the terminal device can first traverse the terminal database to check if there are any terminal plugin business files (related to the first sub-object and containing query data) other than the target plugin business file. If the terminal database contains a terminal plugin business file, terminal plugin media data can be directly generated based on that file. This terminal plugin media data, along with the target plugin media data, is then combined with the target plugin media data to form one or more plugin media data sets displayed in the extended query interface. The terminal device can then arrange and display one or more plugin media data sets sequentially according to the file transfer time corresponding to each plugin media data set. Optionally, if the number of terminal plugin business files in the terminal database is small (e.g., below the threshold for the number of extended files to be displayed), a data query request containing query data can be generated. This data query request can be sent to the network server corresponding to the second application to obtain the corresponding network plugin business file. Then, network plugin media data can be generated and combined with the target plugin media data to form one or more plugin media data sets. Of course, if the network server does not contain the corresponding network plugin service files, the target plugin media data and the aforementioned terminal plugin media data can be directly identified as one or more plugin media data. In other words, the extended query interface will only display the target plugin media data and the terminal plugin media data.

[0164] Optionally, and understandably, if the terminal plugin service file does not exist in the terminal database, a data query request containing the query data can be generated. This data query request can be sent to the network server corresponding to the second application, retrieve the corresponding network plugin service file from the network server, and then generate network plugin media data together with the target plugin media data to form one or more plugin media data sets. Of course, if the network server also does not contain the corresponding network plugin service file, the target plugin media data can be directly determined as one or more plugin media data sets. That is, only the target plugin media data is displayed in the extended query interface.

[0165] Optionally, and understandably, as described above, if the terminal plugin service file exists in the terminal database, terminal plugin media data can be directly generated based on that file. This terminal plugin media data, along with the target plugin media data, will then be displayed as one or more plugin media data sets in the extended query interface. If the first sub-object still requires further queries, it can perform another extended query operation in the extended query interface. The terminal device can respond to this operation, traversing the terminal database and network database again to find more plugin service files and generate the corresponding plugin media data for display.

[0166] In one embodiment, it is understood that when obtaining network plugin service files from a network server, the local database can be updated based on the network plugin service files. That is, when the aforementioned feedback data includes network plugin service files, the terminal database can be updated based on the network plugin service files to obtain an updated terminal database; wherein, the updated database includes the network plugin service files. It is understood that by continuously updating the terminal database, the database storage space will become smaller and smaller. Since the plugin service files stored in the terminal database and the network database are the same (the number of files stored in the terminal database is less than or equal to the number of files stored in the network database), in order to alleviate the storage pressure on the terminal database, this embodiment of the application can display a cleanup prompt message for the plugin service files in the terminal database when the number of plugin service files stored in the terminal database reaches a certain threshold (which can be a manually defined value, such as 100). This cleanup prompt message is used to indicate to the first sub-object that the number of files stored in the terminal database is large at the current moment, and the first sub-object can determine whether to clean up the plugin service files stored in the terminal database based on the cleanup prompt message. If the first sub-object determines that it needs to be cleaned based on the cleanup prompt, then the file cleanup operation for the cleanup prompt can be performed. The terminal device can respond to this operation and clean up the plug-in service files in the terminal database accordingly (for example, the plug-in service files in the terminal database can be sorted according to the order of file transfer time (e.g., from earliest to latest) to obtain the terminal file sequence, and then the first N (N can be a positive integer) plug-in service files in the terminal file sequence can be selected for cleanup and deletion).

[0167] It is understandable that, such as Figure 8 As shown, when terminal device 100a displays the extended query interface 2003, it can display auxiliary filtering function controls. These auxiliary filtering function controls can be used to further filter sub-objects a, and one auxiliary filtering function control can correspond to one filtering dimension. For example, as Figure 8As shown, the auxiliary filtering control can include a sender control, which can correspond to the sender dimension. Sub-object 'a' can trigger an operation on this sender control to filter plug-in media data from one or more plug-in media data whose sender information contains the query data "mobile phone". The auxiliary filtering control can also include a recipient control, which can correspond to the recipient dimension. Sub-object 'a' can trigger an operation on this recipient control to filter plug-in media data from one or more plug-in media data whose recipient information contains the query data "mobile phone". The auxiliary filtering control can also include a subject control, which can correspond to the subject dimension (which can be understood as the title dimension). Sub-object 'a' can trigger an operation on this subject control to filter plug-in media data from one or more plug-in media data whose title content contains the query data "mobile phone". The auxiliary filtering control can also include all controls, which can correspond to all dimensions (such as the recipient dimension, sender dimension, and subject dimension mentioned above). Sub-objects can trigger any auxiliary filtering control to view a portion of the plug-in media data indicated by the auxiliary filtering control. For example, such as Figure 8 As shown, when a child object triggers an operation on the theme control, the terminal device 100a can execute the following: Figure 8 Step 42, as shown, is to respond to the trigger operation of the auxiliary filtering function control (theme control) and obtain a portion of the plug-in media data indicated by the auxiliary filtering function control (theme control) from one or more plug-in media data; wherein, the filtering dimension content of the portion of plug-in media data includes query data, and the filtering dimension content refers to the content corresponding to the target business dimension (such as the theme dimension) in the portion of plug-in media data, and the target business dimension is the dimension indicated by the auxiliary filtering function control (theme control).

[0168] For example, such as Figure 8 As shown, since the title content of plug-in media data U3, "Mobile Phone User Manual," contains the query data "Mobile Phone," and this title content, "Mobile Phone User Manual," corresponds to the topic dimension of plug-in media data U3, plug-in media data U3 can be used to form part of the plug-in media data corresponding to the topic dimension. Similarly, since the title content of plug-in media data U4, "Prohibited Items for Mobile Phones," contains the query data "Mobile Phone," and this title content, "Prohibited Items for Mobile Phones," corresponds to the topic dimension of plug-in media data U4, plug-in media data U4 can be used to form part of the plug-in media data corresponding to the topic dimension. Therefore, it can be seen from the above that, for the topic dimension, the terminal device can determine that its corresponding part of the plug-in media data includes plug-in media data U3 and plug-in media data U4. Further, terminal device 100a can execute as follows: Figure 8Step 43, as shown, involves displaying a portion of the plug-in media data in the extended query interface. Specifically, when displaying this portion of the plug-in media data, the plug-in media data U1, U2, U3, and U4 currently displayed in the extended query interface can be updated to display plug-in media data U3 and U4 respectively.

[0169] It should be understood that the embodiments of this application have added auxiliary filtering functions to the extended query interface, which can support filtering by multiple dimensions (such as sender object dimension, recipient object dimension, subject dimension and all dimensions), making it easier for sub-objects to quickly filter out the corresponding plugin business files from a large number of query results, which can greatly improve query efficiency.

[0170] Further, please see Figure 9 , Figure 9 This is a schematic diagram of a process for displaying target plugin media data provided in an embodiment of this application. This process can correspond to the above. Figure 3 In the corresponding embodiment, the process of displaying target plugin media data in the first application in response to a data query operation targeting the first sub-object is described. For example... Figure 9 As shown, the process may include at least the following steps S501-S503:

[0171] Step S501: In the first application, respond to the data query operation for the first sub-object and display a comprehensive query interface including the plug-in file viewing control in the first application.

[0172] Specifically, after the first sub-object performs a data query operation in the first application, the terminal device can display a comprehensive query interface in the first application. This comprehensive query interface can refer to an interface provided by the first application for displaying comprehensive query results. The comprehensive query results can refer to an object list including target interactive sub-objects, target interactive groups, target application files in the first application, and related plugin business files in the second application. Specifically, a target interactive sub-object can refer to a sub-object whose interaction records (such as session records) contain query data within an interaction (such as a conversation) between the target application and the first sub-object; a target interactive group can refer to a group (composed of the first sub-object and other sub-objects) whose interaction records (such as session records) contain query data within an interaction (such as a conversation) between the target application and the first sub-object; a target application file can refer to an application file corresponding to the first application that contains query data; and related plugin business files can refer to plugin business files in the second application associated with the first sub-object that contain query data.

[0173] In other words, the content presented in the comprehensive query interface is not limited to the query results for plugin business files. In this application, when the terminal device displays the comprehensive query interface, it can display a plugin file viewing control within the interface. The first sub-object can view a list of query results containing only the relevant plugin business files by triggering the plugin file viewing control.

[0174] Step S502: Respond to the triggered operation of the plugin file viewing control and display the plugin data display interface.

[0175] Specifically, after the first sub-object executes the trigger operation for the plugin file viewing control, the terminal device can respond to this trigger operation and display the plugin data display interface. This plugin data display interface can be the same as the comprehensive query interface; alternatively, it can be a new interface independent of the comprehensive query interface (the area of ​​the plugin data display interface is smaller than that of the comprehensive query interface), which can be overlaid on top of the comprehensive query interface when displaying the plugin data display interface.

[0176] Step S503: Display the target plugin media data in the plugin data display interface.

[0177] Specifically, when the plugin data display interface and the comprehensive query interface are the same, the comprehensive query results displayed in the comprehensive query interface can be updated to show the target plugin media data (i.e., from displaying comprehensive query results to displaying query results containing only the target plugin business files). When the plugin data display interface and the comprehensive query interface are independent interfaces, the target plugin media data can be directly displayed in the plugin data display interface. It can be understood that the target plugin media data here refers to all plugin media data associated with the first sub-object and containing query data, contained in the terminal database and network database. In other words, the number of target plugin media data is one or more (or at least two). If the plugin data display interface cannot display all the target plugin media data, the sub-object can load and view more target plugin media data through a swiping operation in the interface (such as the plugin data display interface).

[0178] For ease of understanding, please refer to the following: Figures 10a-10b , Figures 10a-10b This is a schematic diagram illustrating a scenario for displaying target plugin media data, provided in an embodiment of this application. For example... Figure 10aAs shown, terminal device 100b can be the terminal device corresponding to sub-object a. When the target application is installed on terminal device 100b, sub-object a can start and run the target application. Taking the target application as a communication application for an enterprise (hereinafter referred to as the enterprise communication application) as an example, sub-object a can refer to a member of an enterprise S. Sub-object a can start and run the enterprise communication application for enterprise S through terminal device 100b. After sub-object a starts and runs the enterprise communication application, it can log in to the enterprise communication application through its bound account in the enterprise communication application. After logging in to the enterprise communication application, it first enters the homepage of the enterprise communication application. That is to say, the bound account of sub-object a can also be used to refer to sub-object a.

[0179] like Figure 10a As shown, the homepage 9001 may contain a search box 90a. Sub-object a can input query data through this search box 90a to retrieve results related to that query data. For example... Figure 10a As shown, when sub-object a enters the text "mobile phone" in search box 90a and triggers the search control, the text "mobile phone" entered by sub-object a can be called query data, and the triggering operation of sub-object a on the search control can be called a data query operation. Terminal device 100b can respond to this data query operation and display a comprehensive query interface 9002 including a plugin file viewing control. In this embodiment, taking an email plugin as an example, the plugin business file can refer to emails, and the plugin file viewing control can refer to the email control in the comprehensive query interface 9002. Figure 10a As shown, terminal device 100b can, by default, prioritize displaying query results containing all dimensions (such as contact dimension, group chat dimension, email dimension, file dimension, etc.) in the comprehensive query interface 9002. For example, the query results may include the query results for contact "Xiaotu," the query results for group X, the email results sent by child object "Zhao Ke'ai" to child object "a" (which is the corresponding plugin media data U1), and the email results sent by child object "Yangyangyang" to child object "a" (which is the corresponding plugin media data U2). Child object "a" can view a list of query results containing only the plugin media data for emails by triggering the email control.

[0180] For example, such as Figure 10bAs shown, after sub-object a triggers an operation on the email control in the comprehensive query interface 9002, terminal device 100b can respond to this triggering operation, display the plug-in data display interface, and display the plug-in media data U1 and plug-in media data U2 in the plug-in data display interface. Taking the plug-in data display interface as the same as the comprehensive query interface 9002 as an example, after sub-object a triggers an operation on the email control in the comprehensive query interface 9002, terminal device 100b can respond to this triggering operation, updating the query result list of all dimensions displayed in the comprehensive query interface 9002 to a result list containing only plug-in media data U1 and plug-in media data U2.

[0181] It is understood that the comprehensive query interface or plugin data display interface in this application can refer to the query result display interface (such as an H5 interface) corresponding to the second application. The first application can embed this H5 interface, and the search interaction experience in the comprehensive query interface is achieved through a brand-new global search pop-up. The enterprise communication application can provide a sidebar in the comprehensive query interface (the sidebar can display filter controls (such as dimension controls containing plugin file viewing controls), and this sidebar can serve as a filter bar). The dimension filter conditions selected by the sub-object (such as triggering an operation on the above-mentioned email dimension control, then the dimension filter condition can be the email dimension condition) can be passed to the H5 page through parameters. The H5 interface can then display the corresponding query results (such as only displaying the email query result list) according to the filter dimension conditions. Among them, when the H5 page is embedded in the comprehensive query interface of the enterprise communication application, data interaction can be performed through schema and native. After the sub-object enters query data, it can call the search interface provided by the H5 page (which can be called the plugin query interface) to pass the query data to the H5 page in the form of schema, and the H5 page can then initiate a search. Similarly, when a child object selects a filter dimension in the sidebar, the selected filter dimension is passed to the H5 page via schema parameters, and the H5 page then initiates a search request based on the requested parameters.

[0182] It should be understood that this H5 interface can receive query data from the global search box, then initiate a query request. Based on this query request, it can obtain all target plugin business files from the terminal database and the network server, and then generate all target plugin media data (i.e., the number of target plugin media data can be one or more; the number of target plugin media data can also be at least two), and display it in the H5 interface. (When the H5 interface cannot display all the target plugin media data, it can support child objects to scroll or perform other operations to view more, and through scrolling or viewing more, more query results can be viewed). Optionally, it is understood that child objects can select a target plugin media data from multiple target plugin media data to preview its corresponding plugin business file, and the terminal device can divide a region in the comprehensive query interface as an area to display the file preview content, and the terminal device can display the file preview content of the plugin business file in this area. The specific implementation can be as follows: When the first sub-object executes a trigger operation on a target plugin media data, the terminal device can respond to the trigger operation on the target plugin media data and display a plugin data preview area in the plugin data display interface; subsequently, file preview information of the target plugin business file can be displayed in the plugin data preview area; wherein, the file preview information of the target plugin business file is a partial information from the full file details information of the target plugin business file; and the amount of file information in the file preview information is greater than the amount of file information in the target plugin media data. In other words, the target plugin business file presented in the file preview information is more detailed and comprehensive than that presented in the target plugin media data.

[0183] In one feasible embodiment, the plugin data preview area may include a file details viewing control. The first sub-object can view the full file details of the target plugin business file by triggering the file details viewing control. That is, after viewing the preview content of the target plugin business file, the first sub-object can further view the full details.

[0184] For ease of understanding, please refer to the following: Figure 11 , Figure 11 This is a schematic diagram illustrating a scenario of previewing a plugin service file provided in an embodiment of this application. For example... Figure 11 As shown, in the comprehensive query interface 9002, when sub-object a triggers a operation on plug-in media data U2, terminal device 100b can respond to this triggering operation, displaying the plug-in data preview area W in the comprehensive query interface 9002, and displaying the file preview information of the plug-in business file corresponding to the plug-in media data U2 in the plug-in data preview area W, such as... Figure 11As shown, the file preview information may include the title "Model Design Planning", sender information "Zhao Ke'ai", recipient information "Sent to Sub-object A", file transfer time 6:50 PM, and part of the email body content "Mobile phone preview design content: 1. The model is mainly thin and light; 2. Non-foldable screen". Figure 11 As shown, the plugin data preview area W also includes a details view control (i.e., a file details view control). When the sub-object a triggers an operation on it, the terminal device 100b can respond to this trigger operation, display the file details display interface 9003, and display the full file details information for the plugin's business file in the file details display interface 9003. Compared to the file preview information mentioned above, the full file details information includes complete main content (including the main content "3, color is white").

[0185] Optionally, and understandably, the aforementioned plugin data display interface may include auxiliary filtering controls. These controls can be used by the first sub-object to further filter the target plugin media data. Each auxiliary filtering control can correspond to a filtering dimension. When the first sub-object triggers an operation on a certain auxiliary filtering control, the terminal device can respond to the trigger operation and display the filtering dimension and its corresponding input box. The first sub-object can enter the desired dimension query data in the input box, and the terminal device can respond to the input operation and retrieve the target plugin media data containing the dimension query data from at least two target plugin media data sets, as the dimension plugin media data. The dimension query data can refer to the data associated with the filtering dimension entered in the input operation. Subsequently, the terminal device can update the display of at least two target plugin media data sets in the plugin data display interface to the dimension plugin media data.

[0186] It can be understood that the filtering dimension can include the sender dimension. The first sub-object can enter the sender information (such as Zhang San) to be filtered in the corresponding input box. The input sender information "Zhang San" can be called the dimension query data. Then the terminal device can filter out the plug-in media data (i.e., the plug-in media data generated by the plug-in business file sent by Zhang San to the first sub-object) from at least two target plug-in media data, where the sender information contains the dimension query data "Zhang San". The filtering dimension can also include the recipient dimension. The first sub-object can enter the recipient information (such as Zhang San) to be filtered in the corresponding input box. The input recipient information "Zhang San" can be called the dimension query data. Then the terminal device can filter out the plug-in media data (i.e., the plug-in media data generated by the plug-in business file sent by the first sub-object to Zhang San) from at least two target plug-in media data, where the recipient information contains the dimension query data "Zhang San". The filtering dimension can include a topic dimension (title dimension). The first sub-object can enter the desired topic information (e.g., Zhang San) in the corresponding input box. This entered topic information can be called the dimension query data. The terminal device can then filter out plug-in media data whose title information contains the dimension query data from at least two target plug-in media data. Examples of auxiliary filtering function controls will not be provided here. It should be noted that when the first sub-object triggers an operation on a certain auxiliary filtering function control, the terminal device can display a filtering panel in the comprehensive query interface, showing the filtering dimension and its corresponding input box. This filtering panel can be implemented using native functions. After the first sub-object enters the filtering content, it can be passed to the H5 page via the schema parameter. The H5 page then initiates a search request based on the requested parameters.

[0187] For ease of understanding, please refer to the following: Figure 12 , Figure 12 This is a schematic diagram illustrating a data filtering scenario provided in an embodiment of this application. For example... Figure 12 As shown, taking the plugin data display interface as an example of a comprehensive query interface, the comprehensive query interface 9002 can include a filter control (auxiliary filter function control). After a child object a triggers an operation on it, the terminal device 100b can respond to this triggering operation, displaying the sender dimension and recipient dimension of the filter, and simultaneously displaying the input boxes corresponding to the sender dimension and the recipient dimension. Figure 12As shown, after the sender information "Zhao Ke'ai" is entered in the input box corresponding to the sender in sub-object a, the sender information "Zhao Ke'ai" can be called dimension query data. Terminal device 100b can filter the plug-in media data containing the dimension query data "Zhao Ke'ai" in the sender information from plug-in media data U1 and plug-in media data U2 as plug-in media data U1. Then, plug-in media data U1 can be used as dimension plug-in media data. Terminal device 100b can update the display of plug-in media data U1 and plug-in media data U2 displayed in the comprehensive query interface 9002 to plug-in media data U1.

[0188] It should be understood that, in the query service of this application embodiment, by integrating functional plug-ins, a query function for plug-in service files can be added, which can enrich the diversity of query results. At the same time, when displaying the plug-in media data corresponding to the plug-in service file, the main content summary can be displayed simultaneously, which can enrich the presentation of the query results. When the main content summary contains query data, it can also be highlighted, which can facilitate quick location of the query data in the query results and improve query efficiency.

[0189] Further, please see Figure 13 , Figure 13 This is a schematic diagram of an interaction flow provided in an embodiment of this application. The interaction flow can refer to the interaction between a first application, a functional plugin of a second application, and the backend server (also known as a network server) corresponding to the second application. Here, we will illustrate the interaction flow using an example where the first application is an enterprise communication application, the second application is an email application, the functional plugin is an email plugin corresponding to the email application, and the backend server is an email backend server. Figure 13 As shown, the interaction process may include at least the following steps 61-70:

[0190] Step 61: Activate the email plugin in the enterprise communication application.

[0191] Specifically, an email plugin can be integrated into an enterprise communication application. When a child object starts the enterprise communication application, the enterprise communication application can also start the email plugin.

[0192] Step 62: The email plugin sends a request to the email backend server to bind the email account.

[0193] Specifically, before the sub-object has bound its first bound account (which can be understood as the bound account of the sub-object in the enterprise communication application) to its second bound account (which can be understood as the bound account of the sub-object in the email application), the bound account in the enterprise communication application and the email account in the email application can be bound through the email plugin and the email backend server.

[0194] Step 63: The email plugin synchronizes and updates the email index.

[0195] Specifically, when the sub-object binds the two accounts mentioned above, the email plugin can, by default, retrieve the sub-object's historical sent and received emails within a recent period (e.g., within 30 days). During the process of retrieving these historical emails to the local machine (i.e., the database corresponding to the second application, also known as the local database or terminal database), it can establish index relationships between the email subject, sender, recipient, CC, body, and attachments contained in each historical email. One historical email corresponds to one index relationship, thus obtaining an index table containing multiple index relationships. Furthermore, when the sub-object subsequently retrieves or sends emails, it can also establish new index relationships according to the index relationship establishment strategy described above and update the index table.

[0196] Step 64: The enterprise communication application sends a query request to the email plugin.

[0197] Specifically, after the sub-object inputs query data, the enterprise communication application can call the corresponding interface to send a query request to the email plugin.

[0198] Step 65: The email plugin performs a local query.

[0199] Specifically, after the sub-object inputs query data, the email plugin can first search for the corresponding email in the local index table. The search fields include basic email fields such as email subject, sender, recipient, CC, body, and attachments. That is, it iterates through the subject, sender, recipient, CC, body, and attachment to see if the query data is present. If at least one of these fields contains the query data, the email is identified as the target email. It should be noted that for long body texts, the search interface needs to return a summary of the matched body text. This summary can contain the matched query data, so that the query data within the body text summary is highlighted when displaying the summary.

[0200] Step 66: The email plugin returns the first-level list results to the top screen of the enterprise communication application.

[0201] Specifically, the first-level list result is the target email list mentioned above. The email plugin can return this target email list to the enterprise communication application, which can then display it. It can be understood that if the number of target emails in the local query results is sufficient to reach the display threshold (i.e., the number of files to display as described above, such as 3), then the results can be returned to the enterprise communication application; if the display threshold is not reached, a network query can be initiated, i.e., a query request can be sent to the email backend server.

[0202] Step 67: The enterprise communication application sends a request to the email plugin to query more information.

[0203] Specifically, if the sub-object has a need for further querying (i.e., extended querying needs), then execute step 65 above to perform a local query; if the locally stored emails do not support extended queries, then execute step 68 to initiate a network query.

[0204] Step 68: The email plugin sends a query request to the email backend server.

[0205] Step 69: The email backend server returns the network query results to the email plugin.

[0206] Specifically, the network query results returned by the email backend server can be written to the local database and the index table can be updated for subsequent query operations.

[0207] Step 70: The email plugin returns the network query results to the enterprise communication application and displays them on the screen.

[0208] Specifically, the implementation methods of steps 61-70 can be found in the descriptions of the corresponding embodiments above, and will not be repeated here. The beneficial effects they bring will also not be repeated here.

[0209] Further, please see Figure 14 , Figure 14 This is a system logic flowchart provided in an embodiment of this application. Here, we illustrate the system logic flow using an example where the first application is an enterprise communication application, the second application is an email application, the functional plugin is the email plugin corresponding to the email application, and the backend server is the email backend server. Figure 14 The process may include at least the following steps 81-89:

[0210] Step 81: Input query data for the sub-object.

[0211] Step 82: The enterprise communication application calls the email plugin query interface.

[0212] Step 83: Determine whether to perform a local query.

[0213] Specifically, if a local query is performed, proceed to step 85; if no local query is performed, proceed to step 84.

[0214] Step 84: Initiate a network query.

[0215] Step 85: Determine whether the local result has reached the threshold.

[0216] Specifically, if it is determined that the threshold has not been reached, step 84 above can be executed; if it is determined that the threshold has been reached, subsequent step 86 can be executed.

[0217] Step 86: Return the first-level result list.

[0218] Specifically, the email plugin can return a top-level results list to the enterprise communication application. Then, step 87 can be performed.

[0219] Step 87, end the query.

[0220] Step 88: The web server returns the web query results.

[0221] Specifically, after the email plugin initiates a network query to the network server, the network server can return the network query results, which can be compiled into a first-level result list.

[0222] Step 89: The email plugin updates the local database based on the network query results.

[0223] For the specific implementation of steps 81-89, please refer to the description in the corresponding embodiments above. It will not be repeated here, nor will the beneficial effects it brings be repeated.

[0224] Further, please see Figure 15 , Figure 15 This is a schematic diagram of the structure of a data processing apparatus provided in an embodiment of this application. The data processing apparatus can be a computer program (including program code) running on a computer device; for example, the data processing apparatus is an application software. The data processing apparatus can be used to execute... Figure 3 The method shown. (As illustrated) Figure 15 As shown, the data processing device 1 may include a media data display module 11 and a highlighting module 12.

[0225] The media data display module 11 is used to respond to data query operations for the first sub-object in the first application and display target plugin media data in the first application. The target plugin media data is generated based on the target plugin business files associated with the first sub-object. The target plugin business files are obtained by requesting the network server through the plugin query interface when the terminal database is traversed through the plugin query interface and no set of associated plugin business files that meet the file display requirements is found in the terminal database. The file display requirements refer to the display requirements indicated by the plugin data display area. The plugin data display area refers to the area in the first application used to display the target plugin media data. The terminal database refers to the database corresponding to the second application. The plugin query interface is provided by the second application. The network server refers to the server that provides query services for the second application. The first application is different from the second application. The target plugin media data includes a summary of the main content of the target plugin business file. If the main content of the target plugin business file contains the query data input by the data query operation, the summary of the main content is obtained by filtering the main content based on the query data, and the summary of the main content includes the query data.

[0226] The highlighting module 12 is used to highlight the query data contained in the target plugin media data.

[0227] The specific implementation methods of the media data display module 11 and the highlight display module 12 can be found in the above description. Figure 3 The descriptions of steps S101-S102 in the corresponding embodiments will not be repeated here.

[0228] In one embodiment, the target plugin media data displayed in the first application consists of object information of the second sub-object, the title content of the target plugin business file, and a summary of the main content; the second sub-object refers to the object that performs plugin business through the target plugin business file and the first sub-object.

[0229] In one embodiment, the media data display module 11 may include a query interface display unit 111 and a plug-in data display unit 112.

[0230] The query interface display unit 111 is used to respond to a data query operation for the first sub-object in the first application and to display a comprehensive query interface in the first application.

[0231] The plug-in data display unit 112 is used to display the plug-in data display area in the comprehensive query interface, and to display the target plug-in media data in the plug-in data display area.

[0232] The specific implementation methods of the query interface display unit 111 and the plug-in data display unit 112 can be found in the above description. Figure 4The descriptions of steps S201-S202 in the corresponding embodiments will not be repeated here.

[0233] In one embodiment, the target plugin media data is displayed in the plugin data display area of ​​the first application;

[0234] The data processing device 1 may also include: an extended query module 13.

[0235] The extended query module 13 is used to respond to extended query operations for the plug-in data display area and display an extended query interface containing one or more plug-in media data; one or more plug-in media data are associated with the first sub-object, and one or more plug-in media data contain the target plug-in media data.

[0236] For details on the implementation of the extended query module 13, please refer to the above. Figure 8 The descriptions in the corresponding embodiments will not be repeated here.

[0237] In one embodiment, the extended query interface includes auxiliary filtering function controls;

[0238] The data processing device 1 may also include: an auxiliary filtering module 14.

[0239] The auxiliary filtering module 14 is used to respond to the trigger operation of the auxiliary filtering function control, and to obtain a portion of the plug-in media data indicated by the auxiliary filtering function control from one or more plug-in media data; the filtering dimension content of the portion of plug-in media data includes the query data, and the filtering dimension content refers to the content corresponding to the target business dimension in the portion of plug-in media data, and the target business dimension is the dimension indicated by the auxiliary filtering function control;

[0240] The auxiliary filtering module 14 is also used to display some plug-in media data in the extended query interface.

[0241] For details on the implementation of the auxiliary filtering module 14, please refer to the above. Figure 8 The descriptions in the corresponding embodiments will not be repeated here.

[0242] In one embodiment, the data processing device 1 may further include a details display module 15.

[0243] The details display module 15 is used to respond to triggered operations on the target plugin media data and display the file details display interface;

[0244] The details display module 15 is also used to display the full details of the target plugin business file in the file details display interface.

[0245] For details on the implementation of the details display module 15, please refer to the above. Figure 3 The description of step S102 in the corresponding embodiment will not be repeated here.

[0246] In one embodiment, the extended query module 13 may include an interface call unit 131 and an interface retrieval unit 132.

[0247] Interface calling unit 131 is used to respond to extended query operations for the plugin data display area and call the plugin query interface; the plugin query interface is provided by the second application;

[0248] The interface retrieval unit 132 is used to retrieve the query result interface of the second application through the plugin query interface; the query result interface includes one or more plugin media data provided by the second application;

[0249] The interface retrieval unit 132 is also used to determine the query result interface as an extended query interface and display the extended query interface.

[0250] The specific implementation methods of the interface calling unit 131 and the interface retrieval unit 132 can be found in the above description. Figure 8 The descriptions in the corresponding embodiments will not be repeated here.

[0251] In one embodiment, the media data display module 11 may include: a comprehensive interface display unit 113 and a plug-in interface display unit 114.

[0252] The integrated interface display unit 113 is used to respond to data query operations for the first sub-object in the first application and to display an integrated query interface including a plug-in file viewing control in the first application.

[0253] The plugin interface display unit 114 is used to respond to the trigger operation of the plugin file viewing control and display the plugin data display interface;

[0254] The plugin interface display unit 114 is also used to display the target plugin media data in the plugin data display interface.

[0255] The specific implementation methods of the integrated interface display unit 113 and the plug-in interface display unit 114 can be found in the above description. Figure 9 The descriptions of steps S501-S503 in the corresponding embodiments will not be repeated here.

[0256] In one embodiment, the media data display module 11 may further include a preview area display unit 115 and a preview information display unit 116.

[0257] The preview area display unit 115 is used to respond to the trigger operation for the target plugin media data and display the plugin data preview area in the plugin data display interface;

[0258] The preview information display unit 116 is used to display the file preview information of the target plugin business file in the plugin data preview area; the file preview information of the target plugin business file is part of the full file details information of the target plugin business file; the amount of file information in the file preview information is greater than the amount of file information in the target plugin media data.

[0259] The specific implementation methods of the preview area display unit 115 and the preview information display unit 116 can be found in the above description. Figure 9 The description of step S503 in the corresponding embodiment will not be repeated here.

[0260] In one embodiment, the plugin data preview area also includes a file details viewing control;

[0261] The media data display module 11 may also include: a file details display unit 117.

[0262] The file details display unit 117 is used to respond to the trigger operation of the file details viewing control and display the file details display interface;

[0263] The file details display unit 117 is also used to display the full file details information of the target plugin business file in the file details display interface.

[0264] For details on the implementation of the document details display unit 117, please refer to the above. Figure 9 The description of step S503 in the corresponding embodiment will not be repeated here.

[0265] In one embodiment, the plugin data display interface also includes an auxiliary filtering function control; the number of target plugin media data is at least two.

[0266] The media data display module 11 may also include: an input box display unit 118, a dimension media data display unit 119, and an update display unit 120.

[0267] The input box display unit 118 is used to respond to the trigger operation of the auxiliary filtering function control and display the filtering dimension and the corresponding input box of the filtering dimension;

[0268] The dimensional media data display unit 119 is used to respond to input operations on the input box and to obtain target plugin media data containing dimensional query data from at least two target plugin media data as dimensional plugin media data; dimensional query data refers to the data associated with the filtering dimension entered in the input operation.

[0269] Update display unit 120 to update the display of at least two target plugin media data in the plugin data display interface as dimension plugin media data.

[0270] The specific implementation methods of the input box display unit 118, the dimension media data display unit 119, and the update display unit 120 can be found in the above description. Figure 9 The description of step S503 in the corresponding embodiment will not be repeated here.

[0271] In one embodiment, the data processing device 1 may further include: a plug-in interface calling module 16, a traversal module 17, a target file determination module 18, and a step execution module 19.

[0272] Plugin interface call module 16 is used to obtain the number of files displayed as indicated by the plugin data display area, and call the plugin query interface based on the number of files displayed.

[0273] Traversal module 17 is used to traverse the terminal database through the plugin query interface; the terminal database refers to the database corresponding to the second application.

[0274] The target file determination module 18 is used to determine the target plugin business file based on the number of files displayed and the set of associated plugin business files if there is a set of associated plugin business files related to the first sub-object in the terminal database.

[0275] Step execution module 19 is used to generate target plugin media data based on the target plugin business file and to execute the step of displaying the target plugin media data in the plugin data display area.

[0276] The specific implementation methods of the plugin interface call module 16, traversal module 17, target file determination module 18, and step execution module 19 can be found in the above description. Figure 4 The description of step S202 in the corresponding embodiment will not be repeated here.

[0277] In one embodiment, the traversal module 17 may include a content traversal unit 171 and a set generation unit 172.

[0278] Content traversal unit 171 is used to traverse the object information, title content, and main content of the second sub-object contained in the plug-in business file in the terminal database through the plug-in query interface; the second sub-object refers to the object that performs plug-in business through the plug-in business file and the first sub-object in the terminal database.

[0279] The collection generation unit 172 is used to determine the plugin business file as the associated plugin business file associated with the first sub-object if the file traversal content contains query data, and to form an associated plugin business file set based on the associated plugin business file; the file traversal content refers to at least one of the following: object information, title content, and body content.

[0280] The specific implementation methods of the content traversal unit 171 and the set generation unit 172 can be found in the above description. Figure 4 The description of step S202 in the corresponding embodiment will not be repeated here.

[0281] In one embodiment, the target file determination module 18 is further specifically used to obtain the total number of associated plugin business files in the associated plugin business file set;

[0282] The target file determination module 18 is also specifically used to determine if the total number is greater than or equal to the number of files to be displayed, and to obtain the target plugin business file from the set of associated plugin business files based on the number of files to be displayed and the file transfer time corresponding to each associated plugin business file in the set of associated plugin business files.

[0283] The target file determination module 18 is further specifically used to determine that if the total number is less than or equal to the number of files displayed, the set of associated plugin business files does not meet the number of files displayed. It then generates a first data query request containing query data and the number of files displayed through the plugin query interface, sends the first data query request to the network server, and determines one or more first network plugin business files returned by the network server based on the query data and the number of files displayed as target plugin business files. The total number of files in the one or more first network plugin business files is the same as the number of files displayed; the one or more first network plugin business files include a set of associated plugin business files; the one or more first network plugin business files are plugin business files associated with the first sub-object that the network server retrieves from the network database based on the query data; the network database refers to the database corresponding to the network server.

[0284] In one embodiment, the target file determination module 18 may include a file sorting unit 181 and a target file determination unit 182.

[0285] The file sorting unit 181 is used to sort the associated plugin business files in the associated plugin business file set according to the file transfer time corresponding to each associated plugin business file, so as to obtain the plugin file sequence.

[0286] The target file determination unit 182 is used to sequentially obtain K associated plugin business files in the plugin file sequence and determine the K plugin business files as target plugin business files; K is equal to the number of files displayed.

[0287] The specific implementation methods of the file sorting unit 181 and the target file determination unit 182 can be found in the above description. Figure 4 The description of step S202 in the corresponding embodiment will not be repeated here.

[0288] In one embodiment, the extended query module 13 may include: a terminal traversal unit 133, a first interface display unit 134, a request sending unit 135, a plug-in data determination unit 136, and a second interface display unit 137.

[0289] Terminal traversal unit 133 is used to respond to extended query operations for the plug-in data display area, call the plug-in query interface, and traverse the terminal database through the plug-in query interface.

[0290] The first interface display unit 134 is used to generate terminal plug-in media data based on the terminal plug-in service file if a terminal plug-in service file associated with the first sub-object exists in the terminal database, and to form one or more plug-in media data based on the terminal plug-in media data and the target plug-in media data, and to display an extended query interface containing one or more plug-in media data; the terminal plug-in service file does not contain the target plug-in service file.

[0291] The request sending unit 135 is used to generate a second data query request containing query data through the plugin query interface if there is no terminal plugin business file associated with the first sub-object in the terminal database, and send the second data query request to the network server.

[0292] The plug-in data determination unit 136 is used to determine one or more plug-in media data based on the feedback data returned by the network server based on the query data;

[0293] The second interface display unit 137 is used to display an extended query interface containing one or more plug-in media data.

[0294] The specific implementation methods of the terminal traversal unit 133, the first interface display unit 134, the request sending unit 135, the plug-in data determination unit 136, and the second interface display unit 137 can be found in the above description. Figure 4 The description of step S202 in the corresponding embodiment will not be repeated here.

[0295] In one embodiment, the plug-in data determination unit 136 is further configured to, if the feedback data includes a second network plug-in service file, generate network plug-in media data based on the second network plug-in service file, and determine the second network plug-in media data and the target plug-in media data as one or more plug-in media data; the second network plug-in service file is a plug-in service file that the network server queries in the network database based on the query data; the network database refers to the database corresponding to the network server; the second network plug-in service file does not contain the target plug-in service file;

[0296] The plug-in data determination unit 136 is also specifically used to determine the target plug-in media data as one or more plug-in media data if the feedback data does not include the second network plug-in service file.

[0297] In one embodiment, the extended query module 13 may further include a database update unit 138.

[0298] The database update unit 138 is used to update the terminal database based on the second network plug-in service file when the feedback data includes the second network plug-in service file, so as to obtain the updated terminal database; the updated database includes the second network plug-in service file.

[0299] For details on the implementation of the database update unit 138, please refer to the above. Figure 8 The descriptions in the corresponding embodiments will not be repeated here.

[0300] In one embodiment, the data processing device 1 may further include: a main content traversal module 21, a surrounding content acquisition module 22, and a content summary generation module 23.

[0301] The main content traversal module 21 is used to obtain the query data input by the data query operation and traverse the main content of the target plugin business file based on the query data.

[0302] The surrounding content acquisition module 22 is used to acquire the surrounding content of the query data in the main content if the main content contains the query data; in the main content, the data interval distance between the surrounding content and the query data is less than or equal to the interval distance threshold.

[0303] The content summary generation module 23 is used to generate a main content summary based on the surrounding content and query data.

[0304] The specific implementation methods of the main content traversal module 21, the surrounding content acquisition module 22, and the content summary generation module 23 can be found in the above description. Figure 3 The description of step S101 in the corresponding embodiment will not be repeated here.

[0305] In one embodiment, the traversal module 17 may further include: a similar file determination unit 173 and a prompt information display unit 174.

[0306] If the terminal database does not contain a set of associated plugin business files related to the first sub-object, the similar file determination unit 173 retrieves the similar plugin business files related to the first sub-object from the terminal database based on the query data.

[0307] The prompt information display unit 174 is used to generate similar plugin media data based on similar plugin business files, display the similar plugin media data in the first application, and provide a detailed viewing prompt for the similar plugin media data; the detailed viewing prompt is used to instruct the first sub-object to view the full file details of the similar plugin business files through the similar plugin media data.

[0308] The specific implementation methods of the similar file determination unit 173 and the prompt information display unit 174 can be found in the above description. Figure 5 The descriptions of steps S301-S302 in the corresponding embodiments will not be repeated here.

[0309] In one embodiment, the similar file determination unit 173 is further specifically used to obtain the plug-in service file in the terminal database, and the file content contained in the plug-in service file.

[0310] The similar file determination unit 173 is further specifically used to determine the plugin business file as a similar plugin business file associated with the first sub-object if the file content contained in the plugin business file contains similar data that has a similar relationship with the query data.

[0311] In this application embodiment, during the query service of the application, when a sub-object (such as the first sub-object) inputs query data in the application to query the plugin service file related to the query data, this application can determine the target plugin service file in the terminal database or network server based on the query data, and generate target plugin media data based on the target plugin service file. Subsequently, when the target plugin media data is displayed in the application, a summary of the main content of the target plugin service file can be displayed simultaneously. By synchronously displaying the summary of the main content, the specific content contained in the target plugin service file can be clearly reflected, which can greatly enrich the presentation form of the plugin media data and optimize its display effect. Furthermore, when the main content of the target plugin business file contains query data, the main content summary displayed in this application is determined based on the query data within the main content. In other words, the presented main content summary dynamically changes based on the position of the query data within the main content. When displaying the main content summary, the query data within it can be highlighted simultaneously. This not only enriches the presentation format but also allows for quick location of the query data within the target plugin business file through the highlighted query data, improving query efficiency. In summary, this application can enrich the presentation format of query results (such as target plugin media data) and optimize their display effect in the application's query business.

[0312] Further, please see Figure 16 , Figure 16 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Figure 16 As shown above, Figure 15 The device 1 in the corresponding embodiment can be applied to the aforementioned computer device 8000. The computer device 8000 may include a processor 8001, a network interface 8004, and a memory 8005. Furthermore, the computer device 8000 also includes a user interface 8003 and at least one communication bus 8002. The communication bus 8002 is used to enable communication between these components. The user interface 8003 may include a display screen and a keyboard; optionally, the user interface 8003 may also include a standard wired interface or a wireless interface. The network interface 8004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 8005 may be high-speed RAM or non-volatile memory, such as at least one disk storage device. Optionally, the memory 8005 may also be at least one storage device located remotely from the aforementioned processor 8001. Figure 16As shown, the memory 8005, which is a computer-readable storage medium, may include an operating system, a network communication module, a user interface module, and a device control application program.

[0313] exist Figure 16 In the computer device 8000 shown, the network interface 8004 provides network communication functionality; the user interface 8003 is mainly used to provide an input interface for the user; and the processor 8001 can be used to call the device control application program stored in the memory 8005 to achieve:

[0314] In the first application, a data query operation targeting the first sub-object is responded to, and the target plugin media data is displayed in the first application. The target plugin media data is generated based on the target plugin business files associated with the first sub-object. The target plugin business files are obtained by requesting the network server through the plugin query interface when the terminal database is traversed through the plugin query interface and no set of associated plugin business files that meet the file display requirements is found in the terminal database. The file display requirements refer to the display requirements indicated by the plugin data display area. The plugin data display area refers to the area in the first application used to display the target plugin media data. The terminal database refers to the database corresponding to the second application. The plugin query interface is provided by the second application. The network server refers to the server that provides query services for the second application. The first application is different from the second application. The target plugin media data includes a summary of the main content of the target plugin business file. If the main content of the target plugin business file contains the query data input by the data query operation, then the summary of the main content is obtained by filtering the main content based on the query data, and the summary of the main content includes the query data.

[0315] Highlight the query data contained in the target plugin's media data.

[0316] It should be understood that the computer device 8000 described in the embodiments of this application can execute the foregoing text. Figures 3 to 12 The description of the data processing method in the corresponding embodiment can also be performed as described above. Figure 15 The description of the data processing apparatus 1 in the corresponding embodiments will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated here.

[0317] Furthermore, it should be noted that this application embodiment also provides a computer-readable storage medium, which stores a computer program executed by the aforementioned data processing computer device 1000. The computer program includes program instructions, and when the processor executes the program instructions, it can execute the aforementioned... Figures 3 to 12The description of the data processing method in the corresponding embodiments is already provided and will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the computer-readable storage medium embodiments related to this application, please refer to the description of the method embodiments of this application.

[0318] The aforementioned computer-readable storage medium can be an internal storage unit of the data processing apparatus or computer device provided in any of the foregoing embodiments, such as a hard disk or memory of the computer device. The computer-readable storage medium can also be an external storage device of the computer device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., provided on the computer device. Furthermore, the computer-readable storage medium can include both internal and external storage units of the computer device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0319] One aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the method provided in one aspect of the embodiments of this application.

[0320] The terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the term "comprising," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or device that includes a series of steps or units is not limited to the listed steps or modules, but may optionally include steps or modules not listed, or may optionally include other step units inherent to these processes, methods, apparatuses, products, or devices.

[0321] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0322] The methods and related apparatuses provided in this application are described with reference to the method flowcharts and / or structural diagrams provided in this application. Specifically, each block of the method flowchart and / or structural diagram, as well as combinations of blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to create a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing device, generate instructions for implementing the process. Figure 1 A schematic diagram of one or more processes and / or structures. Figure 1 The computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 A schematic diagram of one or more processes and / or structures. Figure 1 The functions specified in one or more boxes. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable apparatus for implementing the process. Figure 1 A process or multiple processes and / or structures illustrate the steps of the functions specified in one or more boxes.

[0323] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application.

Claims

1. A data processing method, characterized in that, include: In the first application, respond to a data query operation for the first sub-object and display the target plugin media data in the first application; The target plugin media data is generated based on the target plugin business file associated with the first sub-object; the target plugin business file is obtained by requesting the network server through the plugin query interface when the terminal database is traversed through the plugin query interface and no set of associated plugin business files that meet the file display quantity is found in the terminal database; the file display quantity refers to the display quantity indicated by the plugin data display area; the plugin data display area refers to the area in the first application used to display the target plugin media data; the terminal database refers to the database corresponding to the second application; the plugin query interface is provided by the second application; the network server refers to the server that provides query services for the second application; the first application is different from the second application; the target plugin media data includes a summary of the main content in the target plugin business file; if the main content in the target plugin business file contains the query data input by the data query operation, then the summary of the main content is obtained by filtering the main content based on the query data, and the summary of the main content includes the query data; The query data contained in the target plugin media data is highlighted.

2. The method according to claim 1, characterized in that, The target plugin media data displayed in the first application consists of the object information of the second sub-object, the title content of the target plugin business file, and the main content summary; the second sub-object refers to the object that performs plugin business through the target plugin business file and the first sub-object.

3. The method according to claim 1, characterized in that, The step of responding to a data query operation for a first sub-object in the first application and displaying the target plugin media data in the first application includes: In the first application, respond to a data query operation targeting the first sub-object and display a comprehensive query interface in the first application; The plugin data display area is displayed in the comprehensive query interface, and the target plugin media data is displayed in the plugin data display area.

4. The method according to claim 1, characterized in that, The target plugin media data is displayed in the plugin data display area of ​​the first application; The method further includes: In response to an extended query operation targeting the plugin data display area, an extended query interface containing one or more plugin media data is displayed; the one or more plugin media data are associated with the first sub-object, and the one or more plugin media data contain the target plugin media data.

5. The method according to claim 4, characterized in that, The extended query interface includes auxiliary filtering function controls; The method further includes: In response to a trigger operation on the auxiliary filtering function control, a portion of the plug-in media data indicated by the auxiliary filtering function control is obtained from the one or more plug-in media data; the filtering dimension content of the portion of the plug-in media data includes the query data, and the filtering dimension content refers to the content corresponding to the target business dimension in the portion of the plug-in media data, and the target business dimension is the dimension indicated by the auxiliary filtering function control; The extended query interface displays the media data of the aforementioned plug-in.

6. The method according to claim 1, characterized in that, The method further includes: In response to a triggered operation on the target plugin media data, a file details display interface is shown. The file details display interface shows the full file details of the target plugin business file.

7. The method according to claim 4, characterized in that, The response to the extended query operation in the plugin data display area displays an extended query interface containing one or more plugin media data, including: In response to an extended query operation targeting the plugin data display area, the plugin query interface is invoked; the plugin query interface is provided by the second application. The query results interface of the second application is retrieved through the plugin query interface; the query results interface includes one or more plugin media data provided by the second application; The query results interface is designated as the extended query interface, and the extended query interface is displayed.

8. The method according to claim 1, characterized in that, The step of responding to a data query operation for a first sub-object in the first application and displaying the target plugin media data in the first application includes: In the first application, respond to data query operations targeting the first sub-object and display a comprehensive query interface including a plugin file viewing control in the first application; In response to a trigger operation on the plugin file viewing control, the plugin data display interface is displayed; The target plugin media data is displayed in the plugin data display interface.

9. The method according to claim 8, characterized in that, The method further includes: In response to a trigger operation on the target plugin media data, a plugin data preview area is displayed on the plugin data display interface; The file preview information of the target plugin business file is displayed in the plugin data preview area; the file preview information of the target plugin business file is a portion of the full file details information of the target plugin business file; the amount of file information in the file preview information is greater than the amount of file information in the target plugin media data.

10. The method according to claim 9, characterized in that, The plugin data preview area also includes a file details viewing control; The method further includes: In response to a trigger operation on the file details viewing control, the file details display interface is displayed; The file details display interface shows the full file details of the target plugin business file.

11. The method according to claim 8, characterized in that, The plugin data display interface also includes auxiliary filtering controls; the number of target plugin media data is at least two. The method further includes: In response to a trigger operation on the auxiliary filtering function control, the filtering dimensions and the corresponding input boxes for the filtering dimensions are displayed; In response to an input operation to the input box, the system retrieves target plugin media data containing dimension query data from at least two target plugin media data sets, and uses this as dimension plugin media data; the dimension query data refers to the data associated with the filtering dimension input in the input operation. The media data of at least two target plugins in the plugin data display interface will be updated and displayed as the media data of the dimension plugin.

12. The method according to claim 3, characterized in that, The method further includes: Obtain the number of files displayed as indicated by the plugin data display area, and call the plugin query interface based on the number of files displayed; The terminal database is traversed through the plugin query interface; the terminal database refers to the database corresponding to the second application. If the terminal database contains a set of associated plugin service files related to the first sub-object, then the target plugin service file is determined based on the number of files displayed and the set of associated plugin service files. The target plugin media data is generated based on the target plugin service file, and the step of displaying the target plugin media data in the plugin data display area is executed.

13. The method according to claim 12, characterized in that, The step of traversing the terminal database through the plugin query interface includes: The plugin query interface is used to iterate through the object information, title content, and main content of the second sub-object contained in the plugin business file in the terminal database; the second sub-object refers to the object that performs plugin business with the first sub-object through the plugin business file in the terminal database. If the file traversal content contains the query data, then the plugin business file is determined as an associated plugin business file related to the first sub-object, and the associated plugin business file set is formed according to the associated plugin business file; the file traversal content refers to at least one of the object information, the title content, and the main content.

14. The method according to claim 12, characterized in that, The step of determining the target plugin business file based on the number of files displayed and the set of associated plugin business files includes: Obtain the total number of associated plugin business files in the associated plugin business file set; If the total number is greater than or equal to the number of files displayed, then the set of associated plugin service files is determined to meet the number of files displayed. Based on the number of files displayed and the file transfer time corresponding to each associated plugin service file in the set of associated plugin service files, the target plugin service file is obtained from the set of associated plugin service files. If the total number is less than the number of files displayed, it is determined that the set of associated plugin business files does not meet the number of files displayed. A first data query request containing the query data and the number of files displayed is generated through the plugin query interface. The first data query request is sent to the network server. One or more first network plugin business files returned by the network server based on the query data and the number of files displayed are identified as the target plugin business files. The total number of files in the one or more first network plugin business files is the same as the number of files displayed. The one or more first network plugin business files include the set of associated plugin business files. The one or more first network plugin business files are plugin business files associated with the first sub-object that the network server retrieves from the network database based on the query data. The network database refers to the database corresponding to the network server.

15. The method according to claim 14, characterized in that, The step of obtaining the target plugin service file from the associated plugin service file set based on the number of files displayed and the file transfer time corresponding to each associated plugin service file in the associated plugin service file set includes: According to the file transfer time corresponding to each associated plugin service file, the associated plugin service files in the associated plugin service file set are sorted to obtain the plugin file sequence; K associated plugin business files are sequentially obtained from the plugin file sequence, and the K plugin business files are determined as the target plugin business files; K is equal to the number of files displayed.

16. The method according to claim 4, characterized in that, The response to the extended query operation in the plugin data display area displays an extended query interface containing one or more plugin media data, including: In response to an extended query operation targeting the plugin data display area, the plugin query interface is invoked, and the terminal database is traversed through the plugin query interface. If a terminal plugin service file associated with the first sub-object exists in the terminal database, then terminal plugin media data is generated based on the terminal plugin service file. The terminal plugin media data and the target plugin media data are combined to form one or more plugin media data sets, and an extended query interface containing the one or more plugin media data sets is displayed. The terminal plugin service file does not contain the target plugin service file. If no terminal plugin service file associated with the first sub-object exists in the terminal database, a second data query request containing the query data is generated through the plugin query interface, and the second data query request is sent to the network server. Based on the feedback data returned by the network server based on the query data, the one or more plugin media data are determined, and an extended query interface containing the one or more plugin media data is displayed.

17. The method according to claim 16, characterized in that, The step of determining the one or more plug-in media data based on the feedback data returned by the network server based on the query data includes: If the feedback data includes a second network plug-in service file, then network plug-in media data is generated based on the second network plug-in service file, and the network plug-in media data and the target plug-in media data are identified as one or more plug-in media data; the second network plug-in service file is a plug-in service file that the network server retrieves from the network database based on the query data; the network database refers to the database corresponding to the network server; the second network plug-in service file does not contain the target plug-in service file; If the feedback data does not include the second network plug-in service file, then the target plug-in media data is determined to be one or more plug-in media data.

18. The method according to claim 17, characterized in that, The method further includes: When the feedback data includes the second network plug-in service file, the terminal database is updated based on the second network plug-in service file to obtain an updated terminal database; the updated database includes the second network plug-in service file.

19. The method according to claim 1, characterized in that, The method further includes: Obtain the query data input in the data query operation, and traverse the main content of the target plugin business file based on the query data; If the main content contains the query data, then the surrounding content of the query data is obtained in the main content; in the main content, the data interval distance between the surrounding content and the query data is less than or equal to the interval distance threshold. The main content summary is generated based on the surrounding content and the query data.

20. The method according to claim 12, characterized in that, The method further includes: If there is no set of associated plugin business files related to the first sub-object in the terminal database, then based on the query data, obtain similar plugin business files related to the first sub-object in the terminal database. Similar plugin media data is generated based on the similar plugin business files, and the similar plugin media data is displayed in the first application, along with a details viewing prompt for the similar plugin media data; the details viewing prompt is used to instruct the first sub-object to view the full file details of the similar plugin business files through the similar plugin media data.

21. The method according to claim 20, characterized in that, The step of retrieving similar plugin business files associated with the first sub-object from the terminal database based on the query data includes: Obtain the plugin service files in the terminal database, as well as the file content contained in the plugin service files; If the file content contained in the plugin business file contains similar data that has a similar relationship with the query data, then the plugin business file is determined to be a similar plugin business file associated with the first sub-object.

22. A data processing apparatus, characterized in that, include: The media data display module is used to respond to data query operations for the first sub-object in the first application and display the target plugin media data in the first application. The target plugin media data is generated based on the target plugin business file associated with the first sub-object; the target plugin business file is obtained by requesting the network server through the plugin query interface when the terminal database is traversed through the plugin query interface and no set of associated plugin business files that meet the file display quantity is found in the terminal database; the file display quantity refers to the display quantity indicated by the plugin data display area; the plugin data display area refers to the area in the first application used to display the target plugin media data; the terminal database refers to the database corresponding to the second application; the plugin query interface is provided by the second application; the network server refers to the server that provides query services for the second application; the first application is different from the second application; the target plugin media data includes a summary of the main content in the target plugin business file; if the main content in the target plugin business file contains the query data input by the data query operation, then the summary of the main content is obtained by filtering the main content based on the query data, and the summary of the main content includes the query data; The highlighting module is used to highlight the query data contained in the target plugin media data.

23. A computer device, characterized in that, include: Processor, memory, and network interface; The processor is connected to the memory and the network interface, wherein the network interface is used to provide network communication functions, the memory is used to store program code, and the processor is used to call the program code to cause the computer device to execute the method according to any one of claims 1-21.

24. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program adapted to be loaded by a processor and to execute the method of any one of claims 1-21.

25. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium, the computer instructions being adapted to be read and executed by a processor to cause a computer device having the processor to perform the method of any one of claims 1-21.

Images