A data processing method and device

Abstract

The present application discloses a data processing method, which includes: obtaining a search statement input by a user, determining an entity keyword and a target demand keyword according to the search statement; obtaining a knowledge aggregation search result item corresponding to the entity keyword, and displaying it in a search result page corresponding to the search statement; including: displaying the content corresponding to the first search result in the first display area of ​​the knowledge aggregation search result item; the first search result is a search result obtained based on the entity keyword and the target demand keyword; displaying the content corresponding to at least one second search result in the second display area of ​​the knowledge aggregation search result item; the second search result is a search result obtained based on the entity keyword and a non-target demand keyword; the non-target demand keyword is a demand keyword that is related to the entity type of the entity keyword and does not match the target demand keyword. By using this solution, the search needs of users can be better met.

Description

Technical Field

[0001] The present application relates to the field of data processing, and in particular to a data processing method and device. Background Art

[0002] When users have questions, they can search for answers through search engines. However, the search results provided by current search engines often cannot meet user needs.

[0003] Therefore, a solution is urgently needed to solve the above problems. Summary of the invention

[0004] The technical problem to be solved by this application is that the search results provided by current search engines cannot meet the needs of users, and a data processing method and device are provided.

[0005] In a first aspect, an embodiment of the present application provides a data processing method, the method comprising:

[0006] Obtaining a search statement input by a user, and determining entity keywords and target demand keywords according to the search statement;

[0007] Obtaining the knowledge aggregation search result item corresponding to the entity keyword and displaying it in the search result page corresponding to the search statement; including:

[0008] Displaying content corresponding to a first search result in a first display area of ​​the knowledge aggregation search result item; the first search result is a search result obtained based on the entity keyword and the target demand keyword;

[0009] Content corresponding to at least one second search result is displayed in the second display area of ​​the knowledge aggregation search result item; the second search result is a search result obtained based on the entity keyword and non-target demand keyword; the non-target demand keyword is a demand keyword that is related to the entity type of the entity keyword and does not match the target demand keyword.

[0010] Optionally, the step of obtaining the knowledge aggregation search result item corresponding to the entity keyword and displaying it in the search result page corresponding to the search statement further includes:

[0011] Obtaining at least one demand keyword corresponding to the entity category to which the entity keyword belongs;

[0012] Obtain search results corresponding to the entity keyword and each demand keyword respectively;

[0013] The content corresponding to the search result corresponding to each demand keyword is displayed in the knowledge aggregation search result item.

[0014] Optionally, each search result corresponding to a demand keyword corresponds to a knowledge module;

[0015] If the target demand keyword hits the demand keyword corresponding to the first knowledge module, the first search result is obtained according to the content of the first knowledge module.

[0016] Optionally, the demand keywords that do not match the target demand keywords include:

[0017] Demand keywords different from the target demand keywords; and / or,

[0018] Demand keywords that belong to different dimensions from the target demand keywords.

[0019] Optionally, content corresponding to the first search result included in the first display area is displayed preferentially.

[0020] In a second aspect, an embodiment of the present application provides a data processing device, the device comprising:

[0021] A first acquisition unit, used to acquire a search statement input by a user;

[0022] A determination unit, configured to determine entity keywords and target demand keywords according to the search statement;

[0023] A second acquisition unit is used to acquire the knowledge aggregation search result item corresponding to the entity keyword;

[0024] A display unit, used to display the knowledge aggregation search result item in the search result page corresponding to the search statement; comprising:

[0025] Displaying content corresponding to a first search result in a first display area of ​​the knowledge aggregation search result item; the first search result is a search result obtained based on the entity keyword and the target demand keyword;

[0026] Content corresponding to at least one second search result is displayed in the second display area of ​​the knowledge aggregation search result item; the second search result is a search result obtained based on the entity keyword and non-target demand keyword; the non-target demand keyword is a demand keyword that is related to the entity type of the entity keyword and does not match the target demand keyword.

[0027] Optionally, the second acquiring unit is further used for:

[0028] Obtain a demand keyword corresponding to an entity category to which at least one of the entity keywords belongs; obtain search results corresponding to the entity keyword and each demand keyword respectively;

[0029] The display unit is further used to display the content corresponding to the search result corresponding to each demand keyword in the knowledge aggregation search result item.

[0030] Optionally, each search result corresponding to a demand keyword corresponds to a knowledge module;

[0031] If the target demand keyword hits the demand keyword corresponding to the first knowledge module, the first search result is obtained according to the content of the first knowledge module.

[0032] Optionally, the demand keywords that do not match the target demand keywords include:

[0033] Demand keywords different from the target demand keywords; and / or,

[0034] Demand keywords that belong to different dimensions from the target demand keywords.

[0035] Optionally, content corresponding to the first search result included in the first display area is displayed preferentially.

[0036] In a third aspect, an embodiment of the present application provides a data processing device, comprising a memory and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by one or more processors, wherein the one or more programs include instructions for performing the following operations:

[0037] Obtaining a search statement input by a user, and determining entity keywords and target demand keywords according to the search statement;

[0038] Obtaining the knowledge aggregation search result item corresponding to the entity keyword and displaying it in the search result page corresponding to the search statement; including:

[0039] Displaying content corresponding to a first search result in a first display area of ​​the knowledge aggregation search result item; the first search result is a search result obtained based on the entity keyword and the target demand keyword;

[0040] Content corresponding to at least one second search result is displayed in the second display area of ​​the knowledge aggregation search result item; the second search result is a search result obtained based on the entity keyword and non-target demand keyword; the non-target demand keyword is a demand keyword that is related to the entity type of the entity keyword and does not match the target demand keyword.

[0041] Optionally, the step of obtaining the knowledge aggregation search result item corresponding to the entity keyword and displaying it in the search result page corresponding to the search statement further includes:

[0042] Obtaining at least one demand keyword corresponding to the entity category to which the entity keyword belongs;

[0043] Obtain search results corresponding to the entity keyword and each demand keyword respectively;

[0044] The content corresponding to the search result corresponding to each demand keyword is displayed in the knowledge aggregation search result item.

[0045] Optionally, each search result corresponding to a demand keyword corresponds to a knowledge module;

[0046] If the target demand keyword hits the demand keyword corresponding to the first knowledge module, the first search result is obtained according to the content of the first knowledge module.

[0047] Optionally, the demand keywords that do not match the target demand keywords include:

[0048] Demand keywords different from the target demand keywords; and / or,

[0049] Demand keywords that belong to different dimensions from the target demand keywords.

[0050] Optionally, content corresponding to the first search result included in the first display area is displayed preferentially.

[0051] In a fourth aspect, an embodiment of the present application provides a computer-readable medium having instructions stored thereon, which, when executed by one or more processors, enables the device to execute any of the methods described in the first aspect above.

[0052] Compared with the prior art, the embodiments of the present application have the following advantages:

[0053] An embodiment of the present application provides a data processing method, which can be executed by a device running a search engine. Specifically: after the user enters a search statement, the device can determine the entity keyword and the target demand keyword based on the search statement. Then, the device can obtain the knowledge aggregation search result item corresponding to the entity keyword, and display it in the search result page corresponding to the search statement. Specifically: the first search result is displayed in the first display area of ​​the knowledge aggregation search result item, and the content corresponding to at least one second search result is displayed in the second display area of ​​the knowledge aggregation search result item. Among them: the first search result is a search result obtained based on the entity keyword and the target demand keyword, and the second search result is a search result obtained based on the entity keyword and the non-target demand keyword; the non-target demand keyword is a demand keyword that is related to the entity type of the entity keyword and does not match the target demand keyword.

[0054] It can be seen that, by using this solution, the second search result and the first search result corresponding to the search statement can be displayed in the knowledge aggregation search result item corresponding to the search result page corresponding to the entity keyword, so that the user can directly view the first search result corresponding to the target demand keyword in the knowledge aggregation search result item of the search result page, and can view other knowledge aggregation search results in the knowledge aggregation search result item, thereby better meeting the user's search needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0056] Figure 1 A flowchart of a data processing method provided in an embodiment of the present application;

[0057] Figure 2 A schematic diagram of the structure of a data processing device provided in an embodiment of the present application;

[0058] Figure 3 A schematic diagram of the structure of the client provided in the embodiment of the present application;

[0059] Figure 4 A schematic diagram of the structure of a server provided in an embodiment of the present application. DETAILED DESCRIPTION

[0060] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0061] The inventor of the present application has found through research that, currently, when a user has questions, he can enter a search statement in the search input area of ​​the search engine to obtain the content he wants to obtain. In one example, if the user enters a search statement related to an entity keyword, the search engine can provide the user with a knowledge aggregation search result item corresponding to the entity keyword.

[0062] In actual applications, the content corresponding to the overview knowledge module is generally displayed in the knowledge aggregation search result item. In the overview knowledge module of the knowledge aggregation search result item, the content displayed in each display area is generally relatively fixed. For example, for disease entity keywords, the content displayed in the overview knowledge module is generally displayed in the order from top to bottom of the display area: common symptoms of patients, consultation departments, commonness, common classifications, and complications, etc. Therefore, the content in the overview knowledge module may not meet the search requirements corresponding to the search statement.

[0063] For example:

[0064] The user enters "drug treatment for upper respiratory tract infection" in the search input area of ​​the search engine, and an overview knowledge module is displayed to the user in the knowledge aggregation search result item, and the corresponding content may include: common symptoms of patients, consultation departments, commonness, common classifications and complications, etc.

[0065] In order to solve the above problems, an embodiment of the present application provides a data processing method. Various non-limiting implementation methods of the present application are described in detail below in conjunction with the accompanying drawings.

[0066] Exemplary Methods

[0067] See also Figure 1 , which is a flow chart of a data processing method provided in an embodiment of the present application.

[0068] The method provided in the embodiment of the present application can be executed by a device running a search engine, for example. The devices mentioned here include but are not limited to terminal devices and servers. The terminal devices mentioned here can be mobile terminals such as smart phones and tablet computers, or terminal devices such as desktop computers.

[0069] Figure 1 The method shown can be implemented, for example, through the following S101-S102.

[0070] S101: Obtain a search statement input by a user, and determine entity keywords and target demand keywords according to the search statement.

[0071] The search sentence mentioned in the embodiments of the present application may be a sentence entered by a user in the search input area of ​​a search engine.

[0072] The entity keyword in the embodiment of the present application may correspond to an entity object of a certain category. The entity keyword may be, for example, the name of an entity object of a certain category. In one example, the entity keyword may belong to a disease keyword. In other words, the entity type corresponding to the entity keyword is a disease class. In this case, the entity keyword may be, for example, the name of a disease. For example, the entity keyword may be "upper respiratory tract infection"; for another example, the entity keyword may be "hypertension".

[0073] The target demand keywords in the embodiments of the present application are used to indicate search requirements. It can be understood that the entity keywords and target demand keywords determined according to the search statement can be used to characterize the content of the dimension indicated by the entity keyword indicated by the target demand keyword that the user wants to know. For example, if the entity keyword is "upper respiratory tract infection" and the target demand keyword is "symptoms", it can indicate that the user wants to know the symptoms of upper respiratory tract infection.

[0074] In an embodiment of the present application, after the device running the search engine obtains the search statement, the search statement can be analyzed to obtain the entity keyword and the target demand keyword. For example, if the search statement is "What are the symptoms of upper respiratory tract infection", the entity keyword can be determined to be "upper respiratory tract infection" and the target demand keyword can be determined to be "symptoms". For another example, if the search statement is "What to do with upper respiratory tract infection", the entity keyword can be determined to be "upper respiratory tract infection" and the target demand keyword can be determined to be "treatment".

[0075] S102: Obtain the knowledge aggregation search result item corresponding to the entity keyword, and display it in the search result page corresponding to the search statement, wherein: the content corresponding to the first search result is displayed in the first display area of ​​the knowledge aggregation search result item, and the content corresponding to at least one second search result is displayed in the second display area of ​​the knowledge aggregation search item.

[0076] It should be noted that the knowledge aggregation search result item corresponding to the entity keyword is used to display the aggregation item of knowledge search results related to the entity keyword, for example, it can be the aggregation item of encyclopedia search results.

[0077] In an embodiment of the present application, unlike traditional technologies, in traditional technologies, in the search results page, the content displayed in each display area of ​​the knowledge aggregation search result item corresponding to a certain category of entity keywords is relatively fixed. For example, for disease-related entity keywords, the content displayed in its knowledge aggregation search result item is displayed in the order from top to bottom of the display area: common symptoms of patients, treatment departments, commonness, common classifications, and complications. In an embodiment of the present application, the knowledge aggregation search result item may include a dynamic display area, and the content displayed in the dynamic display area will change dynamically according to the user's search needs included in the search statement. Specifically, the content displayed in the dynamic display area is related to the entity keyword, and the specific display content is determined according to the target demand keywords determined by the search statement.

[0078] Specifically: the dynamic display area includes a first display area, and the first display area is used to display the content corresponding to the first search result. Wherein: the first search result is a search result obtained based on the entity keyword and the target demand keyword. In an embodiment of the present application, the entity keyword and the target demand keyword can be used as search conditions to obtain the first search result.

[0079] For example, the entity keyword is "upper respiratory tract infection" and the target demand keyword is "symptoms", then the first search result may be content related to the symptoms of upper respiratory tract infection.

[0080] In addition, although the user most likely wants to obtain the search results corresponding to the target demand keyword determined according to the search statement, the user may actually have other search needs, or the search results that can meet other search needs can be actively provided to the user. For example, the user also wants to understand the content of the entity keyword in the dimension indicated by the non-target demand keyword.

[0081] In view of this, in an embodiment of the present application, the dynamic display area may further include a second display area, and the second display area is used to display content corresponding to at least one second search result. Wherein: the second search result is a search result obtained based on the entity keyword and the non-target demand keyword. The non-target demand keyword is a demand keyword that is related to the entity type of the entity keyword and does not match the target demand keyword.

[0082] It should be noted that the demand keywords mentioned here that do not match the target demand keywords may be demand keywords different from the target demand keywords, or may be demand keywords belonging to different dimensions from the target demand keywords. If the first demand keyword and the second demand keyword belong to the same dimension, for example, both belong to the "treatment" dimension, even though the first demand keyword and the second demand keyword correspond to different demand granularities, the first demand keyword and the second demand keyword are considered to match. For example, the first demand keyword "treatment" matches the second demand keyword "drug treatment".

[0083] Regarding the target demand keywords and non-target demand keywords, examples are now given. For example, for the disease entity keyword "upper respiratory tract infection", if the target demand keyword is "symptoms", the non-target demand keywords can be: "cause", "treatment", "department" and one or more of them, these non-target demand keywords are also related to the entity keyword "upper respiratory tract infection", and these non-target demand keywords do not match the target demand keyword "symptoms". Another example: if the target demand keyword is "drug treatment", the non-target demand keywords can be: "cause", "symptoms", "department" and one or more of them, these non-target demand keywords are also related to the entity keyword "upper respiratory tract infection", and these non-target demand keywords do not include the demand keyword "treatment" that matches the target demand keyword "drug treatment".

[0084] In one example, when multiple non-target demand keywords are included, the second display area can display the second search results corresponding to each of the multiple non-target demand keywords. As an example: the entity keyword and each demand keyword in the multiple non-target demand keywords can be used as search conditions to retrieve the second search results corresponding to each non-target demand keyword. For example:

[0085] The entity keyword is: "upper respiratory tract infection", and the non-target demand keywords may include "cause", "treatment" and "department". Then, "upper respiratory tract infection" and "cause" may be used as common search conditions to obtain search result 1; "upper respiratory tract infection" and "treatment" may be used as common search conditions to obtain search result 2; "upper respiratory tract infection" and "department" may be used as common search conditions to obtain search result 3. At this time, three second search results may be included, namely: search result 1, search result 2 and search result 3, and the above three second search results are aggregated in the second display area.

[0086] In an embodiment of the present application, considering that the first search result is the search result corresponding to the search statement input by the user, in order to give priority to satisfying the search requirements corresponding to the search statement, in an embodiment of the present application: on the one hand, when displaying the content corresponding to the first search result and the content corresponding to the second search result, the content corresponding to the first search result can be displayed preferentially. For example, the first display area can be located above the second display area so that the user can view the content corresponding to the first search result preferentially. On the other hand, the content corresponding to the first search result can be controlled to be more detailed than the content corresponding to the second search result, so that the user can obtain more content corresponding to the search statement. For example, the content corresponding to the first search result includes a paragraph of text description, while the second search result only includes a line of text description.

[0087] In the embodiment of the present application, the non-target demand keyword can be determined based on a pre-set demand keyword.

[0088] In one example, demand keywords related to the entity category to which the entity keyword belongs can be pre-stored, and then, non-target demand keywords related to the entity category to which the entity keyword included in the search statement belongs and that do not match the target demand keyword are selected from the pre-stored demand keywords. For example, demand keywords corresponding to disease-related entity keywords can be pre-stored, such as: "symptoms", "cause", "department" and "treatment". Then, when it is determined that the entity keyword included in the search statement belongs to the disease-related keyword, it is determined that the corresponding demand keywords can include "symptoms", "cause", "department" and "treatment"; further, if the target demand keyword is determined to be "symptoms" based on the search statement, the non-target demand keyword can be determined to be several of "cause", "department" and "treatment". The demand keywords related to the entity category mentioned here can be determined manually based on experience, or can be mined based on historical related search data.

[0089] In another example, considering the historical search records of network users, the user's search needs can be reflected to a certain extent. Therefore, in one example, the demand keywords corresponding to the entity category to which the entity keyword belongs can be determined based on the historical search records of the network user. Then, all or part of the demand keywords that do not match the target demand keywords in the demand keywords corresponding to the entity keywords are determined as the non-target demand keywords. For this case, in an embodiment of the present application, before executing S102, the non-target demand keywords can also be determined based on the historical search records of the network user.

[0090] The historical search records of network users mentioned here may include search statements entered by network users in the search input area of ​​the search engine, and may also include search results that network users have clicked on in the past. For example, the historical search statements entered by network users in the search input area include: "What is the treatment department for upper respiratory tract infection?", "What are the symptoms of upper respiratory tract infection?", "How to use drugs to treat upper respiratory tract infection?", and the network user clicks on the search result of "Causes of upper respiratory tract infection", then it can be determined that the demand keywords corresponding to the entity keyword "upper respiratory tract infection" may include: "symptoms", "drug treatment", "department" and "cause".

[0091] In the conventional scheme, for the knowledge aggregation search result items corresponding to the entity keywords included in the search statement, the content displayed in each display area is generally relatively fixed. For example, for disease entity keywords, the content displayed in its knowledge aggregation search result items is generally displayed in the order from top to bottom of the display area: common symptoms of patients, medical departments, commonness, common classifications and complications, etc. Specifically, in the conventional scheme, whether the user searches for "symptoms of upper respiratory tract infection" or "how to treat upper respiratory tract infection", the knowledge aggregation search result items corresponding to the entity keyword "upper respiratory tract infection" included therein are displayed in the preset order: common symptoms of patients, medical departments, commonness, common classifications and complications, etc.

[0092] In this solution, for the knowledge aggregation search result items corresponding to the entity keywords included in the search statement, the content displayed in the first display area and the second display area can dynamically change according to the target search requirements included in the current search statement, and the display method is flexible.

[0093] For example, when the search statement is "symptoms of upper respiratory tract infection", in the knowledge aggregation search result item corresponding to the entity keyword "upper respiratory tract infection", the first display area can display content related to "upper respiratory tract infection + symptoms", and the second display area can display content related to "upper respiratory tract infection + treatment department", "upper respiratory tract infection + cause" and "upper respiratory tract infection + treatment" respectively.

[0094] For another example, when the search statement is "how to treat upper respiratory tract infection", in the knowledge aggregation search result item corresponding to the entity keyword "upper respiratory tract infection", the first display area can display content related to "upper respiratory tract infection + treatment", and the second display area can display content related to "upper respiratory tract infection + treatment department", "upper respiratory tract infection + cause" and "upper respiratory tract infection + symptoms".

[0095] For another example, when the search statement is "How to treat upper respiratory tract infection with drugs", in the knowledge aggregation search result item corresponding to the entity keyword "upper respiratory tract infection", the first display area can display content related to "upper respiratory tract infection + drug treatment", and the second display area can display content related to "upper respiratory tract infection + medical department", "upper respiratory tract infection + cause" and "upper respiratory tract infection + symptoms".

[0096] It is understandable that for the content displayed on the web page, the R&D personnel can implement it through Extensible Markup Language (xml) during the research and development. When implemented through xml, it is necessary to describe the display content of each area in the web page. Once the content displayed in the web page is modified, the software program corresponding to the entire web page needs to be modified. Therefore, for the scenario in which the display content in the first display area and the second display area changes dynamically, the research and development cost is very high. In order to solve this problem, in an embodiment of the present application, the data that needs to be displayed on the web page can be obtained through the Application Programming Interface (API) interface, so that the content to be displayed can be dynamically displayed on the encyclopedia overview page, thereby reducing the research and development cost. The API interface is not described in detail here.

[0097] It should be noted that the content included in the knowledge aggregation search result item corresponding to the entity keyword, in addition to the content corresponding to the first search result and the content corresponding to the second search result, can also include search results corresponding to the entity keyword and each of the demand keywords.

[0098] For example: for the entity keyword "upper respiratory tract infection", the corresponding demand keywords may include: "symptoms", "cause", "treatment department" and "treatment". Then the knowledge aggregation search result item corresponding to the entity keyword "upper respiratory tract infection" may also include: search results corresponding to "upper respiratory tract infection + symptoms", "upper respiratory tract infection + cause", "upper respiratory tract infection + treatment department", and "upper respiratory tract infection + treatment". Therefore, in one example, "obtaining the knowledge aggregation search result item corresponding to the entity keyword, and displaying it in the search result page corresponding to the search statement" may also include: obtaining the search results corresponding to each of the entity keywords and each demand keyword; displaying the content corresponding to the search result corresponding to each demand keyword in the knowledge aggregation search result item.

[0099] It should be noted that in the embodiment of the present application, when the "obtaining the search results corresponding to the entity keyword and each of the demand keywords respectively" is implemented in detail, for example, the entity keyword and each of the demand keywords respectively can be used as search conditions to retrieve the search results corresponding to each of the demand keywords respectively.

[0100] In an embodiment of the present application, the search results corresponding to the respective demand keywords can be displayed in the knowledge aggregation search result item in the form of knowledge modules, wherein one demand keyword corresponds to one knowledge module. The user can switch the knowledge module currently displayed in the knowledge aggregation search result item by clicking the identifier (e.g., name) of the knowledge module. For example, it is displayed in the form of tabs, each tab corresponds to a knowledge module, and the label of each tab can be the demand keyword corresponding to the knowledge module.

[0101] As mentioned above, for the entity keyword, its corresponding knowledge aggregation search result item may include multiple knowledge modules. If the target demand keyword hits the first knowledge module of the entity keyword, the aforementioned first search result can be obtained through the content of the first knowledge module. In one example, the content of the first knowledge module can be used as the first search result. In another example, the summary content of the first knowledge module can be used as the first search result. In this case, the user can click on the logo of the first knowledge module to switch the currently displayed knowledge module to the first knowledge module, so as to learn more about the content related to the target demand keyword.

[0102] For example, the search statement entered by the user is "What are the symptoms of upper respiratory tract infection?", that is, the entity keyword is "upper respiratory tract infection" and the target demand keyword is "symptoms". In the search result page obtained, the knowledge aggregation search result item of "upper respiratory tract infection" includes a knowledge module related to "symptoms", so the first search result can be obtained based on the content of the "symptoms" knowledge module.

[0103] In addition, it should be noted that, in addition to the knowledge modules corresponding to each demand keyword, the knowledge aggregation result item also includes an overview knowledge module, which can be used to display the knowledge aggregation search results of the entity keyword and other content not included in the demand knowledge module. The aforementioned first display area and second display area can be the display areas in the overview knowledge module. In this solution, when a user triggers a search for a search statement, the overview knowledge module of the knowledge aggregation search result item is preferentially displayed in the search results page.

[0104] From the above description, it can be seen that by utilizing this solution, the first search result and the second search result corresponding to the search statement can be displayed in the knowledge aggregation search result item corresponding to the entity keyword, so that the user can directly view the first search result corresponding to the target demand keyword in the knowledge aggregation search result item on the search results page, and can view other knowledge aggregation search results in the knowledge aggregation search result item, thereby better meeting the user's search needs.

[0105] Exemplary Devices

[0106] Based on the method provided in the above embodiment, the embodiment of the present application further provides a device, which is described below in conjunction with the accompanying drawings.

[0107] See also Figure 2 , which is a schematic diagram of the structure of a data processing device provided in an embodiment of the present application. The device 200 may specifically include: a first acquisition unit 201, a determination unit 202, a second acquisition unit 203 and a display unit 204.

[0108] A first acquisition unit 201 is used to acquire a search statement input by a user;

[0109] A determination unit 202, configured to determine entity keywords and target demand keywords according to the search statement;

[0110] The second acquisition unit 203 is used to acquire the knowledge aggregation search result item corresponding to the entity keyword;

[0111] The display unit 204 is used to display the knowledge aggregation search result item in the search result page corresponding to the search statement; including:

[0112] Displaying content corresponding to a first search result in a first display area of ​​the knowledge aggregation search result item; the first search result is a search result obtained based on the entity keyword and the target demand keyword;

[0113] Content corresponding to at least one second search result is displayed in the second display area of ​​the knowledge aggregation search result item; the second search result is a search result obtained based on the entity keyword and non-target demand keyword; the non-target demand keyword is a demand keyword that is related to the entity type of the entity keyword and does not match the target demand keyword.

[0114] Optionally, the second acquiring unit 203 is further used to:

[0115] Obtain a demand keyword corresponding to an entity category to which at least one of the entity keywords belongs; obtain search results corresponding to the entity keyword and each demand keyword respectively;

[0116] The display unit 204 is further configured to display the content corresponding to the search result corresponding to each demand keyword in the knowledge aggregation search result item.

[0117] Optionally, each search result corresponding to a demand keyword corresponds to a knowledge module;

[0118] If the target demand keyword hits the demand keyword corresponding to the first knowledge module, the first search result is obtained according to the content of the first knowledge module.

[0119] Optionally, the demand keywords that do not match the target demand keywords include:

[0120] Demand keywords different from the target demand keywords; and / or,

[0121] Demand keywords that belong to different dimensions from the target demand keywords.

[0122] Optionally, content corresponding to the first search result included in the first display area is displayed preferentially.

[0123] Since the device 200 is a device corresponding to the method provided in the above method embodiment, the specific implementation of each unit of the device 200 is based on the same concept as the above method embodiment. Therefore, for the specific implementation of each unit of the device 200, reference can be made to the description part of the above method embodiment, which will not be repeated here.

[0124] The method provided in the embodiment of the present application can be executed by a client or a server. The client and server that execute the above method are described below respectively.

[0125] Figure 3 1 shows a block diagram of a client 300. For example, the client 300 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0126] Reference Figure 3 The client 300 may include one or more of the following components: a processing component 302 , a memory 304 , a power component 306 , a multimedia component 308 , an audio component 310 , an input / output (I / O) interface 33 , a sensor component 314 , and a communication component 316 .

[0127] The processing component 302 generally controls the overall operation of the client 300, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 302 may include one or more processors 320 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 302 may include one or more modules to facilitate the interaction between the processing component 302 and other components. For example, the processing component 302 may include a multimedia module to facilitate the interaction between the multimedia component 308 and the processing component 302.

[0128] The memory 304 is configured to store various types of data to support operations on the client 300. Examples of such data include instructions for any application or method operating on the client 300, contact data, phone book data, messages, pictures, videos, etc. The memory 304 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0129] The power supply component 306 provides power to the various components of the client 300. The power supply component 306 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the client 300.

[0130] The multimedia component 308 includes a screen that provides an output interface between the client 300 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 308 includes a front camera and / or a rear camera. When the client 300 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and the rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0131] The audio component 310 is configured to output and / or input audio signals. For example, the audio component 310 includes a microphone (MIC), and when the client 300 is in an operation mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 304 or sent via the communication component 316. In some embodiments, the audio component 310 also includes a speaker for outputting audio signals.

[0132] The I / O interface provides an interface between the processing component 302 and the peripheral interface module, which may be a keyboard, a click wheel, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0133] The sensor assembly 314 includes one or more sensors for providing various aspects of status assessment for the client 300. For example, the sensor assembly 314 can detect the open / closed state of the device 300, the relative positioning of components, such as the display and keypad of the client 300, and the sensor assembly 314 can also detect the position change of the client 300 or a component of the client 300, the presence or absence of user contact with the client 300, the orientation or acceleration / deceleration of the client 300, and the temperature change of the client 300. The sensor assembly 314 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 314 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 314 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0134] The communication component 316 is configured to facilitate wired or wireless communication between the client 300 and other devices. The client 300 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 316 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 316 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0135] In an exemplary embodiment, the client 300 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the following methods:

[0136] Obtaining a search statement input by a user, and determining entity keywords and target demand keywords according to the search statement;

[0137] Obtaining the knowledge aggregation search result item corresponding to the entity keyword and displaying it in the search result page corresponding to the search statement; including:

[0138] Displaying content corresponding to a first search result in a first display area of ​​the knowledge aggregation search result item; the first search result is a search result obtained based on the entity keyword and the target demand keyword;

[0139] Content corresponding to at least one second search result is displayed in the second display area of ​​the knowledge aggregation search result item; the second search result is a search result obtained based on the entity keyword and non-target demand keyword; the non-target demand keyword is a demand keyword that is related to the entity type of the entity keyword and does not match the target demand keyword.

[0140] Optionally, the step of obtaining the knowledge aggregation search result item corresponding to the entity keyword and displaying it in the search result page corresponding to the search statement further includes:

[0141] Obtaining at least one demand keyword corresponding to the entity category to which the entity keyword belongs;

[0142] Obtain search results corresponding to the entity keyword and each demand keyword respectively;

[0143] The content corresponding to the search result corresponding to each demand keyword is displayed in the knowledge aggregation search result item.

[0144] Optionally, each search result corresponding to a demand keyword corresponds to a knowledge module;

[0145] If the target demand keyword hits the demand keyword corresponding to the first knowledge module, the first search result is obtained according to the content of the first knowledge module.

[0146] Optionally, the demand keywords that do not match the target demand keywords include:

[0147] Demand keywords different from the target demand keywords; and / or,

[0148] Demand keywords that belong to different dimensions from the target demand keywords.

[0149] Optionally, content corresponding to the first search result included in the first display area is displayed preferentially.

[0150] Figure 4 4 is a schematic diagram of the structure of the server in the embodiment of the present application. The server 400 may have relatively large differences due to different configurations or performances, and may include one or more central processing units (CPU) 422 (for example, one or more processors) and memory 432, and one or more storage media 430 (for example, one or more mass storage devices) storing application programs 442 or data 444. Among them, the memory 432 and the storage medium 430 can be short-term storage or permanent storage. The program stored in the storage medium 430 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the server. Furthermore, the central processing unit 422 can be configured to communicate with the storage medium 430 to execute a series of instruction operations in the storage medium 430 on the server 400.

[0151] Furthermore, the CPU 422 may execute the following method:

[0152] Obtaining a search statement input by a user, and determining entity keywords and target demand keywords according to the search statement;

[0153] Obtaining the knowledge aggregation search result item corresponding to the entity keyword and displaying it in the search result page corresponding to the search statement; including:

[0154] Displaying content corresponding to a first search result in a first display area of ​​the knowledge aggregation search result item; the first search result is a search result obtained based on the entity keyword and the target demand keyword;

[0155] Content corresponding to at least one second search result is displayed in the second display area of ​​the knowledge aggregation search result item; the second search result is a search result obtained based on the entity keyword and non-target demand keyword; the non-target demand keyword is a demand keyword that is related to the entity type of the entity keyword and does not match the target demand keyword.

[0156] Optionally, the step of obtaining the knowledge aggregation search result item corresponding to the entity keyword and displaying it in the search result page corresponding to the search statement further includes:

[0157] Obtaining at least one demand keyword corresponding to the entity category to which the entity keyword belongs;

[0158] Obtain search results corresponding to the entity keyword and each demand keyword respectively;

[0159] The content corresponding to the search result corresponding to each demand keyword is displayed in the knowledge aggregation search result item.

[0160] Optionally, each search result corresponding to a demand keyword corresponds to a knowledge module;

[0161] If the target demand keyword hits the demand keyword corresponding to the first knowledge module, the first search result is obtained according to the content of the first knowledge module.

[0162] Optionally, the demand keywords that do not match the target demand keywords include:

[0163] Demand keywords different from the target demand keywords; and / or,

[0164] Demand keywords that belong to different dimensions from the target demand keywords.

[0165] Optionally, content corresponding to the first search result included in the first display area is displayed preferentially.

[0166] The server 400 may also include one or more power supplies 426, one or more wired or wireless network interfaces 450, one or more input and output interfaces 456, one or more keyboards 456, and / or one or more operating systems 441, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

[0167] The present application also provides a computer-readable medium having instructions stored thereon, which, when executed by one or more processors, causes the device to perform the following method:

[0168] Obtaining a search statement input by a user, and determining entity keywords and target demand keywords according to the search statement;

[0169] Obtaining the knowledge aggregation search result item corresponding to the entity keyword and displaying it in the search result page corresponding to the search statement; including:

[0170] Displaying content corresponding to a first search result in a first display area of ​​the knowledge aggregation search result item; the first search result is a search result obtained based on the entity keyword and the target demand keyword;

[0171] Content corresponding to at least one second search result is displayed in the second display area of ​​the knowledge aggregation search result item; the second search result is a search result obtained based on the entity keyword and non-target demand keyword; the non-target demand keyword is a demand keyword that is related to the entity type of the entity keyword and does not match the target demand keyword.

[0172] Optionally, the step of obtaining the knowledge aggregation search result item corresponding to the entity keyword and displaying it in the search result page corresponding to the search statement further includes:

[0173] Obtaining at least one demand keyword corresponding to the entity category to which the entity keyword belongs;

[0174] Obtain search results corresponding to the entity keyword and each demand keyword respectively;

[0175] The content corresponding to the search result corresponding to each demand keyword is displayed in the knowledge aggregation search result item.

[0176] Optionally, each search result corresponding to a demand keyword corresponds to a knowledge module;

[0177] If the target demand keyword hits the demand keyword corresponding to the first knowledge module, the first search result is obtained according to the content of the first knowledge module.

[0178] Optionally, the demand keywords that do not match the target demand keywords include:

[0179] Demand keywords different from the target demand keywords; and / or,

[0180] Demand keywords that belong to different dimensions from the target demand keywords.

[0181] Optionally, content corresponding to the first search result included in the first display area is displayed preferentially.

[0182] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0183] It should be understood that the present application is not limited to the precise structures described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

[0184] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. A data processing method, characterized in that: The method comprises: Obtaining a search statement input by a user, and determining an entity keyword and a target demand keyword according to the search statement; the entity keyword corresponds to an entity object of a single category; the target demand keyword is used to indicate the search demand; Obtaining the knowledge aggregation search result item corresponding to the entity keyword and displaying it in the search result page corresponding to the search statement; including: Displaying content corresponding to a first search result in a first display area of ​​the knowledge aggregation search result item; the first search result is a search result obtained based on the entity keyword and the target demand keyword; Displaying content corresponding to at least one second search result in the second display area of ​​the knowledge aggregation search result item; the second search result is a search result obtained based on the entity keyword and the non-target demand keyword; the non-target demand keyword is a demand keyword related to the entity type of the entity keyword and not matching the target demand keyword; the demand keyword not matching the target demand keyword includes a demand keyword different from the target demand keyword; and / or a demand keyword belonging to a different dimension from the target demand keyword; The non-target demand keywords may be determined based on pre-set demand keywords and / or determined based on the user's historical search records.

2. The method according to claim 1, characterized in that The step of obtaining the knowledge aggregation search result item corresponding to the entity keyword and displaying it in the search result page corresponding to the search statement further includes: Obtaining at least one demand keyword corresponding to the entity category to which the entity keyword belongs; Obtain search results corresponding to the entity keyword and each demand keyword respectively; The content corresponding to the search result corresponding to each demand keyword is displayed in the knowledge aggregation search result item.

3. The method according to claim 2, characterized in that The search results corresponding to each demand keyword correspond to a knowledge module; If the target demand keyword hits the demand keyword corresponding to the first knowledge module, the first search result is obtained according to the content of the first knowledge module.

4. The method according to claim 1, characterized in that: The content corresponding to the first search result included in the first display area is displayed preferentially.

5. A data processing device, characterized in that: The device comprises: A first acquisition unit, used to acquire a search statement input by a user; A determination unit, configured to determine entity keywords and target demand keywords according to the search statement; the entity keywords correspond to entity objects of a single category; the target demand keywords are used to indicate search requirements; A second acquisition unit is used to acquire the knowledge aggregation search result item corresponding to the entity keyword; A display unit, used to display the knowledge aggregation search result item in the search result page corresponding to the search statement; comprising: Displaying content corresponding to a first search result in a first display area of ​​the knowledge aggregation search result item; the first search result is a search result obtained based on the entity keyword and the target demand keyword; Displaying content corresponding to at least one second search result in the second display area of ​​the knowledge aggregation search result item; the second search result is a search result obtained based on the entity keyword and the non-target demand keyword; the non-target demand keyword is a demand keyword that is related to the entity type of the entity keyword and does not match the target demand keyword; the demand keyword that does not match the target demand keyword includes a demand keyword that is different from the target demand keyword; and / or, a demand keyword that belongs to a different dimension from the target demand keyword; wherein the non-target demand keyword is determined based on a pre-set demand keyword and / or is determined based on the user's historical search records.

6. The device according to claim 5, characterized in that The second acquisition unit is further used for: Obtain a demand keyword corresponding to an entity category to which at least one of the entity keywords belongs; obtain search results corresponding to the entity keyword and each demand keyword respectively; The display unit is further used to display the content corresponding to the search result corresponding to each demand keyword in the knowledge aggregation search result item.

7. The device according to claim 6, characterized in that The search results corresponding to each demand keyword correspond to a knowledge module; If the target demand keyword hits the demand keyword corresponding to the first knowledge module, the first search result is obtained according to the content of the first knowledge module.

8. The device according to claim 5, characterized in that The content corresponding to the first search result included in the first display area is displayed preferentially.

9. A data processing device, characterized in that: The device comprises a memory and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by one or more processors, and the one or more programs include being used to perform the data processing method as described in any one of claims 1 to 4.

10. A computer-readable medium having instructions stored thereon, which, when executed by one or more processors, causes a device to execute the data processing method according to any one of claims 1 to 4.

Images