CN113535435B

CN113535435B - Page data processing method and device, computer equipment and storage medium

Info

Publication number: CN113535435B
Application number: CN202110831805.0A
Authority: CN
Inventors: 张晓栋; 张博军; 彭安
Original assignee: Beijing Sankuai Online Technology Co Ltd
Current assignee: Beijing Sankuai Online Technology Co Ltd
Priority date: 2021-07-22
Filing date: 2021-07-22
Publication date: 2022-06-07
Anticipated expiration: 2041-07-22
Also published as: CN113535435A

Abstract

The embodiment of the application discloses a page data processing method and device, computer equipment and a storage medium, and belongs to the technical field of internet application. The method comprises the following steps: acquiring configuration information of a target entry page; determining a data interface of at least one landing page corresponding to the target entry page based on the configuration information of the target entry page; acquiring page data of at least one landing page based on a data interface of the at least one landing page; converting the page data into a binary data stream according to a specified data structure; pushing the binary data stream to the target terminal; according to the scheme, the acquisition and the preloading of the page data of the landing page are directly realized through the API layer, the service access flow is simplified, the expandability of the service is improved, and the development and updating efficiency of the application program is further improved.

Description

Page data processing method and device, computer equipment and storage medium

Technical Field

The present application relates to the field of internet application technologies, and in particular, to a page data processing method and apparatus, a computer device, and a storage medium.

Background

Pages in an Application (APP) can be generally divided into a portal page and a landing page, wherein a user can select to enter a certain landing page containing specific information from the portal page.

In the related art, in order to reduce the delay of jumping from the portal page to the landing page, the operator of APP can generally provide a pre-loading service for landing pages. Specifically, a Remote Procedure Call (RPC) service is set in the background server of the APP as a preloading service, and when an APP client in the terminal requests an entry page, the background server can actively push page data of a landing page corresponding to the entry page to the terminal through the RPC service.

However, based on the solutions in the related art, a special RPC service needs to be added in the background, and the process of accessing each service to the RPC service is complicated, resulting in poor scalability of the service.

Disclosure of Invention

The embodiment of the application provides a page data processing method and device, computer equipment and a storage medium. The technical scheme is as follows:

in one aspect, an embodiment of the present application provides a page data processing method, where the method includes:

acquiring configuration information of a target entry page, wherein the target entry page is an entry page requested by a target terminal; the entrance page comprises a triggering entrance of the landing page;

determining a data interface of at least one landing page corresponding to the target entry page based on the configuration information of the target entry page;

acquiring page data of at least one landing page based on at least one data interface of the landing page;

converting the page data into a binary data stream according to a specified data structure;

pushing the binary data stream to the target terminal so that the target terminal can analyze page data of the target landing page from the binary data stream when receiving a trigger operation on a trigger inlet of the target landing page; the target landing page is any one of the at least one landing page.

displaying a target entry page requested by the request, wherein the target entry page comprises at least one triggering entry of a landing page;

receiving a binary data stream pushed by a server, wherein the binary data stream is obtained by converting page data according to a specified data structure after the server determines at least one data interface of the landing page based on the configuration information of the target entry page and obtains the page data of at least one landing page based on the at least one data interface of the landing page;

when receiving a trigger operation on a trigger inlet of a target landing page, analyzing page data of the target landing page from the binary data stream; the target landing page is any one of the at least one landing page;

and displaying the target landing page based on the page data of the target landing page.

On the other hand, an embodiment of the present application provides a page data processing apparatus, where the apparatus includes:

the configuration information acquisition module is used for acquiring configuration information of a target entry page, wherein the target entry page is an entry page requested by a target terminal; the entrance page comprises a triggering entrance of the landing page;

the data interface determining module is used for determining a data interface of at least one landing page corresponding to the target entry page based on the configuration information of the target entry page;

the page data acquisition module is used for acquiring page data of at least one landing page based on a data interface of the at least one landing page;

the data conversion module is used for converting the page data into a binary data stream according to a specified data structure;

the data pushing module is used for pushing the binary data stream to the target terminal so that the target terminal can analyze page data of the target landing page from the binary data stream when receiving a triggering operation on a triggering entry of the target landing page; the target landing page is any one of the at least one landing page.

In a possible implementation manner, the configuration information obtaining module includes:

the message sending submodule is used for responding to an entry page request sent by the target terminal received by an entry page interface server and sending an entry page field message through the entry page interface server; the portal page request is used for requesting to acquire the target portal page;

the receiving submodule is used for receiving the entry page field message through the landing page interface server;

and the extraction submodule is used for extracting the configuration information of the target entry page from the entry page field message through the landing page interface server.

In one possible implementation, the message sending submodule is configured to,

in response to the entry page interface server receiving an entry page request sent by the target terminal, extracting configuration information of the target entry page from entry page information returned to the target terminal from a data interface of the target entry page through the entry page interface server;

sending, by the portal page interface server, the portal page field message including configuration information of the target portal page.

In a possible implementation manner, when the portal page interface server extracts the configuration information of the target portal page from the portal page information returned to the target terminal from the portal page interface corresponding to the target portal page, the message sending sub-module is configured to,

intercepting and identifying a first target object with annotation in the portal page information through the portal page interface server;

and analyzing the annotation in the first target object through the portal page interface server to obtain the configuration information of the target portal page.

In a possible implementation manner, the message sending sub-module is configured to send the portal page field message to a target message platform through the portal page interface server;

the receiving submodule is used for monitoring the entry page field message received by the target message platform through the landing page interface server.

In one possible implementation, the portal page field message contains a preload context field and an item field;

the item field comprises the configuration information of the target entry page;

the preloaded context field contains context information of the target terminal.

In one possible implementation manner, the data interface determining module is configured to,

matching the configuration information of the target entry page with each consumption group through the landing page interface server, wherein each consumption group in each consumption group corresponds to a data interface;

and determining a data interface corresponding to the target consumption group matched with the configuration information of the target entry page as at least one data interface of the landing page through the landing page interface server.

In one possible implementation, the apparatus further includes:

the intercepting module is used for intercepting and identifying a second target object with annotation in the code of the data interface of the landing page when the landing page interface server initializes the data interface of the landing page;

the analysis module is used for analyzing the annotation in the second target object through the landing page interface server to obtain the configuration information of the landing page;

and the creating module is used for creating the consumption group of the landing page based on the configuration information of the landing page through the landing page interface server.

the portal page display module is used for displaying a target portal page requested by a request, and the target portal page comprises at least one triggering portal of a landing page;

the data stream receiving module is used for receiving a binary data stream pushed by the server, wherein the binary data stream is obtained by the server through determining at least one data interface of the landing page based on the configuration information of the target entry page, acquiring page data of at least one landing page based on the at least one data interface of the landing page and converting the page data according to a specified data structure;

the page data analysis module is used for analyzing the page data of the target landing page from the binary data stream when receiving the trigger operation of the trigger inlet of the target landing page; the target landing page is any one of the at least one landing page;

and the landing page display module is used for displaying the target landing page based on the page data of the target landing page.

In another aspect, an embodiment of the present application provides a computer device, where the computer device includes a processor and a memory, where the memory stores at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the page data processing method according to the above aspect.

In another aspect, an embodiment of the present application provides a computer-readable storage medium, where at least one computer program is stored, and the at least one computer program is loaded and executed by a processor to implement the page data processing method according to the above aspect.

According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the page data processing method according to the above aspect.

The technical scheme provided by the embodiment of the application has the beneficial effects that at least:

when the target terminal requests an entry page, a data Interface corresponding to a landing page in the entry page can be directly acquired through configuration information of the entry page so as to acquire page data of the landing page, and then the page data is converted into a binary data stream according to a uniform data format and is pushed to the target terminal, so that the acquisition and preloading of the page data of the landing page are directly realized through an Application Programming Interface (API) layer, a service access flow is simplified, the expandability of a service is improved, and the development and updating efficiency of the Application program is improved.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.

FIG. 1 is a schematic diagram of a page push system provided by an exemplary embodiment of the present application;

FIG. 2 is a system framework diagram to which the embodiment of FIG. 1 relates;

FIG. 3 is a flowchart illustrating a method for processing page data according to an exemplary embodiment of the present application;

FIG. 4 is a flowchart illustrating a method for processing page data according to an exemplary embodiment of the present application;

FIG. 5 is a message structure diagram of an entry page field message to which the embodiment shown in FIG. 4 relates;

FIG. 6 is a message passing flow diagram related to the embodiment shown in FIG. 4;

FIG. 7 is a pre-loading flow diagram of the embodiment of FIG. 4;

FIG. 8 is a pre-load timing diagram related to the embodiment of FIG. 4;

FIG. 9 is a block diagram of a page data processing apparatus according to an exemplary embodiment of the present application;

FIG. 10 is a block diagram of a page data processing apparatus according to an exemplary embodiment of the present application;

FIG. 11 is a block diagram of a computer device provided in an exemplary embodiment of the present application;

fig. 12 is a schematic structural diagram of a terminal according to an exemplary embodiment of the present application.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings in which the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

Referring to fig. 1, a schematic diagram of a behavior page pushing system according to an embodiment of the present application is shown. The system may include: a first terminal 110, a server cluster 120.

The first terminal 110 is installed and operated with an application 111 supporting a portal page and a landing page, and the application 111 may be a comment type application, a social platform type application, an instant messaging type application, a game application, and the like. When the first terminal runs the application 111, a user interface of the application 111 is displayed on the screen of the first terminal 110. The first terminal 110 is a terminal used by the first user 112, and the first user 112 can open a portal page in the application 111 using the first terminal 110 and open a landing page in the application 111 from the portal page to browse page details in the landing page.

Only one first terminal is shown in fig. 1, but there are a plurality of other terminals that may access the server 120 in different embodiments. Optionally, there are one or more terminals corresponding to the developer, and a development and editing platform for the application programs supporting the portal page and the landing page is installed on the terminal, the developer can edit and update the application programs on the terminal, and transmit the updated application program installation package to the server 120 through a wired or wireless network, and the first terminal 110 can download the application program installation package from the server 120 to update the application programs.

The first terminal 110 and other terminals are connected to the server 120 through a wireless network or a wired network.

The server cluster 120 may include at least one of a plurality of servers, a cloud computing platform, and a virtualization center. Server cluster 120 is used to provide background services for applications that support portal pages and landing pages. Optionally, the server cluster 120 undertakes primary computing work and the terminals undertake secondary computing work; or, the server cluster 120 undertakes the secondary computing work, and the terminal undertakes the primary computing work; alternatively, the server cluster 120 and the terminal perform cooperative computing by using a distributed computing architecture.

In one illustrative example, the server cluster 120 includes a memory 121, a processor 122, a user account database 123, a page service module 124, and an Input/Output Interface (I/O Interface) 125 for a user. The processor 122 is configured to load an instruction stored in the server cluster 120, and process data in the user account database 123 and the page service module 124; the user account database 123 is configured to store data of a user account used by the first terminal 110 and other terminals, such as a head portrait of the user account, a nickname of the user account, and a region where the user account is located; the page service module 124 is used for providing a push service of page data (including page data of a portal page and page data of a landing page); the user-facing I/O interface 125 is used to establish communication with the first terminal 110 and/or other terminals through a wireless or wired network to exchange data.

In the embodiment of the present application, the server cluster 120 is divided according to the sub-services provided, and may also be divided into a plurality of sub-servers. For example, please refer to fig. 2, which illustrates a system framework diagram according to an embodiment of the present application. As shown in fig. 2, the server cluster 120 is divided into a portal page interface server 120a, a landing page interface server 120b, and a target message platform 120 c.

The portal page interface server 120a is configured to implement a portal page related service, and may maintain a data interface of each portal page that can be exposed by the application 111, and push page data of the portal page to the first terminal 110 in response to an operation that is executed by a user in the application 111 of the first terminal 110 and triggers the presentation of the portal page.

The landing page interface server 120b is configured to implement a landing page related service, maintain data interfaces of each landing page that can be displayed by the application 111, and push page data of the landing page to the first terminal 110 in response to a request for obtaining the landing page by the application 111 of the first terminal 110.

The target message platform 120c described above is used to deliver messages between various other sub-servers in the server 120, including and not limited to the portal page interface server 120a and the landing page interface server 120 b.

Referring to fig. 3, a flowchart of a page data processing method according to an exemplary embodiment of the present application is shown. The method may be performed by a computer device, and the computer device may include a server cluster and a target terminal, where the server cluster may be the server cluster 120 referred to in fig. 1 or fig. 2, and the target terminal may be the first terminal 110 referred to in fig. 1 or fig. 2. As shown in fig. 3, the computer device may perform the pushing of page data of landing pages by performing the following steps.

Step 301, a server cluster acquires configuration information of a target entry page, wherein the target entry page is an entry page requested by a target terminal; the portal page contains a trigger portal for landing pages.

Step 302, the target terminal displays the requested target entry page, and the target entry page includes at least one triggering entry of the landing page.

Taking the example that the computer device is a server cluster, when an application program in the target terminal is started and a trigger operation for displaying the target portal page is received, the target terminal may request the target portal page from the network side, at this time, the server cluster returns page data of the portal page to the target terminal, and meanwhile, the server cluster may also obtain configuration information of the target portal page.

The configuration information of the target portal page may be used to indicate a data interface API corresponding to a landing page in the target portal page.

The landing page data interface can be used for providing landing page data.

In a possible implementation manner, the step of the server cluster acquiring the configuration information of the target portal page may be implemented by a portal page interface server (e.g., the portal page interface server 120a in the system framework shown in fig. 2) and a landing page interface server (e.g., the landing page interface server 120b in the system framework shown in fig. 2) in an interactive manner. For example, the portal page interface server may acquire the configuration information of the target portal page in a process that the target terminal requests the target portal page, and provide the configuration information of the target portal page to the landing page interface server.

Step 303, the server cluster determines a data interface of at least one landing page corresponding to the target portal page based on the configuration information of the target portal page.

In the embodiment of the application, the server cluster can obtain the data interface of the landing page in the target portal page in a matching manner according to the configuration information of the target portal page.

Taking the above fig. 2 as an example, the step may be executed by the landing page interface server, that is, after the landing page interface server obtains the configuration information provided by the portal page interface server, the landing page interface server may obtain the data interface of the landing page in the target portal page through matching the configuration information.

And 304, the server cluster acquires page data of at least one landing page based on at least one data interface of the landing page.

In the embodiment of the present application, a server cluster, for example, a landing page interface server in a server, may pull page data of a landing page according to a data interface of the landing page.

Step 305, the server cluster converts the page data into a binary data stream according to a specified data structure.

In this embodiment of the application, after a server cluster (for example, a landing page interface server) pulls page data of a landing page, the page data of the landing page may be reconstructed according to a specified data structure, and then the reconstructed page data is converted into a binary data stream.

Step 306, the server cluster pushes the binary data stream to the target terminal, so that the target terminal can analyze the page data of the target landing page from the binary data stream when receiving the trigger operation of the trigger entry of the target landing page; the target landing page is any one of the at least one landing pages; correspondingly, the target terminal receives the binary data stream pushed by the server cluster.

Step 307, when the target terminal receives the trigger operation of the trigger entry of the target landing page, analyzing the page data of the target landing page from the binary data stream; the target landing page is any one of the at least one landing page.

And 308, the target terminal displays the target landing page based on the page data of the target landing page.

In the embodiment of the application, different landing pages can correspond to different services/providers, and correspondingly, different data structures (for example, different data models) can be provided.

To sum up, according to the scheme shown in the embodiment of the application, when the target terminal requests the entry page, the data interface corresponding to the landing page in the entry page can be directly obtained through the configuration information of the entry page to obtain the page data of the landing page, and then the page data is converted into a binary data stream according to a uniform data format and is pushed to the target terminal, so that the acquisition and preloading of the page data of the landing page are directly realized through the API layer, the service access flow is simplified, the service expandability is improved, and the development and update efficiency of the application program is improved.

Referring to fig. 4, a flowchart of a page data processing method according to an exemplary embodiment of the present application is shown. The method may be performed by a computer device, and the computer device may include a server cluster and a target terminal, where the server cluster may be the server cluster 120 referred to in fig. 1 or fig. 2, and the target terminal may be the first terminal 110 referred to in fig. 1 or fig. 2. As shown in fig. 4, the computer device may perform the following steps to push and display the page data of the landing page.

Step 401, the target terminal sends a portal page request to the server cluster, and the server cluster receives the portal page request.

Wherein the portal page request is used for requesting to acquire the target portal page.

In one possible implementation manner, the target terminal may send the portal page request to a portal page interface server in the server cluster to request to acquire the target portal page.

Step 402, in response to the portal page interface server receiving the portal page request sent by the target terminal, the server cluster sends a portal page field message through the portal page interface server.

In this embodiment of the present application, when a user in a target terminal triggers and presents a target portal page in an application program, the target terminal may send a portal page request to a portal page interface server in a server cluster, where the portal page request may include a page address of the target portal page, such as a Uniform Resource Locator (URL).

After receiving the portal page request, the portal page interface server may return page data of the target portal page to the target terminal, so that the target terminal may display the target portal page through the application program.

For example, the portal page interface server may return page data of the target portal page to the target terminal through the data interface of the target portal page.

Meanwhile, the portal page interface server also sends a portal page field message to trigger the floor page interface server to start the preloading of the page data of the floor page when the target terminal displays the portal page.

In one possible implementation, the portal page interface server may be provided with a first preloaded component, which may be a Software Development Kit (SDK). After receiving the portal page request, the portal page interface server may generate the portal page field message according to the relevant information of the target portal page (e.g., the landing page included in the target interface page and the information of the target terminal), and send the portal page field message.

the item field contains the configuration information of the target entry page;

Referring to fig. 5, a message structure diagram of an entry page field message according to an embodiment of the present application is shown. As shown in fig. 5, in the preloading message 50 (i.e. the above-mentioned portal page field message), the service information of the portal page is placed in the Item 51(Item), for example, in the parameter field (Params) of the Item 51, and the rest of the client information is placed in the client context (mobileContext) of the preloading context 52 (preloadContext). The portal page interface server provides the encapsulated object (i.e. the portal page field message) to the landing page interface server, and the landing page interface server can acquire the full information of the interface access participation (i.e. the configuration information of the target portal page).

In fig. 5, the entry information of the interface generally includes the frame context and the service parameters corresponding to the landing page.

For example, as shown in fig. 5, context information such as the system source of the requested APP, the mobile phone model, the client version number, and the like may be stored in the mobileContext.

Params contains the business parameters, and the business parameters are set in the Params by the portal page interface server.

In a possible implementation manner, when sending the portal page field message, the server cluster may, in response to the portal page interface server receiving the portal page request sent by the target terminal, extract, by the portal page interface server, the configuration information of the target portal page from the portal page information returned to the target terminal by the data interface of the target portal page; then, the portal page field message containing the configuration information of the target portal page is transmitted through the portal page interface server.

In this embodiment of the present application, when the portal page interface server returns portal page information (including page data of the target portal page) to the target terminal through the data interface of the target portal page, the portal page interface server may extract configuration information of the target portal page from the portal page information, add the configuration information to the portal page field message, and provide the portal page field message to the landing page interface server.

In the embodiment of the present application, the data interface corresponding to the target portal page is developed and provided by a developer of the target portal page, and correspondingly, the configuration information of the target portal page may also be configured by the developer of the target portal page, that is, when a new portal page is developed, the developer of the portal page only needs to add corresponding configuration information to the portal page information returned to the terminal by the portal page interface, that is, the pre-loading requirement for the landing page included in the portal page may be supported on one side of the portal page, so that the development efficiency of the portal page compatible with the pre-loading function of the landing page is greatly improved.

In this embodiment of the present application, when the server cluster extracts the configuration information of the target portal page from the portal page information through the portal page interface server, the first target object with the annotation in the portal page information may be intercepted and identified through the portal page interface server, and the annotation in the first target object is analyzed through the portal page interface server, so as to obtain the configuration information of the target portal page.

Optionally, the first preloading component in the portal page interface server may be provided with an interceptor, and when the data interface corresponding to the target portal page returns a portal page message to the target terminal, the interceptor may intercept the portal page message and parse the configuration information in the form of the annotation from the portal page message.

In an exemplary aspect, the interceptor of the first preload component may be an internal front-end protocol framework based interceptor. Wherein, the interceptor can be implemented by Spring-based interceptor technology.

Wherein the interceptor may be implemented by relying on a Java (a computer programming language) reflection mechanism. The interceptor may be a dynamic proxy implemented based on the Java Development Kit (JDK). For example, an interceptor is applied in the facet-oriented programming, which may call a method before or after a service (service) or a method.

The configuration information of the target portal page carried by the portal page field message may be configured by a code block as shown in table 1 below.

TABLE 1

In the embodiment of the application, after the portal page interface server intercepts the portal page message returned to the target terminal from the data interface of the target portal page through the interceptor, the annotated bean in the portal page field message can be searched through the bean object in the spring, and then the configuration information of the target portal page is obtained through analysis.

Step 403, receiving the portal page field message through the landing page interface server.

In the embodiment of the application, the portal page field message can be transmitted between the portal page interface server and the landing page interface server through a target message platform.

For example, the server cluster may send the portal page field message to the target message platform through the portal page interface server; correspondingly, the server cluster monitors the entry page field message received by the target message platform through the landing page interface server.

In this embodiment, the server cluster may register, to the target message platform, an entry page field message required for monitoring a data interface of each landing page maintained in the landing page interface server through the landing page interface server.

The landing page interface server can acquire the configuration information of each landing page when initializing the data interface of each landing page, and register and monitor the entry page field message related to the configuration information to the target message platform based on the configuration information of the landing page.

For example, taking the case that the configuration information of the landing page includes the header information (topic) of the landing page as an example, when the data interface of the landing page is initialized, the landing page interface server acquires the configuration information of the landing page, and registers the listening service with the target message platform based on topic in the configuration information, and the subsequent target message platform may send the portal page field message related to topic to the landing page interface server.

The configuration information of the landing page can be configured to the landing page interface server in an annotation form, for example, when the landing page interface server initializes the data interface of the landing page, a second target object with an annotation in a code of the data interface of the landing page is intercepted and identified; and analyzing the annotation in the second target object through the landing page interface server to obtain the configuration information of the landing page.

In the embodiment of the application, a developer of the landing page only needs to set the configuration information of the landing page in an annotated form in the code corresponding to the landing page, after the subsequent landing page is accessed into the system, when the landing page interface server initializes the data interface of the landing page, the configuration information of the landing page can be intercepted and analyzed through the interceptor, and developers/maintenance personnel who do not need to set corresponding configuration information for each accessed landing page in the landing page interface server are not required to greatly improve the efficiency of the landing page access system.

In this embodiment of the present application, a second preloading component may be set in the landing page interface server, and an interceptor may be set in the second preloading component, and the landing page interface server may intercept, through the interceptor in the second preloading component, a related object that includes configuration information of a landing page in a code corresponding to a data interface of the landing page.

The first preloading component and the second preloading component may be implemented as Java Archive (JAR) packages, which may be deployed after being referenced by a backend Java web (web) server of a landing page or a portal page.

The target message platform may be a common platform, for example, a message system based on a distributed log. The message queue may be deployed on a server designated by the distributed messaging system (i.e., the target messaging platform).

Step 404, extracting the configuration information of the target portal page from the portal page field message through the landing page interface server.

In a possible implementation manner, after the landing page interface server monitors the portal page field message from the target message platform, the configuration information of the target portal page may be extracted from the portal page field message.

Step 405, the server cluster determines, through the landing page interface server, a data interface of at least one landing page corresponding to the target portal page based on the configuration information of the target portal page.

In a possible implementation manner, the determining the data interface of the landing page based on the configuration information of the target portal page includes:

and determining the data interface corresponding to the target consumption group matched with the configuration information of the target entry page as at least one data interface of the landing page through the landing page interface server.

In the embodiment of the application, a plurality of consumption groups can be arranged in the landing page interface server, each consumption group can correspond to one landing page data interface, and the monitored configuration information of the target portal page is consumed through the consumption groups.

In the embodiment of the application, the landing page interface server can be used for creating the consumption group of the landing page based on the configuration information of the landing page.

In the embodiment of the present application, the consumption groups are in one-to-one correspondence with downstream interfaces (i.e., data interfaces of landing pages), for example, for a case where the portal pages are different but the landing pages are the same, the same topic is used by the same corresponding landing page in different portal pages, and the consumption is performed by a fixed interface. And each data interface of the landing page is added, so that a consumption group needs to be added.

Please refer to fig. 6, which shows a message passing flow diagram according to an embodiment of the present application; the procedure of delivering and consuming the portal page field message can refer to fig. 6. In fig. 6, each card 61 in the list page 60 may have a portal page field message 62 corresponding thereto, and the portal page field message 62 is broadcast to each consumption group 63 and consumed by the consumption group 63 adapted to the downstream service (e.g., sent by the consumption group to the corresponding downstream landing page interface).

The landing page generally corresponds to one interface, and may correspond to a plurality of interfaces. For example, the commodity detail page of the comment APP has a plurality of interfaces, some interfaces return basic information of merchants, some interfaces return group purchase information, and the like. The purpose of splitting the consumption groups in the embodiment of the present application is to allow each landing page interface that needs to receive the broadcast message to receive the message, because the message can be consumed by only one consumer within the consumption group, but the same message can be repeatedly consumed between different consumption groups.

In the embodiment of the present application, the configuration information of the landing page may also be configured through an annotation, for example, the annotation code corresponding to the configuration information of the landing page may refer to table 2 below.

TABLE 2

When initializing the data interface of the landing page, the landing page interface server intercepts the configuration information of the landing page, namely, the corresponding relation between the target consumption group and the data interface of the landing page can be established through the configuration information of the landing page, so that the rapid access of the landing page is realized.

In step 406, the server cluster obtains page data of at least one landing page based on at least one data interface of the landing page.

The server cluster can obtain at least one page data of the landing page based on at least one data interface of the landing page through the landing page interface server.

Step 407, the server cluster converts the page data into a binary data stream according to the specified data structure.

The server cluster can convert the page data into a binary data stream according to a specified data structure through the landing page interface server.

In step 408, the server cluster pushes the binary data stream to the target terminal.

The server cluster can push the binary data stream to the target terminal through the landing page interface server.

Step 409, when the target terminal receives the trigger operation of the trigger entry of the target landing page, the page data of the target landing page is analyzed from the binary data stream, and the target landing page is displayed.

In the embodiment of the application, the JAR package is provided for the portal page and the landing page by using the interceptor technology to complete the preloading task. The access of preloading can be completed only by performing simple annotation and development on the API layer on the entry page and the landing page, and the development cost is extremely low. And intercepting an interface of an API layer interface entry page by using a web interceptor technology, and sending a queue message. And after receiving the queue message, the landing page interface calls the landing page API interface to carry out binary serialization pushing on the return model to the client, and the preloading task is completed.

Please refer to fig. 7, which illustrates a preloading flow diagram according to an embodiment of the present application; please refer to fig. 8, which shows a preload timing diagram according to an embodiment of the present application; referring to fig. 7 and 8, the implementation process of the above scheme may be as shown in fig. 7 and 8, where relevant information required by the landing page interface 72 is collected from the portal page interface 71 and sent to a specific message queue 73, and the landing page interface 72 configures a corresponding topic for listening consumption, and sends the content of the corresponding landing page interface to the client, for example, to push the content to the client through a SharkPush message channel or a Pike message channel. When the user requests the corresponding landing page interface, the client directly returns the cached data without requesting back-end service.

To sum up, according to the scheme shown in the embodiment of the present application, when a target terminal requests an entry page, a data interface corresponding to a landing page in the entry page may be directly obtained through configuration information of the entry page to obtain page data of the landing page, and then the page data is converted into a binary data stream according to a uniform data format and pushed to the target terminal, so that the acquisition and preloading of the page data of the landing page are directly achieved through an API layer, a service access flow is simplified, the expandability of a service is improved, and further, the development and update efficiency of an application program is improved.

Fig. 9 is a block diagram of a page data processing apparatus according to an exemplary embodiment of the present application, where the apparatus may be used to perform all or part of the steps performed by the server cluster in the method shown in fig. 3 or fig. 4, and the apparatus includes:

a configuration information obtaining module 901, configured to obtain configuration information of a target entry page, where the target entry page is an entry page requested by a target terminal; the entrance page comprises a triggering entrance of the landing page;

a data interface determining module 902, configured to determine, based on the configuration information of the target entry page, a data interface of at least one landing page corresponding to the target entry page;

a page data obtaining module 903, configured to obtain page data of at least one landing page based on a data interface of the at least one landing page;

a data conversion module 904, configured to convert the page data into a binary data stream according to a specified data structure;

the data pushing module 905 is configured to push the binary data stream to the target terminal, so that when the target terminal receives a trigger operation on a trigger entry of a target landing page, the page data of the target landing page is analyzed from the binary data stream; the target landing page is any one of the at least one landing page.

In a possible implementation manner, the configuration information obtaining module 901 includes:

the receiving submodule is used for receiving the field message of the entry page through the landing page interface server;

In one possible implementation, the message sending submodule is configured to,

and the receiving submodule is used for monitoring the entry page field message received by the target message platform through the landing page interface server.

In one possible implementation, the data interface determining module 902 is configured to,

In one possible implementation, the apparatus further includes:

Fig. 10 is a block diagram of a page data processing apparatus according to an exemplary embodiment of the present application, where the apparatus may be used to perform all or part of the steps performed by the target terminal in the method shown in fig. 3 or fig. 4, and the apparatus includes:

the portal page display module 1001 is configured to display a requested target portal page, where the target portal page includes at least one trigger portal of a landing page;

a data stream receiving module 1002, configured to receive a binary data stream pushed by a server, where the binary data stream is obtained by determining, by the server, a data interface of at least one landing page based on the configuration information of the target entry page, and after obtaining page data of the at least one landing page based on the data interface of the at least one landing page, converting the page data according to a specified data structure;

the page data analysis module 1003 is configured to, when receiving a trigger operation on a trigger entry of a target landing page, analyze page data of the target landing page from the binary data stream; the target landing page is any one of the at least one landing page;

and a landing page display module 1004, configured to display the target landing page based on the page data of the target landing page.

FIG. 11 is a block diagram illustrating a computer device in accordance with an exemplary embodiment. The computer device may be implemented as a server cluster in the above method embodiments. The computer device 1100 includes a central processing unit 1101, a system Memory 1104 including a Random Access Memory (RAM) 1102 and a Read-Only Memory (ROM) 1103, and a system bus 1105 connecting the system Memory 1104 and the central processing unit 1101. The computer device 1100 also includes a basic input/output system 1106, which facilitates transfer of information between devices within the computer, and a mass storage device 1107 for storing an operating system 1113, application programs 1114, and other program modules 1115.

The mass storage device 1107 is connected to the central processing unit 1101 through a mass storage controller (not shown) that is connected to the system bus 1105. The mass storage device 1107 and its associated computer-readable media provide non-volatile storage for the computer device 1100. That is, the mass storage device 1107 may include a computer-readable medium (not shown) such as a hard disk or Compact disk Read-Only Memory (CD-ROM) drive.

Without loss of generality, the computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, flash memory or other solid state storage technology, CD-ROM, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer storage media is not limited to the foregoing. The system memory 1104 and mass storage device 1107 described above may be collectively referred to as memory.

The computer device 1100 may connect to the internet or other network devices through the network interface unit 1111 that is connected to the system bus 1105.

The memory further includes one or more programs, the one or more programs are stored in the memory, and the central processor 1101 implements all or part of the steps executed by the server cluster in the method shown in fig. 3 or fig. 4 by executing the one or more programs.

Fig. 12 shows a schematic structural diagram of a terminal 1200 according to an exemplary embodiment of the present application. The terminal 1200 may be a portable mobile terminal such as: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion video Experts compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, motion video Experts compression standard Audio Layer 4), a notebook computer, or a desktop computer. Terminal 1200 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, and so forth.

In general, terminal 1200 includes: a processor 1201 and a memory 1202.

The processor 1201 may include one or more processing cores, such as a 4-core processor, a 12-core processor, or the like. The processor 1201 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). In some embodiments, the processor 1201 may be integrated with a GPU (Graphics Processing Unit, image Processing interactor), and the processor 1201 may further include an AI (Artificial Intelligence) processor.

Memory 1202 may include one or more computer-readable storage media, which may be non-transitory. Memory 1202 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 1202 is used to store at least one instruction for all or part of the steps executed by the target terminal in the method provided by processor 1201 to implement various method embodiments in the present application.

In some embodiments, the terminal 1200 may further optionally include: a peripheral interface 1203 and at least one peripheral. The processor 1201, memory 1202, and peripheral interface 1203 may be connected by a bus or signal line. Various peripheral devices may be connected to peripheral interface 1203 via a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 1204, display 1205, camera assembly 1206, audio circuitry 1207, positioning assembly 1208, and power supply 1209.

The peripheral interface 1203 may be used to connect at least one peripheral associated with I/O (Input/Output) to the processor 1201 and the memory 1202.

The Radio Frequency circuit 1204 is used for receiving and transmitting a Radio Frequency (RF) signal.

The display screen 1205 is used to display a UI (user interface). The display screen 1205 also has the ability to capture touch signals on or over the surface of the display screen 1205.

Camera assembly 1206 is used to capture images or video.

The audio circuitry 1207 may include a microphone and a speaker.

The positioning component 1208 is configured to locate a current geographic Location of the terminal 1200 to implement navigation or LBS (Location Based Service).

The power supply 1209 is used to provide power to various components within the terminal 1200.

In some embodiments, terminal 1200 also includes one or more sensors 1210. The one or more sensors 1210 include, but are not limited to: acceleration sensor 1211, gyro sensor 1212, pressure sensor 1213, fingerprint sensor 1214, optical sensor 1215, and proximity sensor 1216.

Those skilled in the art will appreciate that the configuration shown in fig. 12 is not intended to be limiting of terminal 1200 and may include more or fewer components than shown, or some components may be combined, or a different arrangement of components may be used.

In an exemplary embodiment, a non-transitory computer readable storage medium including instructions, such as a memory including at least one computer program, executable by a processor to perform all or part of the steps of the method illustrated in the corresponding embodiment of fig. 3 or 4 is also provided. The non-transitory computer readable storage medium may be, for example, ROM, RAM, CD-ROM.

According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the terminal reads the computer instructions from the computer-readable storage medium, and executes the computer instructions, so that the terminal performs the method provided in the various alternative implementations of the above-described aspects.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

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

Claims

1. A page data processing method, wherein the method is executed by a server cluster, and the method comprises the following steps:

responding to an entry page request sent by a target terminal received by an entry page interface server, and sending an entry page field message through the entry page interface server; the portal page request is used for requesting to acquire a target portal page; the target entry page comprises a trigger entry of a landing page;

receiving the entry page field message through a landing page interface server;

extracting the configuration information of the target entry page from the entry page field message through the landing page interface server, wherein the configuration information of the target entry page is used for indicating a data interface API corresponding to a landing page in the target entry page;

acquiring page data of at least one landing page based on a data interface of the at least one landing page;

pushing the binary data stream to the target terminal so that the target terminal can analyze page data of the target landing page from the binary data stream when receiving a trigger operation on a trigger entry of the target landing page; the target landing page is any one of the at least one landing page.

2. The method according to claim 1, wherein said sending, by the portal page interface server, a portal page field message in response to the portal page interface server receiving the portal page request sent by the target terminal comprises:

3. The method according to claim 2, wherein the extracting, by the portal page interface server, the configuration information of the target portal page from the portal page information returned to the target terminal by the portal page interface corresponding to the target portal page comprises:

4. The method of claim 1, wherein sending a portal page field message through the portal page interface server comprises:

sending the portal page field message to a target message platform through the portal page interface server;

the receiving, by the landing page interface server, the entry page field message includes:

and monitoring the entry page field message received by the target message platform through the landing page interface server.

5. The method of claim 1, wherein the portal page field message contains a preload context field and an item field;

6. The method of claim 1, wherein determining the landing page data interface based on the configuration information of the target portal page comprises:

matching the configuration information of the target entry page with each consumption group through a landing page interface server, wherein each consumption group in each consumption group corresponds to a data interface;

7. The method of claim 6, further comprising:

intercepting and identifying a second target object with annotation in a code of the data interface of the landing page when the landing page interface server initializes the data interface of the landing page;

analyzing the annotation in the second target object through the landing page interface server to obtain the configuration information of the landing page;

and creating a consumption group of the landing page based on the configuration information of the landing page through the landing page interface server.

8. A page data processing method is characterized in that the method is executed by a target terminal, and the method comprises the following steps:

displaying a target entry page requested by a request, wherein the target entry page comprises at least one triggering entry of a landing page;

receiving a binary data stream pushed by a server cluster, wherein the binary data stream is obtained by converting page data according to a specified data structure after the server cluster determines at least one data interface of the landing page based on the configuration information of the target entry page and obtains the page data of at least one landing page based on the at least one data interface of the landing page; the configuration information of the target portal page is information which is extracted from a portal page field message by the server cluster through a landing page interface server, wherein the server cluster responds to the portal page request sent by the target terminal and received by the portal page interface server, the portal page field message is sent by the portal page interface server, the landing page field message is received by the landing page interface server, and the landing page interface server is used for extracting the portal page field message; the portal page request is used for requesting to acquire the target portal page; the configuration information of the target entry page is used for indicating a data interface API corresponding to a landing page in the target entry page;

9. A page data processing apparatus, characterized in that the apparatus comprises:

the system comprises a configuration information acquisition module, a configuration information acquisition module and a control module, wherein the configuration information acquisition module is used for responding to an entry page interface server receiving an entry page request sent by a target terminal and sending an entry page field message through the entry page interface server, the entry page request is used for requesting to acquire a target entry page, and the target entry page comprises a trigger entry of a landing page; receiving the entry page field message through a landing page interface server; extracting the configuration information of the target entry page from the entry page field message through the landing page interface server, wherein the configuration information of the target entry page is used for indicating a data interface API corresponding to a landing page in the target entry page;

10. A page data processing apparatus, characterized in that the apparatus comprises:

the data stream receiving module is used for receiving a binary data stream pushed by a server cluster, wherein the binary data stream is obtained by the server cluster through determining at least one data interface of the landing page based on the configuration information of the target entry page, and converting the page data according to a specified data structure after acquiring the page data of at least one landing page based on the data interface of the landing page; the configuration information of the target portal page is information which is extracted from a portal page field message by the server cluster through a landing page interface server, wherein the server cluster responds to the portal page request sent by a target terminal and received by the portal page interface server, the portal page field message is sent by the portal page interface server, the landing page field message is received by the landing page interface server, and the landing page interface server is used for extracting the portal page field message; the portal page request is used for requesting to acquire the target portal page; the configuration information of the target entry page is used for indicating a data interface API corresponding to a landing page in the target entry page;

11. A computer device comprising a processor and a memory, said memory having stored therein at least one computer program, said at least one computer program being loaded and executed by said processor to implement the page data processing method according to any one of claims 1 to 8.

12. A computer-readable storage medium, in which at least one computer program is stored, which is loaded and executed by a processor to implement the page data processing method according to any one of claims 1 to 8.