CN116132419A

CN116132419A - Page generation method and device, electronic equipment and storage medium

Info

Publication number: CN116132419A
Application number: CN202211466830.4A
Authority: CN
Inventors: 张亚涛
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2022-11-22
Filing date: 2022-11-22
Publication date: 2023-05-16

Abstract

The disclosure provides a method, a device, electronic equipment and a storage medium for page generation, relates to the technical field of computers, and particularly relates to the technical fields of cloud service technology, data transmission technology and the like. The specific implementation scheme is as follows: the edge node acquires page request information of a designated page sent by a client; acquiring page content of the appointed page according to the page request information; wherein, the page content has association relation with the page request information; and assembling the designated page according to the page content so as to output the assembled designated page to the client.

Description

Page generation method and device, electronic equipment and storage medium

Technical Field

The disclosure relates to the technical field of computers, in particular to the technical fields of cloud service technology, data transmission technology and the like, and particularly relates to a method, a device, electronic equipment and a storage medium for page generation.

Background

With the popularity of web page (web) application services and the hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP) protocol, the HTTP protocol is preferred for information interaction in an increasing number of text content interaction scenarios. Among these, the most widely used and richest application scenarios are web site services. The web site service is typically comprised of a plurality of cross-regional internet data centers (Internet Data Center, IDC).

Disclosure of Invention

The disclosure provides a method, a device, electronic equipment and a storage medium for page generation.

According to an aspect of the present disclosure, there is provided a method of page generation, applied to an edge node, including:

acquiring page request information of a designated page sent by a client;

acquiring page content of the appointed page according to the page request information; wherein, the page content has association relation with the page request information;

and assembling the designated page according to the page content so as to output the assembled designated page to the client.

According to another aspect of the present disclosure, there is provided an apparatus for generating a page, provided at an edge node, including:

the request acquisition unit is used for acquiring page request information of a designated page sent by the client;

the content acquisition unit is used for acquiring the page content of the designated page according to the page request information; wherein, the page content has association relation with the page request information;

and the page output unit is used for assembling the specified page according to the page content so as to output the assembled specified page to the client.

According to still another aspect of the present disclosure, there is provided an electronic apparatus including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein, the liquid crystal display device comprises a liquid crystal display device,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the aspects and methods of any one of the possible implementations described above.

According to yet another aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the method of the aspects and any possible implementation described above.

According to a further aspect of the present disclosure there is provided a computer program product comprising a computer program which, when executed by a processor, implements the method of the aspects and any one of the possible implementations described above.

According to the technical scheme, the page request information of the designated page sent by the client can be obtained through the edge node, and further, the page content of the designated page can be obtained according to the page request information, and the page content and the page request information have an association relation, so that the designated page can be assembled according to the page content, the assembled designated page can be output to the client, and the page request information sent by the client can be directly processed through the edge node to assemble and generate the page content corresponding to the page request information, so that the response time of page loading is shortened, the influence of a traditional web server on service deployment efficiency is reduced to a certain extent, and the efficiency and reliability of page generation are improved.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.

Drawings

The drawings are for a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

FIG. 1 is a schematic diagram according to a first embodiment of the present disclosure;

FIG. 2 is a schematic diagram according to a second embodiment of the present disclosure;

fig. 3 is a schematic diagram of an architecture of an edge node according to a second embodiment of the present disclosure;

fig. 4 is a schematic diagram of an application scenario of a method of page generation according to a second embodiment of the present disclosure;

FIG. 5 is a schematic diagram according to a third embodiment of the present disclosure;

fig. 6 is a block diagram of an electronic device for implementing a method of page generation of an embodiment of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

It will be apparent that the described embodiments are some, but not all, of the embodiments of the present disclosure. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments in this disclosure without inventive faculty, are intended to be within the scope of this disclosure.

It should be noted that, the terminal device in the embodiments of the present disclosure may include, but is not limited to, smart devices such as a mobile phone, a personal digital assistant (Personal Digital Assistant, PDA), a wireless handheld device, and a Tablet Computer (Tablet Computer); the display device may include, but is not limited to, a personal computer, a television, or the like having a display function.

In addition, the term "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

With the popularity of web application services and HTTP protocols, the HTTP protocol is preferentially selected to be used for information interaction in more and more text content interaction scenes, wherein the most wide application scene is also the most abundant web site service.

Currently, typically during page generation, when a web page is requested in a browser or other web container, an HTTP request is sent that falls onto a conventional centralized web server after domain name system (Domain Name System, DNS) DNS resolution and a series of load balancing. While web servers are typically made up of multiple cross-regional IDCs, it is still central to the conceptual understanding of the system, and the tasks of the different IDC bearers are different, there will be some redundant IDC designs for disaster recovery. Regardless of the country and region in which the user is located, these requests are forwarded to the same Gateway portal (Gateway), which is then responsible for forwarding the requests to the web server in the downstream IDC. Therefore, with the continuous expansion of the number of users and the service scenario, the pressure borne by the web server in the IDC is more and more, and the problem of overlong response time may exist, so that the user experience is poor. Moreover, the flexible service for users in different areas cannot be satisfied, and the aim of reducing the central service pressure and simultaneously not influencing the waiting time of the users cannot be achieved.

Therefore, it is needed to provide a method for generating a page, which can shorten the response time of page loading and improve the speed and reliability of page rendering generation.

Fig. 1 is a schematic diagram according to a first embodiment of the present disclosure, as shown in fig. 1.

101. And acquiring page request information of the designated page sent by the client.

102. Acquiring page content of the appointed page according to the page request information; and the page content and the page request information have an association relation.

103. And assembling the designated page according to the page content so as to output the assembled designated page to the client.

It should be noted that, steps 101 to 103 may be performed by the edge node.

It should be noted that the specified page may include a browser-based page opened by the user. In response to a user opening operation of the specified page, the edge node may acquire page request information of the specified page from the client.

The execution bodies 101 to 103 may be part or all of the applications on the terminal side, or may be functional units such as plug-ins or software development kits (Software Development Kit, SDKs) provided in the applications on the terminal side, or may be processing engines in servers on the network side, or may be distributed systems on the network side, for example, processing engines or distributed systems in a page processing platform on the network side, which is not particularly limited in this embodiment.

In this way, the edge node can acquire the page request information of the designated page sent by the client, and further, the page content of the designated page can be acquired according to the page request information, and the page content and the page request information have an association relationship, so that the designated page can be assembled according to the page content, and the assembled designated page can be output to the client.

Optionally, in one possible implementation manner of this embodiment, the page request information may specifically include a container identifier, and the page content may specifically include the first page content. In 102, the first page content may be obtained according to the container identifier.

In this implementation, container identification may be used to identify static information for a page. The container identification may include HTTP path information specifying the page.

In this implementation, the first page content, i.e., static information of the page, may include container style information and container content information.

In particular, the container style information may include static style information for the page. For example, the style of the region of the title, list, etc. in the page.

In particular, the container content information may include static content information for the page. For example, specific text, pictures, videos, etc. of the title, list, etc. areas in the page.

In a specific implementation of this implementation, in 103, the specified page may be assembled specifically according to the container style information and the container content information.

In this way, when the page request information includes the container identifier, the edge node can obtain the container style information and the container content information of the first page content according to the container identifier, and further directly assemble the designated page according to the container style information and the container content information.

Optionally, in one possible implementation manner of this embodiment, the page request information includes a container identifier and at least one content block identifier, where the page content includes a first page content and a second page content, and in 102, the first page content may be specifically acquired according to the container identifier, and the second page content may be acquired according to at least one content block identifier, so as to obtain the page content according to the first page content and the second page content.

In this implementation, the page request information includes a container identification and at least one content block identification. The container identification may be used to identify static information for the page. The container identification may specifically include HTTP path information specifying the page.

In particular, content chunk identification, i.e., content segment ID, may be used to identify dynamic information for a page. The content chunk identification may include, but is not limited to, chunk identification ID, user identification ID, zone identification ID, and the like. For example, the content chunk ID is 1.2.3, the chunk ID is 1, the user ID is 2, and the region ID is 3.

In particular, a page may comprise at least one content block, each content block comprising dynamic information of the page. Each content chunk has a corresponding content chunk identification.

In this implementation, the page content includes a first page content and a second page content.

In particular, the first page content may include container style information and container content information. The container style information may include static style information for the page. For example, the style of the region of the title, list, etc. in the page. The container content information may include static content information for the page. For example, the container content information may include, but is not limited to, specific text, pictures, videos, etc. of the title, list, etc. areas in the page.

In particular, the second page content may include at least one piece of content block information. The content block information may include dynamic information of the page. For example, content chunk information may include, but is not limited to, dynamic lists in pages, user avatars, product information recommended to users, and the like.

In a specific implementation of this implementation, in 103, the acquired content block information may be specifically determined according to the acquisition situation of the second page content, and the specified page may be assembled according to the first page content and the acquired content block information.

In this specific implementation process, because the multiple pieces of content block information related to each page have different loading durations of different pieces of content block information, the obtaining condition of the second page content may include additionally obtaining each piece of content block information and directly obtaining all pieces of content block information.

In one aspect of the specific implementation process, the acquiring condition of the second page content is that each piece of content block information is additionally acquired, the acquired piece of content block information can be determined first, then the designated page can be assembled according to the first page content and the acquired piece of content block information, so that the assembled designated page can be sent to the client, the piece of content block information can be additionally acquired, namely, the piece of content block information which is not acquired before is acquired, and the acquired new piece of content block information is additionally sent to the client until the display of the whole designated page is completed.

Specifically, the acquired new content block information may be additionally transmitted to the client using a response addition mode of the HTTP protocol.

In another case in the specific implementation process, the second page content acquiring condition is that all content block information is directly acquired, and the designated page can be assembled according to the container style information and the container content information in the first page content and all acquired content block information, so that the assembled page can be sent to the client.

In this way, when the page request information includes the container identifier and at least one content block identifier, the edge node may obtain the first page content according to the container identifier, obtain the second page content including at least one content block information according to the at least one content block identifier, further determine the obtained content block information according to the obtaining condition of the second page content, and assemble the specified page according to the first page content and the obtained content block information.

Moreover, by continuously assembling the designated pages according to the acquisition condition of the second page content, the response time for generating the complex page with more dynamic content information can be effectively shortened, and the page generation efficiency is further improved.

Optionally, in one possible implementation manner of this embodiment, in 102, a storage location of the page content corresponding to the page request information may be further determined by using a preconfigured index table according to the page request information, and the page content of the specified page may be acquired according to the storage location.

In this implementation, the preconfigured index table may include a correspondence of page request information and a storage location of page content.

Specifically, the correspondence between different page contents and the storage medium may be preconfigured, that is, the storage location of the page contents is determined. Meanwhile, the corresponding relation between the page request information and the page content can be preconfigured. Based on the two corresponding relations, a preconfigured index table can be obtained.

In one specific implementation of this implementation, the page request information includes a container identification, and the page content includes first page content. And determining the storage position of the page content corresponding to the container identifier by utilizing a preconfigured index table according to the container identifier, and acquiring the first page content, namely the page content of the specified page according to the storage position.

In one specific implementation of this implementation, the page request information includes a container identification, and the page content includes first page content. The storage position of the first page content corresponding to the container identifier can be determined by utilizing a preconfigured index table according to the container identifier, and the first page content is acquired according to the storage position.

Here, the first page content is the page content of the specified page. The first page content may specifically include static information of the page.

In this particular implementation, the storage locations of the first page content, i.e., static information of the page, may include, but are not limited to, edge node local servers and cloud object storage servers.

In another specific implementation of this implementation, the page request information includes a container identification and at least one content block identification, and the page content includes a first page content and a second page content. The storage position of the first page content corresponding to the container identifier and the storage position of the second page content corresponding to each content block identifier can be determined by utilizing a preconfigured index table according to the container identifier and at least one content block identifier, the first page content is acquired according to the storage position of the first page content, and the second page content is acquired according to the storage position of the second page content.

Here, the first page content and the second page content are page contents of a specified page. The first page content may specifically include static information of the page. The second page content may include dynamic information of the page.

In this particular implementation, the storage locations of the first page content may include, but are not limited to, edge node local servers and cloud object storage servers.

The storage locations of the second page content may include, but are not limited to, cloud function servers and traditional web servers.

In one case of this specific implementation, the second page content includes content that varies irregularly but does not depend on a large amount of background data, and the storage location of such content may be a cloud function server.

In another aspect of this particular implementation, the second page content includes content that requires reliance on a large amount of background data, where such content may be stored in a conventional web server.

Therefore, the storage position of the page content corresponding to the page request information can be determined by the edge node through the pre-configured index table, and further, the page content of the designated page is acquired according to the storage position, so that the efficiency and the accuracy of acquiring the page content can be improved, and the efficiency and the reliability of generating the page are further improved.

It should be noted that, the method for generating a page may be implemented by combining multiple specific implementation procedures provided in the foregoing implementation manner with multiple specific implementation procedures for acquiring page content provided in the present implementation manner. The detailed description may refer to the relevant content in the foregoing implementation, and will not be repeated here.

Optionally, in one possible implementation manner of this embodiment, before 102, authentication processing may be further performed according to a preset permission rule and the page request information, so as to obtain an authentication result; and determining whether to acquire the page content of the appointed page according to the authentication result.

In an implementation, the preset permission rule may include a user level corresponding to the page content. The user viewable page content is different for different user levels.

In another specific implementation process of the implementation manner, according to the page request information, user information of the page is obtained, and then whether the user meets a user grade of viewing page content of the page or not can be judged according to a preset permission rule, if yes, the page content of the appointed page can be obtained, the subsequent operation is continuously executed, if not, rollback is executed, and prompt information, for example, prompt information for prompting the user to log in or pay reminding, is sent to the user.

For example, the user level may include a super member and a general member, the page content presented to the super member may be different from the page content presented to the general member, and some of the page content may be unviewable by the general member and may need to be upgraded to the super member for viewing.

Therefore, the authority of the user can be judged according to the user grade required by the page request and the grade of the user who requests the page, the page content corresponding to the grade is provided for the user, the corresponding page content is provided for users with different user grades, the pertinence and individuation of the page content service are improved, and the reliability of the generated page is further improved.

It should be noted that, the method for generating a page may be implemented by combining various specific implementation procedures provided in the foregoing implementation manner with various specific implementation procedures provided in the present implementation manner for determining whether to acquire page content. The detailed description may refer to the relevant content in the foregoing implementation, and will not be repeated here.

Alternatively, in one possible implementation manner of the present embodiment, in 101, page request information of a specified page resolved by DNS may be specifically acquired.

In this implementation, first, the DNS may be used to analyze page request information of a specified page sent by the client. And then, according to the space-time distance between the edge node and the client side and the traffic pressure of the edge node, sending the page request information to the corresponding edge node so that the edge node can acquire the page request information.

In this way, through the analysis of the DNS on the page request information, the page request can be sent to the edge node with the optimal space-time distance and traffic pressure, so that the edge node can provide subsequent page generation service, and the reliability and efficiency of page generation are further improved.

It will be appreciated that other existing manners may be utilized to obtain the page request information, and the method is not limited in this regard.

It should be noted that, the method for generating a page may be implemented by combining various specific implementation procedures provided in the foregoing implementation manner with the manner of obtaining the page request information of the specified page provided in the present implementation manner. The detailed description may refer to the relevant content in the foregoing implementation, and will not be repeated here.

In this embodiment, the edge node may obtain the page request information of the designated page sent by the client, and further may obtain, according to the page request information, the page content of the designated page, where the page content has an association relationship with the page request information, so that the designated page may be assembled according to the page content, so as to output the assembled designated page to the client.

In addition, by adopting the technical scheme provided by the embodiment, when the page request information comprises the container identifier, the edge node can acquire the container style information and the container content information of the first page content according to the container identifier, and further directly assemble the designated page according to the container style information and the container content information.

In addition, by adopting the technical scheme provided by the embodiment, when the page request information comprises the container identifier and at least one content block identifier, the edge node can acquire the first page content according to the container identifier, acquire the second page content comprising at least one content block information according to the at least one content block identifier, further determine the acquired content block information according to the acquisition condition of the second page content, and assemble the designated page according to the first page content and the acquired content block information.

Moreover, the appointed page is continuously assembled according to the acquisition condition of the second page content, so that the response time for generating the complex page with more dynamic content information can be effectively shortened, and the page generation efficiency is further improved.

In addition, by adopting the technical scheme provided by the embodiment, the storage position of the page content corresponding to the page request information can be determined by the edge node through the pre-configured index table, and further, the page content of the designated page is acquired according to the storage position, so that the efficiency and the accuracy of acquiring the page content can be improved, and the efficiency and the reliability of generating the page are further improved.

In addition, by adopting the technical scheme provided by the embodiment, the authority of the user can be judged according to the user grade required by the request page and the grade of the user who requests the page, and the page content corresponding to the grade is provided for the user, so that the corresponding page content is provided for users with different user grades, the pertinence and individuation of the page content service are improved, and the reliability of the generated page is further improved.

Fig. 2 is a schematic diagram, as shown in fig. 2, according to a second embodiment of the present disclosure.

In this embodiment, fig. 3 is a schematic diagram of an architecture of an edge node according to a second embodiment of the present disclosure. As shown in fig. 3, after receiving the page request, the edge node 309 may perform request authentication 301, and if the request meets the requirement, may perform acquisition of content information 302, specifically may acquire static content information from the cloud object storage service 304 through the cache service 303, and may continuously acquire dynamic content information, that is, content block information 307, from the cloud function service 305 and/or the web service 306. Then, the content information 308 is assembled, that is, the page corresponding to the page request is assembled according to the acquired static content information and dynamic content information. Finally, the assembled page is sent to the client or web container. If the authentication request results are not in accordance with the requirements, the return operation can be executed, and prompt information is directly sent to the client.

Further, it is understood that the edge node 309 may be provided on the basis of the original conventional centralized web service 310, as shown in fig. 3.

The method of page generation in this embodiment will now be described in detail with reference to fig. 2 and 3.

201. And acquiring page request information.

In this implementation, the page request information may include, but is not limited to, a container identification and at least one content block identification.

In particular, the number of information identifications for a single page may be one or more. If the number is one, the information identifier is the container identifier. If multiple, the information identity may be a container identity and at least one content block identity.

Here, the container identification may be HTTP path information of the current request page.

202. And carrying out authentication processing according to a preset authority rule and page request information to determine whether to acquire corresponding page contents.

Specifically, if yes, execution 203 is continued, and if not, a "fallback" logic is executed, and a prompt message is sent to the client to prompt the user of the client.

In particular, different page content may correspond to different user ratings, which also means different presentation content. Therefore, the user identity can be judged according to the preset permission rule and the acquired page request information.

Illustratively, when page request information of a user is received at an edge node, a judgment is made according to a required user level of the requested page and a user level of the current request of the page, if the requirement is met, a subsequent logic is normal, otherwise, a 'fallback' logic is executed. For example, the user may be prompted to log in or pay for a reminder.

203. And acquiring static information of the page according to the container identification in the page request information.

204. And acquiring dynamic information of the page according to at least one content block identifier in the page request information, wherein the dynamic information of the page comprises at least one content block information.

In this implementation, page content can be divided into two categories: one type is static content information which does not change frequently, namely static information of pages; the content information of blocks in a certain part of the page in another type is changed frequently, namely the dynamic information of the page.

Here, the static information of the page, i.e., the first page content, may include container style information and container content information. The dynamic information of the page, i.e. the second page content, may comprise at least one content block information. The content block information may also become a content clip.

In this embodiment, on the one hand, the information identifier in the page request information, that is, the correspondence between the container identifier and the at least one content block identifier and the page content, may be pre-established.

Specifically, the corresponding relation between the information identification in the page request information and the page content is established in the development and compiling stage, and the corresponding relation is marked by a specified format, wherein the specified format can comprise JSON or XML. Then, the corresponding relation is serialized into a formulated configuration file and deployed into an edge node. The corresponding relation can be returned through other web services and application programming interfaces (Application Programming Interface, API) aiming at page request information with stronger control granularity, such as cloud function services, cloud object storage services, traditional web services and the like, and the interfaces and other configuration systems are opened, so that the dynamic and configuration are more convenient.

In this embodiment, on the other hand, the correspondence between the different page contents and the storage medium may be pre-established, that is, the storage locations corresponding to the different page contents may be pre-configured. The storage medium may include a cloud object storage server, a cloud function server, a static resource server, a web server, and the like.

Specifically, when a correspondence relationship between content block information (content pieces) configuring page contents and storage media is established, different page contents should use different storage media because different page request information and language words correspond to different page contents, and when a service carries a large number of presence requests, a large number of page contents will exist. For example, if N pages are carried, each supporting M languages, n×m page contents need to be provided. Wherein the content static generation and the content dynamic generation are involved, and different strategies use different storage media.

Further, when the correspondence between the content segments and the storage medium is established, static generation (Static Site Generator, SSG) and dynamic generation (Dynamic Site Generator, DSG) may be selected. The static generation can use cloud object storage service to acquire corresponding static content in the edge node, and is generally applicable to pages with unchanged content. Dynamic generation may use a cloud function service in which content segments are dynamically generated, typically for pages where the content does not change periodically but does not rely on large amounts of background data. Conventional web services are required if pages that rely on large amounts of background data are required.

It will be appreciated that because web services and background data are generally more conformable or lightweight, conventional web services may be used for pages that require reliance on large amounts of background data. In addition, the cloud function service can also realize the function, but a large amount of facilities are required to be built due to the need of opening and providing a network foundation of the background data service, and the relative cost is high.

Specifically, according to the corresponding relationship between the container identifier and the static information of the page in the page request information, the page content corresponding to the container identifier, that is, the static information of the corresponding page, may be obtained from the cloud object storage server and/or the edge node local server.

In this embodiment, specifically, according to the correspondence between each content block identifier in the page request information and the dynamic information of the page, the page content corresponding to the content block identifier, that is, the dynamic information of the corresponding page, may be obtained from the cloud function server and/or the conventional web server.

In addition, it can be appreciated that, on the one hand, for content that does not change frequently, such as statically generated content information, the edge node can cache the static information for subsequent requests, thereby reducing service pressure and shortening response time. On the other hand, caching is not applicable to dynamically generated content block information, because the content block information is assembled in the cloud function service and the web service according to different request user data, is influenced by dynamic change of user dimension, and possibly relates to personal information of a user, and an edge node does not perform caching processing.

205. And assembling the page according to the static information of the page and the acquired content block information so as to send the assembled page to the client.

Specifically, according to the acquisition condition of the dynamic information of the page, the acquired content block information is determined; 206. the unobtained content block information is continuously acquired.

207. And additionally transmitting the newly acquired content block information to the client so that the client displays the complete page content.

In this embodiment, the page request information includes a container identification and at least one content block identification. According to the corresponding relation between the container identification and the static information of the page in the page request information, page content corresponding to the container identification, namely the static information of the corresponding page, is acquired from a cloud object storage server and/or an edge node local server, after the page content is assembled, the page with partial page content after the assembly can be sent to a client, but the HTTP connection is not closed, the page content corresponding to the content block identification is continuously acquired from a cloud function server and/or a web server according to the corresponding relation between each content block identification in the page request information and the dynamic information of the page, and each content block information is added to a response by utilizing the response adding characteristic of the HTTP protocol until the acquisition of all content block information is completed, and the HTTP connection response can be closed. Thus, the response time of the page depending on the background data in the complex page can be effectively shortened.

For example, if there are a container identifier and a plurality of content block identifiers in the page request information, that is, HTTP path information and content fragment ID of the current request page, the static information of the page corresponding to the HTTP path information is preferentially obtained, which may also be referred to as "page content container" and immediately returned to the upstream client, but the response is not closed, and at this time, the client may receive the returned page content and normally render and display the same. When the block content segment corresponding to the rest block content segment ID returns, continuing to add after sending the response of the 'page content container', adding n times after n segment IDs exist, and closing the ending response when all the block content segments are added. At this point the client/web container will subsequently receive the chunk content segments and eventually present the complete page content.

In addition, if only one container identifier exists in the page request information, namely the HTTP path information of the current request page, the obtained and assembled page content can be directly returned to the upstream client and the ending response is closed.

In this embodiment, loading and assembling of the page content may be completed through the correspondence between the identification information in the page request information and the page content, and after the series of operation steps are performed, the complete page content may be returned to the client or the web container through the response.

In this embodiment, fig. 4 is a schematic diagram of an application scenario of a method of page generation according to a second embodiment of the present disclosure, as shown in fig. 4. The application scenario includes a client 401, an edge node 402, a cloud object storage service/server 403, a cloud function service/server 404, a web service/server 405, a static resource service/server 406, a DNS407, and a gateway 408. Cloud services 409 may include edge nodes 402, cloud object storage services 403, cloud function services 404. Wherein the edge node 402 may be configured to perform the method of page generation in the present embodiment. It is to be appreciated that the edge node 402 can be configured on the basis of existing web services.

The method of page generation in this embodiment will now be described in detail with reference to fig. 4 and the practical application scenario.

Specifically, in the practical application scenario, the Domain name (Domain) information configuration specification name (cname) of the practical business service may be attached to a DNS407 server controllable by the cloud service provider or the business party. As shown in fig. 4, when a user makes a page request at a client 401 or a web container, first, the page request information may go through a designated DNS407 server, and the DNS407 server may combine with the area where the requesting user is located to screen out an edge node 402 with the smallest distance and highest relative weight. All page requests and responses of the user may then be processed by the edge node 402, i.e. the method of page generation in the present embodiment is performed by the edge node 402.

It will be appreciated that the edge nodes 402 may be a lightweight web service that may be allowed to run simple logic and may provide APIs for users to call, that the edge nodes 402 typically provide a runtime in which users may write logic, that the runtime may have a sandbox mechanism for security reasons, and that restrictions may be placed on the segments of logic that may be executed therein, including but not limited to APIs, storage, networking, etc.

For example cloudflare Workers and edge. Js of the smart cloud, which both provide edge node 402 services that carry JavaScript runtime. While cloudflare Workers provides a runtime of the V8 JavaScript engine, edge. Js of the intelligent cloud provides JavaScript runtime plug-ins extended on nginnx, and different bearer modes cause some differences between them, but the idea is consistent in main implementation.

Specifically, the page request sent by the user, after DNS resolution, may be forwarded to the edge node 402 with the best spatio-temporal distance and traffic pressure, where different runtimes are provided on the edge node 402 for the user to execute custom logic thereon. In the custom logic, a page request sent by a user is received, and the page request is analyzed to obtain all information identifiers of the page request, namely a container identifier and a content block identifier. Specific page content information can be obtained from the corresponding storage medium according to the information identification of the page request.

Further, the operation in the edge node 402 may assemble the obtained content block information (content segment) according to the information identifier by different strategies, so as to complete the assembly to form a complete page content information, and finally, the completed content is responded to the client 401 or the web container, so as to realize the processing rendering and displaying preview of the page.

In addition, at the content compiling stage or when processing the request, the corresponding relation between the page unique identification and the page content can be configured and stored in a file of the structural content such as JSON or XML. What is performed at the compilation stage is a statically generated correspondence and the relationship is serialized into a file and deployed into edge node 402 and cloud service 409 by means of persistent integration or static file upload. In this way, the edge node 402 can automatically parse the corresponding content and its storage medium when requesting the static generated page content information.

In addition, in the present implementation, the cloud service 409 as shown in fig. 4 may specifically include the following basic functions:

(1) cloudflare Wokers and smart cloud edge. All of the de-centralized rendering logic is executed in this runtime.

(2) And the cloudflash R2 and the intelligent cloud object storage (Baidu Object Storage, BOS) are responsible for storing static generated page contents, static resources and other content information.

(3) cloudflare Wokers and intelligent cloud function computation (Cloud Function Compute, CFC), providing a complete primitive function, responsible for executing the function logic in the edge node 402, performing dynamic generation based on the content block information required by the page.

(4) The cache object in cloudflare Workers is responsible for caching the statically generated content, so that the response time is prolonged, and the service pressure is reduced. The fetch event in Wokers invokes the cache object, processes the cache and responds.

In addition, in this embodiment, the page request information may be dynamically distributed to different edge nodes 402 according to the different areas where the users are located. Custom logic is executed in JavaScript runtime of edge node 402.

Specifically, according to the content loading corresponding to the region where the user is located, the function of displaying different contents in different regions can be realized. Cloud service providers may provide the ability for different regions (regions) to operate independently, with customized logic deployed through the regions within the different regions to achieve this functionality.

For example, user A may exhibit function a 'in an edge node 402 corresponding to a Region, and if user B is not in the Region, user B may not support function a' when requesting page services. Such a service approach is more flexible than traditional centralized web services.

It can be understood that the page generation method in this embodiment is also applicable to embedded pages in mobile terminals such as mobile phones. The edge node function may also be migrated to the webview container of the mobile terminal. The mobile-side system may include webview containers that are not limited to android, IOS, etc.

By adopting the technical scheme provided by the embodiment, according to the page request sent by the user, the edge node closest to the region from which the request is sent or with the best traffic load can be resolved, and the request is forwarded to the edge node in a mode of fourth-layer load balancing (network layer). The edge nodes may be large network nodes throughout the world provided by cloud service providers, so there are generally any number of edge nodes. The page request is loaded onto different edge nodes according to different conditions, so that a central service in the traditional sense does not exist for bearing the view rendering generation service of the page. When the edge node receives the request forwarded from the upstream, the page content required by the page request is acquired from the cloud object storage server/cloud function server/traditional center rendering web server through the cache or proxy service, and the assembly is completed. The problems of request authentication, page resource processing and the like in the page assembly process are all processed through the edge node. And (3) finishing assembly, returning the assembled page content to the client of the user through the edge node again, and finishing rendering and previewing, thereby finishing the view rendering generation process of the decentralised page. Therefore, the basic functions of page authentication and resource and content assembly are packaged by sending page request analysis to different edge nodes, and required content is dynamically obtained from object storage service and cloud function service according to the request, so that the decentralization effect of page rendering generation is realized, the processing process of page content can be free from the constraint of a traditional web server, service discretization and content fine granularity control for a designated area are realized, and the rendering generation speed and performance of the page are maximally improved.

Moreover, by adopting the technical scheme, as the application scene of the cloud service is more and more abundant and the stability is guaranteed and the support degree is improved, the edge nodes of the cloud service, which are distributed in all countries and regions around the world, are considered to be fully applied to replace the conventional web service in the conventional sense, different users select the edge node with the nearest distance or the minimum flow pressure to bear the user, the user request is processed on the edge node, and a web service mode without a central point is formed on the basis. The user customizing function aiming at different regions is realized while the traditional centralized web service function is reserved, and the time consumption and experience of the user request are greatly optimized due to the factors of space-time distance, so that the construction and bandwidth cost of the conventional IDC can be reduced, the development and deployment efficiency of web application is improved, and the cost reduction and synergy are maximally realized.

It should be noted that, for simplicity of description, the foregoing method embodiments are all described as a series of acts, but it should be understood by those skilled in the art that the present disclosure is not limited by the order of acts described, as some steps may be performed in other orders or concurrently in accordance with the present disclosure. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all of the preferred embodiments, and that the acts and modules referred to are not necessarily required by the present disclosure.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments.

Fig. 5 is a schematic diagram according to a third embodiment of the present disclosure, as shown in fig. 5. The apparatus 500 for page generation of the present embodiment may include a request acquisition unit 501, a content acquisition unit 502, and a page output unit 503. A request acquiring unit 501, configured to acquire page request information of a specified page sent by a client; a content obtaining unit 502, configured to obtain, according to the page request information, page content of the specified page; wherein, the page content has association relation with the page request information; and the page output unit is used for assembling the specified page according to the page content so as to output the assembled specified page to the client. The page generation apparatus 500 may be disposed at an edge node.

It should be noted that, part or all of the page generating apparatus in this embodiment may be an application located at a terminal, or may be a functional unit such as a plug-in unit or a software development kit (Software Development Kit, SDK) disposed in the application located at the terminal, or may be a processing engine located in a server on a network side, or may be a distributed system located on the network side, for example, a processing engine or a distributed system in a page processing platform on the network side, which is not limited in this embodiment.

Optionally, in one possible implementation manner of this embodiment, the page request information includes a container identifier, the page content includes a first page content, and the content obtaining unit may specifically be configured to obtain the first page content according to the container identifier, where the first page content includes container style information and container content information.

Alternatively, in one possible implementation manner of the present embodiment, the page output unit 503 may be specifically configured to assemble the specified page according to the container style information and the container content information.

Optionally, in one possible implementation manner of this embodiment, the page request information includes a container identifier and at least one content block identifier, the page content includes a first page content and a second page content, and the content obtaining unit 502 may be further configured to obtain the first page content according to the container identifier; acquiring the second page content according to at least one content block identifier; wherein the second page content includes at least one content block information.

Optionally, in a possible implementation manner of this embodiment, the page output unit 503 may be further configured to determine, according to the acquisition situation of the second page content, acquired content block information; and assembling the designated page according to the first page content and the acquired content block information.

Optionally, in one possible implementation manner of this embodiment, the content obtaining unit 502 may be further configured to determine, according to the page request information, a storage location of the page content corresponding to the page request information by using a preconfigured index table; and acquiring page content of the designated page according to the storage position.

Optionally, in one possible implementation manner of this embodiment, the content obtaining unit 502 may be further configured to perform authentication processing according to a preset permission rule and the page request information, so as to obtain an authentication result, and further determine whether to obtain the page content of the specified page according to the authentication result.

In this embodiment, the request obtaining unit obtains the page request information of the specified page sent by the client, so that the content obtaining unit may obtain the page content of the specified page according to the page request information; the page content and the page request information have an association relation, so that the page output unit can assemble the specified page according to the page content, so that the assembled specified page is output to the client, and the page request information sent by the client can be directly processed through the edge node to assemble and generate the page content corresponding to the page request information, so that the response time of page loading is shortened, the influence of the traditional web server on service deployment efficiency is reduced to a certain extent, and the efficiency and reliability of page generation are improved.

In the technical scheme of the disclosure, the related acquisition of the personal information of the user, such as configuration information of the user, storage, application and the like, accords with the regulations of related laws and regulations and does not violate the popular regulations of the public order.

According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.

Fig. 6 illustrates a schematic block diagram of an example electronic device 600 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 6, the electronic device 600 includes a computing unit 601 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 602 or a computer program loaded from a storage unit 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the electronic device 600 can also be stored. The computing unit 601, ROM 602, and RAM 603 are connected to each other by a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

A number of components in the electronic device 600 are connected to the I/O interface 605, including: an input unit 606 such as a keyboard, mouse, etc.; an output unit 607 such as various types of displays, speakers, and the like; a storage unit 608, such as a magnetic disk, optical disk, or the like; and a communication unit 609 such as a network card, modem, wireless communication transceiver, etc. The communication unit 609 allows the electronic device 600 to exchange information/data with other devices through a computer network, such as the internet, and/or various telecommunication networks.

The computing unit 601 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 601 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 601 performs the respective methods and processes described above, such as a method of page generation. For example, in some embodiments, the method of page generation may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 608. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 600 via the ROM 602 and/or the communication unit 609. When a computer program is loaded into RAM 603 and executed by computing unit 601, one or more steps of the method of page generation described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform the method of page generation in any other suitable way (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on 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.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.

The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server incorporating a blockchain.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel or sequentially or in a different order, provided that the desired results of the technical solutions of the present disclosure are achieved, and are not limited herein.

The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.

Claims

1. A method of page generation, applied to an edge node, comprising:

acquiring page request information of a designated page sent by a client;

2. The method of claim 1, wherein the page request information includes a container identification, the page content includes a first page content, and the obtaining the page content of the specified page according to the page request information includes:

acquiring the first page content according to the container identifier, wherein,

the first page content includes container style information and container content information.

3. The method of claim 2, wherein the assembling the specified page according to the page content comprises:

and assembling the designated page according to the container style information and the container content information.

4. The method of claim 1, wherein the page request information includes a container identification and at least one content block identification, the page content includes a first page content and a second page content, the obtaining the page content of the specified page according to the page request information includes:

acquiring the first page content according to the container identifier;

acquiring the second page content according to at least one content block identifier; wherein the second page content includes at least one content block information.

5. The method of claim 4, wherein the assembling the specified page according to the page content comprises:

determining acquired content block information according to the acquisition condition of the second page content;

and assembling the designated page according to the first page content and the acquired content block information.

6. The method according to any one of claims 1-5, wherein the acquiring the page content of the specified page according to the page request information further comprises:

determining a storage position of page content corresponding to the page request information by utilizing a pre-configured index table according to the page request information;

and acquiring page content of the designated page according to the storage position.

7. The method according to any one of claims 1-6, wherein before the acquiring the page content of the specified page according to the page request information, further comprises:

carrying out authentication processing according to a preset authority rule and the page request information to obtain an authentication result;

and determining whether to acquire the page content of the appointed page according to the authentication result.

8. The device for generating the page is arranged at an edge node and comprises the following components:

9. The apparatus of claim 8, wherein the page request information includes a container identification, the page content includes a first page content, and the content acquisition unit is specifically configured to:

10. The apparatus of claim 9, wherein the page output unit is specifically configured to

11. The apparatus of claim 8, wherein the page request information includes a container identification and at least one content block identification, the page content includes a first page content and a second page content, the content acquisition unit is further configured to:

Acquiring the first page content according to the container identifier;

12. The apparatus of claim 11, wherein the page output unit is further configured to:

13. The apparatus according to any one of claims 8-12, wherein the content acquisition unit is further configured to:

14. The apparatus according to any one of claims 8-13, wherein the content acquisition unit is further configured to:

15. An electronic device, comprising:

at least one processor; and

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.

16. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-7.

17. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any of claims 1-7.