CN111831942A

CN111831942A - Method and device for displaying search results on page and electronic equipment

Info

Publication number: CN111831942A
Application number: CN201910298051.XA
Authority: CN
Inventors: 俞换萍
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2019-04-15
Filing date: 2019-04-15
Publication date: 2020-10-27

Abstract

The embodiment of the invention provides a method, a device and electronic equipment for displaying a page of a search result. The method for displaying the search result page comprises the following steps: generating an asynchronous API request according to the obtained searching entity information and the label page information indicated by the display expansion state instruction; acquiring data required by the page in an expanded state according to the asynchronous API request, and splicing the API of the script language template corresponding to the label page through the data required by the page in the expanded state; and loading the API of the script language template in an asynchronous request mode, and rendering the data of the script language template to display the expanded state page of the search result. By the embodiment of the invention, the display effect of the search result can be improved.

Description

Method and device for displaying search results on page and electronic equipment

Technical Field

The embodiment of the invention relates to the technical field of computers, in particular to a method and a device for displaying a page of a search result, electronic equipment and a computer storage medium.

Background

In the prior art, after searching for an entity, a user displays a search result by simulating a tab page in a page, and the page displaying the search result includes a plurality of tab pages (tab). For example, the search entity is "Langya list", and the corresponding tab pages in the page displaying the search result include "diversity scenario", "main creation", and "episode" and the like.

The problem with this way of displaying search results is that: when a user clicks a tab page in a page displaying a search result to view content in the tab page, the page displaying the search result initiates a secondary search request and performs an operation of refreshing the page displaying the search result. In this process, the refresh operation may cause page flickering, and a waiting time is required, resulting in poor display effect of the search result.

Disclosure of Invention

In view of the above, embodiments of the present invention provide a solution for displaying a page of a search result to solve some or all of the above problems.

According to a first aspect of the embodiments of the present invention, a method for displaying a page of search results is provided, including: generating an asynchronous API request according to the obtained searching entity information and the label page information indicated by the display expansion state instruction; acquiring data required by the page in an expanded state according to the asynchronous API request, and splicing the API of the script language template corresponding to the label page through the data required by the page in the expanded state; and loading the API of the script language template in an asynchronous request mode, and rendering the data of the script language template to display the expanded state page of the search result.

According to a second aspect of the embodiments of the present invention, a method for displaying a page of search results is provided, including: receiving an unfolding trigger operation of a suspended unfolding-state page inlet in a current page, and generating a display unfolding-state instruction according to the unfolding trigger operation; generating an asynchronous API request according to the search entity information and the label page information corresponding to the display expansion state instruction, and acquiring data required by the expansion state page through the asynchronous API request; and splicing the API of the script language template corresponding to the label page according to the data required by the expanded state page, and rendering the data acquired through the API of the script language template to display the expanded state page of the search result.

According to a third aspect of the embodiments of the present invention, an apparatus for page display of search results is provided, including: the generating module is used for generating an asynchronous API request according to the acquired searching entity information and the label page information indicated by the display expansion state instruction; the splicing module is used for acquiring data required by the expanded state page according to the asynchronous API request and splicing the API of the script language template corresponding to the label page through the data required by the expanded state page; and the loading module is used for loading the API of the script language template in an asynchronous request mode, rendering the data of the script language template and displaying the expanded state page of the search result.

According to a fourth aspect of the embodiments of the present invention, an apparatus for page displaying search results is provided, including: the first receiving module is used for receiving an unfolding trigger operation of a suspended unfolding state page entrance in a current page and generating a display unfolding state instruction according to the unfolding trigger operation; the data acquisition module is used for generating an asynchronous API request according to the search entity information and the label page information corresponding to the display expansion state instruction, and acquiring data required by the expansion state page through the asynchronous API request; and the rendering display module is used for splicing the API of the script language template corresponding to the label page according to the data required by the expanded state page, and rendering the data acquired through the API of the script language template so as to display the expanded state page of the search result.

According to a fifth aspect of embodiments of the present invention, there is provided an electronic apparatus, including: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus; the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the operation corresponding to the method for page display of the search result according to the first aspect or the second aspect.

According to a sixth aspect of embodiments of the present invention, there is provided a computer storage medium having stored thereon a computer program which, when executed by a processor, implements a method of page displaying search results as described in the first or second aspect.

According to the scheme for page display of the search result provided by the embodiment of the invention, the expanded state page can be hoisted through the asynchronous API request, the search result is displayed by using the expanded state page, and the data required by the expanded state page and the data of the script language template corresponding to the label page are obtained through the asynchronous request mode, so that the page is not refreshed when the data of the label page is displayed in the expanded state page, and the problems that the page flickers, the waiting is needed and the like caused by refreshing the page in the existing search result display mode are solved.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present invention, and it is also possible for a person skilled in the art to obtain other drawings based on the drawings.

FIG. 1 is a flowchart illustrating steps of a method for displaying a search result in a page according to a first embodiment of the present invention;

FIG. 2 is a diagram illustrating an expanded state page according to a first embodiment of the present invention;

FIG. 3 is a flowchart illustrating steps of a method for displaying a page of search results according to a second embodiment of the present invention;

FIG. 4 is a flowchart illustrating steps of a method for displaying a page of search results according to a third embodiment of the present invention;

FIG. 5 is a flowchart illustrating steps of a method for displaying a page of search results according to a fourth embodiment of the present invention;

FIG. 6 is a flowchart illustrating steps of a method for displaying a page of search results according to a fifth embodiment of the present invention; fig. 7 is a block diagram illustrating an apparatus for displaying a page of a search result according to a sixth embodiment of the present invention;

fig. 8 is a block diagram illustrating an apparatus for displaying a search result page according to a seventh embodiment of the present invention;

fig. 9 is a block diagram illustrating an apparatus for displaying a page of a search result according to an eighth embodiment of the present invention;

fig. 10 is a block diagram illustrating an apparatus for displaying a page of search results according to a ninth embodiment of the present invention;

fig. 11 is a schematic structural diagram of an electronic device according to a sixth embodiment of the present invention;

FIG. 12 is a schematic illustration of a page displaying search results in one of the usage scenarios;

FIG. 13 is a flowchart of the steps for generating data responsive to an asynchronous API request using a server in the scenario.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the embodiments of the present invention, the technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments of the present invention shall fall within the scope of the protection of the embodiments of the present invention.

The following further describes specific implementation of the embodiments of the present invention with reference to the drawings.

Example one

Referring to fig. 1, a flowchart illustrating steps of a method for displaying a page of search results according to a first embodiment of the present invention is shown.

The method for displaying the search result page in the embodiment comprises the following steps:

step S102: and generating an asynchronous API request according to the acquired search entity information and the tag page information indicated by the display expansion state instruction.

And the display expansion state instruction is used for indicating searching according to the searching entity information and displaying the searching result through an expansion state page (max state).

As shown in fig. 2, the expanded state page includes a plurality of tab pages (tab), and different tab pages may be used to display different categories of search results, so as to implement a classified display of the search results, so that the user can view the search results more conveniently.

The tab pages contained in the corresponding expanded state pages may be different for different search entities. For example, when the search entity is a person, the tab page included in the expanded page may be a "home page", "work", "travel", or other tab pages; when the search entity is a city, the tab page included in the expanded page may be "sight", "history", or the like.

In this embodiment, when the display expanded state instruction is acquired, the asynchronous API (interface) request is generated in an appropriate manner according to the search entity information and the tab page information indicated by the display expanded state instruction, so as to call an API in an asynchronous request manner according to the asynchronous API request, and acquire data required by the expanded state page.

Specifically, the search entity information includes, but is not limited to, a search entity word (query). The search entity words may be cities (e.g., Beijing, etc.), characters, television shows, movies, and the like.

Of course, in other embodiments, one skilled in the art may add or subtract content contained in the search entity information as needed. For example, the search entity information may further include an industry entity unique identifier (mkey) to which the search entity word belongs, where the industry entity unique identifier is used to indicate an industry entity to which the search entity word belongs.

For different search entity words, a person skilled in the art can set corresponding industry entity unique identifiers for the search entity words as required, for example, the search entity words are "beijing", the corresponding industry entity unique identifiers are "city", and the like.

The tab page information is used for indicating the tab page displayed when the page enters the expanded state. Those skilled in the art may acquire the tab information in an appropriate manner as needed, which is not limited in this embodiment.

For example, the tab page information may be obtained according to a preset default tab page; or the tab information may be obtained according to a clicked control in a page displaying the search result, and the like.

Step S104: and acquiring data required by the page in the expanded state according to the asynchronous API request, and splicing the API of the script language template corresponding to the label page through the data required by the page in the expanded state.

In this embodiment, according to the asynchronous API request, the data required by the expanded state page is obtained in an asynchronous request manner, so that decoupling between the expanded state page and other pages is achieved, for example, coupling between the expanded state page content data and content data of other pages, coupling between static resources of the expanded state page and static resources of other pages, and the like, so that the data required by the expanded state page does not depend on the data and static resources of other pages.

Through the method, a person skilled in the art can trigger the display expansion state instruction from any page (such as a news headline page, an existing page for displaying search results, an expansion state page and the like) according to needs, and generate the asynchronous API request to suspend the expansion state page, so that the suspension mode of the expansion state page is more diversified, and the adaptability is better.

For different service scenarios and/or search entities, the data required by the corresponding expanded state page may be different.

In this embodiment, the data required by the page in the expanded state includes, but is not limited to, setting information (settings). The setting information is used for indicating the tab pages contained in the expanded state page. Of course, in other embodiments, other information, such as color information (colors), log information (log), and the like, may also be included in the data required by the expanded state page.

Those skilled in the art can configure the setting information as long as the tab page included in the page in the expanded state can be indicated by the setting information. For example, the setting information is configured to indicate the tab page included in the page in the expanded state by means of a tab page identifier. For example, the tab page is identified as "home", indicating that the tab page in the expanded state page includes the tab page with the tab page name of "home", the tab page is identified as "work", indicating that the tab page in the expanded state page includes the tab page with the tab page name of "work", and so on.

Optionally, the setting information may further indicate a sequential relationship between the tab pages through a sequential relationship between the tab page identifiers.

According to the acquired data required by the expanded page, the API of the script language template corresponding to the label page can be spliced to acquire the data of the script language template corresponding to the label page, so that the expanded page is displayed according to the data of the script language template.

The script language template can be a script language template corresponding to any tab page contained in the expanded state page. The scripting language template may be any suitable template, such as a PHP template, Ruby template, Python template, or the like.

For those skilled in the art, according to the service requirement, the API of the script language template corresponding to the tab page can be spliced in a proper manner according to the data required by the expanded state page.

For example, the data required by the page in the expanded state is obtained according to the asynchronous API request, and the APIs of the script language template corresponding to the tab page are spliced according to the setting information and the preset splicing rule. For example, the preset splicing rule indicates that the API of the script language template corresponding to the tab page is spliced through the tab page identifier, the search entity word, the industry entity unique identifier, and the like indicated by the setting information.

A person skilled in the art may preset an appropriate splicing rule as needed, which is not limited in this embodiment.

Step S106: and loading the API of the script language template in an asynchronous request mode, and rendering the data of the script language template to display the expanded state page of the search result.

In this embodiment, the API of the scripting language template is loaded in an asynchronous request manner to obtain data of the scripting language template corresponding to the tab page. The asynchronous request mode can avoid page flicker and blank without reloading the whole page when rendering is carried out according to the acquired data, and can reduce the waiting time when the page in an expanded state is displayed; in addition, the search results are displayed in the form of the page in the expanded state, so that the user can check the search results more conveniently, and the display effect of the search results is better.

By the embodiment, the expanded state page can be hoisted through the asynchronous API request, the search result is displayed by using the expanded state page, the data required by the expanded state page and the data of the script language template corresponding to the tab page are acquired through the asynchronous request mode, the page is not refreshed when the data of the tab page is displayed in the expanded state page, and the problems that the page flickers, the waiting and the like are caused by the refreshed page in the existing search result display mode are solved.

The method for displaying the search result page of the embodiment may be executed by any suitable electronic device with data processing capability, including but not limited to: servers, mobile terminals (such as tablet computers, mobile phones and the like), PCs and the like.

Example two

Referring to fig. 3, a flowchart illustrating steps of a method for displaying a page of search results according to a second embodiment of the present invention is shown.

The method for displaying the search result page of the present embodiment includes the foregoing steps S102 to S106.

In this embodiment, the page in the expanded state includes a floating layer frame developed for the ILayer interface, and the floating layer frame includes a tab area for displaying a tab page name and a content area for displaying a tab page content. The ILayer interface is an abstract ILayer interface, and a person skilled in the art can define methods included in the ILayer interface according to needs, such as a creation method create (), an interactive method active (), a background cutting method disable (), a destruction method destroy (), and the like.

Because the floating Layer frames included in the expanded state page are developed facing the ILayer interface, when the floating Layer frames interact with other layers (the floating Layer pages, each floating Layer page is implemented for abstract Layer classes), the floating Layer frames interact according to the rules of the ILayer interface, so that developers of the floating Layer frames can customize different floating Layer frames (such as the floating Layer frames of the expanded state page, the floating Layer frames of the navigation bar and the like) according to different business scene requirements, and meanwhile, the floating Layer frames can share all the layers (the floating Layer pages) which are developed.

In addition, one skilled in the art can develop different general Layer components (such as picture walls and the like) based on the abstract Layer class for different service calls. The design based on the abstract ILayer interface and the Layer category well solves the defects of universality and flexibility of a floating Layer frame, and solves the problem that in the prior art, the same floating Layer page can be used in different floating Layer frames and the same floating Layer page can be used in different service scenes, so that the floating Layer page and the floating Layer frame need to be repeatedly developed.

With continued reference to fig. 3, in the present embodiment, the step S106 includes the following sub-steps:

substep S1061: and loading the API of the script language template in an asynchronous request mode, rendering the data of the script language template in the content area of the expanded state page, and rendering the label page name of the label page indicated by the setting information in the label area of the expanded state page.

In this embodiment, the data of the script language template may be HTML strings, json data, pictures, etc. that are easy to be interpreted by a browser.

The data of the scripting language template may be rendered into the content area of the expanded state page by one skilled in the art in any suitable manner.

For example, according to the data and setting information of the scripting language template, a floating layer frame and a floating layer page used in the expanded page are obtained, the floating layer frame comprises the tag area and the content area, and the floating layer page is configured in the content area of the floating layer frame. Rendering data of the script language template in the content area, and rendering a tab page name of a tab page indicated by the setting information in the tab area.

It should be noted that, when the page in the expanded state includes a plurality of tab pages, different tab pages may correspond to different floating layer pages.

Substep S1062: and displaying an expanded state page of the search result according to the rendering data of the tag area and the content area.

In this embodiment, the expanded state page may be displayed by drawing rendering data of the tab area and the content area. Of course, in other embodiments, the expanded state page may be displayed in any other suitable manner.

In addition, the floating layer frame and the floating layer page realize one set of ILayer interface at the same time, and the basic floating layer frame faces the interface instead of realizing, so that the universality and flexibility of the floating layer frame and the floating layer page are better.

EXAMPLE III

Referring to fig. 4, a flowchart illustrating steps of a method for displaying a page of search results according to a third embodiment of the present invention is shown.

The method for displaying the search result page of the present embodiment includes the foregoing steps S102 to S106. The step S106 may adopt the implementation manner described in the second embodiment or other implementation manners.

In this embodiment, the method further includes:

step S108: and configuring a front-end route corresponding to the label page by using a front-end route frame according to the label page in the expanded state page.

The front-end route can realize the jump between pages at the front end without reloading the pages, and the jump between label pages in the expanded state pages and/or the jump between the expanded state pages of different entities can be realized by configuring the front-end route.

In this embodiment, in order to implement mutual jumping of the expanded state page between different entities and different industry entities, the expanded state page is completely decoupled from the service scene. For example, the url (uniform resource locator) of the expanded state page is decoupled from the urls that suspend other pages of the expanded state page, and so on.

In order to make the url of the expanded state page an independent url, the front end routing framework has at least one of the following functions: rule matching based on regular is supported, so that matching rules can be customized according to services; a perfect hook mechanism (hook) to extend more complex business logic; the match function helps the service to acquire params (parameters), query (search entity words) and hash value (hash value) in url of the page in the expanded state so as to realize the customized service logic based on the service scene; the front-end routing framework simultaneously supports an Html5API and a Hash API, and supports seamless switching of the two, so that history records of the browser or url in an address bar are operated through the Html5API and the Hash API, and non-refresh page switching is further achieved.

Those skilled in the art may implement the front-end routing framework in an appropriate manner as needed, which is not limited in this embodiment.

When the front-end route corresponding to the tab page is configured by using the front-end route frame according to the tab page in the expanded state page, a person skilled in the art can configure the front-end route corresponding to the tab page in an appropriate manner as needed. For example, according to the label page identifier of each label page, a corresponding url is configured, and according to the function of the front-end routing framework, the front-end routing of each label page is configured.

Step S110: and acquiring the content data of the tab page to be switched according to the received tab page switching request and the front-end route matched with the tab page to be switched.

And the tab page switching request is used for indicating the tab page to be switched in the page in the unfolding state. And after receiving the tab page switching request, determining a matched front-end route according to the indicated tab page to be switched, and further acquiring the content data of the tab page to be switched so as to display the content data in the page in the unfolding state.

Optionally, in order to increase the display speed, the content data of the tab page to be switched is content data obtained by calling an API of a script language template corresponding to the spliced tab page to be switched in an asynchronous request manner in advance. Therefore, the content data of the tab pages to be switched can be pre-cached, so that the delay is smaller when the switching among the tab pages in the page in the expanded state is realized through the front-end route, and the non-perception switching of a user is realized.

It should be noted that, in order to reduce the occupation of resources and traffic, when the content data of the tab page to be switched is pre-cached, the content data of all the tab pages in the expanded page may be pre-cached as needed, or the content data of the uncached tab page associated with the currently displayed tab page may be pre-cached according to the currently displayed tab page.

In addition, according to the configuration of the front-end route corresponding to the tab page, the decoupling between the url of the expanded page and the urls of other pages can be realized, so that the technicians in the field can realize the non-refresh switching of the tab page in the expanded page through the front-end route according to the requirements. Because the front-end routing framework has multiple functions, the technical personnel in the field can expand the service requirement according to the needs and improve the adaptability of the front-end routing framework.

Example four

Referring to fig. 5, a flowchart illustrating steps of a method for displaying a page of search results according to a fourth embodiment of the present invention is shown.

step S502: and receiving an unfolding trigger operation of the suspended and unfolded-state page entrance in the current page, and generating a display unfolding-state instruction according to the unfolding trigger operation.

The current page may be any page configured with a suspended expanded page entry, including but not limited to: news headlines pages, existing pages displaying search results, and expanded state pages.

The hoisting expansion state page entrance can be configured at a required position of the current page, when expansion triggering operation for the hoisting expansion state page entrance is received, a display expansion state instruction is generated according to the expansion triggering operation, so that searching is performed according to searching entity information through the display expansion state instruction, and a searching result is displayed through the expansion state page (max state).

Those skilled in the art can configure the suspended and expanded page entry at an appropriate position in the current page in an appropriate manner, which is not limited in this embodiment. For example, the current page is a news headline page, and a "max" identifier may be configured at the character information in the news headline page, so that the "max" identifier becomes an entry of the suspended expanded-state page, and when the user clicks the character information, an expanded-state display instruction is generated.

In this embodiment, the display expansion state instruction indicates that the search entity information and the tab information exist.

For example, if the display expanded state instruction is generated based on a suspended expanded state page entry in a news headline page, the tab information may be obtained according to a preset default tab. For another example, if the display expansion instruction is generated based on a suspended expansion page entry in a page displaying the search result, the tab information may be obtained according to a clicked control in the page displaying the search result, and the like.

Step S504: and generating an asynchronous API request according to the search entity information and the label page information corresponding to the display expansion state instruction, and acquiring the data required by the expansion state page through the asynchronous API request.

Those skilled in the art can generate asynchronous API requests in an appropriate manner according to business needs. For example, an asynchronous API (interface) request is generated according to search entity information and tab page information corresponding to a display development state instruction and a preset generation rule, and an API is called in an asynchronous request mode according to the asynchronous API request to obtain data required by the development state page.

Therefore, decoupling between the expanded state page and other pages is realized, for example, coupling between the expanded state page content data and the content data of other pages, coupling between the static resources of the expanded state page and the static resources of other pages, and the like, so that the data required by the expanded state page does not depend on the data and the static resources of other pages.

Optionally, the setting information may also indicate a position relationship between tab pages (i.e. a sequential relationship between tab pages) through a sequential relationship between the tab page identifiers.

Step S506: and splicing the API of the script language template corresponding to the label page according to the data required by the expanded state page, and rendering the data acquired through the API of the script language template to display the expanded state page of the search result.

And loading the API of the script language template in an asynchronous request mode to acquire the data of the script language template corresponding to the label page. The asynchronous request mode can avoid page flicker and blank without reloading the whole page when rendering is carried out according to the acquired data, and can reduce the waiting time when the page in an expanded state is displayed; in addition, the search results are displayed in the form of the page in the expanded state, so that the user can check the search results more conveniently, and the display effect of the search results is better.

By the embodiment, the unfolding trigger operation can be received in any current page configured with the hanging unfolding state page entrance, and the display unfolding state instruction can be generated. The method has the advantages that the expanded state page can be hoisted through the asynchronous API request according to the instruction for displaying the expanded state, the search result is displayed through the expanded state page, the data needed by the expanded state page and the data of the script language template corresponding to the label page are obtained through the asynchronous request mode, the page can not be refreshed when the data of the label page is displayed in the expanded state page, and the problems that the page flickers, the waiting is needed and the like caused by the refreshing of the page in the existing search result display mode are solved.

EXAMPLE five

Referring to fig. 6, a flowchart illustrating steps of a method for displaying a page of search results according to a fifth embodiment of the present invention is shown.

The method for displaying the search result page of the present embodiment includes the foregoing steps S502 to S506.

Wherein the method further comprises the steps of:

step S508: receiving a switching trigger operation on a tab page to be displayed in an expanded state page, and generating a tab page switching request according to the switching trigger operation.

Any suitable operation can be preset by those skilled in the art as a switching trigger operation according to business requirements, for example, a click operation or a sliding operation of a tab page to be displayed, and the like.

And generating a tab page switching request according to the received switching trigger operation so as to indicate that the tab page currently displayed in the page in the unfolded state is switched to the tab page to be switched indicated by the tab page switching request.

Step S510: and according to the label page switching request and the front end route matched with the label page to be switched, obtaining and rendering and displaying the content data of the label page to be switched.

And determining a matched front-end route according to the label page to be switched indicated by the label page switching request, acquiring the content data of the label page to be switched through the determined front-end route, and rendering and displaying the content data.

Step S512: and determining an associated label page associated with the displayed label page according to the position relation among the label pages in the expanded state page.

It should be noted that this step is an optional step, and may be performed at any appropriate time after step S510, or in parallel with step S510.

In a specific implementation, according to the position relationship between the tab pages in the page in the expanded state, the previous tab page and the next tab page adjacent to the displayed tab page are determined as candidate associated tab pages, and the tab page which is not cached with content data in advance in the candidate associated tab pages is determined as an associated tab page.

Step S514: and pre-acquiring the content data of the associated label page according to the API of the script language template corresponding to the associated label page, so as to render and display the pre-acquired content data of the associated label page when receiving the switching trigger operation of the associated label page.

The API of the script language template corresponding to the associated tab page may be obtained in the same manner as in step S506, or obtained in another suitable manner, which is not described in detail in this embodiment.

And when the content data of the associated label page is pre-acquired, loading the API of the script language template corresponding to the label page in an asynchronous request mode to acquire the data of the script language template corresponding to the label page. Therefore, when the tab page switching request indicates the associated tab page, rendering display can be directly performed according to the acquired content data, so that the time consumption during display is further reduced, and the response speed is improved.

EXAMPLE six

Referring to fig. 7, a block diagram of an apparatus for displaying a page of a search result according to a sixth embodiment of the present invention is shown.

The apparatus for displaying a page of a search result of this embodiment includes a generating module 602, a splicing module 604, and a loading module 606.

The generating module 602 is configured to generate an asynchronous API request according to the search entity information and the tab information indicated by the acquired display and development state instruction.

In this embodiment, when the display expanded state instruction is acquired, the asynchronous API (interface) request is generated according to the search entity information and the tab page information indicated by the display expanded state instruction, so as to call an API in an asynchronous request manner according to the asynchronous API request, and acquire data required by the expanded state page.

The splicing module 604 is configured to obtain data required by the expanded state page according to the asynchronous API request, and splice an API of a script language template corresponding to the tab page through the data required by the expanded state page.

The loading module 606 is configured to load the API of the scripting language template in an asynchronous request manner, and render the data of the scripting language template to display an expanded page of the search result.

According to the embodiment, the expanded state page can be hoisted through the asynchronous API request, the search result is displayed by using the expanded state page, the data required by the expanded state page and the data of the script language template corresponding to the tab page are obtained through the asynchronous request mode, the page can be not refreshed when the data of the tab page is displayed in the expanded state page, and the problems that the page flickers, the waiting is needed and the like caused by the refreshed page in the existing search result display mode are solved.

EXAMPLE seven

Referring to fig. 8, a block diagram of an apparatus for displaying a page of a search result according to a seventh embodiment of the present invention is shown.

The apparatus for displaying a search result page of this embodiment includes the aforementioned generating module 602, splicing module 604, and loading module 606.

Optionally, the expanded state page includes a floating layer frame developed for an ILayer interface, and the floating layer frame includes a tab area for displaying a tab name and a content area for displaying a tab content.

The ILayer interface is an abstract ILayer interface, and a person skilled in the art can define methods included in the ILayer interface according to needs, such as a creation method create (), an interactive method active (), a background cutting method disable (), a destruction method destroy (), and the like.

With continued reference to fig. 8, optionally, the loading module 606 includes a rendering module 6061 and a display module 6062.

The rendering module 6061 is configured to load the API of the scripting language template in an asynchronous request manner, render the data of the scripting language template in the content area of the expanded page, and render the tab page name of the tab page indicated by the setting information in the tab area of the expanded page.

The display module 6062 is configured to display an expanded page of the search result according to the rendering data of the tag area and the content area.

Optionally, with continued reference to fig. 8, the apparatus further comprises a configuration module 608 and a switching module 610.

The configuration module 608 is configured to configure a front-end route corresponding to the tab page by using a front-end routing framework according to the tab page in the expanded page.

In order to make the url of the expanded state page an independent url, the front end routing framework has at least one of the following functions: rule matching based on regular is supported, so that matching rules can be customized according to services; a perfect hook mechanism (hook) to extend more complex business logic; the match function helps the service to acquire params (parameters), query (search entity words) and hash value (hash value) in url of the page in the expanded state so as to realize the customized service logic based on the service scene; the front-end routing framework simultaneously supports the Html5API and the HashAPI, and supports seamless switching of the Html5API and the HashAPI, so that history records of the browser or url in an address bar are operated through the Html5API and the HashAPI, and non-refresh page switching is achieved.

The switching module 610 is configured to obtain content data of the tab page to be switched according to the received tab page switching request and the front-end route matched with the tab page to be switched.

Moreover, according to the configuration of the front-end route corresponding to the tab page, the decoupling between the url of the expanded page and the urls of other pages can be realized, so that the technicians in the field can realize the non-refresh switching of the tab page in the expanded page through the front-end route according to the requirements. Because the front-end routing framework has multiple functions, the technical personnel in the field can expand the service requirement according to the needs and improve the adaptability of the front-end routing framework.

Example eight

Referring to fig. 9, a block diagram of an apparatus for displaying a page of a search result according to an eighth embodiment of the present invention is shown.

The apparatus for displaying a page of a search result of this embodiment includes a first receiving module 902, a data obtaining module 904, and a rendering and displaying module 906.

The first receiving module 902: the display device is used for receiving the unfolding trigger operation of the suspended and unfolded state page entrance in the current page and generating a display unfolding state instruction according to the unfolding trigger operation.

The data acquisition module 904: and the system is used for generating an asynchronous API request according to the search entity information and the label page information corresponding to the display expansion state instruction, and acquiring the data required by the expansion state page through the asynchronous API request.

Rendering display module 906: and the expanded state page is used for splicing the API of the script language template corresponding to the label page according to the data required by the expanded state page, and rendering the data acquired through the API of the script language template so as to display the search result.

Example nine

Referring to fig. 10, a block diagram of an apparatus for displaying a page of search results according to a ninth embodiment of the present invention is shown.

The apparatus for displaying a page of a search result of this embodiment includes the aforementioned first receiving module 902, data obtaining module 904, and rendering and displaying module 906.

Optionally, the apparatus further comprises a second receiving module 908 and a switching display module 910.

The second receiving module 908: the display device is used for receiving switching trigger operation of the tab page to be displayed in the page in the expanded state and generating a tab page switching request according to the switching trigger operation.

The switching display module 910: and the front end router is used for obtaining and rendering and displaying the content data of the tab page to be switched according to the tab page switching request and the front end router matched with the tab page to be switched.

Optionally, the apparatus further comprises an association determination module 912 and a preloading module 914.

Association determination module 912: and the method is used for determining the associated tab page associated with the displayed tab page according to the position relation among the tab pages in the expanded state page.

It should be noted that this module is an optional module, which can be operated at any appropriate time after the display module 910 is switched, or in parallel with the switching of the display module 910.

The preload module 914: and the API is used for pre-acquiring the content data of the associated label page according to the script language template corresponding to the associated label page, so that the content data of the pre-acquired associated label page is rendered and displayed when the switching trigger operation of the associated label page is received.

The API of the script language template corresponding to the associated tab page may be obtained in the same manner as in the rendering and displaying module 506, or obtained in another suitable manner, which is not described in detail in this embodiment.

Example ten

Referring to fig. 11, a schematic structural diagram of an electronic device according to a tenth embodiment of the present invention is shown, and the specific embodiment of the present invention does not limit the specific implementation of the electronic device.

As shown in fig. 11, the electronic device may include: a processor (processor)1102, a communication Interface 1104, a memory 1106, and a communication bus 1108.

Wherein:

the processor 1102, communication interface 1104, and memory 1106 communicate with one another via a communication bus 1108.

A communication interface 1104 for communicating with other electronic devices such as a terminal device or a server.

The processor 1102 is configured to execute the program 1110, and may specifically perform relevant steps in the above method embodiment of displaying a page of a search result.

In particular, the program 1110 can include program code that includes computer operating instructions.

The processor 1102 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement an embodiment of the present invention. The electronic device comprises one or more processors, which can be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.

A memory 1106 for storing a program 1110. Memory 1106 may comprise high-speed RAM memory and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

The program 1110 may be specifically configured to cause the processor 1102 to perform the following operations: generating an asynchronous API request according to the obtained searching entity information and the label page information indicated by the display expansion state instruction; acquiring data required by the page in an expanded state according to the asynchronous API request, and splicing the API of the script language template corresponding to the label page through the data required by the page in the expanded state; and loading the API of the script language template in an asynchronous request mode, and rendering the data of the script language template to display the expanded state page of the search result.

In an optional implementation manner, the data required by the expanded state page includes setting information, and the setting information is used for indicating a tab page included in the expanded state page.

In an optional implementation manner, the program 1110 is further configured to enable the processor 1102 to obtain, according to the asynchronous API request, data required by the expanded state page when the data required by the expanded state page is obtained according to the asynchronous API request and the API of the scripting language template corresponding to the tab page is spliced through the data required by the expanded state page, and splice the API of the scripting language template corresponding to the tab page through the setting information and the preset splicing rule.

In an optional implementation, the expanded state page comprises a floating layer frame developed facing the ILayer interface, and the floating layer frame comprises a tag area for displaying a tag page name and a content area for displaying the content of the tag page.

In an alternative embodiment, the program 1110 is further configured to cause the processor 1102 to load the API of the scripting language template in the asynchronous request manner, when the API of the scripting language template is loaded in the asynchronous request manner and data of the scripting language template is rendered to display an expanded state page of a search result, load the API of the scripting language template in the asynchronous request manner and render the data of the scripting language template in a content area of the expanded state page, and render a tab page name of a tab page indicated by the setting information in a tab area of the expanded state page; and displaying an expanded state page of the search result according to the rendering data of the tag area and the content area.

In an alternative embodiment, program 1110 is further configured to cause processor 1102 to configure a front-end route corresponding to a tab page in the expanded state page using a front-end routing framework according to the tab page; and acquiring the content data of the tab page to be switched according to the received tab page switching request and the front-end route matched with the tab page to be switched.

In an optional implementation manner, the content data of the tab page to be switched is content data obtained by calling an API of a script language template corresponding to the spliced tab page to be switched in an asynchronous request manner in advance.

Alternatively, the program 1110 may be specifically configured to cause the processor 1102 to perform the following operations: receiving an unfolding trigger operation of a suspended unfolding-state page inlet in a current page, and generating a display unfolding-state instruction according to the unfolding trigger operation; generating an asynchronous API request according to the search entity information and the label page information corresponding to the display expansion state instruction, and acquiring data required by the expansion state page through the asynchronous API request; and splicing the API of the script language template corresponding to the label page according to the data required by the expanded state page, and rendering the data acquired through the API of the script language template to display the expanded state page of the search result.

In an optional implementation manner, the program 1110 is further configured to enable the processor 1102 to receive a switching trigger operation on a tab page to be displayed in an expanded page, and generate a tab page switching request according to the switching trigger operation; and according to the label page switching request and the front end route matched with the label page to be switched, obtaining and rendering and displaying the content data of the label page to be switched.

In an alternative embodiment, the program 1110 is further configured to enable the processor 1102 to determine an associated tab page associated with the displayed tab page according to a position relationship between tab pages in the expanded state page; and pre-acquiring the content data of the associated label page according to the API of the script language template corresponding to the associated label page, so as to render and display the pre-acquired content data of the associated label page when receiving the switching trigger operation of the associated label page.

For specific implementation of each step in the program 1110, reference may be made to corresponding steps and corresponding descriptions in units in the above-described method embodiment for performing page display on a search result, which are not described herein again. It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described devices and modules may refer to the corresponding process descriptions in the foregoing method embodiments, and are not described herein again.

Through the electronic equipment of the embodiment, the expanded state page can be hoisted through the asynchronous API request, the search result is displayed by using the expanded state page, the data required by the expanded state page and the data of the script language template corresponding to the label page are acquired through the asynchronous request mode, the page can be not refreshed when the data of the label page is displayed in the expanded state page, and the problems that the page flickers, the waiting and the like are caused by the refreshed page in the existing search result display mode are solved.

It should be noted that, according to the implementation requirement, each component/step described in the embodiment of the present invention may be divided into more components/steps, and two or more components/steps or partial operations of the components/steps may also be combined into a new component/step to achieve the purpose of the embodiment of the present invention.

The above-described method according to an embodiment of the present invention may be implemented in hardware, firmware, or as software or computer code storable in a recording medium such as a CDROM, RAM, a floppy disk, a hard disk, or a magneto-optical disk, or as computer code originally stored in a remote recording medium or a non-transitory machine-readable medium downloaded through a network and to be stored in a local recording medium, so that the method described herein may be stored in such software processing on a recording medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware such as an ASIC or FPGA. It will be appreciated that the computer, processor, microprocessor controller or programmable hardware includes memory components (e.g., RAM, ROM, flash memory, etc.) that can store or receive software or computer code that, when accessed and executed by the computer, processor or hardware, implements the method of page display of search results described herein. Further, when a general-purpose computer accesses code for implementing the method for page displaying search results shown herein, execution of the code transforms the general-purpose computer into a special-purpose computer for performing the method for page displaying search results shown herein.

Usage scenarios

In this usage scenario, the expanded page is suspended from the page on which the search result is displayed, and the search result is displayed. FIG. 12 illustrates a page displaying search results, including simulated tab pages 1-5, through which the process of lifting the expanded state page and displaying the search results includes:

step A: and generating an asynchronous API request according to the acquired search entity information and the tag page information indicated by the display expansion state instruction.

For example, when the user clicks on tab page 2 in the page displaying the search result, since tab page 2 is a suspended expanded state page entry, an expanded state page display instruction is generated and acquired. The display expanded state page instruction is used for indicating search entity information (such as search entity words, industry entity unique identifiers and the like) and label page information (such as label page identifiers of the label page 2), and the like.

Those skilled in the art can generate a matching asynchronous API request using the search entity information and the tab page information according to the service settings of different service scenarios.

And B: and acquiring data required by the page in the expanded state according to the asynchronous API request, and splicing the API of the script language template corresponding to the label page through the data required by the page in the expanded state.

And sending the asynchronous API request to the server in an asynchronous request mode. In the present usage scenario, the server performs the process shown in FIG. 13 based on the received asynchronous API request. The method specifically comprises the following steps:

if the asynchronous API request hangs up an expanded page frame (max. php), parameters (parsepams) in the asynchronous API request are analyzed according to the configuration of the max. php, and entity words such as search, unique industrial entity identification and the like are obtained.

And processing the analysis result to obtain an api parameter (apiParams) meeting the requirements of the service database, so that flexible control of interface parameter configuration can be realized. The api parameter is a parameter required when requesting data from a service database, and the api parameter may be different for different service databases.

Php requests data from the service database and sends the api parameters (such as searching entity words) to the service database by adopting a data acquisition mode of service database configuration according to the acquired api parameters and service database configuration. In the use scenario, three data acquisition modes of the service database are exemplified, such as a uniform acquisition mode (getArbiterData), an api mode (getApiData), and a secondary search mode (getUrldata).

And acquiring original data (maxdata) returned by the service database. The original data is subjected to parsing processing (parsemaxtdata), and data conforming to the HTML specification (getMaxHtml) is acquired, and data of the expanded-state page (pageData) is generated from the data conforming to the HTML specification. The data of the expanded state page includes data (data), an error (err), a message (msg), and the like, wherein the data (data) includes color information (color), log information (log), setting information (settings), tpl data, and the like of the expanded state page.

According to needs, a person skilled in the art can set that debug is executed when parsing processing is performed on the original data, and a debug result (showDebug) is displayed.

The data required by the expanded state page returned by the server and acquired by the browser can be all or part of the data of the expanded state page. In the use scenario, the data required by the expanded state page includes setting information, the setting information includes a tab page identifier of a tab page included in the expanded state page, and the browser can splice an API of a script language template corresponding to the tab page according to the acquired tab page identifier.

When the APIs of the script language templates corresponding to the tab pages are to be spliced, the APIs of the script language templates of all the tab pages may be spliced, or only the APIs of the script language templates of the required tab pages may be spliced.

And C: and loading the API of the script language template in an asynchronous request mode, and rendering the data of the script language template to display the expanded state page of the search result.

The API for loading the script language template in the asynchronous request mode obtains data of the script language template, which includes content data of the tab page, such as a floating page of the tab page, text content, and the like. And calling the corresponding API to obtain the corresponding floating layer frame and the floating layer page according to the obtained data of the script language template, and rendering the floating layer frame, the floating layer page and the content thereof to display the expanded page of the search result.

Step D: configuring a front-end route.

The browser can also carry out front-end routing configuration according to the received data required by the page in the expansion state. For example, a regular matching rule is added according to the service requirement, a hook is set, a matching method match () is used to obtain parameters (Params) in url, search entity words (query), hash values (hash), paths (path) and the like, or the history of the browser is operated through a navigation method navigator (), a push method push (), a replacement method replace () or a listening method list () in the Html5API or the HashAPI.

Step E: and acquiring the content data of the tab page to be switched according to the received tab page switching request and the front-end route matched with the tab page to be switched.

And when the user clicks a certain tab page in the displayed expanded page, generating and receiving a tab page switching request. And acquiring the content data of the tab page to be switched according to the received tab page switching request and the front-end route matched with the tab page to be switched.

If the user clicks some other entity (such as a certain song or movie) in the displayed expanded state page, the expanded state page of the clicked entity can be hoisted and displayed through the current expanded state page, and the process is the same as or similar to the process of hoisting and displaying the expanded state page, so that the process is not repeated.

Because the expanded state page of the other entity can be directly hoisted from the expanded state page of one entity, and the switching between the expanded state pages of the two entities is realized through the front-end routing, the pages do not need to be refreshed, and the source returning and user guiding are better in clickability.

In the use scene, the expansion page can be hung at any page, the page does not need to be refreshed when the expansion page is switched, the expansion page of another entity can be hung at the expansion page of any entity, the page does not need to be refreshed, and the problems that the browser waits and can be flashed and user experience is influenced because one page refreshing operation is performed when the page displaying the search result or the floating layer simulation tag page is switched in the prior art are solved.

Those of ordinary skill in the art will appreciate that the various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present embodiments.

The above embodiments are only for illustrating the embodiments of the present invention and not for limiting the embodiments of the present invention, and those skilled in the art can make various changes and modifications without departing from the spirit and scope of the embodiments of the present invention, so that all equivalent technical solutions also belong to the scope of the embodiments of the present invention, and the scope of patent protection of the embodiments of the present invention should be defined by the claims.

Claims

1. A method for displaying a page of search results, comprising:

generating an asynchronous API request according to the obtained searching entity information and the label page information indicated by the display expansion state instruction;

acquiring data required by the page in an expanded state according to the asynchronous API request, and splicing the API of the script language template corresponding to the label page through the data required by the page in the expanded state;

and loading the API of the script language template in an asynchronous request mode, and rendering the data of the script language template to display the expanded state page of the search result.

2. The method according to claim 1, wherein the data required by the expanded state page comprises setting information indicating a tab page included in the expanded state page.

3. The method according to claim 2, wherein the obtaining of the data required by the expanded state page according to the asynchronous API request and the splicing of the API of the script language template corresponding to the tab page by the data required by the expanded state page are specifically:

and acquiring data required by the page in the expanded state according to the asynchronous API request, and splicing the API of the script language template corresponding to the label page through the setting information and a preset splicing rule.

4. The method of claim 3, wherein the expanded state page comprises a floating-layer frame developed for an ILayer interface, the floating-layer frame comprising a tab area for displaying a tab page name and a content area for displaying tab page content.

5. The method of claim 4, wherein loading the API of the scripting language template by asynchronous request and rendering the data of the scripting language template to display an expanded state page of search results comprises:

loading an API of the script language template in an asynchronous request mode, rendering data of the script language template in a content area of the expanded page, and rendering a label page name of a label page indicated by the setting information in a label area of the expanded page;

and displaying an expanded state page of the search result according to the rendering data of the tag area and the content area.

6. The method of claim 1, further comprising:

configuring a front-end route corresponding to the label page by using a front-end route frame according to the label page in the expanded state page;

and acquiring the content data of the tab page to be switched according to the received tab page switching request and the front-end route matched with the tab page to be switched.

7. The method according to claim 6, wherein the content data of the tab page to be switched is content data obtained by calling an API of a script language template corresponding to the spliced tab page to be switched in an asynchronous request mode in advance.

8. A method for displaying a page of search results, comprising:

receiving an unfolding trigger operation of a suspended unfolding-state page inlet in a current page, and generating a display unfolding-state instruction according to the unfolding trigger operation;

generating an asynchronous API request according to the search entity information and the label page information corresponding to the display expansion state instruction, and acquiring data required by the expansion state page through the asynchronous API request;

and splicing the API of the script language template corresponding to the label page according to the data required by the expanded state page, and rendering the data acquired through the API of the script language template to display the expanded state page of the search result.

9. The method of claim 8, further comprising:

receiving a switching trigger operation on a tab to be displayed in an expanded page, and generating a tab switching request according to the switching trigger operation;

and according to the label page switching request and the front end route matched with the label page to be switched, obtaining and rendering and displaying the content data of the label page to be switched.

10. The method according to claim 8 or 9, characterized in that the method further comprises:

determining an associated label page associated with the displayed label page according to the position relation among the label pages in the page in the expanded state;

and pre-acquiring the content data of the associated label page according to the API of the script language template corresponding to the associated label page, so as to render and display the pre-acquired content data of the associated label page when receiving the switching trigger operation of the associated label page.

11. An apparatus for page display of search results, comprising:

the generating module is used for generating an asynchronous API request according to the acquired searching entity information and the label page information indicated by the display expansion state instruction;

the splicing module is used for acquiring data required by the expanded state page according to the asynchronous API request and splicing the API of the script language template corresponding to the label page through the data required by the expanded state page;

and the loading module is used for loading the API of the script language template in an asynchronous request mode, rendering the data of the script language template and displaying the expanded state page of the search result.

12. The apparatus according to claim 11, wherein the data required for the expanded state page includes setting information indicating a tab page included in the expanded state page.

13. The apparatus according to claim 12, wherein the splicing module is configured to obtain data required by the page in the expanded state according to the asynchronous API request, and splice the APIs of the script language templates corresponding to the tab pages according to the setting information and a preset splicing rule.

14. The apparatus of claim 13, wherein the expanded state page comprises a floating-layer frame developed for an ILayer interface, the floating-layer frame comprising a tab area for displaying a tab name and a content area for displaying tab content.

15. The apparatus of claim 14, wherein the loading module comprises:

the rendering module is used for loading the API of the script language template in an asynchronous request mode, rendering the data of the script language template in the content area of the expanded page, and rendering the label page name of the label page indicated by the setting information in the label area of the expanded page;

and the display module is used for displaying the expanded state page of the search result according to the rendering data of the tag area and the content area.

16. The apparatus of claim 11, further comprising:

the configuration module is used for configuring a front-end route corresponding to the label page by using a front-end route frame according to the label page in the expanded state page;

and the switching module is used for acquiring the content data of the label page to be switched according to the received label page switching request and the front-end route matched with the label page to be switched.

17. The apparatus according to claim 16, wherein the content data of the tab page to be switched is content data obtained by calling an API of a script language template corresponding to the spliced tab page to be switched in an asynchronous request manner in advance.

18. An apparatus for page display of search results, comprising:

the first receiving module is used for receiving an unfolding trigger operation of a suspended unfolding state page entrance in a current page and generating a display unfolding state instruction according to the unfolding trigger operation;

the data acquisition module is used for generating an asynchronous API request according to the search entity information and the label page information corresponding to the display expansion state instruction, and acquiring data required by the expansion state page through the asynchronous API request;

and the rendering display module is used for splicing the API of the script language template corresponding to the label page according to the data required by the expanded state page, and rendering the data acquired through the API of the script language template so as to display the expanded state page of the search result.

19. The apparatus of claim 18, further comprising:

the second receiving module is used for receiving switching triggering operation of the tab page to be displayed in the search result page and generating a tab page switching request according to the switching triggering operation;

and the switching display module is used for obtaining and rendering and displaying the content data of the label page to be switched according to the label page switching request and the front-end route matched with the label page to be switched.

20. The apparatus of claim 18 or 19, further comprising:

the association determining module is used for determining an associated label page associated with the displayed label page according to the position relationship among the label pages in the search result page;

and the pre-loading module is used for pre-acquiring the content data of the associated label page according to the API of the script language template corresponding to the associated label page, so as to render and display the pre-acquired content data of the associated label page when receiving the switching triggering operation of the associated label page.

21. An electronic device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;

the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the operation corresponding to the method for page display of the search result according to any one of claims 1-7 or the operation corresponding to the method for page display of the search result according to any one of claims 8-10.

22. A computer storage medium having stored thereon a computer program which, when executed by a processor, implements a method of page displaying search results as claimed in any one of claims 1 to 7, or which, when executed, implements a method of page displaying search results as claimed in any one of claims 8 to 10.