Page configuration method, system, device, apparatus and storage medium

Abstract

This disclosure relates to the field of computer technology, and in particular to a page configuration method, system, apparatus, device, and storage medium. The server-side implementation method is as follows: Obtaining a page request transmitted by the client; sending a data retrieval instruction to the operator based on the page request, and obtaining template data, floor data, rule data, and dependency data returned by the operator; determining the target processing rule corresponding to the page request in the rule data; executing the target processing rule to process the page request, and calling the dependency interfaces required for the execution of the target processing rule configured in the dependency data; obtaining the target page template corresponding to the page request from the template data, and obtaining the target floor sequence corresponding to the target page template from the floor data; returning the target floor sequence to the client. This disclosure addresses the shortcomings of existing technologies where page configuration heavily relies on the skill level of technical personnel, leading to low efficiency, and achieves efficient page configuration.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to a page configuration method, system, apparatus, device, and storage medium. Background Technology

[0002] In existing technologies, web pages displayed on devices such as computers, smartphones, and PCs—for example, pages displayed in e-commerce systems—require technical personnel to develop, build, or maintain them. There are typically two rapid deployment solutions: one involves technical personnel developing and maintaining the pages based on the existing interface capabilities of the platform. However, due to the large number of interfaces, the configuration process is complex, with many redundant fields, leading to inefficiency. The other approach involves assigning a specific team of technical personnel to develop the page, and then handing it over to a new team for maintenance. However, this configuration process still heavily relies on the skill level of the technical personnel, and the new team often lacks a deep understanding of the existing code, making later maintenance and iterative updates difficult, again resulting in inefficiency. Both of these methods suffer from inefficiency due to their heavy reliance on the skill level of the technical personnel. Summary of the Invention

[0003] This disclosure provides a page configuration method, system, apparatus, device, and storage medium to address the shortcomings of existing technologies where page configuration heavily relies on the skill level of technicians, leading to low efficiency, and to achieve efficient page configuration.

[0004] This disclosure provides a page configuration method applied to a server, comprising: obtaining a page request transmitted by a client; sending a data acquisition instruction to an operation terminal according to the page request, and obtaining template data, floor data, rule data, and dependency data returned by the operation terminal; determining a target processing rule in the rule data corresponding to the page request; executing the target processing rule to process the page request, and calling the dependency interfaces configured in the dependency data required for the execution of the target processing rule; obtaining a target page template corresponding to the page request from the template data, and obtaining a target floor sequence corresponding to the target page template from the floor data; and returning the target floor sequence to the client, wherein the client is used to parse the target floor sequence to generate a page.

[0005] According to a page configuration method provided in this disclosure, the server includes a page software development kit (SDK); obtaining a page request transmitted by a client includes: based on the SSD, obtaining the page request transmitted by the client through a gateway interface registered in the gateway, wherein the gateway interface is used to connect the client and the server; sending a data acquisition instruction to the operation end according to the page request to obtain template data, floor data, rule data, and dependency data returned by the operation end includes: based on the SSD, sending a data acquisition instruction to the operation end according to the page request to obtain the template data, floor data, rule data, and dependency data returned by the operation end; determining the target processing rule corresponding to the page request in the rule data includes: based on the SSD, parsing the page request to obtain a request path, wherein the request path includes the gateway interface through which the page request passes, and the rule data includes the correspondence between the gateway interface and the target processing rule; determining the target processing rule according to the gateway interface in the request path and the correspondence.

[0006] According to a page configuration method provided in this disclosure, the server includes a service cluster; after obtaining the target floor sequence corresponding to the target page template from the floor data, and before returning the target page template and the target floor sequence to the client, the method further includes: obtaining upstream dependency data through the dependency interface based on the service cluster; filling data for each floor in the target floor sequence based on the upstream dependency data; and returning the target floor sequence to the client, which includes: returning the filled target floor sequence to the client based on the service cluster, wherein the filled target floor sequence includes at least one component data corresponding to the floor, and the component data is used to support the display of the floor on the client.

[0007] According to a page configuration method provided in this disclosure, before filling data for each floor in the target floor sequence based on the upstream dependency data, the method further includes: based on the service cluster, closing at least one floor in the target floor sequence through a preset filter, wherein the preset filter is set according to the principles of whitelisting, traffic switching, and / or grayscale; filling data for each floor in the target floor sequence based on the upstream dependency data includes: based on the service cluster, filling data for each floor in the target floor sequence that is not closed through the upstream dependency data.

[0008] This disclosure also provides a page configuration method applied to a client, comprising: generating a page request when a page trigger instruction is received; transmitting the page request to a server, wherein the server is used to obtain the page request transmitted by the client; sending a data acquisition instruction to an operator according to the page request, and obtaining template data, floor data, rule data, and dependency data returned by the operator; determining the target processing rule corresponding to the page request in the rule data; calling the dependency interface configured in the dependency data required to execute the target processing rule, and executing the target processing rule to process the page request; obtaining the target page template corresponding to the page request from the template data, and obtaining the target floor sequence corresponding to the target page template from the floor data; returning the target floor sequence to the client; obtaining the target floor sequence returned by the server; and parsing the target floor sequence to generate a page.

[0009] According to a page configuration method provided in this disclosure, the step of parsing the target floor sequence to generate a page includes: loading component data corresponding to each floor in the target floor sequence; loading style information corresponding to each floor in the target floor sequence; loading the sorting of each floor in the target floor sequence; and rendering and generating the page based on the component data, the style information, and the sorting.

[0010] This disclosure also provides a page configuration method applied to an operational end, comprising: receiving a data configuration instruction; configuring and storing template data, floor data, rule data, and dependency data according to the data configuration instruction; obtaining a data acquisition instruction sent by a server; and returning the template data, floor data, rule data, and dependency data to the server according to the data acquisition instruction; wherein, the template data includes at least one page template, the floor data includes a floor sequence corresponding to each page template, and each floor sequence includes at least one floor arranged in sequence; the floor data includes related data for at least one floor, wherein the related data includes at least one of the floor's identifier, style information, and component data; the rule data includes at least one request processing rule; and the dependency data includes dependency interfaces required when each processing rule is executed, and each processing rule obtains the corresponding page template after calling the dependency interface.

[0011] According to a page configuration method provided in this disclosure, after configuring and storing template data, floor data, rule data, and dependency data according to the data configuration instruction, the method further includes: receiving an update configuration instruction; configuring the latest template data, latest floor data, latest rule data, and / or latest dependency data according to the update configuration instruction; and updating the corresponding template data, floor data, rule data, and / or dependency data according to the latest template data, the latest floor data, the latest rule data, and / or the latest dependency data.

[0012] According to a page configuration method provided in this disclosure, after configuring rule data according to the data configuration instruction, the method further includes: receiving a gateway configuration instruction; configuring the correspondence between the gateway interface and the processing rule according to the gateway configuration instruction, wherein the page software development kit in the server determines the target processing rule according to the correspondence.

[0013] This disclosure also provides a page configuration system, including a server, a client, and an operation terminal; the client is used to generate a page request when receiving a page trigger instruction; transmit the page request to the server; obtain the target floor sequence returned by the server; parse the target floor sequence to generate a page; the server is used to obtain the page request transmitted by the client; send a data acquisition instruction to the operation terminal according to the page request, obtain template data, floor data, rule data, and dependency data returned by the operation terminal; determine the target processing rule in the rule data corresponding to the page request; and execute the target processing rule to process the page request. The system calls the dependency interfaces required for executing the target processing rules configured in the dependency data, retrieves the target page template corresponding to the page request from the template data, and retrieves the target floor sequence corresponding to the target page template from the floor data; returns the target floor sequence to the client; the operation terminal receives data configuration instructions; configures and stores template data, floor data, rule data, and dependency data according to the data configuration instructions; retrieves data retrieval instructions sent by the server; and returns the template data, floor data, rule data, and dependency data to the server according to the data retrieval instructions.

[0014] According to a page configuration system provided in this disclosure, the server includes a page software development kit (SDK). The SSD is configured to: acquire a page request transmitted by a client through a gateway interface registered in a gateway, wherein the gateway interface connects the client and the server; send a data acquisition instruction to an operator based on the page request to acquire template data, floor data, rule data, and dependency data returned by the operator; parse the page request to obtain a request path, wherein the request path includes the gateway interface through which the page request passes, and the rule data includes the correspondence between the gateway interface and the target processing rule; and determine the target processing rule based on the gateway interface in the request path and the correspondence.

[0015] According to a page configuration system provided in this disclosure, the server includes a service cluster; the page software development kit is used to transmit the target page template, the target floor sequence, and the target processing rules to the service cluster; the service cluster is used to obtain upstream dependency data through the dependency interface; based on the upstream dependency data, it populates data for each floor in the target floor sequence; and returns the populated target floor sequence to the client, wherein the populated target floor sequence includes at least one component data corresponding to the floor, and the component data is used to support the display of the floor on the client.

[0016] According to a page configuration system provided in this disclosure, the service cluster is used to close at least one floor in the target floor sequence through a preset filter, wherein the preset filter is set according to the principles of whitelisting, traffic cutting, and / or grayscale; and to populate data for each floor in the target floor sequence that is not closed through the upstream dependency data.

[0017] This disclosure also provides a server-side device for page configuration, comprising: a first acquisition module for acquiring a page request transmitted by a client; a second acquisition module for sending a data acquisition instruction to an operator according to the page request, and acquiring template data, floor data, rule data, and dependency data returned by the operator; a determination module for determining a target processing rule in the rule data corresponding to the page request; an execution module for executing the target processing rule to process the page request, and calling the dependency interfaces configured in the dependency data required for the execution of the target processing rule, acquiring a target page template corresponding to the page request from the template data, and acquiring a target floor sequence corresponding to the target page template from the floor data; and a sequence return module for returning the target floor sequence to the client, wherein the client is used to parse the target floor sequence to generate a page.

[0018] This disclosure also provides a client device for page configuration, comprising: a request generation module, configured to generate a page request when a page trigger instruction is received; a request transmission module, configured to transmit the page request to a server, wherein the server is configured to obtain the page request transmitted by the client, send a data acquisition instruction to an operator according to the page request, obtain template data, floor data, rule data, and dependency data returned by the operator, determine the target processing rule corresponding to the page request in the rule data, call the dependency interface configured in the dependency data required to execute the target processing rule, and execute the target processing rule to process the page request, obtain the target page template corresponding to the page request from the template data, and obtain the target floor sequence corresponding to the target page template from the floor data, and return the target floor sequence to the client; a third acquisition module, configured to acquire the target floor sequence returned by the server; and a parsing module, configured to parse the target floor sequence to generate a page.

[0019] This disclosure also provides an operator-side device for page configuration, comprising: an instruction receiving module for receiving data configuration instructions; a data configuration module for configuring and storing template data, floor data, rule data, and dependency data according to the data configuration instructions; a fourth acquisition module for acquiring data acquisition instructions sent by a server; and a data return module for returning the template data, floor data, rule data, and dependency data to the server according to the data acquisition instructions.

[0020] The template data includes at least one page template; the floor data includes a floor sequence corresponding to each page template, and each floor sequence includes at least one floor arranged in sequence; the floor data includes related data for at least one floor, wherein the related data includes at least one of the floor's identifier, style information, and component data; the rule data includes at least one request processing rule; the dependency data includes the dependency interfaces required for the execution of each processing rule, and each processing rule obtains the corresponding page template after calling the dependency interface.

[0021] This disclosure also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the page configuration method as described in any of the preceding claims.

[0022] This disclosure also provides a non-transitory computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the page configuration method as described in any of the preceding claims.

[0023] The page configuration method, system, device, equipment, and storage medium disclosed herein complete page configuration through the cooperation of a client, server, and operator. The operator is used to configure and store template data, floor data, rule data, and dependency data. After receiving a page request from the client, the server retrieves pre-configured template data, floor data, rule data, and dependency data from the operator based on the request. Then, after determining the target rule data, the server executes the target rule data and calls the dependency interfaces in the dependency data to determine the target page template and the corresponding target floor sequence. The server returns the target floor sequence to the client, which generates the page based on the target floor data. In this process, the configuration of template data, floor data, rule data, and dependency data is pre-completed by the operator, and the use of template data and floor data makes the configuration process templated and floor-based, reducing the configuration difficulty for the operator and improving configuration efficiency. The server automatically obtains the target floor sequence by executing pre-set target processing rules and calling the dependency interfaces required by those rules; finally, the client generates the page based on the target floor sequence. The server and client sides have implemented automated page configuration, freeing up a significant amount of manpower and further improving configuration efficiency. Meanwhile, the operations side features templated and layered configuration. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0025] Figure 1 This is a flowchart illustrating the page configuration method provided in this publication, which uses the server as the execution entity.

[0026] Figure 2 This is a flowchart illustrating the page configuration method with the client as the execution subject provided in this disclosure;

[0027] Figure 3 This is a flowchart illustrating the page configuration method provided in this public disclosure, which uses the operator's side as the execution entity.

[0028] Figure 4 This is a schematic diagram of the page configuration system structure provided in this publication;

[0029] Figure 5 This is a functional diagram of the various components of the configuration system provided in this disclosure;

[0030] Figure 6This is one of the schematic diagrams illustrating the implementation logic of the page configuration method provided in this disclosure;

[0031] Figure 7 This is the second schematic diagram illustrating the implementation logic of the page configuration method provided in this public disclosure;

[0032] Figure 8 This is the third schematic diagram illustrating the implementation logic of the page configuration method provided in this public disclosure;

[0033] Figure 9 This is a schematic diagram of the server-side device structure for page configuration provided in this disclosure;

[0034] Figure 10 This is a schematic diagram of the client device structure for page configuration provided in this disclosure;

[0035] Figure 11 This is a schematic diagram of the server-side device structure for page configuration provided in this public disclosure;

[0036] Figure 12 This is a schematic diagram of the structure of the electronic device provided in this disclosure. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the protection scope of the embodiments of this disclosure.

[0038] The technical terms mentioned in this disclosure are explained as follows:

[0039] Software Development Kit (SDK): refers to the collection of development tools required by software engineers to build application software for specific software packages, software frameworks, hardware platforms, operating systems, etc.

[0040] Service-Oriented Architecture (SOA) is a component model that breaks down an application into different functional units (called services) and connects them through well-defined interfaces and protocols. These interfaces are defined in a neutral manner, independent of the hardware platform, operating system, and programming language used to implement the service. This allows services built on a wide variety of systems to interact in a unified and universal way.

[0041] H5 page: A web page generated based on Hyper Text Markup Language (HTML).

[0042] Remote Procedure Call Protocol (RPC): A protocol that allows a program on a remote computer to request services over a network without needing to know the underlying network technology.

[0043] Generalized invocation: The most direct manifestation of this is that service consumers do not need to implement any interface to complete the service invocation.

[0044] MVFLEX Expression Language (MVEL) is a dynamic / static embeddable expression language and a language that provides runtime for the Java platform.

[0045] Rules engine: A component that can reduce the complexity of complex business logic components and reduce the maintenance and scalability costs of applications.

[0046] Page Template: A pre-set template that the client needs to display. One page template corresponds to one target floor sequence, and one target floor sequence corresponds to at least one floor.

[0047] Template data: consists of at least one page template.

[0048] Floor: Used to support the implementation of a unitized functional module, such as displaying user information on a page.

[0049] Floor data: includes at least one floor.

[0050] Processing rules: Supporting data for implementing preset data processing logic.

[0051] Dependency Interfaces: Interfaces that need to be called when executing rules.

[0052] Traffic cutting is a method of controlling the ingress traffic when the system encounters a fault or when traffic ingress is deliberately controlled (such as during canary releases).

[0053] Hypertext Transfer Protocol (HTTP): A simple request-response protocol that specifies what messages a client might send to a server and what kind of response it might receive.

[0054] The page configuration method disclosed herein is implemented through the cooperation of a client, a server, and an operation unit. The client and server can interact with each other, and the server and operation unit can also interact with each other. The client ultimately generates the page for display. It should be noted that the client, server, and operation unit can be implemented on different processing devices, such as computers, smartphones, tablets, and any other device with data processing capabilities. Since the client needs to display the final generated page to the user, the device on which the client resides must have page display functionality; for example, the client device must include a display interface capable of displaying the generated page.

[0055] First, the page configuration method provided in this publication will be introduced with the server as the execution subject.

[0056] In one embodiment, such as Figure 1 As shown, the process of implementing the page configuration method with the server as the execution entity is as follows:

[0057] Step 101: Obtain the page request transmitted by the client.

[0058] In this embodiment, the client and server can interact with each other. When the client receives a page trigger instruction, it generates a page request and then transmits the page request to the server. The server then obtains the page request and performs subsequent processing based on it. The page request carries specified information, such as the client type.

[0059] Step 102: Send a data retrieval instruction to the operations side according to the page request, and obtain the template data, floor data, rule data and dependency data returned by the operations side.

[0060] In this embodiment, after the server receives the page request, it generates a data retrieval instruction based on the page request and transmits the data retrieval instruction to the operations side. After receiving the data retrieval instruction, the operations side returns the template data, floor data, rule data, and dependency data required by the server to the server.

[0061] In this embodiment, the template data includes at least one page template, the floor data includes a floor sequence corresponding to each page template, and each floor sequence includes at least one floor arranged in order; the floor data includes related data for at least one floor, wherein the related data includes at least one of the floor identifier, style information and component data; the rule data includes at least one request processing rule; the dependency data includes the dependency interface required when each processing rule is executed, and each processing rule obtains the corresponding page template after calling the dependency interface.

[0062] Specifically, a page can be constructed from at least one floor. A page template represents a page display template. Each page template requires at least one floor to build a page; all the floors required for a page template form the floor sequence corresponding to that page template. The floors in the floor sequence are arranged in the configured order. Different page templates may have duplicate floors. For example, page template 1 corresponds to floors 1, 2, and 3; page template 2 corresponds to floors 2 and 3. Floor data includes relevant data for each floor. For example, the operations side stores pre-configured identifiers and style information for each floor; or the floor component data is React Native (RN) components. Rule data includes at least one pre-configured processing rule, which refers to a logical rule that can process data. This processing rule can be executed under specific conditions, such as with the support of a rule engine, to complete the processing logic specified by the rule. When any processing rule is executed, at least one dependency interface needs to be called. This dependency interface is used to obtain third-party data required for the execution of the processing rule, such as an identity interface, which determines the identity data corresponding to the page request. More specifically, the dependency interface can be configured based on existing APIs.

[0063] Step 103: Determine the target processing rule in the rule data that corresponds to the page request.

[0064] In this embodiment, the rule data pre-configured on the operation side includes at least one processing rule, and each processing rule can implement preset processing logic. The page request transmitted by the client to the server is used to request the generation of a page with a specific style. Generating this page requires the execution of a processing rule, that is, the execution of the target processing rule.

[0065] In this embodiment, the processing rules are essentially logic code written by technical personnel, such as expression languages ​​based on Java applications, and more specifically, processing rules written based on the MVFLEX Expression Language (MVEL), i.e., MVEL rules. The MVEL rules configured and stored on the operations side are static data, and a rule engine for executing these MVEL rules, such as an MVEL engine, is pre-written into the server side. The rule engine ensures that the processing rules can be executed correctly on the server side. The rule engine is a component that can reduce the complexity of complex business logic components and lower the maintenance and scalability costs of the application.

[0066] Step 104: Execute the target processing rules to process the page request, and call the dependency interfaces required for the execution of the target processing rules configured in the dependency data. Obtain the target page template corresponding to the page request from the template data, and obtain the target floor sequence corresponding to the target page template from the floor data.

[0067] In this embodiment, after determining the target processing rule, the server executes the target processing rule to process the page request. Simultaneously, the processing rule pre-writes the dependency interfaces required for execution. The target processing rule processes the page request based on the configured dependency interfaces. After executing the page request, the target processing rule can obtain the target page template corresponding to the page request from the template data, and then obtain the target floor sequence corresponding to the target page template from the floor data. The target floor sequence includes at least one floor for generating the page.

[0068] Step 105: Return the target floor sequence to the client, where the client is used to parse the target floor sequence to generate the page.

[0069] In this embodiment, after obtaining the target floor sequence, the server returns the target floor sequence to the client that sent the page request, and the client parses the target floor sequence to generate the page.

[0070] In one embodiment, the server includes a page software development kit (SDK) and a service cluster. The SDK is pre-configured according to actual needs and requirements. The service cluster includes at least one virtual server, each implementing a pre-defined function, such as populating floor information with third-party identity data. The servers in the service cluster can run concurrently. More specifically, the service cluster is based on a Service-Oriented Architecture (SOA) cluster. SOA is a component model that breaks down different functional units of an application (called services) and connects them through well-defined interfaces and protocols. By adopting the SDK and SOA cluster, the processing speed of page requests can be accelerated, and page configuration efficiency can be improved.

[0071] In one embodiment, the page SDK completes pre-defined pre-processing. Specifically, when the server includes the page software development kit, it obtains the page request transmitted by the client, and the implementation process is as follows: Based on the page software development kit, it obtains the page request transmitted by the client through the gateway interface registered in the gateway, wherein the gateway interface is used to connect the client and the server. It sends a data acquisition instruction to the operation end according to the page request, and obtains the template data, floor data, rule data, and dependency data returned by the operation end, and the implementation process is as follows: Based on the page software development kit, it sends a data acquisition instruction to the operation end according to the page request, and obtains the template data, floor data, rule data, and dependency data returned by the operation end. It determines the target processing rule corresponding to the page request in the rule data, and the implementation process is as follows: Based on the page software development kit, it parses the page request and obtains the request path, wherein the request path includes the gateway interface through which the page request passes, and the rule data includes the correspondence between the gateway interface and the target processing rule; based on the gateway interface and the correspondence in the request path, the target processing rule is determined.

[0072] In this embodiment, page requests sent by the client are transmitted to the server through a gateway. The gateway can perform functions such as request forwarding, authentication, and risk control interception. More specifically, the client can be an app, a mini-program, or an H5 page based on Hyper Text Markup Language (HText Markup Language). The gateway interface used for data interaction between different client types and the server is different. The operator pre-binds the processing rules and gateway interfaces and registers them with the gateway. The rule data also pre-writes the correspondence between gateway interfaces and processing rules. When the server obtains a page request through the interface, it parses the request and, through the request path carried by the page request, can determine the gateway interface through which the page request passed, thereby obtaining the target processing rule corresponding to the gateway interface and invoking the target processing rule.

[0073] In this embodiment, the operator can pre-configure the mapping between gateway interfaces and page templates, with one gateway interface corresponding to at least one page template. Specifically, for example, a gateway interface used by an app can correspond to multiple app-specific page templates; a gateway interface used by an H5 client can correspond to multiple H5-style page templates. In this way, page requests from different client types pass through different gateway interfaces, thus determining the corresponding processing rules. Simultaneously, the page templates are also corresponding, avoiding processing confusion between different client types and improving processing efficiency.

[0074] In this embodiment, before the SOA cluster receives a page request, the SDK intercepts the request and determines the target processing rule based on the gateway interface the request passes through. According to this target processing rule, the SDK calls the necessary dependent interfaces, which are third-party interfaces in the microservice, such as the identity interface, to determine whether the request is from a regular user or a non-regular user. Among the multiple page templates corresponding to the gateway interface, the SDK selects the target page template based on the user's identity, and then obtains the target floor sequence to be displayed based on the target page template.

[0075] In one embodiment, the server includes a service cluster. After obtaining the target floor sequence corresponding to the target page template from the floor data, before returning the target page template and the target floor sequence to the client, the server obtains upstream dependency data through a dependency interface based on the service cluster. Based on the upstream dependency data, data is populated for each floor in the target floor sequence. The target floor sequence is then returned to the client. Specifically, the populated target floor sequence includes at least one component data corresponding to a floor, which is used to support the display of the floor on the client.

[0076] In this embodiment, after the SDK completes the pre-processing, the SOA continues to complete the page request based on the target processing rules. More specifically, the template data and floor data configured and stored on the operations side only configure the architecture and style of the page and floors. For example, when the operations side configures the floor sequence corresponding to a page template, it only configures the identifier and style data of each floor, reducing the amount of redundant data when the server executes the target processing rules. If each floor can be displayed normally on the client, data needs to be populated for each floor in the target floor sequence. Since the populated data (i.e., upstream dependency data) can be provided by a third party through the dependency interface, and the target floor sequence is determined according to the target processing rules, data is populated through the dependency interface to ensure that the client can render and generate the page normally.

[0077] In this embodiment, the SDK pre-implements generic invocation based on the Remote Procedure Call Protocol (RPC) framework. The most direct manifestation of generic invocation is that service consumers do not need to implement any interface to complete service invocation. Using generic invocation reduces configuration difficulty and improves configuration efficiency.

[0078] In one embodiment, the service cluster can implement floor filtering. Before populating each floor in the target floor sequence with data based on upstream dependency data, at least one floor in the target floor sequence is shut down using a preset filter based on the service cluster. This preset filter is set according to principles of whitelisting, traffic switching, and / or gray-scale deployment. Specifically, the process of populating each floor in the target floor sequence with data based on upstream dependency data is as follows: Data is populated for each floor in the target floor sequence that is not shut down, using the upstream dependency data from the service cluster.

[0079] In this embodiment, technicians can pre-write whitelists, traffic-cutting lists, and / or gray-scale lists into the service cluster according to actual conditions and needs. Based on the principles of whitelists, traffic-cutting, and / or gray-scale, filters are used to filter floors. For example, if the method provided in the above embodiment has determined that the identity corresponding to the page request is a regular user rather than a non-regular user, then according to the whitelist, a specific floor in the target floor sequence corresponding to the page request needs to be closed. This specific floor is closed using a preset filter, and then data is populated for each floor in the target floor sequence that is not closed. Through the above process, the flexibility of floor management is increased, ensuring that the client can display the correct page and improving the configuration effect.

[0080] In this embodiment, the page request can also include relevant data about floors already existing on the client's end, such as the identifiers of existing floors. After parsing the page request, the server can avoid repeatedly filling in the floor data already present on the client's end. After the server returns the target floor sequence to the client, the client can render and generate the page based on the floor-related data already existing locally and the floor-related data transmitted by the server. In this way, the floor-related data already stored on the client can be reused, reducing the amount of data transmitted between the client and the server, speeding up processing and transmission, and avoiding resource waste.

[0081] In this embodiment, a preview function can also be provided to specific users through a service pre-configured in the SOA cluster, thereby enhancing the user experience.

[0082] The following section describes the page configuration methods provided by this disclosure, using the client as the execution subject.

[0083] In one embodiment, such as Figure 2 As shown, the process of implementing the page configuration method with the client as the execution subject is as follows:

[0084] Step 201: When a page trigger instruction is received, a page request is generated.

[0085] In this embodiment, a page trigger instruction is generated when a user has a need. For example, when the client is opened during a promotion in an e-commerce system, the client generates a page request.

[0086] Step 202: The page request is transmitted to the server, whereby the server receives the page request transmitted by the client; sends a data retrieval instruction to the operations side based on the page request, and retrieves the template data, floor data, rule data, and dependency data returned by the operations side; determines the target processing rule corresponding to the page request in the rule data; calls the dependency interface configured in the dependency data to execute the target processing rule and executes the target processing rule to process the page request; retrieves the target page template corresponding to the page request from the template data, and retrieves the target floor sequence corresponding to the target page template from the floor data; and returns the target floor sequence to the client.

[0087] In this embodiment, the client transmits a page request to the server. The server, based on the page request and the template data, floor data, rule data, and dependency data pre-set by the operator, obtains the final target floor sequence. The server then returns the target floor sequence to the client.

[0088] Step 203: Obtain the target floor sequence returned by the server.

[0089] Step 204: Parse the target floor sequence to generate the page.

[0090] In this embodiment, after the client obtains the target floor sequence returned by the server, the client parses the target floor sequence and generates the final page to be displayed locally.

[0091] In one embodiment, the client parses the target floor sequence to generate a page. The specific implementation process is as follows: loading the component data corresponding to each floor in the target floor sequence; loading the style information corresponding to each floor in the target floor sequence; loading the sorting of each floor in the target floor sequence; and rendering and generating the page based on the component data, style information, and sorting.

[0092] In this embodiment, the client generates pages in a layered and component-based manner. Specifically, each layer in the target layer sequence corresponds to a specific component data. The client loads the component data for each layer, then loads the style information corresponding to each layer, and finally renders the final page to be displayed according to the arrangement order of each layer in the target layer sequence. More specifically, each layer can be rendered concurrently, improving rendering speed and providing the page to the user faster.

[0093] In this embodiment, the client can also render and generate a page based on the locally stored floor component data and the newly added floor component data transmitted by the server, avoiding resource waste, making full use of local resources, reducing the amount of data transmission between the client and the server, and further improving page configuration efficiency.

[0094] The following section describes the page configuration method provided in this publication, focusing on the operational side.

[0095] In one embodiment, such as Figure 3 As shown, the process of implementing the page configuration method with the operation side as the execution entity is as follows:

[0096] Step 301: Receive data configuration instructions.

[0097] Step 302: Configure and store template data, floor data, rule data, and dependency data according to the data configuration instructions.

[0098] Step 303: Obtain the data retrieval command sent by the server.

[0099] Step 304: According to the data acquisition instructions, return the template data, floor data, rule data, and dependency data to the server.

[0100] The template data includes at least one page template; the floor data includes a floor sequence corresponding to each page template, and each floor sequence includes at least one floor arranged in order; the floor data includes related data for at least one floor, wherein the pipeline data includes at least one of the floor identifier and style information component data; the rule data includes at least one request processing rule; the dependency data includes the dependency interface required for the execution of each processing rule, and each processing rule obtains the corresponding page template after calling the dependency interface.

[0101] In this embodiment, the operator uses data configuration instructions to pre-configure and store template data, floor data, rule data, and dependency data. When the server requests the template data, floor data, rule data, and dependency data from the operator via a data retrieval instruction, the requested template data, floor data, rule data, and dependency data are returned to the server, enabling the server to obtain the target floor sequence. After the server transmits the target floor sequence to the client, the client renders and generates a page for display.

[0102] In a specific example, the operations team can configure template data, floor data, rule data, and dependency data through a visual interface. Templates can be switched, and the type of each page template can be selected. Specific parameters for each page template can be configured through its sub-interfaces, enabling template management. The floor management sub-interface allows configuration of specific parameters for each floor. Style management is also possible through the visual interface, configuring style information for templates or floors, including style names and codes. The interface displays the configured style information, providing previews and information such as the creator and creation time, facilitating management by operations personnel. Rule data is configured through the floor data dependency rule sub-interface. Finally, the interface management sub-interface allows configuration of various dependency interfaces within the dependency data, and may also allow configuration of gateway interfaces.

[0103] In one embodiment, after configuring and storing template data, floor data, rule data, and dependency data according to the data configuration instruction, an update configuration instruction is received; according to the update configuration instruction, the latest template data, latest floor data, latest rule data, and / or latest dependency data are configured; and according to the latest template data, latest floor data, latest rule data, and / or latest dependency data, the corresponding template data, floor data, rule data, and / or dependency data are updated.

[0104] In this embodiment, the operations side supports dynamic data configuration. When technical personnel have update needs, they can configure the latest template data, floor data, rule data, and / or dependency data using update configuration commands. Then, based on the latest template data, floor data, rule data, and / or dependency data, the stored template data, floor data, rule data, and / or dependency data are updated accordingly. For example, if a new promotional floor is added, the update configuration command can update the stored floor data as the latest floor data.

[0105] In one specific embodiment, dynamic data binding of dependency data and rule data can be achieved through a configuration interface provided by the operations team. For example, through the interface configuration interface provided by the operations team, various preset parameters can be configured, such as the interface method name (e.g., sayHello), the system it belongs to, the type (e.g., http or jsf), the interface address (e.g., com.jd.test), the monitoring master serialization given key (umpkey), the parameter list (e.g., "java.lang.String", "long"), and the timeout (in milliseconds). Furthermore, this interface can be modified or new interfaces can be added at any time, achieving dynamic data configuration and improving flexibility.

[0106] In one specific embodiment, the operations side also provides an interface for hot deployment of processing rules and dependent interfaces. For example, through the rule management interface provided by the operations side, various preset parameters such as the rule's English name (e.g., test3), the rule's Chinese name (ceshi3), the selected interface (e.g., queryForCountByProductld), and the rule content can be configured. The rule content can be implemented by directly writing code, further enhancing the flexibility of the operations side when configuring various data.

[0107] Based on the interface provided by the operator in the above embodiments, the required functions can also be preset in the form of icons, buttons, etc. For example, buttons such as "Save as draft", "Submit and publish", and "Cancel" can be set to realize the corresponding functions.

[0108] In one embodiment, after configuring rule data according to the data configuration instruction, the operator receives a gateway configuration instruction; according to the gateway configuration instruction, it configures the correspondence between the gateway interface and the processing rules, wherein the page software development kit in the server determines the target processing rule according to the correspondence.

[0109] In this embodiment, the server obtains page requests from different gateway interfaces, determines the target processing rules through the request path in the page request, and needs to configure the correspondence between gateway interfaces and processing rules to ensure that the page configuration is executed smoothly and correctly.

[0110] In one specific embodiment, the operation side includes an operation platform and a configuration center. The operation platform provides various configuration interfaces. Once the template data, floor data, rule data, and / or dependency data are configured and officially released, the released effective data—that is, the effective template data, floor data, rule data, and / or dependency data—is stored in the configuration center. More specifically, the configuration center can periodically pull the latest configuration data from the configuration platform at preset intervals—that is, the latest template data, the latest floor data, the latest rule data, and / or the latest dependency data—and update the data already stored in the configuration center, implementing "long polling." This ensures that the data in the configuration center is the latest configured data, further ensuring that the server obtains the latest configured template data, floor data, rule data, and / or dependency data, thereby ensuring that the page generated by the client is in the latest form.

[0111] This disclosure also provides a page configuration system, which is used to implement the page configuration methods provided in the above embodiments, and the details will not be repeated.

[0112] like Figure 4 As shown, the page configuration system includes server 401, client 402, and operation terminal 403.

[0113] Client 402 is used to generate a page request when a page trigger instruction is received; transmit the page request to server 401; obtain the target floor sequence returned by server 401; and parse the target floor sequence to generate the page.

[0114] Server 401 is used to obtain the page request transmitted by client 402; according to the page request, it sends a data acquisition instruction to operation server 403 to obtain the template data, floor data, rule data, and dependency data returned by operation server 403; it determines the target processing rule corresponding to the page request in the rule data; it executes the target processing rule to process the page request, and calls the dependency interface required for the execution of the target processing rule configured in the dependency data, obtains the target page template corresponding to the page request from the template data, and obtains the target floor sequence corresponding to the target page template from the floor data; and returns the target floor sequence to client 402.

[0115] The operations side 403 is used to receive data configuration instructions; configure and store template data, floor data, rule data, and dependency data according to the data configuration instructions; obtain data retrieval instructions sent by the server side 401; and return the template data, floor data, rule data, and dependency data to the server side 401 according to the data retrieval instructions.

[0116] In one embodiment, server 401 includes a page software development kit.

[0117] The page software development kit (SDK) is used to obtain page requests transmitted by client 402 through the gateway interface registered in the gateway. The gateway interface is used to connect client 402 and the server. Based on the page request, it sends a data acquisition instruction to the operation terminal 403 to obtain template data, floor data, rule data, and dependency data returned by the operation terminal 403. It parses the page request to obtain the request path, where the request path includes the gateway interface through which the page request passes, and the rule data includes the correspondence between the gateway interface and the target processing rule. Based on the gateway interface and the correspondence in the request path, it determines the target processing rule.

[0118] In one embodiment, server 401 includes a service cluster.

[0119] The page software development kit is used to transmit the target page template, target floor sequence, and target processing rules to the service cluster.

[0120] The service cluster is used to obtain upstream dependency data through the dependency interface; based on the upstream dependency data, it populates data for each floor in the target floor sequence; and returns the target floor sequence with populated data to the client 402. The target floor sequence with populated data includes component data corresponding to at least one floor. The component data is used to support the display of the floor on the client 402.

[0121] In one embodiment, the service cluster is used to shut down at least one floor in the target floor sequence using a preset filter, wherein the preset filter is set according to the principles of whitelisting, traffic cutting, and / or grayscale; and to populate each floor in the target floor sequence that is not shut down with data using upstream dependency data.

[0122] In one embodiment, the operations side 403 includes an operations platform and a configuration center.

[0123] The operation platform is used to receive data configuration instructions; and to configure template data, floor data, rule data, and dependency data according to the data configuration instructions.

[0124] The configuration center is used to store template data, floor data, rule data, and dependency data; to obtain data retrieval instructions sent by the server 401; and to return the template data, floor data, rule data, and dependency data to the server 401 according to the data retrieval instructions.

[0125] In one embodiment, such as Figure 5 The diagram illustrates the functions of each component of the configuration system. The operations-side configuration platform (i.e., the operations backend) implements template data configuration (template management), floor data configuration (floor management), rule data configuration, and dependency data configuration. More specifically, it can be refined into configuration rules for skin management, operational activities, and other processing rules. The data configured and activated on the operations platform is written to the configuration center, which performs data storage. Furthermore, this configuration center can consist of multiple configuration nodes, implementing a distributed storage model. The underlying data required for various methods implemented on the operations side is stored in a MySQL database. Various functions on the operations side are implemented by calling the underlying data in the MySQL database. More specifically, the MySQL database adopts the required architecture, for example, a master database and at least one slave database.

[0126] In this embodiment, the SDK on the server side starts upon receiving a page request and intercepts the request. Based on the request, it requests the latest style configuration file from the configuration center's cloud storage, specifically the template data, floor data, rule data, and dependency data stored in the configuration center. Taking MVEL-based rule data as an example, the template, floor, and MVEL rule data are distributed to the template and MVEL rule processing SDK (i.e., the page SDK). Simultaneously, the pre-processing dependency interface is called based on the dependency data. After the SDK pre-processes, further processing of the target floor sequence is completed based on the pre-configured servers in the SOA cluster, such as floor data population and data filtering. Then, the SOA cluster transmits the populated template data to the client (taking the APP as an example). The APP renders and generates its native page based on the floors in the template corresponding to the target floor sequence. For example, if the template includes floors 1, 2, 3, and 4, the APP generates and displays pages based on floors 1, 2, 3, and 4.

[0127] In a specific embodiment, such as Figure 6 As shown, if the page request generated by the client is an HTTP request, this HTTP request is transmitted to the server through the gateway, where it is intercepted by the interceptor configured in the server-side SDK. The server retrieves floor, template, rule, and dependency configurations (i.e., template data, floor data, rule data, and dependency data) from the configuration center. The target processing rules are executed through the rule engine configured in the SDK, which implements generic calls based on an RPC framework. The SDK intercepts the HTTP request, processes it according to the MVEL rules, and then sends the target floor sequence (i.e., the new floor list) to the SOA cluster. The SOA cluster handles the filtering of closed floors, calls upstream dependencies, populates floor data, and returns the floor identity document (id) and the data-bound list. During this process, SOA calls upstream dependencies through dependency interfaces. More specifically, upstream dependencies can be pre-set user information, orders, store followers, friends, wallets, Business Intelligence (BI), and other dependency data.

[0128] In this embodiment, as Figure 7 As shown, the SOA cluster distributes template floors (the target floor sequence for data filling) to the client via the gateway. The client then loads the floor components, floor styles, floor sorting, and renders the floor data, ultimately generating the app's native page.

[0129] In one embodiment, such as Figure 8As shown, the client is implemented in the form of an APP, the server includes SOA and SDK, and the operation side includes a configuration center and an operation platform (i.e., an operation configuration platform).

[0130] In this scenario, the operations backend configures template data, floor data, rule data, and dependency data. After configuring the dependency data, data binding can be performed, and once binding is complete, an interface can be generated and registered with the gateway. The template data and multiple function (Color) gateway interfaces will be bound. When the front-end rendering SDK starts, it will fetch style information (template data, floor data) and render based on the style information and the information obtained from the Color gateway.

[0131] In this embodiment, when a user browses a page through the APP, a page request is made. Before the page request is processed by SOA, the SDK first completes the preprocessing of the request.

[0132] The SDK supports whitelisting, volume splitting, and canary deployments. Users selected for whitelisting, volume splitting, or canary deployments will see different templates than regular users, allowing them to preview new features. When an HTTP request arrives, it is intercepted, and the target processing rules for that interface are obtained based on the request path. The SDK then executes the `mvel` function according to these rules, calls dependent interfaces, selects a template based on the execution result, and finally passes the processed request to the SOA.

[0133] Upon receiving the request processed by the SDK, SOA filters out certain sections of the template, as some sections have been disabled by users. After filtering, it performs business logic processing by concurrently calling upstream dependencies based on the selected section. Finally, it assembles the data and returns it to the app.

[0134] The app receives data from the server, parses the template's floor data list, selects the corresponding component based on the floor number (an identifier), and dynamically renders the floors according to their style and order. After concurrent rendering, the final result is displayed to the user. For events like major promotions, adding promotional floors and decorations only requires the operations team to modify the template configuration and add the floors.

[0135] The page configuration method and system disclosed herein complete page configuration through the cooperation of a client, server, and operations team. The operations team is used to configure and store template data, floor data, rule data, and dependency data. After receiving a page request from the client, the server retrieves the pre-configured template data, floor data, rule data, and dependency data from the operations team based on the request. Then, after determining the target rule data, the server executes the target rule data and calls the dependency interfaces in the dependency data to determine the target page template and the corresponding target floor sequence. The server returns the target floor sequence to the client, which generates the page based on the target floor data. In this process, the configuration of template data, floor data, rule data, and dependency data is pre-completed by the operations team, and the use of template data and floor data makes the configuration process templated and floor-based, reducing the configuration difficulty for the operations team and improving configuration efficiency. The server automatically obtains the target floor sequence by executing pre-set target processing rules and calling the dependency interfaces required by those rules; finally, the client generates the page based on the target floor sequence. The server and client achieve automated page configuration, freeing up significant manpower and further improving configuration efficiency. The operation side features templated and floor-based configurations.

[0136] Meanwhile, the page configuration method can be automatically executed every time a page request is triggered, achieving an intelligent configuration process through cooperation between the server and the operations team. Furthermore, the latest configuration data from the operations team can be promptly fed back to the client-side page, improving configuration efficiency and page display efficiency.

[0137] For new businesses, we provide end-to-end transaction solutions, from front-end to back-end services, saving costs. For growing businesses, we provide back-end services to help improve functionality and offer front-end component integration with back-end services to enhance the front-end experience. For mature businesses, we provide dynamic layout configuration capabilities, enabling front-end configuration and layering, improving efficiency. We also provide general transaction services, allowing the configuration platform to output dynamic, layered data structures for the front-end, enabling personalized displays. Furthermore, we support converting React Native components to HTML5, achieving one-time development adaptability across three platforms, supporting dynamic styles, configuration center configuration, and local rendering to generate layers.

[0138] The following describes the server-side apparatus for page configuration provided in the embodiments of this disclosure. The server-side apparatus for page configuration described below can be referred to in correspondence with the page configuration method with the server as the execution subject described above. For example... Figure 9 As shown, the server-side device used for page configuration includes:

[0139] The first acquisition module 901 is used to acquire page requests transmitted by the client;

[0140] The second acquisition module 902 is used to send a data acquisition instruction to the operation terminal according to the page request, and to acquire the template data, floor data, rule data and dependency data returned by the operation terminal;

[0141] The determination module 903 is used to determine the target processing rule in the rule data that corresponds to the page request;

[0142] The execution module 904 is used to execute the target processing rules to process page requests, and to call the dependency interfaces required for the execution of the target processing rules configured in the dependency data, to obtain the target page template corresponding to the page request from the template data, and to obtain the target floor sequence corresponding to the target page template from the floor data;

[0143] The sequence return module 905 is used to return the target floor sequence to the client, where the client is used to parse the target floor sequence to generate a page.

[0144] In one embodiment, the first acquisition module 901 is used to acquire page requests transmitted by the client through a gateway interface registered in the gateway, based on the page software development kit. The gateway interface is used to connect the client and the server.

[0145] The second acquisition module 902 is used to send a data acquisition instruction to the operation terminal based on the page software development kit, and to acquire the template data, floor data, rule data and dependency data returned by the operation terminal.

[0146] The determination module 903 is used to parse page requests and obtain request paths based on the page software development kit. The request path includes the gateway interfaces through which the page request passes, and the rule data includes the correspondence between the gateway interfaces and the target processing rules. The target processing rules are determined based on the gateway interfaces and their correspondence in the request path.

[0147] The server-side device used for page configuration is pre-configured with the page software development kit.

[0148] In one embodiment, the server-side apparatus for page configuration further includes a data population module;

[0149] The data population module is used to obtain the target floor sequence corresponding to the target page template from the floor data, and before returning the target page template and target floor sequence to the client, it obtains upstream dependency data through the dependency interface based on the service cluster; based on the upstream dependency data, it populates data for each floor in the target floor sequence.

[0150] The sequence return module 905 is used to return the target floor sequence with populated data to the client based on the service cluster. The target floor sequence with populated data includes at least one component data corresponding to a floor. The component data is used to support the display of the floor on the client.

[0151] Among them, the server-side device used for page configuration is pre-configured with a service cluster.

[0152] In one embodiment, the server-side device for page configuration further includes a filtering module;

[0153] The filtering module is used to close at least one floor in the target floor sequence based on upstream dependency data before data filling for each floor in the target floor sequence. Based on the service cluster, the preset filter is set according to the principles of whitelist, traffic cutting and / or grayscale.

[0154] The data population module is used to populate data for each floor in the target floor sequence that is not closed, based on the service cluster and upstream dependency data.

[0155] The following describes a client device for page configuration provided in embodiments of this disclosure. The client device for page configuration described below corresponds to the page configuration method with the client as the execution subject described above. Figure 10 As shown, the client devices used for page configuration include:

[0156] The request generation module 1001 is used to generate a page request when a page trigger instruction is received;

[0157] The request transmission module 1002 is used to transmit page requests to the server. The server is used to obtain the page request transmitted by the client, send a data acquisition instruction to the operation end according to the page request, obtain the template data, floor data, rule data and dependency data returned by the operation end, determine the target processing rule corresponding to the page request in the rule data, call the dependency interface configured in the dependency data to execute the target processing rule and execute the target processing rule to process the page request, obtain the target page template corresponding to the page request from the template data, and obtain the target floor sequence corresponding to the target page template from the floor data, and return the target floor sequence to the client.

[0158] The third acquisition module 1003 is used to acquire the target floor sequence returned by the server.

[0159] Parsing module 1004 is used to parse the target floor sequence to generate the page.

[0160] In one embodiment, the parsing module 1004 is used to load component data corresponding to each floor in the target floor sequence; load style information corresponding to each floor in the target floor sequence; load the sorting of each floor in the target floor sequence; and render and generate a page based on the component data, style information, and sorting.

[0161] The following describes the operator-side device for page configuration provided in the embodiments of this disclosure. The operator-side device for page configuration described below can be referred to in correspondence with the page configuration method with the operator-side as the execution subject described above. Figure 11 As shown, the operational devices used for page configuration include:

[0162] Instruction receiving module 1101 is used to receive data configuration instructions;

[0163] The data configuration module 1102 is used to configure and store template data, floor data, rule data and dependency data according to the data configuration instructions;

[0164] The fourth acquisition module 1103 is used to acquire data acquisition instructions sent by the server;

[0165] The data return module 1104 is used to return template data, floor data, rule data and dependency data to the server according to the data acquisition instructions;

[0166] The template data includes at least one page template; the floor data includes a floor sequence corresponding to each page template, and each floor sequence includes at least one floor arranged in order; the floor data includes related data for at least one floor, wherein the related data includes at least one of the following: floor identifier, style information, and component data; the rule data includes at least one request processing rule; and the dependency data includes the dependency interfaces required when each processing rule is executed, and each processing rule obtains the corresponding page template after calling the dependency interface.

[0167] In one embodiment, the operator device for page configuration further includes an update module;

[0168] The update module is used to configure and store template data, floor data, rule data, and dependency data according to the data configuration instructions, and then receive update configuration instructions; configure the latest template data, floor data, rule data, and / or dependency data according to the update configuration instructions; and update the corresponding template data, floor data, rule data, and / or dependency data according to the latest template data, floor data, rule data, and / or dependency data.

[0169] In one embodiment, the operator device for page configuration further includes a gateway configuration module;

[0170] The gateway configuration module is used to configure rule data according to data configuration instructions, and then receive gateway configuration instructions; according to the gateway configuration instructions, it configures the correspondence between gateway interfaces and processing rules. Among them, the page software development kit in the server determines the target processing rule based on the correspondence.

[0171] Figure 12 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 12 As shown, the electronic device may include: a processor 1201, a communication interface 1202, a memory 1203, and a communication bus 1204. The processor 1201, communication interface 1202, and memory 1203 communicate with each other via the communication bus 1204. The processor 1201 can call logical instructions in the memory 1203 to execute a page configuration method with the server as the execution entity. This method includes: obtaining a page request transmitted by the client; sending a data acquisition instruction to the operator based on the page request to obtain template data, floor data, rule data, and dependency data returned by the operator; determining the target processing rule corresponding to the page request in the rule data; executing the target processing rule to process the page request, and calling the dependency interface required for the execution of the target processing rule configured in the dependency data; obtaining the target page template corresponding to the page request from the template data, and obtaining the target floor sequence corresponding to the target page template from the floor data; and returning the target floor sequence to the client, wherein the client is used to parse the target floor sequence to generate a page.

[0172] Alternatively, a page configuration method with the client as the execution subject can be used. This method includes: generating a page request when a page trigger instruction is received; transmitting the page request to the server, wherein the server is used to obtain the page request transmitted by the client; sending a data acquisition instruction to the operation end according to the page request, and obtaining the template data, floor data, rule data, and dependency data returned by the operation end; determining the target processing rule corresponding to the page request in the rule data; calling the dependency interface configured in the dependency data for executing the target processing rule, and executing the target processing rule to process the page request; obtaining the target page template corresponding to the page request from the template data, and obtaining the target floor sequence corresponding to the target page template from the floor data; returning the target floor sequence to the client; obtaining the target floor sequence returned by the server; and parsing the target floor sequence to generate a page.

[0173] Alternatively, a page configuration method can be used to execute the operation-side execution entity. This method includes: receiving a data configuration instruction; configuring and storing template data, floor data, rule data, and dependency data according to the data configuration instruction; obtaining a data retrieval instruction sent by the server; and returning the template data, floor data, rule data, and dependency data to the server according to the data retrieval instruction. The template data includes at least one page template; the floor data includes a floor sequence corresponding to each page template, and each floor sequence includes at least one floor arranged in sequence; the floor data includes related data for at least one floor, including at least one of floor identifiers, style information, and component data; the rule data includes at least one request processing rule; and the dependency data includes the dependency interfaces required for the execution of each processing rule, with each processing rule obtaining the corresponding page template after calling the dependency interface.

[0174] Furthermore, the logical instructions in the aforementioned memory 1203 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of this disclosure, essentially, or the parts that contribute to the prior art, or parts of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0175] On the other hand, this disclosure also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions, and when the program instructions are executed by a computer, the computer can execute the page configuration method provided by the above methods, which is a server-side execution subject. The method includes: obtaining a page request transmitted by a client; sending a data acquisition instruction to an operator according to the page request, and obtaining template data, floor data, rule data, and dependency data returned by the operator; determining the target processing rule in the rule data corresponding to the page request; executing the target processing rule to process the page request, and calling the dependency interface required for the execution of the target processing rule configured in the dependency data; obtaining the target page template corresponding to the page request from the template data, and obtaining the target floor sequence corresponding to the target page template from the floor data; and returning the target floor sequence to the client, wherein the client is used to parse the target floor sequence to generate a page.

[0176] Alternatively, the computer can execute the page configuration method provided by the above methods, which is a client-side execution subject. This method includes: generating a page request when a page trigger instruction is received; transmitting the page request to a server, wherein the server is used to obtain the page request transmitted by the client; sending a data acquisition instruction to an operator based on the page request, and obtaining template data, floor data, rule data, and dependency data returned by the operator; determining the target processing rule in the rule data corresponding to the page request; calling the dependency interface configured in the dependency data required to execute the target processing rule, and executing the target processing rule to process the page request; obtaining the target page template corresponding to the page request from the template data, and obtaining the target floor sequence corresponding to the target page template from the floor data; returning the target floor sequence to the client; obtaining the target floor sequence returned by the server; and parsing the target floor sequence to generate a page.

[0177] Alternatively, the computer can execute the page configuration method provided by the above methods, with the operator as the execution subject. This method includes: receiving a data configuration instruction; configuring and storing template data, floor data, rule data, and dependency data according to the data configuration instruction; obtaining a data retrieval instruction sent by the server; and returning the template data, floor data, rule data, and dependency data to the server according to the data retrieval instruction. The template data includes at least one page template; the floor data includes a floor sequence corresponding to each page template, and each floor sequence includes at least one floor arranged in sequence; the floor data includes related data for at least one floor, including at least one of floor identifiers, style information, and component data; the rule data includes at least one request processing rule; and the dependency data includes the dependency interfaces required when each processing rule is executed, with each processing rule obtaining the corresponding page template after calling the dependency interface.

[0178] In another aspect, this disclosure also provides a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program implements a page configuration method with the execution of the aforementioned provided servers as the execution subject. The method includes: obtaining a page request transmitted by a client; sending a data acquisition instruction to an operator based on the page request, and obtaining template data, floor data, rule data, and dependency data returned by the operator; determining the target processing rule in the rule data corresponding to the page request; executing the target processing rule to process the page request, and calling the dependency interface required for the execution of the target processing rule configured in the dependency data; obtaining the target page template corresponding to the page request from the template data, and obtaining the target floor sequence corresponding to the target page template from the floor data; and returning the target floor sequence to the client, wherein the client is used to parse the target floor sequence to generate a page.

[0179] Alternatively, when the computer program is executed by a processor, it implements a page configuration method with the aforementioned clients as the execution subject. This method includes: generating a page request upon receiving a page trigger instruction; transmitting the page request to a server, whereby the server is used to obtain the page request transmitted by the client; sending a data acquisition instruction to an operator based on the page request, and acquiring template data, floor data, rule data, and dependency data returned by the operator; determining the target processing rule corresponding to the page request in the rule data; calling the dependency interface configured in the dependency data for executing the target processing rule, and executing the target processing rule to process the page request; obtaining the target page template corresponding to the page request from the template data, and obtaining the target floor sequence corresponding to the target page template from the floor data; returning the target floor sequence to the client; acquiring the target floor sequence returned by the server; and parsing the target floor sequence to generate a page.

[0180] Alternatively, when the computer program is executed by a processor, it implements a page configuration method with the execution of the aforementioned provided operational terminals as the execution subject. This method includes: receiving a data configuration instruction; configuring and storing template data, floor data, rule data, and dependency data according to the data configuration instruction; obtaining a data retrieval instruction sent by the server; and returning the template data, floor data, rule data, and dependency data to the server according to the data retrieval instruction. The template data includes at least one page template; the floor data includes a floor sequence corresponding to each page template, and each floor sequence includes at least one floor arranged in sequence; the floor data includes related data for at least one floor, including at least one of floor identifiers, style information, and component data; the rule data includes at least one request processing rule; and the dependency data includes the dependency interfaces required when each processing rule is executed, with each processing rule obtaining the corresponding page template after calling the dependency interface.

[0181] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0182] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0183] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this disclosure, and are not intended to limit them. Although this disclosure has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this disclosure.

Claims

1. A page configuration method, characterized by, Applied to a server side, comprising: Obtaining a page request transmitted by a client side; Sending a data acquisition instruction to an operation side according to the page request, and obtaining template data, floor data, rule data and dependent data returned by the operation side; Determining a target processing rule corresponding to the page request in the rule data; Executing the target processing rule to process the page request, calling a dependent interface required by the target processing rule for execution in the dependent data, obtaining a target page template corresponding to the page request from the template data, and obtaining a target floor sequence corresponding to the target page template from the floor data; Returning the target floor sequence to the client side, wherein the client side is configured to parse the target floor sequence to generate a page; The server side comprises a page software development kit; The obtaining of the page request transmitted by the client side comprises: Based on the page software development kit, the page request transmitted by the client side is obtained through a gateway interface registered in a gateway, wherein the gateway interface is configured to connect the client side and the server side; The sending of the data acquisition instruction to the operation side according to the page request, and the obtaining of the template data, the floor data, the rule data and the dependent data returned by the operation side, comprise: Based on the page software development kit, the data acquisition instruction is sent to the operation side according to the page request, and the template data, the floor data, the rule data and the dependent data returned by the operation side are obtained; The determination of the target processing rule corresponding to the page request in the rule data comprises: Based on the page software development kit, the request path is obtained by parsing the page request, wherein the request path comprises the gateway interface through which the page request passes, and the rule data comprises a corresponding relationship between the gateway interface and the target processing rule; the target processing rule is determined according to the gateway interface in the request path and the corresponding relationship.

2. The page configuration method of claim 1, wherein, The server side comprises a service cluster; After the target floor sequence corresponding to the target page template is obtained from the floor data, before the target page template and the target floor sequence are returned to the client side, the method further comprises: Based on the service cluster, upstream dependent data is obtained through the dependent interface; and each floor in the target floor sequence is data-filled based on the upstream dependent data; The returning of the target floor sequence to the client side comprises: Based on the service cluster, the target floor sequence with filled data is returned to the client side, wherein the target floor sequence with filled data comprises component data corresponding to at least one floor, and the component data is configured to support the floor to be displayed on the client side.

3. The page configuration method of claim 2, wherein, Before the data filling of each floor in the target floor sequence based on the upstream dependent data, the method further comprises: Based on the service cluster, at least one floor in the target floor sequence is closed through a preset filter, wherein the preset filter is set according to the principles of white list, traffic cutting and / or gray scale; The data filling of each floor in the target floor sequence based on the upstream dependency data comprises: Based on the service cluster, the upstream dependency data is used to fill the data of each floor in the target floor sequence that is not closed.

4. A page configuration method characterized by, Applied to a client, comprising: When receiving a page triggering instruction, generating a page request; Transmitting the page request to a server, wherein the server is configured to acquire the page request transmitted by the client; according to the page request, sending a data acquisition instruction to an operation end to acquire template data, floor data, rule data and dependency data returned by the operation end; determining a target processing rule in the rule data corresponding to the page request; calling a dependent interface configured in the dependency data required for executing the target processing rule, and executing the target processing rule to process the page request; acquiring a target page template corresponding to the page request from the template data, and acquiring a target floor sequence corresponding to the target page template from the floor data; returning the target floor sequence to the client; Acquiring the target floor sequence returned by the server; Generating a page by parsing the target floor sequence; The server comprises a page software development kit; The page request transmitted by the client is acquired based on the page software development kit through a gateway interface registered in a gateway, wherein the gateway interface is used to connect the client and the server; According to the page request, a data acquisition instruction is sent to an operation end to acquire template data, floor data, rule data and dependency data returned by the operation end based on the page software development kit; According to the page request, a data acquisition instruction is sent to an operation end to acquire template data, floor data, rule data and dependency data returned by the operation end based on the page software development kit; Based on the page software development kit, the request path is parsed to acquire the gateway interface, and the corresponding relationship between the gateway interface and the target processing rule is included in the rule data; according to the gateway interface in the request path and the corresponding relationship, the target processing rule is determined. The target floor sequence is parsed to generate a page, comprising: Loading component data corresponding to each floor in the target floor sequence respectively; 5. The page configuration method of claim 4, wherein, Loading style information corresponding to each floor in the target floor sequence respectively; Loading the order of each floor in the target floor sequence; Based on the component data, the style information and the order, the page is rendered and generated. Applied to an operation end, comprising: Receiving a data configuration instruction; 6. A page configuration method characterized by, According to the data configuration instruction, configuring and storing template data, floor data, rule data and dependency data; Acquiring a data acquisition instruction sent by a server; ​ ​ According to the data acquisition instruction, the template data, the floor data, the rule data and the dependency data are returned to the server; The template data includes at least one page template, the floor data includes a floor sequence corresponding to each page template, and each floor sequence includes at least one floor arranged in sequence; the floor data includes relevant data of at least one floor, wherein the relevant data includes at least one of an identifier, style information and component data of the floor; the rule data includes at least one processing rule of a request; the dependency data includes a dependency interface required when each processing rule is executed, and each processing rule obtains a corresponding page template after calling the dependency interface; According to the data configuration instruction, the rule data is configured, and the method further includes: receiving a gateway configuration instruction; According to the gateway configuration instruction, the correspondence between the gateway interface and the processing rule is configured, wherein the page software development kit in the server determines a target processing rule according to the correspondence.

7. The page configuration method of claim 6, wherein, According to the data configuration instruction, the template data, the floor data, the rule data and the dependency data are configured and stored, and the method further includes: receiving an update configuration instruction; According to the update configuration instruction, the latest template data, the latest floor data, the latest rule data and / or the latest dependency data are configured; According to the latest template data, the latest floor data, the latest rule data and / or the latest dependency data, the corresponding template data, floor data, rule data and / or dependency data are updated.

8. A page configuration system, characterized by The system includes a server, a client and an operation end; The client is configured to generate a page request when receiving a page trigger instruction, transmit the page request to the server, and obtain a target floor sequence returned by the server; The target floor sequence is parsed to generate a page; The server is configured to obtain the page request transmitted by the client, send a data acquisition instruction to the operation end according to the page request, and obtain template data, floor data, rule data and dependency data returned by the operation end; Determine a target processing rule in the rule data corresponding to the page request, execute the target processing rule to process the page request, call a dependency interface required when the target processing rule is executed in the dependency data, obtain a target page template corresponding to the page request from the template data, and obtain a target floor sequence corresponding to the target page template from the floor data; The target floor sequence is returned to the client; The operation end is configured to receive a data configuration instruction, configure and store template data, floor data, rule data and dependency data according to the data configuration instruction, obtain a data acquisition instruction sent by the server, and return the template data, the floor data, the rule data and the dependency data to the server according to the data acquisition instruction; The server includes a page software development kit; The page software development kit is used to obtain the page request transmitted by the client through a gateway interface registered in a gateway, wherein the gateway interface is used to connect the client and the server; send a data acquisition instruction to an operation end according to the page request, acquire template data, floor data, rule data and dependent data returned by the operation end; parse the page request to acquire a request path, wherein the request path includes the gateway interface passed through by the page request, and the rule data includes a correspondence between the gateway interface and the target processing rule; and determine the target processing rule according to the gateway interface in the request path and the correspondence.

9. The page configuration system of claim 8, wherein, The server includes a service cluster; The page software development kit is used to transmit the target page template, the target floor sequence and the target processing rule to the service cluster; The service cluster is used to acquire upstream dependent data through the dependent interface; Based on the upstream dependent data, data filling is performed on each floor in the target floor sequence; and the target floor sequence with filled data, including component data corresponding to at least one floor, is returned to the client, wherein the component data is used to support the floor to be displayed on the client.

10. The page configuration system of claim 9, wherein, The service cluster is used to close at least one floor in the target floor sequence through a preset filter, wherein the preset filter is set according to the principles of a white list, traffic cutting and / or gray scale; and data filling is performed on each floor in the target floor sequence that is not closed through the upstream dependent data.

11. A server device for page configuration, characterized by, Comprise: A first acquisition module is used to acquire a page request transmitted by a client; A second acquisition module is used to send a data acquisition instruction to an operation end according to the page request, acquire template data, floor data, rule data and dependent data returned by the operation end; A determination module is used to determine a target processing rule corresponding to the page request in the rule data; An execution module is used to execute the target processing rule to process the page request, call a dependent interface required when the target processing rule is executed in the dependent data, acquire a target page template corresponding to the page request from the template data, and acquire a target floor sequence corresponding to the target page template from the floor data; A sequence return module is used to return the target floor sequence to the client, wherein the client is used to parse the target floor sequence to generate a page; The server includes a page software development kit; The first acquisition module is specifically used to acquire the page request transmitted by the client through a gateway interface registered in a gateway based on the page software development kit, wherein the gateway interface is used to connect the client and the server; The second acquisition module is specifically used to send a data acquisition instruction to an operation end according to the page request based on the page software development kit, acquire template data, floor data, rule data and dependent data returned by the operation end; The determining module is specifically configured to parse the page request based on the page software development kit to obtain a request path, wherein the request path includes the gateway interface through which the page request passes, and the rule data includes a correspondence between the gateway interface and the target processing rule; and determine the target processing rule according to the gateway interface in the request path and the correspondence.

12. A client device for page configuration, characterized by Comprise: The request generation module is configured to generate a page request when a page triggering instruction is received; The request transmission module is configured to transmit the page request to a server, wherein the server is configured to obtain the page request transmitted by the client, send a data acquisition instruction to an operation end according to the page request, acquire template data, floor data, rule data and dependent data returned by the operation end, determine a target processing rule corresponding to the page request in the rule data, call a dependent interface configured in the dependent data required for executing the target processing rule, execute the target processing rule to process the page request, acquire a target page template corresponding to the page request from the template data, and acquire a target floor sequence corresponding to the target page template from the floor data, and return the target floor sequence to the client; The third acquisition module is configured to acquire the target floor sequence returned by the server; The analysis module is configured to analyze the target floor sequence to generate a page; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; 13. An operation end device for page configuration, characterized by, The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software development kit; The server comprises a page software The template data includes at least one page template, the floor data includes a floor sequence corresponding to each page template, and each floor sequence includes at least one floor arranged in sequence; the floor data includes relevant data of at least one floor, wherein the relevant data includes at least one of an identifier, style information and component data of the floor; the rule data includes at least one processing rule for request processing; the dependency data includes a dependency interface required when each processing rule is executed, and each processing rule obtains the corresponding page template after calling the dependency interface. The gateway configuration module is further configured to receive a gateway configuration instruction after the rule data is configured according to a data configuration instruction; and configure a correspondence between a gateway interface and a processing rule according to the gateway configuration instruction, wherein the page software development kit in the server determines a target processing rule according to the correspondence.

14. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The processor executes the program to implement the page configuration method of any one of claims 1 to 3. Alternatively, the processor executes the program to implement the page configuration method of any one of claims 4 to 5. Alternatively, the processor executes the program to implement the page configuration method of any one of claims 6 to 7.

15. A non-transitory computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the page configuration method of any one of claims 1 to 3. Alternatively, the computer program is executed by the processor to implement the page configuration method of any one of claims 4 to 5. Alternatively, the computer program is executed by the processor to implement the page configuration method of any one of claims 6 to 7.

Images