CN113590974B

CN113590974B - Recommendation page configuration method and device, electronic equipment and computer readable medium

Info

Publication number: CN113590974B
Application number: CN202111147217.1A
Authority: CN
Inventors: 闫澎飞
Original assignee: Beijing Missfresh Ecommerce Co Ltd
Current assignee: Shenzhen Zhuanxin Intellectual Property Service Co.,Ltd.
Priority date: 2021-09-29
Filing date: 2021-09-29
Publication date: 2022-01-28
Anticipated expiration: 2041-09-29
Also published as: CN113590974A

Abstract

The embodiment of the disclosure discloses a recommendation page configuration method, a recommendation page configuration device, electronic equipment and a computer readable medium. One embodiment of the method comprises: responding to a received page request sent by a user terminal, and acquiring a page embedded point log corresponding to the user terminal and a target page identifier; analyzing the page buried point log according to each access anchor mark in each access anchor mark to generate historical page access information to obtain a historical page access information set; generating at least one piece of recommended backward visit page information based on the backward visit page identifiers in each backward visit page identifier sequence included in the historical page access information set; according to the at least one piece of recommended post-visit page information, performing recommended post-visit page configuration on a page file corresponding to the page request to obtain a recommended page file; and sending the recommended page file to the user terminal. This embodiment saves the user's operating time to browse frequently visited pages.

Description

Recommendation page configuration method and device, electronic equipment and computer readable medium

Technical Field

The embodiment of the disclosure relates to the technical field of computers, in particular to a recommended page configuration method, a recommended page configuration device, electronic equipment and a computer readable medium.

Background

With the development of computer network technology, the network platform technology is also in the process of rapid development, and web pages become effective ways for providing online information presentation. At present, when a webpage is displayed, the method generally adopted is as follows: and the same page is displayed aiming at the client requests of different users.

However, when the web page is displayed in the above manner, the following technical problems often exist:

firstly, the display content of the uniformly configured pages is single, and the pages cannot be correspondingly configured according to the page access habits of different users, so that the users can browse the frequently accessed pages only by executing more operations, and the operation time of browsing the frequently accessed pages by the users is wasted;

secondly, the link control for accessing the frequently accessed page cannot be configured according to the page operation when the user previously accesses the frequently accessed page, so that the user needs to spend a long time in the current page to know the way of accessing the frequently accessed page, and the operation time of browsing the frequently accessed page by the user is wasted.

Disclosure of Invention

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

Some embodiments of the present disclosure propose a recommendation page configuration method, apparatus, electronic device and computer readable medium to solve one or more of the technical problems mentioned in the background section above.

In a first aspect, some embodiments of the present disclosure provide a recommendation page configuration method, including: responding to a received page request sent by a user terminal, and acquiring a page embedded point log corresponding to the user terminal and a target page identifier, wherein the page embedded point log comprises each access anchor identifier, and the target page identifier corresponds to the page request; analyzing the page buried point log according to each access anchor mark in the access anchor marks to generate historical page access information to obtain a historical page access information set, wherein the historical page access information comprises a post-visit page mark sequence corresponding to the target page mark; generating at least one piece of recommended backward visit page information based on the backward visit page identifiers in each backward visit page identifier sequence included in the historical page access information set; according to the at least one piece of recommended post-visit page information, performing recommended post-visit page configuration on a page file corresponding to the page request to obtain a recommended page file; and sending the recommended page file to the user terminal.

In a second aspect, some embodiments of the present disclosure provide a recommendation page configuring apparatus, including: an obtaining unit, configured to, in response to receiving a page request sent by a user terminal, obtain a page burial point log corresponding to the user terminal and a target page identifier, where the page burial point log includes respective access anchor identifiers, and the target page identifier corresponds to the page request; the analysis unit is configured to analyze the page buried point log according to each access anchor identifier in the access anchor identifiers to generate historical page access information to obtain a historical page access information set, wherein the historical page access information includes a post-visit page identifier sequence corresponding to the target page identifier; the generating unit is configured to generate at least one piece of recommended backward visit page information based on the backward visit page identifiers in each backward visit page identifier sequence included in the historical page access information set; the configuration unit is configured to perform recommended post-visit page configuration on the page file corresponding to the page request according to the at least one piece of recommended post-visit page information to obtain a recommended page file; a sending unit configured to send the recommended page file to the user terminal.

In a third aspect, some embodiments of the present disclosure provide an electronic device, comprising: one or more processors; a storage device having one or more programs stored thereon, which when executed by one or more processors, cause the one or more processors to implement the method described in any of the implementations of the first aspect.

In a fourth aspect, some embodiments of the present disclosure provide a computer readable medium on which a computer program is stored, wherein the program, when executed by a processor, implements the method described in any of the implementations of the first aspect.

The above embodiments of the present disclosure have the following advantages: by the recommended page configuration method of some embodiments of the disclosure, the operation time of the user for browsing frequently visited pages is saved. Specifically, the reason why the operation time for the user to browse the frequently accessed pages is wasted is that: the display content of the uniformly configured page is single, and the page cannot be correspondingly configured according to the page access habits of different users, so that the user needs to execute more operations to browse the frequently accessed page, and the operation time for the user to browse the frequently accessed page is wasted. Based on this, in the recommended page configuration method according to some embodiments of the present disclosure, first, in response to receiving a page request sent by a user terminal, a page embedded point log corresponding to the user terminal and a target page identifier is obtained. The page buried point log comprises access anchor point identifications, and the target page identification corresponds to the page request. Therefore, when the user terminal requests to browse the page corresponding to the target page identifier, the page embedded point log corresponding to the page request can be obtained, and the obtained page embedded point log records the relevant information when the user corresponding to the user terminal accesses the page. And then, according to each access anchor mark in the access anchor marks, analyzing the page buried point log to generate historical page access information, and obtaining a historical page access information set. The historical page access information comprises a post-visit page identification sequence corresponding to the target page identification. Therefore, the post-visit page identification sequence included in the historical page visit information set obtained through analysis can represent each link of the page visited by the user after visiting the page corresponding to the target page identification. And then, generating at least one piece of recommended backward visit page information based on the backward visit page identifications in each backward visit page identification sequence included in the historical page visit information set. Therefore, the recommended post-visit page information can be used as the related information of the configuration parameters when the page file is configured. And secondly, according to the at least one piece of recommended post-visit page information, performing recommended post-visit page configuration on the page file corresponding to the page request to obtain a recommended page file. Therefore, the related control for accessing the recommended backward visit page can be configured in the page file corresponding to the page request according to the information of each recommended backward visit page. And finally, sending the recommended page file to the user terminal. Therefore, the user terminal can render and display the recommended page file. And because each piece of recommended backward visit page information for configuring the page file corresponding to the target page identifier is generated according to the backward visit page identifier sequence obtained by analyzing the page embedded point log, for the page corresponding to the target page identifier, the related controls for accessing the recommended backward visit page in the pages displayed in different user terminals are different, and the recommended backward visit page information is generated according to the page access habit related information (each backward visit page identifier sequence) of the user, so that the operation steps of the user for browsing the frequently visited pages can be reduced. And further saves the operation time of the user for browsing frequently accessed pages.

Drawings

The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and elements are not necessarily drawn to scale.

FIG. 1 is a schematic diagram of one application scenario of a recommendation page configuration method, according to some embodiments of the present disclosure;

FIG. 2 is a flow diagram of some embodiments of a recommendation page configuration method according to the present disclosure;

FIG. 3 is a flow diagram of further embodiments of a recommendation page configuration method according to the present disclosure;

FIG. 4 is a schematic block diagram of some embodiments of a recommendation page configuration apparatus according to the present disclosure;

FIG. 5 is a schematic structural diagram of an electronic device suitable for use in implementing some embodiments of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.

It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings. The embodiments and features of the embodiments in the present disclosure may be combined with each other without conflict.

It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.

It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.

The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.

The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.

FIG. 1 is a schematic diagram of one application scenario of a recommendation page configuration method according to some embodiments of the present disclosure.

In the application scenario of fig. 1, first, the computing device 101 may obtain a page burial point log 104 corresponding to the user terminal 102 and the target page identifier in response to receiving a page request 103 sent by the user terminal 102. The page buried point log 104 includes access anchor point identifiers 105. The target page identification corresponds to the page request 103. Then, the computing device 101 may perform parsing processing on the page burial point log 104 according to each of the access anchor identifications 105 to generate historical page access information, so as to obtain a historical page access information set 106. The historical page access information comprises a post-visit page identification sequence corresponding to the target page identification. Thereafter, the computing device 101 may generate at least one piece of recommended backward page information 108 based on the backward page identifications in the respective backward page identification sequences 107 included in the above-mentioned historical page access information set 106. Secondly, the computing device 101 may perform recommended post-visit page configuration on the page file 109 corresponding to the page request 103 according to the at least one piece of recommended post-visit page information 108, so as to obtain a recommended page file 110. Finally, the computing device 101 may send the recommended page file 110 to the user terminal 102.

The computing device 101 may be hardware or software. When the computing device is hardware, it may be implemented as a distributed cluster composed of multiple servers or terminal devices, or may be implemented as a single server or a single terminal device. When the computing device is embodied as software, it may be installed in the hardware devices enumerated above. It may be implemented, for example, as multiple software or software modules to provide distributed services, or as a single software or software module. And is not particularly limited herein.

It should be understood that the number of computing devices in FIG. 1 is merely illustrative. There may be any number of computing devices, as implementation needs dictate.

With continued reference to FIG. 2, a flow 200 of some embodiments of a recommendation page configuration method according to the present disclosure is shown. The recommendation page configuration method comprises the following steps:

step 201, in response to receiving a page request sent by a user terminal, obtaining a page embedded point log corresponding to the user terminal and a target page identifier.

In some embodiments, an executing body (e.g., the computing device 101 shown in fig. 1) of the recommended page configuration method may obtain, in response to receiving a page request sent by a user terminal, a page burial point log corresponding to the user terminal and a target page identifier. The page request may be a request for browsing a web page of a web application. The page request may also be a request to browse a terminal application page. The target page identification corresponds to the page request. The target page identifier may be a page identifier representing a page requested to be browsed by the page request. The page identifier can be a url website, and can also be an identifier for uniquely identifying the page. The page buried point log may be a buried point log obtained by previously burying points in the page. The page buried point log comprises each access anchor point identifier. The access anchor point identifier may be an identifier for uniquely indicating that the user accesses the application program once according to the page sequence. For example, the user starts to access page 1 of the application at "2021/9/18: 00", then accesses from page 1 to page 2, and then accesses from page 2 to page 4, which all correspond to an access anchor identifier "001". In practice, the execution main body may obtain, from the terminal, a page burial point log in which the user terminal identifier is the same as the user terminal identifier, the application program identifier is the same as the application program identifier corresponding to the page request, and the page burial point log includes the target page identifier, in a wired connection manner or a wireless connection manner. The terminal may be the user terminal, or may be another terminal storing a page dotted log associated with the execution entity. It should be noted that the wireless connection means may include, but is not limited to, a 3G/4G connection, a WiFi connection, a bluetooth connection, a WiMAX connection, a Zigbee connection, a uwb (ultra wideband) connection, and other wireless connection means now known or developed in the future. Therefore, when the user terminal requests to browse the page corresponding to the target page identifier, the page embedded point log corresponding to the page request can be obtained, and the obtained page embedded point log records the relevant information when the user corresponding to the user terminal accesses the page.

Step 202, according to each access anchor mark in each access anchor mark, analyzing the page buried point log to generate historical page access information, and obtaining a historical page access information set.

In some embodiments, the execution main body may parse the page burial point log according to each of the access anchor identifiers to generate historical page access information, so as to obtain a historical page access information set. The historical page access information comprises a post-visit page identification sequence corresponding to the target page identification. In practice, first, the execution body may extract page burial point log information corresponding to the access anchor point identifier from the page burial point log. The page buried point log information may be log information in the page buried point log whose access anchor identifier is the same as the access anchor identifier. Then, the page identifier analysis processing can be performed on the page embedded point log information to obtain a page identifier set. And then, according to the access time corresponding to each page identifier in the page identifier set, sequencing the page identifier set in an ascending order to obtain a page identifier sequence. It is understood that when a user accesses each page, the corresponding access time is recorded in the page-landed log. Thus, each page identification corresponds to an access time. Then, the page identifier whose access time is earlier than or equal to the access time corresponding to the target page identifier in the page identifier sequence may be deleted, and the deleted page identifier sequence may be used as a subsequent page identifier sequence. Finally, the post-visit page identification sequence can be determined as historical page visit information. Therefore, the post-visit page identification sequence included in the historical page visit information set obtained through analysis can represent each link of the page visited by the user after visiting the page corresponding to the target page identification.

As an example, the execution body may extract, from the page-embedded-point log information, each page identifier corresponding to a page identifier as a page identifier set through a tag corresponding to the page identifier. The label may be a "pageId". The resulting set of page identifications may be [1, 2, 3, 4, 5, 6 ]. The target page identification may be 3. Then, the execution body may perform ascending sorting on the page identifiers according to the sequence of the access time, so as to obtain a page identifier sequence. The resulting page identification sequence may be [1, 2, 3, 4, 5, 6 ]. Next, the page identifiers 1, 2, and 3 whose access time is earlier than or equal to the access time corresponding to the target page identifier 3 in the page identifier sequence may be deleted, and the obtained post-visit page identifier sequence is [4, 5, 6 ]. Finally, the above-mentioned post-visit page identification sequence [4, 5, 6] may be determined as the historical page visit information.

Step 203, generating at least one piece of recommended backward visit page information based on the backward visit page identifiers in each backward visit page identifier sequence included in the historical page access information set.

In some embodiments, the execution subject may generate at least one piece of recommended backward page information based on the backward page identifier in each backward page identifier sequence included in the historical page access information set. In practice, first, the execution subject may select, from each of the backward access page identifier sequences, a backward access page identifier sequence arranged at a top position as a target backward access page identifier, to obtain a target backward access page identifier set. Then, the target post-visit page identifier with the largest repetition amount of the target post-visit page identifiers can be selected from the target post-visit page identifier set as recommended post-visit page information. Therefore, the recommended post-visit page information can be used as the related information of the configuration parameters when the page file is configured.

As an example, each of the post-visit page identification sequences may be [ [4, 5, 6], [5, 6, 7], [6, 7], [5, 6, 8] ]. First, the execution body may select a top backward page identifier sequence from each of the backward page identifier sequences as a target backward page identifier, and obtain a target backward page identifier set [4, 5, 6, 5 ]. Then, the target post-visit page identifier 5 with the largest repetition number of the target post-visit page identifiers may be selected from the target post-visit page identifier set [4, 5, 6, 5] as the recommended post-visit page information.

And step 204, according to the at least one piece of recommended post-visit page information, performing recommended post-visit page configuration on the page file corresponding to the page request to obtain a recommended page file.

In some embodiments, the execution subject may perform recommended post-visit page configuration on the page file corresponding to the page request according to the at least one piece of recommended post-visit page information, so as to obtain a recommended page file. The page file may be a file for configuring a displayed page. For example, the page file may be an HTML file. The above-mentioned page file may also be a CSS file. In practice, for each piece of recommended post-visit page information, the execution main body may add, to the page file, a code block of a page link control corresponding to a target post-visit page identifier included in the recommended post-visit page information. The code block comprises a page link control label, page link control display characters and a page address corresponding to the page identifier. Therefore, the related control for accessing the recommended backward visit page can be configured in the page file corresponding to the page request according to the information of each recommended backward visit page.

As an example, for the target post-visit page identifier 5 included in the recommended post-visit page information exemplified in step 203, the execution main body may add, to the page file, a code block "< a href =" https:// yyy.com/YYY/yyy.html "> < button >" of the page link control corresponding to the target post-visit page identifier 5. Wherein "https:// YYY.com/YYY/YYY.html" is the web address corresponding to the target post-visit page identifier 5.

Step 205, sending the recommended page file to the user terminal.

In some embodiments, the execution subject may send the recommended page file to the user terminal in a wired connection manner or a wireless connection manner. Therefore, the user terminal can render and display the recommended page file.

With further reference to FIG. 3, a flow 300 of further embodiments of a recommendation page configuration method is illustrated. The flow 300 of the recommendation page configuration method includes the following steps:

step 301, in response to receiving a page request sent by a user terminal, obtaining a page embedded point log corresponding to the user terminal and a target page identifier.

In some embodiments, the specific implementation of step 301 and the technical effect thereof may refer to step 201 in those embodiments corresponding to fig. 2, and are not described herein again.

Step 302, according to each post-visit page identifier in the post-visit page identifier sequence, performing page operation analysis processing on the page buried point log to obtain a page operation information set.

In some embodiments, an execution subject of the recommended page configuration method (e.g., computing device 101 shown in fig. 1) may extract page operation information characterizing a page corresponding to the post-visit page identification from the page burial point log. The page operation information may include a page control type. The page control type may be a type of control operated by a user. Therefore, the page control type of the user when accessing the page corresponding to the page identification can be determined.

Step 303, generating historical page access information based on the post-visit page identification sequence and the page operation information set.

In some embodiments, the execution subject may generate historical page access information based on the post-visit page identification sequence and the set of page operation information. The historical page access information comprises the page operation information set. In practice, the execution body may combine the post-visit page identification sequence and the page operation information set into historical page access information. Therefore, historical page access information which simultaneously comprises the user page access habit and the page operation habit related information can be generated.

And step 304, generating at least one piece of recommended backward visit page information based on the backward visit page identifications in each backward visit page identification sequence included in the historical page visit information set.

In practice, the execution body may generate the historical page access information based on the post-visit page identification sequence and the page operation information set by:

firstly, extracting a first backward visit page identifier from each backward visit page identifier sequence in the backward visit page identifier sequences to serve as a first backward visit page identifier, and obtaining a first backward visit page identifier set.

And secondly, performing duplicate removal processing on the first post-visit page identifier set to obtain the first post-visit page identifier set subjected to duplicate removal processing as a second post-visit page identifier set.

And thirdly, sequencing the second post-visiting page identifier set according to the number of each second post-visiting page identifier in the second post-visiting page identifier set included in the first post-visiting page identifier set to obtain a second post-visiting page identifier sequence. In practice, the execution body may perform descending order processing on the second backward access page identifier set according to a descending order of the number of each second backward access page identifier in the second backward access page identifier set included in the first backward access page identifier set, so as to obtain a second backward access page identifier sequence.

And fourthly, sequentially selecting a first number of second post-visit page identifications from the second post-visit page identification sequence as a first recommended post-visit page identification set according to the first target mode. The first target mode may be a front-to-back mode. In practice, the execution subject may sequentially select a first number of second backward-visited page identifiers from the second backward-visited page identifier sequence as a first recommended backward-visited page identifier set in a front-to-back manner. The first number is less than or equal to the number of second backward page identifiers included in the second backward page identifier sequence. Here, the specific setting of the first number is not limited.

And fifthly, combining the first recommended post-visit page identification set and the first configuration tag to obtain first recommended post-visit page information. The first configuration tag may be a tag used for representing that each first recommended post-visit page identifier in the first recommended post-visit page identifier set is a tag with a large number of first visits of the user in the page corresponding to the page request. In practice, the execution subject may perform splicing combination on the first recommended post-visit page identifier set and the first configuration tag to obtain a character string after the splicing combination as the first recommended post-visit page information. For example, the first set of recommended post-visit page identifications may be [5, 4 ]. The first configuration tab may be "identification of the most visited first page". The first recommended post-visit page information may be "the identifier of the page with the largest number of visits: [5,4]".

The execution main body may further combine the first recommended post-visit page identifier set and the first configuration tag to obtain first recommended post-visit page information by the following substeps:

and a first sub-step of selecting page operation information corresponding to the first recommended post-visit page identifier from all page operation information sets included in the historical page access information set as first page operation information according to each first recommended post-visit page identifier in the first recommended post-visit page identifier set to obtain a first page operation information set. And the page operation information corresponding to the first recommended post-visit page identifier is the page operation information representing the page which is jumped to the first recommended post-visit page identifier.

And a second substep of combining the first recommended post-visit page identifier set, the first page operation information set and the first configuration tag to obtain first recommended post-visit page information. In practice, the execution main body may perform splicing and combination on the first recommended post-visit page identifier set, the first page operation information set, and the first configuration tag, and obtain a character string after splicing and combination as first recommended post-visit page information. For example, the first set of recommended post-visit page identifications may be [5, 4 ]. The first page operation information set may be button, text. Wherein the button corresponds to the first recommended post-visit page identifier 5. the text corresponds to the first recommended post-visit page identifier 4. The first configuration tab may be "identification of the most visited first page". The first recommended post-visit page information may be "the identifier of the page with the largest number of visits: [5, 4], [ button, text ] ".

Through the first step to the fifth step, the generated first recommended post-visit page information may include both the page which is characterized by the user and which is visited first in the page corresponding to the page request and the operation related information when the page is visited, that is, the first recommended post-visit page identifier set and the first page operation information set.

And sixthly, extracting the post-visiting page identifier arranged at the last position from each post-visiting page identifier sequence in each post-visiting page identifier sequence to be used as a third post-visiting page identifier, and obtaining a third post-visiting page identifier set.

And seventhly, performing duplicate removal processing on the third post-visit page identification set to obtain the third post-visit page identification set subjected to duplicate removal processing as a fourth post-visit page identification set.

And eighthly, sequencing the fourth post-visit page identifier set according to the number of each fourth post-visit page identifier in the fourth post-visit page identifier set included in the third post-visit page identifier set to obtain a fourth post-visit page identifier sequence. In practice, the execution body may perform descending order processing on the third backward access page identifier set according to a descending order of the number of each fourth backward access page identifier in the fourth backward access page identifier set included in the third backward access page identifier set, so as to obtain a fourth backward access page identifier sequence.

And a ninth step of sequentially selecting a second number of fourth backward visit page identifiers from the fourth backward visit page identifier sequence as a second recommended backward visit page identifier set according to a second target mode, wherein the second target mode can be a front-to-back mode. Here, the second target mode may be the same as the first target mode or may be different from the first target mode. The first target mode and the second target mode are determined according to the mode of the sorting process. When the sorting process is an ascending process, the first target mode and the second target mode are from back to front. When the sorting processing is descending processing, the first target mode and the second target mode are from front to back. In practice, the execution subject may sequentially select a second number of fourth backward page identifiers from the fourth backward page identifier sequence as a second recommended backward page identifier set in a front-to-back manner. The second number is less than or equal to the number of the fourth backward page identifiers included in the fourth backward page identifier sequence. Here, the specific setting of the second number is not limited.

And step ten, combining the second recommended post-visit page identification set and the second configuration tag to obtain second recommended post-visit page information. The second configuration tag may be a tag used for representing that each second recommended post-visit page identifier in the second recommended post-visit page identifier set is a tag with a large number of last visits of the user in the page corresponding to the page request. In practice, the execution subject may perform splicing combination on the second recommended post-visit page identifier set and the second configuration tag to obtain a character string after the splicing combination as second recommended post-visit page information. For example, the second set of recommended post-visit page identifications may be [6 ]. The first configuration tab may be "identification of the page with the most last access". The second recommended post-visit page information may be "an identifier of a page with the largest number of last visits: [6]".

The execution main body may combine the second recommended post-visit page identifier set and the second configuration tag to obtain second recommended post-visit page information by the following substeps:

and a first substep of selecting page operation information corresponding to the second recommended post-visit page identifier from each page operation information set included in the historical page access information set as second page operation information according to each second recommended post-visit page identifier in the second recommended post-visit page identifier set to obtain a second page operation information set. And the page operation information corresponding to the second recommended post-visit page identifier is the page operation information representing the page which is jumped to the second recommended post-visit page identifier.

And a second substep, combining the second recommended post-visit page identification set, the second page operation information set and the second configuration tag to obtain second recommended post-visit page information. In practice, the execution subject may perform splicing and combination on the second recommended post-visit page identifier set, the second page operation information set, and the second configuration tag, and obtain a character string after splicing and combination as second recommended post-visit page information. For example, the second set of recommended post-visit page identifications may be [6 ]. The second page operation information set may be button. Wherein the button corresponds to the second recommended post-visit page identifier 6. The second configuration tab may be "identification of the page with the most last access". The second recommended post-visit page information may be "an identifier of a page with the largest number of last visits: [6] and button.

Through the sixth step to the tenth step, the generated second recommended post-visit page information may include both the page that is last visited in the page corresponding to the page request and the operation related information when the page is visited, which characterize the user, that is, the second recommended post-visit page identifier set and the second page operation information set.

And 305, performing recommended post-visit page configuration on the page file corresponding to the page request according to the at least one piece of recommended post-visit page information to obtain a recommended page file.

In some embodiments, the executing entity may perform recommended post-visit page configuration on the page file corresponding to the page request according to the at least one piece of recommended post-visit page information, to obtain a recommended page file, through the following steps:

in a first step, for each first recommended post-visit page identifier included in the first recommended post-visit page information, the execution main body may use first page operation information corresponding to the first recommended post-visit page identifier in the first page operation information set as target first page operation information, and add a page link control corresponding to the first recommended post-visit page identifier and the target first page operation information in the page file according to the first configuration tag. In practice, a code of a page link control corresponding to the first recommended post-visit page identifier and the target first page operation information may be added to the code block of the first container corresponding to the first configuration tag.

As an example, the first configuration tab may be "identification of the page with the largest number of first accesses". The code block of the first container may be "< div > < h1> the page 1> </div >" with the largest number of access times at first. The first recommended post-visit page identification may be 5. The first page operation information corresponding to the first recommended subsequent page identifier may be "button". The added code may be "< div > < h1> page </h1> < a href =" https:// yyy.com/YYY/yy.html "> < button > click jump to page 5 > </a > </div >" with the largest number of first accesses. Wherein "https:// YYY.com/YYY/YYY.html" is the web address corresponding to the target post-visit page identifier 5.

And secondly, for each second recommended post-visit page identifier included in the second recommended post-visit page information, the execution subject may use second page operation information corresponding to the second recommended post-visit page identifier in the second page operation information set as target second page operation information, and add a page link control corresponding to the second recommended post-visit page identifier and the target second page operation information in the obtained added page file according to the second configuration tag. In practice, a code of a page link control corresponding to the second recommended visited page identifier and the target second page operation information may be added to the code block of the second container corresponding to the second configuration tag.

As an example, the second configuration tab may be "identification of page with the largest number of last accesses". The code block of the second container may be "< div > < h1> the page </h1> </div >" having the largest number of last accesses. The second recommended post-visit page identification may be 6. The second page operation information corresponding to the second recommended post-visit page identifier may be "button". The added code may be "< div > < h1> page </h1> < a href =" https:// xxx.com/XXX/xxx.html "> < button > click jump to page 6</button > </a > </div >" with the most number of last accesses. Wherein "https:// XXX.com/XXX/XXX.html" is the web address corresponding to the target post-visit page identifier 6.

And thirdly, determining the added page file as a recommended page file.

Through the step 305, the related control for accessing the recommended backward page with the higher number of the first access times and the related control for accessing the recommended backward page with the higher number of the last access times can be configured in the page file corresponding to the page request according to the first recommended backward page identifier set with the higher number of the first access times, the first page operation information set, and the second recommended backward page identifier set with the higher number of the last access times and the second page operation information set.

Step 302 and step 305 are taken as an inventive point of the embodiment of the present disclosure, and solve the technical problem two mentioned in the background art, "the link control for accessing the frequently accessed page cannot be configured according to the page operation when the user previously accesses the frequently accessed page, which results in that the user needs to know the path for accessing the frequently accessed page for a long time in the current page, and the operation time for browsing the frequently accessed page by the user is wasted". Factors that cause a waste of operation time for a user to browse frequently visited pages are often as follows: the inability to configure the link control for accessing a frequently accessed page based on the page operations when the user previously accessed the frequently accessed page results in the user needing to know the way to access the frequently accessed page for a longer period of time in the current page. If the above factors are solved, the effect of saving the operation time of the user for browsing frequently accessed pages can be achieved. In order to achieve the effect, according to each post-visit page identifier in the post-visit page identifier sequence, the page operation analysis processing is performed on the page embedded point log, so that a page operation information set is obtained. Thus, the page control type of the user when visiting the later page can be determined. Therefore, according to the operation of jumping to a later-visited page by a user, page link controls for visiting the page with the first visit times and page link controls for visiting the page with the last visit times are configured in the page file corresponding to the current page request. And furthermore, the time that the user needs to know the path of accessing the page with more first access times or last access times in the page corresponding to the current page request can be reduced, and the operation time of the user for browsing frequently accessed pages is saved.

And step 306, sending the recommended page file to the user terminal.

In some embodiments, the specific implementation of step 306 and the technical effect thereof may refer to step 205 in those embodiments corresponding to fig. 2, and are not described herein again.

Step 307, in response to receiving a post-visit page request corresponding to any added page link control sent by the user terminal, sending a page file of a post-visit page identifier corresponding to the post-visit page request to the user terminal.

In some embodiments, the execution subject may send, to the user terminal, a page file of a visited page identifier corresponding to the visited page request in response to receiving a visited page request corresponding to any added page link control sent by the user terminal. The page link control of the page file is used for controlling the page link control of the page file to be displayed, and the page link control of the page file is used for controlling the page link control of the page file to be displayed. Therefore, after a post-visit page request corresponding to the page link control is received, the page file of the post-visit page identification corresponding to the page link control is sent to the user terminal, and the user terminal renders a page in the display screen according to the received page file again.

As can be seen from fig. 3, compared with the description of some embodiments corresponding to fig. 2, the flow 300 of the recommended page configuration method in some embodiments corresponding to fig. 3 embodies steps extended to configure a pagefile according to page operation information. Therefore, the solutions described in the embodiments can reduce the time that the user needs to know the way of accessing the page with the higher number of first accesses or the page with the higher number of last accesses in the page corresponding to the current page request, and save the operation time of the user for browsing the frequently accessed pages.

With further reference to fig. 4, as an implementation of the methods shown in the above figures, the present disclosure provides some embodiments of a recommendation page configuring apparatus, which correspond to those shown in fig. 2, and which may be specifically applied in various electronic devices.

As shown in fig. 4, the recommendation page configuring apparatus 400 of some embodiments includes: acquisition section 401, analysis section 402, generation section 403, configuration section 404, and transmission section 405. The obtaining unit 401 is configured to, in response to receiving a page request sent by a user terminal, obtain a page embedded point log corresponding to the user terminal and a target page identifier, where the page embedded point log includes each access anchor identifier, and the target page identifier corresponds to the page request; the parsing unit 402 is configured to parse the page buried point log according to each of the access anchor identifiers to generate historical page access information, so as to obtain a historical page access information set, where the historical page access information includes a post-visit page identifier sequence corresponding to the target page identifier; the generating unit 403 is configured to generate at least one piece of recommended backward visit page information based on the backward visit page identifiers in each backward visit page identifier sequence included in the historical page visit information set; the configuration unit 404 is configured to perform recommended post-visit page configuration on the page file corresponding to the page request according to the at least one piece of recommended post-visit page information, so as to obtain a recommended page file; the transmitting unit 405 is configured to transmit the recommended page file to the user terminal.

It will be understood that the elements described in the apparatus 400 correspond to various steps in the method described with reference to fig. 2. Thus, the operations, features and resulting advantages described above with respect to the method are also applicable to the apparatus 400 and the units included therein, and will not be described herein again.

Referring now to FIG. 5, a block diagram of an electronic device (e.g., computing device 101 of FIG. 1) 500 suitable for use in implementing some embodiments of the present disclosure is shown. The electronic device shown in fig. 5 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 5, electronic device 500 may include a processing means (e.g., central processing unit, graphics processor, etc.) 501 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM) 502 or a program loaded from a storage means 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data necessary for the operation of the electronic apparatus 500 are also stored. The processing device 501, the ROM 502, and the RAM 503 are connected to each other through a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.

Generally, the following devices may be connected to the I/O interface 505: input devices 506 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 507 including, for example, a Liquid Crystal Display (LCD), speakers, vibrators, and the like; storage devices 508 including, for example, magnetic tape, hard disk, etc.; and a communication device 509. The communication means 509 may allow the electronic device 500 to communicate with other devices wirelessly or by wire to exchange data. While fig. 5 illustrates an electronic device 500 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided. Each block shown in fig. 5 may represent one device or may represent multiple devices as desired.

In particular, according to some embodiments of the present disclosure, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, some embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In some such embodiments, the computer program may be downloaded and installed from a network via the communication means 509, or installed from the storage means 508, or installed from the ROM 502. The computer program, when executed by the processing device 501, performs the above-described functions defined in the methods of some embodiments of the present disclosure.

It should be noted that the computer readable medium described in some embodiments of the present disclosure may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In some embodiments of the disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In some embodiments of the present disclosure, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.

The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: responding to a received page request sent by a user terminal, and acquiring a page embedded point log corresponding to the user terminal and a target page identifier, wherein the page embedded point log comprises each access anchor identifier, and the target page identifier corresponds to the page request; analyzing the page buried point log according to each access anchor mark in the access anchor marks to generate historical page access information to obtain a historical page access information set, wherein the historical page access information comprises a post-visit page mark sequence corresponding to the target page mark; generating at least one piece of recommended backward visit page information based on the backward visit page identifiers in each backward visit page identifier sequence included in the historical page access information set; according to the at least one piece of recommended post-visit page information, performing recommended post-visit page configuration on a page file corresponding to the page request to obtain a recommended page file; and sending the recommended page file to the user terminal.

Computer program code for carrying out operations for embodiments of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in some embodiments of the present disclosure may be implemented by software, and may also be implemented by hardware. The described units may also be provided in a processor, and may be described as: a processor includes an acquisition unit, an analysis unit, a generation unit, a configuration unit, and a transmission unit. The names of these units do not form a limitation on the unit itself in some cases, for example, the obtaining unit may also be described as a unit for obtaining a page burial point log corresponding to the user terminal and the target page identifier in response to receiving a page request sent by the user terminal.

The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.

The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention in the embodiments of the present disclosure is not limited to the specific combination of the above-mentioned features, but also encompasses other embodiments in which any combination of the above-mentioned features or their equivalents is made without departing from the inventive concept as defined above. For example, the above features and (but not limited to) technical features with similar functions disclosed in the embodiments of the present disclosure are mutually replaced to form the technical solution.

Claims

1. A recommendation page configuration method comprises the following steps:

responding to a received page request sent by a user terminal, and acquiring a page embedded point log corresponding to the user terminal and a target page identifier, wherein the page embedded point log comprises each access anchor identifier, and the target page identifier corresponds to the page request;

analyzing the page buried point log according to each access anchor mark in the access anchor marks to generate historical page access information to obtain a historical page access information set, wherein the historical page access information comprises a post-visit page mark sequence corresponding to the target page mark;

generating at least one piece of recommended post-visit page information based on post-visit page identifications in each post-visit page identification sequence included in the historical page access information set, wherein each piece of recommended post-visit page information in the at least one piece of recommended post-visit page information comprises at least one target post-visit page identification, and each target post-visit page identification in the at least one target post-visit page identification is a post-visit page identification arranged at the head or the tail of the corresponding post-visit page identification sequence;

according to the at least one piece of recommended post-visit page information, performing recommended post-visit page configuration on the page file corresponding to the page request to obtain a recommended page file, wherein the performing recommended post-visit page configuration on the page file corresponding to the page request comprises:

for each piece of recommended post-visit page information in the at least one piece of recommended post-visit page information, adding a page link control corresponding to each target post-visit page identifier included in the recommended post-visit page information into the page file, so that each configured page link control is fixedly displayed on the page when the page corresponding to the page file is displayed at a terminal;

and sending the recommended page file to the user terminal.

2. The method of claim 1, wherein the parsing the page burial point log to generate historical page access information comprises:

according to each post-visit page identifier in the post-visit page identifier sequence, performing page operation analysis processing on the page embedded point log to obtain a page operation information set;

generating historical page access information based on the post-visit page identification sequence and the page operation information set, wherein the historical page access information comprises the page operation information set.

3. The method of claim 2, wherein the generating at least one piece of recommended backward page information based on the backward page identifier in each backward page identifier sequence included in the historical page access information set comprises:

extracting a first backward visit page identifier arranged at the head of each backward visit page identifier sequence from each backward visit page identifier sequence to serve as a first backward visit page identifier, and obtaining a first backward visit page identifier set;

performing duplicate removal processing on the first post-visiting page identification set to obtain the first post-visiting page identification set subjected to duplicate removal processing as a second post-visiting page identification set;

sequencing the second post-visiting page identifier sets according to the number of each second post-visiting page identifier in the second post-visiting page identifier sets included in the first post-visiting page identifier sets to obtain second post-visiting page identifier sequences;

according to a first target mode, sequentially selecting a first number of second post-visit page identifications from the second post-visit page identification sequence as a first recommended post-visit page identification set;

and combining the first recommended post-visit page identification set and the first configuration tag to obtain first recommended post-visit page information.

4. The method of claim 3, wherein the combining the first recommended post-visit page identification set and the first configuration tag to obtain first recommended post-visit page information comprises:

according to each first recommended post-visit page identifier in the first recommended post-visit page identifier set, selecting page operation information corresponding to the first recommended post-visit page identifier from all page operation information sets in the historical page access information set as first page operation information to obtain a first page operation information set;

and combining the first recommended post-visit page identification set, the first page operation information set and the first configuration tag to obtain first recommended post-visit page information.

5. The method of claim 4, wherein the generating at least one piece of recommended backward page information based on the backward page identifier in each backward page identifier sequence included in the historical page access information set comprises:

extracting a post-visiting page identifier arranged at the last position from each post-visiting page identifier sequence in each post-visiting page identifier sequence as a third post-visiting page identifier to obtain a third post-visiting page identifier set;

performing duplicate removal processing on the third post-visit page identification set to obtain a third post-visit page identification set subjected to duplicate removal processing as a fourth post-visit page identification set;

sequencing the fourth post-visit page identifier sets according to the number of each fourth post-visit page identifier in the fourth post-visit page identifier sets included in the third post-visit page identifier sets to obtain fourth post-visit page identifier sequences;

according to a second target mode, sequentially selecting a second number of fourth post-visiting page identifications from the fourth post-visiting page identification sequence as a second recommended post-visiting page identification set;

and combining the second recommended post-visit page identification set and a second configuration tag to obtain second recommended post-visit page information.

6. The method of claim 5, wherein the combining the second recommended post-visit page identification set and the second configuration tag to obtain second recommended post-visit page information comprises:

selecting page operation information corresponding to the second recommended post-visit page identification from all page operation information sets included in the historical page access information set as second page operation information according to each second recommended post-visit page identification in the second recommended post-visit page identification set to obtain a second page operation information set;

and combining the second recommended post-visit page identification set, the second page operation information set and the second configuration tag to obtain second recommended post-visit page information.

7. The method of claim 6, wherein the performing, according to the at least one piece of recommended post-visit page information, recommended post-visit page configuration on the page file corresponding to the page request to obtain a recommended page file comprises:

for each first recommended post-visit page identifier included in the first recommended post-visit page information, taking first page operation information corresponding to the first recommended post-visit page identifier in the first page operation information set as target first page operation information, and adding a page link control corresponding to the first recommended post-visit page identifier and the target first page operation information in the page file according to the first configuration tag;

for each second recommended post-visit page identifier included in the second recommended post-visit page information, taking second page operation information corresponding to the second recommended post-visit page identifier in the second page operation information set as target second page operation information, and adding a page link control corresponding to the second recommended post-visit page identifier and the target second page operation information in the obtained added page file according to the second configuration tag;

and determining the obtained added page file as a recommended page file.

8. The method of claim 7, wherein the method further comprises:

and responding to a received post-visit page request which is sent by the user terminal and corresponds to any added page link control, and sending a page file of a post-visit page identifier corresponding to the post-visit page request to the user terminal.

9. A recommendation page configuring apparatus comprising:

the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is configured to respond to a received page request sent by a user terminal and acquire a page buried point log corresponding to the user terminal and a target page identifier, the page buried point log comprises each access anchor identifier, and the target page identifier corresponds to the page request;

the analysis unit is configured to analyze the page buried point log according to each access anchor point identifier in the access anchor point identifiers to generate historical page access information to obtain a historical page access information set, wherein the historical page access information comprises a post-visit page identifier sequence corresponding to the target page identifier;

a generating unit configured to generate at least one piece of recommended backward visit page information based on backward visit page identifiers in each backward visit page identifier sequence included in the historical page access information set, wherein each piece of recommended backward visit page information in the at least one piece of recommended backward visit page information includes at least one target backward visit page identifier, and each target backward visit page identifier in the at least one target backward visit page identifier is a backward visit page identifier arranged at the head or the tail of the corresponding backward visit page identifier sequence;

a configuration unit, configured to perform recommended post-visit page configuration on the page file corresponding to the page request according to the at least one piece of recommended post-visit page information, to obtain a recommended page file, where the performing recommended post-visit page configuration on the page file corresponding to the page request includes:

a transmitting unit configured to transmit the recommended page file to the user terminal.

10. An electronic device, comprising:

one or more processors;

a storage device having one or more programs stored thereon,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-8.

11. A computer-readable medium, on which a computer program is stored, wherein the program, when executed by a processor, implements the method of any one of claims 1-8.