Page processing method and device, electronic equipment and storage medium

By acquiring and rendering the page configuration information and component data of target products in the e-commerce platform, and adopting a visual configuration method, the problem of low efficiency in customized e-commerce development is solved, and efficient page development and maintenance are achieved.

CN121807293APending Publication Date: 2026-04-07TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-01-05
Publication Date
2026-04-07

AI Technical Summary

Technical Problem

The existing customized hard-coded development of e-commerce platforms is inefficient, and the adjustment of product rules and function maintenance are complex, resulting in high development and maintenance costs for e-commerce platforms.

Method used

It adopts a page processing method, obtains the page configuration information and functional component configuration data of the target product, and dynamically renders the page using a visual configuration method, decoupling static layout and dynamic data, and supporting component selection and configuration item settings.

Benefits of technology

It improved page development efficiency, reduced the maintenance complexity of the e-commerce platform, enabled flexible component configuration and product management, and reduced development and maintenance costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121807293A_ABST
    Figure CN121807293A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a page processing method and device, electronic equipment and a storage medium, and can relate to the technical field of page visual configuration.The method comprises the steps that in response to an opening operation for a target function page of a target commodity, page configuration information of the target function page of the target commodity is obtained, the page configuration information comprises structure information of each functional component in the target functional page; and obtaining configuration data of the target commodity corresponding to each functional component, and displaying a target functional page of the target commodity according to the page configuration information and the configuration data corresponding to each functional component. According to the method, the page configuration information of the target function page of the target commodity and the function configuration data of the commodity are decoupled, and the page is dynamically rendered in a configuration mode, so that the page development efficiency is improved, and the page maintenance and transformation cost is reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application belongs to the field of computer technology and may relate to the field of page visualization configuration technology. Specifically, this application relates to a page processing method, apparatus, electronic device and storage medium. Background Technology

[0002] With the rapid development of the internet and e-commerce, building a dedicated online store has become an important way for businesses to expand their online operations.

[0003] Current e-commerce platforms primarily rely on customized, hard-coded development. Because electronic products are extremely diverse, encompassing both physical products like smart devices and digital accessories, and virtual services such as memberships and online top-ups, there are significant differences in product definitions (e.g., hardware parameters, service cycles, authorization methods) and sales logic (e.g., activation verification, after-sales guarantees, package deals, renewal mechanisms). Therefore, adding a new product to an e-commerce platform requires streamlining the sales logic, designing the interface, and developing the functionality. This process demands substantial R&D manpower, resulting in low platform development efficiency.

[0004] Furthermore, in hard-coded mode, the functional components in an e-commerce platform are often deeply coupled with the specific sales logic of a particular product. If it is necessary to adjust the product rules, optimize the functions, or fix vulnerabilities later, it is necessary to trace the related code for targeted modification. The operation process is cumbersome and complicated, which significantly increases the maintenance and transformation costs of the e-commerce platform system. Summary of the Invention

[0005] This application provides a page processing method, apparatus, electronic device, and storage medium. The specific technical solution is as follows: On one hand, embodiments of this application provide a page processing method, the method comprising: In response to the opening operation of the target function page of the target product, the page configuration information of the target function page of the target product is obtained, and the page configuration information includes the structural information of each functional component in the target function page; Obtain the configuration data for each of the functional components corresponding to the target product; Based on the page configuration information and the configuration data corresponding to each functional component, the target functional page of the target product is rendered and displayed.

[0006] Optionally, for each functional page, the functional components in the page configuration information of the functional page are configured in the following way: The configuration page that displays the function page includes a component selection control; In response to a trigger operation on the component selection control, a candidate component list is displayed, the candidate component list including multiple candidate components; In response to the selection operation for the plurality of candidate components, the various functional components of the functional page are obtained.

[0007] Optionally, the structural information of each functional component includes the structural information of each configuration item in the functional component; The step of obtaining the configuration data corresponding to each of the functional components for the target product includes: For each of the aforementioned functional components, obtain the configuration data of the target product corresponding to each configuration item in the functional component; Each configuration item in each of the candidate components is configured in the following way: The component configuration page of the candidate component is displayed, and the component configuration page includes a configuration item setting area; The configuration item setting area receives configuration item setting operations for the candidate component, thereby obtaining each configuration item in the candidate component.

[0008] Optionally, for each product in the e-commerce platform, the configuration data for each configuration item corresponding to that product is configured in the following way: The product configuration page for the product is displayed, and the product configuration page includes a product addition control; In response to a trigger operation that adds a control to the product, the product configuration area of ​​the newly added product is displayed; The basic data of newly added products is received through the product configuration area. The basic data includes the configuration data of each product corresponding to each configuration item.

[0009] On the other hand, embodiments of this application provide a page processing apparatus, the apparatus comprising: The page configuration acquisition module is used to acquire the page configuration information of the target function page of the target product in response to the opening operation of the target function page of the target product. The page configuration information includes the structural information of each functional component in the target function page. A configuration data acquisition module is used to acquire configuration data for each of the functional components corresponding to the target product; The page display module is used to render and display the target function page of the target product based on the page configuration information and the configuration data corresponding to each of the functional components.

[0010] For each functional page, the functional components in the page configuration information of the functional page are configured in the following way: The configuration page that displays the function page includes a component selection control; In response to a trigger operation on the component selection control, a candidate component list is displayed, the candidate component list including multiple candidate components; In response to the selection operation for the plurality of candidate components, the various functional components of the functional page are obtained.

[0011] Optionally, the structural information of each functional component includes the structural information of each configuration item in the functional component; The configuration data acquisition module can be used for: For each of the aforementioned functional components, obtain the configuration data of the target product corresponding to each configuration item in the functional component; Each configuration item in each of the candidate components is configured in the following way: The component configuration page of the candidate component is displayed, and the component configuration page includes a configuration item setting area; The configuration item setting area receives configuration item setting operations for the candidate component, thereby obtaining each configuration item in the candidate component.

[0012] Optionally, for each product in the e-commerce platform, the configuration data for each configuration item corresponding to that product is configured in the following way: The product configuration page for the product is displayed, and the product configuration page includes a product addition control; In response to a trigger operation that adds a control to the product, the product configuration area of ​​the newly added product is displayed; The basic data of newly added products is received through the product configuration area. The basic data includes the configuration data of each product corresponding to each configuration item.

[0013] Optionally, the page configuration acquisition module can be used for: Based on the product identifier of the target product and the mapping relationship between each product identifier and product type in the e-commerce platform, the target product type to which the target product belongs is determined; Based on the target product type and the page identifier of the target function page, the page configuration information of the target function page of the target product type is determined from the local database; wherein, the local database stores the page configuration information of multiple function pages of multiple product types; The configuration data acquisition module can be used for: Based on the product identifier of the target product and the page identifier of the target function page, a configuration data retrieval request is sent to the server; Receive configuration data returned by the server for each functional component in the target functional page corresponding to the target product; The page display module can be used for: Based on the page configuration information, each functional component in the target functional page is pre-rendered; The configuration data of each of the aforementioned functional components is added to the corresponding pre-rendered functional component.

[0014] Optionally, the configuration data acquisition module can be used for: For each of the aforementioned functional components, the component logic corresponding to the functional component is invoked to obtain the configuration data of the target product corresponding to the functional component.

[0015] Optionally, the configuration data acquisition module can be used for: For each of the aforementioned functional components, determine the configuration items within that functional component; For each configuration item in the functional component, the data acquisition logic of the configuration item is invoked to obtain the configuration data of the target product corresponding to the configuration item.

[0016] Optionally, the page configuration acquisition module can be used for: Determine if the current runtime environment is a development environment; If the current operating environment is a development environment, a page configuration information retrieval request is sent to the server; the page configuration information returned by the server based on the target product type and the page identifier of the target function page is received. If the current operating environment is not a development environment, the page configuration information of the target function page of the target product type is determined from the local database based on the target product type and the page identifier of the target function page.

[0017] Optionally, the configuration data acquisition module can be used for: Based on the product identifier of the target product, determine whether the target product is a configurable display product; If so, obtain the configuration data for each of the functional components corresponding to the target product.

[0018] This application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the method provided in any optional embodiment of this application.

[0019] On the other hand, embodiments of this application also provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method provided in any optional embodiment of this application.

[0020] On the other hand, embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the methods provided in any optional embodiment of this application.

[0021] The beneficial effects of the technical solution provided in this application are as follows: The page processing method provided in this application, when loading the target function page of a target product, first loads the structural information of each functional component in the target function page, and then obtains the configuration data of the target product corresponding to each functional component. This method decouples the static page layout from the dynamic product data, dynamically rendering the page in a configurable manner, greatly improving page development efficiency and reducing the complexity of e-commerce maintenance. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0023] Figure 1 A schematic diagram illustrating the implementation environment to which the page processing method provided in the embodiments of this application is applicable; Figure 2 This is a flowchart illustrating a page processing method provided in an embodiment of this application; Figure 3 A schematic diagram of the component structure of a functional page provided in an embodiment of this application; Figure 4 A schematic diagram of a configuration page for a functional page provided in an embodiment of this application; Figure 5 A schematic diagram of a component configuration page provided in an embodiment of this application; Figure 6 A schematic diagram of a product configuration page provided in an embodiment of this application; Figure 7 A flowchart of page loading provided for embodiments of this application; Figure 8 A schematic diagram illustrating the component invocation logic provided in the embodiments of this application; Figure 9 A schematic diagram illustrating the front-end loading page configuration provided in an embodiment of this application; Figure 10 A flowchart illustrating the configurable development process of an e-commerce platform provided in this application embodiment; Figure 11 This is a schematic diagram of the structure of a page processing device provided in an embodiment of this application; Figure 12This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0024] The embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the embodiments described below with reference to the accompanying drawings are exemplary descriptions for explaining the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions of the embodiments of this application.

[0025] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the terms “comprising” and “including” as used in embodiments of this application mean that the corresponding feature can be implemented as the presented feature, information, data, step, operation, element, and / or component, but do not exclude implementation as other features, information, data, step, operation, element, component, and / or combinations thereof supported by the art. It should be understood that when we say that an element is “connected” or “coupled” to another element, the one element can be directly connected or coupled to the other element, or it can mean that the one element and the other element establish a connection relationship through an intermediate element. Furthermore, “connected” or “coupled” as used herein can include wireless connection or wireless coupling. The term “and / or” as used herein indicates at least one of the items defined by the term; for example, “A and / or B” can be implemented as “A,” or as “B,” or as “A and B.” When describing multiple (two or more) items, if the relationship between the multiple items is not explicitly defined, the multiple items can refer to one, several or all of the multiple items. For example, the description of "parameter A includes A1, A2, A3" can be implemented as parameter A includes A1 or A2 or A3, or it can be implemented as parameter A includes at least two of the three items A1, A2 and A3.

[0026] To better understand and explain the methods provided in the embodiments of this application, some technical terms involved in the embodiments of this application will be explained and described below.

[0027] Standard Product Unit (SPU): The basic unit for product information management in e-commerce. It consists of a set of reusable and easily searchable standardized information used to describe the common characteristics of products. Its core features are unrelated to sales attributes such as merchant, color, or style; it focuses solely on the essential attributes of the product. For example, specific models of products like the iPhone 4 each constitute an independent SPU, while the same SPU can contain multiple SKUs of different colors and specifications.

[0028] The smallest available stock keeping unit (SKU) is defined as the smallest unit for maintaining and controlling inventory, typically measured in pieces, boxes, pallets, etc. SKUs are assigned a unique identifier to goods received by the customer and placed in the warehouse, serving as a necessary method for logistics management in distribution centers. SKUs are commonly translated as inventory unit, stock unit, goods storage unit, inventory preservation unit, unitized unit, single item, or variety. Depending on business requirements, they can also be referred to as the smallest retail unit, smallest sales unit, smallest management unit, or inventory counting unit.

[0029] Figure 1 This is a schematic diagram of the implementation environment to which the page processing method provided in this application applies. The implementation environment includes a first terminal 10, a server 20, and a second terminal 30. The first terminal 10 runs or has an e-commerce development application installed. Through this development application, various functional pages of multiple product types in the e-commerce can be configured in a component-based manner, and the page configuration information of each functional page can be sent to the server 20 for deployment. The server 20 is a backend server that provides e-commerce related services. The second terminal 30 runs or has an e-commerce application installed. Through this application, the functional pages of each product in the e-commerce can be viewed and corresponding functional operations can be performed. This application does not limit the form of the application; it can be a client (Application, APP), a mini-program, or a webpage.

[0030] Specifically, the development application running in the first terminal 10 provides a visual configuration page. Developers can use the component selection control on the configuration page to select various functional components included in the functional page from the candidate component list that is triggered to be displayed, generate the page configuration information of the functional page, and send the generated page configuration information of the functional page to the server 20 in response to the developer's configuration submission operation.

[0031] When a user accesses a specific function page of a product through the e-commerce application in the second terminal 30, in response to the user's opening operation of the function page, a page retrieval request for the function page is sent to the server 20. Based on the page retrieval request, the server 20 can find the page configuration information of the function page and the configuration data of each functional component of the product corresponding to the function page, and send the page configuration information and each configuration data to the second terminal 30. The second terminal 30 can render and display the function page based on the obtained page configuration information of the function page and the configuration data of each component of the product corresponding to the function page.

[0032] Optionally, the development application in the first terminal 10 can also configure basic data for various products in the e-commerce platform and send the configured basic data to the server 20. The basic data (or configuration data) of the products includes, but is not limited to, product name, product type, product specifications, product image, product expiration date, etc. So that when a certain function page of the product is loaded through the second terminal 30, the server 20 can determine the configuration data of each component of the product corresponding to the function page from the basic data configured for the product.

[0033] Optionally, the development application in the first terminal 10 can also configure the configuration items contained in each functional component of the function page. The configuration items for the same functional component can be the same or different for different types of products. When a certain function page of the product is loaded through the second terminal 30, the server 20 can query the configuration data of each configuration item of each functional component of the product corresponding to the function page.

[0034] The aforementioned server 20 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server. The terminal (including the first terminal 10 and the second terminal 30) can be a smartphone, tablet computer, laptop computer, desktop computer, smart voice interaction device (e.g., smart speaker), wearable electronic device (e.g., smartwatch), in-vehicle terminal, smart home appliance (e.g., smart TV), AR / VR device, etc., but is not limited to these.

[0035] The first terminal 10 and the server 20, and the second terminal 30 and the server 20, can be directly or indirectly connected via wired or wireless communication methods. For example, they can be connected via wired or wireless networks. The wired network can include local area networks, metropolitan area networks, and wide area networks, while the wireless network can include Bluetooth, Wi-Fi, and other networks that enable wireless communication.

[0036] The technical solutions of this application and their effects are described below through several embodiments. It should be noted that the following embodiments can be referenced, borrowed from, or combined with each other. Identical terms, similar features, and similar implementation steps in different embodiments will not be repeated.

[0037] This application provides a page processing method that can be executed by any electronic device, such as a webpage processing device. Figure 1 It can be executed on any terminal or server within the system. For ease of description, the following explanation uses a terminal as the execution subject.

[0038] Figure 2This is a flowchart illustrating a page processing method provided in an embodiment of this application, specifically including the following steps S110-S130, wherein: Step S110: In response to the opening operation of the target function page for the target product, obtain the page configuration information of the target function page for the target product.

[0039] The e-commerce platform includes various functional pages for products, such as product introduction pages (product details pages), payment pages, review management pages, and after-sales service pages. Each functional page can consist of multiple components with different functions, such as... Figure 3 As shown, the product introduction page consists of several different functional components: top card, usage overview card, core usage scenarios card, purchase help card, frequently asked questions card, and bottom function bar.

[0040] The page configuration information for each functional page can include the structural information of each functional component in that functional page. The structural information of the functional component can include the HTML skeleton structure of the functional component, the component style (CSS file), and standardized static resource data such as static text in the functional component (such as the text or labels on the button such as "Buy Now" or "Add to Cart").

[0041] Understandably, e-commerce platforms offer a range of products, from physical goods like smart devices and digital accessories to virtual products such as membership services, coupons, and red envelope covers. The core attributes and sales logic of different products vary significantly, leading to personalized needs for component configurations on different product pages. For example, physical products require attention to services such as logistics, inventory management, and after-sales service; therefore, their product pages need to include components for logistics information, inventory display, and after-sales support. Virtual products, on the other hand, prioritize services such as activation and distribution, expiration date management, and usage rules; thus, their product pages need to include components for activation processes and expiration date reminders.

[0042] In this embodiment, in response to a user's action of opening a target function page for a target product in an e-commerce platform, the terminal can send a page retrieval request for the target function page to the e-commerce platform's server. This request includes a page identifier for the target function page and a product identifier for the target product. The page identifier uniquely identifies the target function page in the e-commerce platform; for example, the page identifier can be a page address. The server can then retrieve the page configuration information corresponding to the target function page for the target product from the database based on the product identifier and the page identifier, and send this information to the terminal. The database stores associated product identifiers for various products, page identifiers for various function pages, and page configuration information.

[0043] Optionally, different types of products may have different component layouts on various functional pages, while the component layouts of functional pages for the same type of product are usually consistent. Based on this characteristic, page configuration information for various functional pages can be set according to product type. In response to the opening operation of a target functional page for a target product, the target product type can be determined based on the product identifier of the target product and the mapping relationship between product identifiers and product types in the e-commerce platform. Then, based on the target product type and the page identifier of the target functional page, the page configuration information corresponding to that target product type for the target functional page can be retrieved from the database. The database contains associated page identifiers and page configuration information for multiple product types and multiple functional pages.

[0044] Step S120: Obtain the configuration data for each functional component corresponding to the target product.

[0045] After loading the page configuration information of the target function page, the configuration data of each functional component corresponding to the target product on that target function page can be further obtained. Among them, the configuration data of the product corresponding to the functional component is dynamic data that needs to be synchronized in real time. It may change in real time with the adjustment of time, scenario or operational strategy, and the latest data needs to be loaded from the backend server.

[0046] Optionally, after receiving a page retrieval request, the server can determine the functional components within the target functional page based on the page identifier carried in the request. For each functional component, the server can then invoke the component logic based on the product identifier of the target product to obtain the configuration data corresponding to that functional component. For example, for a basic product information display component, the configuration data for the target product corresponding to that functional component includes basic information such as product name, unit price, and inventory. For a core usage scenario component, the configuration data for the target product corresponding to that functional component includes the usage scenario of the target product.

[0047] Step S130: Render and display the target function page of the target product based on the page configuration information and the configuration data corresponding to each functional component.

[0048] In this embodiment of the application, the terminal can generate the target function page of the target product by rendering through the rendering engine based on the structural information of each functional component in the current page and the configuration data of the target product corresponding to each functional component.

[0049] In this embodiment, the various functional pages (including their functional components) in the e-commerce platform can be implemented through visual configuration, supporting the selection of functional components to build functional pages as needed. The visual configuration process for functional pages includes: The configuration page for the display function page includes a component selection control; In response to a trigger action on the component selection control, a list of candidate components is displayed, which includes multiple candidate components; In response to the selection operation of multiple candidate components, the various functional components of the function page are obtained.

[0050] The configuration page for this function page can be the configuration page for adding a new page, and each candidate component in the candidate component list can be a standardized component formed by splitting according to fixed functional logic based on the characteristics of each product's sales services.

[0051] Each candidate component encapsulates complete / closed-loop independent logic, including its business logic, state management, data requests, and interactions. The implementation of all component functionalities is independent of external page logic or global state. For example, the coupon selection component encapsulates the entire process logic, including coupon list retrieval, validity period verification, and discount calculation.

[0052] When a new component needs to be added to a functional page, it can be directly imported through configuration to call its encapsulated logic to achieve the corresponding function. There is no need to modify the core logic of the page or write additional adaptation code, which greatly improves the efficiency of component reuse and the flexibility of page construction.

[0053] In this embodiment of the application, functional pages that have been configured and launched can also be configurably adjusted. For example, when the sales logic of a product or the associated service process changes (such as changing to a pre-sale deposit payment mode), developers can delete the functional components corresponding to the original sales logic and add functional components corresponding to the pre-sale mode through visual operations on the configuration page of the functional page where the product logic has changed.

[0054] Optionally, developers can also configure basic information about feature pages through this configuration page, such as... Figure 4 As shown, the configuration page of this function page can also include input controls for various basic information of the function page. Users can customize basic information such as page name, page link, page to which the specified location belongs, and upload page illustrations. Users can also select multiple components from a preset standardized candidate component list by clicking the component selection control to obtain the various functional components associated with the current function page.

[0055] In this embodiment, a visual configuration method is used to flexibly adapt to the component layout requirements of different functional pages for different products. Page layout configuration can be completed without modifying the code, enabling efficient integration of new pages into the e-commerce platform. During page loading, page configuration information and configuration data for each functional component corresponding to the product can be loaded separately. This design, which decouples static page layout from dynamic product data, greatly improves page development efficiency and reduces the complexity of e-commerce platform maintenance.

[0056] In this embodiment, each functional component can be further divided into multi-dimensional configuration items, and the structural information of each functional component includes the structural information of each configuration item in the functional component. For example, for a product price display component, it can be divided into configuration items such as price font size, color, and discount label style; for a frequently asked questions card, it can be divided into configuration items such as question title, question link, and link to view more questions.

[0057] Since each functional component includes multiple configuration items, when obtaining the configuration data of the target product corresponding to each functional component in step S120, for each functional component, the configuration data of the target product corresponding to each configuration item in the functional component is obtained.

[0058] Each configuration item in the candidate component list can be configured in the following way: The component configuration page displays the candidate components, and includes a configuration setting area. The configuration setting area receives configuration setting operations for candidate components, and obtains each configuration item in the candidate components.

[0059] Each candidate component in the candidate component list can also be obtained through a visual configuration method.

[0060] like Figure 5 As shown, the configuration settings area of ​​the component configuration page includes multiple configuration item selection controls. Each control allows users to select a configuration item associated with the component from a pool of candidate options. These candidate options can be standardized configuration items derived from various functional characteristics of each component. For example, taking the product display component as an example, developers can use the configuration item selection controls to select configuration items associated with the component, such as product title, product type, product origin, and product image.

[0061] Optionally, the component configuration page can also include input controls for various basic component information. This allows for visual configuration or modification of the component's basic information, eliminating the need for coding and significantly lowering the configuration barrier. The basic component information includes component priority, component version number, thumbnail, etc. This visual configuration of basic information... To enable refined and customized configurations across multiple scenarios, each configuration item can be further categorized by platform (e.g., app, mini-program, H5), user identity (e.g., regular user, member user, administrator), and internationalization (e.g., multilingual, multi-regional adaptation rules). This allows for automatic matching of corresponding configuration items based on different usage scenarios. Furthermore, if a configuration item involves visual attributes such as color or images, additional configuration options for dark and light modes can be added to further enhance the comprehensiveness of multi-scenario adaptation.

[0062] Optionally, when obtaining the configuration data of a product corresponding to each configuration item, for each functional component, the configuration items contained in that functional component can be determined first; for each configuration item in that functional component, the data acquisition logic for that configuration item is called to obtain the configuration data of the target product corresponding to that configuration item. The configuration data of the product corresponding to the functional component includes the configuration data of each configuration item under that functional component.

[0063] Optionally, the data acquisition logic for each configuration item can also be designed as a closed loop, meaning that the data acquisition logic for each configuration item does not depend on the logic of other components or page layers. When business requirements change and it is necessary to add or delete configuration items for functional components, there is no need to modify the page logic or component logic. The configuration items in the component can be flexibly adjusted by adding, deleting, or modifying them through configuration.

[0064] This application embodiment makes the combination and display of page functions more flexible through configuration. When adding new products, there is no need to redevelop the functions of the standard process. The component layout requirements of the page can be flexibly adapted through visual configuration, which greatly reduces development costs.

[0065] In this embodiment of the application, the configuration data of each product in the e-commerce platform can also be obtained through visual configuration. The visual configuration process for products includes: The product configuration page displays the product information, which includes controls for adding a new product. In response to a triggering operation that adds a control to a product, the product configuration area for the newly added product is displayed; The product configuration area receives the basic data of newly added products. The basic data of the products includes the configuration data of each configuration item corresponding to the product.

[0066] like Figure 6 As shown, the product configuration page includes multiple configured products and a "Add Product" control. Users can click the "Add Product" control to add products and configure their data. Basic product data includes the product name, product ID, product specifications, product type, product image, and usage instructions from the details page. By decoupling product data from business logic, products can be configured visually, significantly shortening the product listing cycle and enabling flexible product addition.

[0067] Optionally, the product configuration page also includes configuration controls for each configured product. When the basic data of a product changes, developers can click on the corresponding product's configuration control and modify the corresponding data visually in the product configuration area. This method enables rapid updates of basic product data without writing code, ensuring convenient data changes and lowering the operational threshold.

[0068] Optionally, considering the hierarchical relationship between SPUs and SKUs in the e-commerce marketplace, when managing the configuration data of each product using a visual configuration method, the configuration at the product SPU level (such as general specifications and parameters) can be performed on the product SPU configuration page to obtain a unified configuration template for that product SPU. Then, for each product SKU under that product SPU, the configuration at the product SKU level can be performed on the product SKU configuration page according to the differentiated characteristics of that product SKU.

[0069] This hierarchical configuration model for SPUs and SKUs allows for the reuse of general SPU configurations without repetitive operations, while also enabling flexible setting of SKU-specific configuration data. This significantly improves the efficiency and accuracy of product configuration while reducing the configuration complexity for multi-SKU products.

[0070] In this embodiment, to optimize user experience and reduce page blanking time, the page configuration information of each functional page in the e-commerce platform can be pre-packaged and sent to the terminal. When accessing the target functional page of a target product, the terminal can load the corresponding page configuration information from its local database and pre-render the basic structure of the components on the page, and then asynchronously request and load the dynamic data of each functional component on the page, ensuring smooth page loading.

[0071] When determining the page configuration information of the target function page of the target product in step S110, the target product type to which the target product belongs can be determined based on the product identifier of the target product and the mapping relationship between each product identifier and product type in the e-commerce platform; based on the target product type and the page identifier of the target function page, the page configuration information of the target function page of the target product type can be determined from the local database; wherein, the local database stores the page configuration information of multiple function pages of multiple product types, and the page configuration information stored in the local database can be that it was sent to the terminal along with the installation package during the installation phase of the e-commerce platform and stored in the terminal's local database.

[0072] In step S120, when obtaining the configuration data of the functional components corresponding to the target product, a configuration data acquisition request can be sent to the server based on the product identifier of the target product and the page identifier of the target functional page; and the configuration data of each functional component in the target functional page corresponding to the target product returned by the server can be received. Optionally, for each functional component in the target functional page, a configuration data acquisition request corresponding to the functional component can be sent to the server based on the component identifier of the functional component and the product identifier of the target product, and the configuration data of the target product corresponding to the functional component returned by the server can be received.

[0073] After reading the page configuration information of the target function page from the local terminal, the various functional components in the target function page can be pre-rendered based on the page configuration information; after asynchronously loading the configuration data of each functional component corresponding to the target product, the configuration data of each functional component can be added to the pre-rendered corresponding functional component for integration to obtain the target function page.

[0074] like Figure 7 As shown, after a user opens a product's function page in the e-commerce platform via a terminal, the user can read the page configuration information of the corresponding function page from the front end based on the product ID in the page link, perform pre-rendering based on the page configuration information, and send a configuration data retrieval request to the e-commerce platform's server based on the product ID. The server can call the component logic of each component in the function page to obtain the corresponding configuration data and return it to the front end. The front end can then add the obtained configuration data to the component architecture of the corresponding component to display the complete function page.

[0075] In this application embodiment, configuring product / function pages in an e-commerce platform can be a modification of the existing e-commerce platform. This can result in the coexistence of configurable pages and original function pages. The original function pages exhibit significant coupling in their component logic layer, with component logic bound to page logic (e.g., a component's function triggering depends on the page's global state). In contrast, the components in the configurable pages of this application embodiment employ a closed-loop logic design, encapsulating complete business logic and data interaction within each component. This achieves complete decoupling between component logic and page logic, allowing for arbitrary assembly and configuration. Furthermore, considering the differences in component logic between the old and new pages, component compatibility must also be considered.

[0076] In this embodiment, for components already in use in online products, the corresponding UI elements can be encapsulated into independent pure UI components. These pure UI components are used only for visual rendering and do not contain any business logic. Based on this, a component logic layer enables differentiated adaptation between old and new pages. Specifically, when an old product page calls this pure UI component, the component logic layer automatically associates it with the original page execution logic; while when a new configurable page calls this pure UI component, the component logic layer triggers the execution of the closed-loop business logic encapsulated in the component, without relying on the page's global logic.

[0077] This design of "pure UI element reuse" and "differentiated scheduling of logic layer" allows new and old pages to use the same visual elements, achieving component-based configuration while minimizing the impact on existing e-commerce business.

[0078] like Figure 8 As shown, for the original functional pages of the e-commerce platform, the page logic layer includes "main page flow logic," "component 2 logic," and "component 3 & 4 linkage logic." The main page flow logic relies on the internal logic of logical UI component 1 in the page UI layer and the rendering capabilities of pure UI components. The component 2 logic relies on the functional logic corresponding to logical UI component 2. Most of the logical UI components in the original functional pages cannot run independently and need to cooperate with the page logic to complete the full display of the functional pages.

[0079] The configurable page architecture provided in this application retains only the main page flow logic in the page logic layer, and encapsulates all the "pure UI components" and "logic UI components 1-4" in the page UI layer into independent units. Each component has built-in closed-loop business logic, and components can be selected from the candidate component list as needed to build the page, improving the ability to freely assemble and flexibly configure components.

[0080] Among them, the pure UI components in the logical UI components of the original functional pages and the configuration page architecture can share the original UI element resources (such as button styles, icon materials, etc.), which not only ensures the consistency of the interface style, but also avoids repeated development and resource redundancy, and achieves the compatibility of the new and old architectures at the UI layer.

[0081] Because the application deployment and testing phases have high requirements for user experience, necessitating smooth page loading and fast response times, page configuration information can be pre-packaged and sent to the front end. When a user accesses the page, the configuration can be read directly from the local machine, eliminating the need for real-time network requests to fetch the configuration and effectively avoiding the impact of network latency on page loading speed. However, in the development environment, where the focus is more on verifying configuration capabilities, the latest configuration needs to be fetched from the backend and used for development and testing.

[0082] Therefore, when loading the page configuration information of the target function page, it can first determine whether the current running environment is a development environment; if the current running environment is a development environment, a page configuration information retrieval request is sent to the server, and the page configuration information returned by the server based on the target product type and the page identifier of the target function page is received; if the current running environment is not a development environment, the page configuration information of the target function page of the target product type is determined from the local database based on the target product type and the page identifier of the target function page.

[0083] Furthermore, when requesting the server to fetch page configuration, a multi-level caching mechanism combining browser caching and local caching can be used. The target page configuration can be searched layer by layer in the cache chain first. If no corresponding data is found in either level of cache, a request to retrieve page configuration information is sent to the server.

[0084] like Figure 9 As shown, when loading the target function page of the target product, it checks whether the current running environment is a development environment. If the current running environment is not a development environment, the page configuration information of the target function page of the target product is obtained from the local database. If the current running environment is a development environment, the page configuration information of the target function page is searched in the browser cache and the local cache (localStorage) in turn. If neither cache is hit, that is, neither the browser cache nor the local cache stores the page configuration information of the target function page, the page configuration information of the target function page is requested from the e-commerce server. If either cache is hit, the version number of the hit cache data is compared with the version number of the page configuration information stored in the local database. If they match, the hit cache data is used as the page configuration information of the current target function page. If they do not match, the cache is ignored, and the page configuration information of the target function page is still requested from the server.

[0085] Specifically, for page configuration information read from the cache, the browser cache data is automatically updated; for page configuration information fetched from the server, the local cache data is updated to provide the latest cache data support for subsequent requests.

[0086] In this embodiment, the configuration page requires all route links to include the product ID to control the page loading of the corresponding product's configuration. If the configuration page is a new page, a new routing rule is added directly, carrying the product ID field in the routing parameters, to ensure that the new page can obtain the product ID through the routing parameters and thus load the corresponding configuration data.

[0087] For pages that are already online, if the routing links cannot be adjusted due to business constraints, compatibility and adaptation for configurable transformation can be achieved by adding routing preprocessing logic. In the original routing configuration, a "configurable usage flag" is added for products that enable configurability. When a routing request is triggered, the preprocessing logic will first check this flag. If it is determined that the product is a configurable display product, the routing request will be forwarded to the routing logic layer of the configurable page; otherwise, the page logic corresponding to the original route will still be used.

[0088] If there is a situation where old and new page routes coexist, a new route rule pointing to the configurable page can be added before the existing route rule according to the route priority rules. Taking advantage of the first-to-first-used characteristic of route definition order, when a user accesses the route link, the newly added configurable page route will be matched first.

[0089] When loading a page, the system can prioritize matching the corresponding configurable page route based on the page link of the target product's target function page, according to routing priority rules. Upon successful matching, the system uses the product ID in the routing parameters to query the product's configurability flag using preprocessing logic to determine if the target product is a configurable display product. If it is, the system retrieves the page configuration information of the configurable page from the local database or server, and, based on the product ID, retrieves the configuration data for each functional component within that configurable page from the server.

[0090] This application provides a complete process for configurable development of an e-commerce platform. (See also...) Figure 10 Specifically, it may include the following steps S300-S390, wherein: Step S300: When adding a new component, configure the various configuration items associated with the new component.

[0091] Step S310: When adding a new function page, select each function component of the new function page from the candidate component list and determine the page configuration information of the new page.

[0092] Step S320: When adding a new product, accept the basic data of the new product through the product configuration area.

[0093] Step S330: Pre-download the configuration information of each page in the e-commerce platform to the local terminal.

[0094] In this embodiment of the application, the functional components, functional pages and products in the e-commerce platform can be visually configured through the configuration center.

[0095] When changes occur in the sales services of products in the e-commerce platform, corresponding functional components can be configured based on the newly added / changed service functions. Specifically, in response to a component addition operation, the component configuration page for the new component is displayed. Configuration item settings are received through the configuration item setting area on the component configuration page, obtaining the various configuration items associated with the new component. These configuration items within a component are standardized configuration items formed by breaking down multiple functional characteristics of the component.

[0096] When developing a specific functional page in an e-commerce platform, one can access the configuration page for the newly added functional page in the configuration center. In response to the triggering operation of the component selection control on this configuration page, a list of candidate components is displayed. Based on the required functions for this functional page, various functional components can be selected from multiple candidate components. The candidate components in the list are standardized components formed by breaking down fixed functional logic based on the characteristics of each product's sales and services. Each candidate component encapsulates complete / closed-loop independent logic.

[0097] When adding a new product in the e-commerce platform, users can access the product configuration page in the configuration center. This product configuration page includes a product addition control. In response to a trigger operation on the product addition control, the product configuration area for the new product is displayed. The product configuration area receives the basic data of the new product, which includes the configuration data for each configuration item.

[0098] It should be noted that the embodiments of this application do not restrict the order in which components, function pages and products are added and configured in steps S300-S320.

[0099] To optimize user experience and reduce page blanking time, the page configuration information of each functional page in the e-commerce platform can be pre-packaged and sent to the terminal. When accessing a functional page, the terminal can quickly load the corresponding page configuration information from the local database.

[0100] Step S340: In response to the opening operation of the target function page for the target product, determine whether the target product is a configurable display product; if yes, execute steps S350-S380; if no, execute step S390.

[0101] In this application embodiment, configuring product / function pages in an e-commerce platform can be a modification of the existing e-commerce platform. This may result in the coexistence of configurable pages and original function pages. Specifically, some products in the original e-commerce platform may not yet be integrated into the configurable system and still use traditional customized page development logic. Therefore, when loading the function page of any product, it is necessary to first determine the product's configurability activation status, i.e., whether the target product is a configurable or non-configurable display product, and then match the corresponding page loading logic based on the determination result.

[0102] Specifically, when the target product is a configurable product, the structural information of each functional component of the corresponding functional page and the configuration data of the product corresponding to each functional component are loaded and the page is rendered; when the target product is a non-configurable product, the original page rendering process is used.

[0103] Step S350: Obtain the page configuration information of the target function page of the target product from the local terminal.

[0104] Step S360: Based on the page configuration information, pre-render each functional component in the target functional page.

[0105] Step S370: Send a product data retrieval request to the server. The server calls the component logic corresponding to each functional component in the target functional page and reads the configuration data of the target product corresponding to each functional component from the product's basic configuration data.

[0106] Step S380: The server sends the configuration data of each functional component corresponding to the target product to the terminal, and the terminal adds the configuration data corresponding to each functional component to the pre-rendered corresponding functional component.

[0107] When the target product is a configurable product, the corresponding page configuration information is obtained from the local database of the terminal according to the page identifier of the target function page, and pre-rendering is performed based on the page configuration information.

[0108] The terminal can send a product data retrieval request to the server. Based on the product identifier of the target product in the product data retrieval request, the server retrieves the full basic configuration data of the target product. Based on the page identifier of the target function page in the product data retrieval request, the server calls the component logic corresponding to each function component in the target function page and reads the configuration data of the target product corresponding to each function component from the full basic configuration data of the target product.

[0109] The server sends the configuration data for each functional component corresponding to the target product to the terminal. The terminal can then add the configuration data for each functional component to the pre-rendered component architecture of the corresponding functional component to display the complete target product's target function page.

[0110] Step S390: Send a page retrieval request to the server to obtain the original functional page data corresponding to the target product, and render the product based on the original functional page data.

[0111] When the target product is a non-configurable product, the original page rendering process of the e-commerce platform is followed. A page retrieval request is sent to the server to obtain the original functional page data corresponding to the target product. The terminal can then render the product based on the obtained original functional page data.

[0112] Based on and Figure 2 The page processing method shown in this application follows the same principle. This application provides a page processing apparatus, such as... Figure 11 As shown, the page processing device 200 may include: a page configuration acquisition module 210, a configuration data acquisition module 220, and a page display module 230, wherein: The page configuration acquisition module 210 is used to acquire the page configuration information of the target function page of the target product in response to the opening operation of the target function page of the target product. The page configuration information includes the structural information of each functional component in the target function page. The configuration data acquisition module 220 is used to acquire configuration data of the target product corresponding to each of the functional components; The page display module 230 is used to render and display the target function page of the target product according to the page configuration information and the configuration data corresponding to each of the functional components.

[0113] Optionally, for each functional page, the functional components in the page configuration information of the functional page are configured in the following way: The configuration page that displays the function page includes a component selection control; In response to a trigger operation on the component selection control, a candidate component list is displayed, the candidate component list including multiple candidate components; In response to the selection operation for the plurality of candidate components, the various functional components of the functional page are obtained.

[0114] Optionally, the structural information of each functional component includes the structural information of each configuration item in the functional component; The configuration data acquisition module 220 can be used for: For each of the aforementioned functional components, obtain the configuration data of the target product corresponding to each configuration item in the functional component; Each configuration item in each of the candidate components is configured in the following way: The component configuration page of the candidate component is displayed, and the component configuration page includes a configuration item setting area; The configuration item setting area receives configuration item setting operations for the candidate component, thereby obtaining each configuration item in the candidate component.

[0115] Optionally, for each product in the e-commerce platform, the configuration data for each configuration item corresponding to that product is configured in the following way: The product configuration page for the product is displayed, and the product configuration page includes a product addition control; In response to a trigger operation that adds a control to the product, the product configuration area of ​​the newly added product is displayed; The basic data of newly added products is received through the product configuration area. The basic data includes the configuration data of each product corresponding to each configuration item.

[0116] Optionally, the page configuration acquisition module 210 can be used for: Based on the product identifier of the target product and the mapping relationship between each product identifier and product type in the e-commerce platform, the target product type to which the target product belongs is determined; Based on the target product type and the page identifier of the target function page, the page configuration information of the target function page of the target product type is determined from the local database; wherein, the local database stores the page configuration information of multiple function pages of multiple product types; The configuration data acquisition module 220 can be used for: Based on the product identifier of the target product and the page identifier of the target function page, a configuration data retrieval request is sent to the server; Receive configuration data returned by the server for each functional component in the target functional page corresponding to the target product; The page display module 230 can be used for: Based on the page configuration information, each functional component in the target functional page is pre-rendered; The configuration data of each of the aforementioned functional components is added to the corresponding pre-rendered functional component.

[0117] Optionally, the configuration data acquisition module 220 can be used for: For each of the aforementioned functional components, the component logic corresponding to the functional component is invoked to obtain the configuration data of the target product corresponding to the functional component.

[0118] Optionally, the configuration data acquisition module 220 can be used for: For each of the aforementioned functional components, determine the configuration items within that functional component; For each configuration item in the functional component, the data acquisition logic of the configuration item is invoked to obtain the configuration data of the target product corresponding to the configuration item.

[0119] Optionally, the page configuration acquisition module 210 can be used for: Determine if the current runtime environment is a development environment; If the current operating environment is a development environment, a page configuration information retrieval request is sent to the server; the page configuration information returned by the server based on the target product type and the page identifier of the target function page is received. If the current operating environment is not a development environment, the page configuration information of the target function page of the target product type is determined from the local database based on the target product type and the page identifier of the target function page.

[0120] Optionally, the configuration data acquisition module 220 can be used for: Based on the product identifier of the target product, determine whether the target product is a configurable display product; If so, obtain the configuration data for each of the functional components corresponding to the target product.

[0121] based on Figure 11 The page processing device shown can load page configuration information and configuration data of each functional component of the product on the page when loading the target function page of the target product. This design, which decouples the static page layout from the dynamic product data, greatly improves page development efficiency and reduces the complexity of e-commerce maintenance.

[0122] In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0123] This application provides an electronic device, including a memory, a processor, and a computer program stored in the memory. When the processor executes the computer program stored in the memory, it can implement the method in any optional embodiment of this application.

[0124] Figure 12 A schematic diagram of the structure of an electronic device to which an embodiment of the present invention applies is shown, such as... Figure 12 As shown, the electronic device can be a server or a terminal, and it can be used to implement the methods provided in any embodiment of the present invention.

[0125] like Figure 12 As shown, the electronic device 2000 may primarily include at least one processor 2001. Figure 12 The diagram shows components such as a memory 2002, a communication module 2003, and an input / output interface 2004. Optionally, these components can be connected and communicate with each other via a bus 2005. It should be noted that... Figure 12 The structure of the electronic device 2000 shown is merely illustrative and does not constitute a limitation on the electronic devices to which the methods provided in the embodiments of this application are applicable.

[0126] The memory 2002 can be used to store operating systems and applications, etc. The applications can include computer programs that implement the methods shown in the embodiments of the present invention when invoked by the processor 2001, and can also include programs for implementing other functions or services. The memory 2002 can be ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices that can store information and computer programs, or it can be EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disk storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.

[0127] Processor 2001 is connected to memory 2002 via bus 2005, and implements corresponding functions by calling application programs stored in memory 2002. Processor 2001 can be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this invention. Processor 2001 can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0128] Electronic device 2000 can connect to a network via communication module 2003 (which may include, but is not limited to, components such as a network interface) to communicate with other devices (such as terminals or servers) through the network and achieve data interaction, such as sending data to or receiving data from other devices. Communication module 2003 may include wired network interfaces and / or wireless network interfaces, meaning the communication module may include at least one of wired or wireless communication modules.

[0129] Electronic device 2000 can connect to required input / output devices, such as keyboards and display devices, via input / output interface 2004. Electronic device 2000 itself may have a display device, and other display devices can also be connected externally via interface 2004. Optionally, storage devices, such as hard drives, can also be connected via interface 2004 to store data from electronic device 2000, retrieve data from storage device, or store data from storage device into memory 2002. It is understood that input / output interface 2004 can be a wired interface or a wireless interface. Depending on the actual application scenario, the device connected to input / output interface 2004 can be a component of electronic device 2000 or an external device connected to electronic device 2000 when needed.

[0130] The bus 2005 used to connect the components may include a pathway for transmitting information between the components. The bus 2005 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Depending on its function, the bus 2005 can be divided into address bus, data bus, control bus, etc.

[0131] Optionally, for the solution provided in the embodiments of the present invention, the memory 2002 can be used to store a computer program that executes the solution of the present invention, and the processor 2001 runs the computer program. When the processor 2001 runs the computer program, it implements the operation of the method or apparatus provided in the embodiments of the present invention.

[0132] Based on the same principle as the method provided in the embodiments of this application, the embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the corresponding content of the aforementioned method embodiments.

[0133] This application also provides a computer program product, which includes a computer program that, when executed by a processor, can implement the corresponding content of the aforementioned method embodiments.

[0134] It should be noted that the terms "first," "second," "third," "fourth," "1," "2," etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in a sequence other than that shown in the figures or text.

[0135] It should be understood that although arrows indicate various operation steps in the flowcharts of this application's embodiments, the order in which these steps are implemented is not limited to the order indicated by the arrows. Unless explicitly stated herein, in some implementation scenarios of this application's embodiments, the implementation steps in each flowchart can be executed in other orders as required. Furthermore, some or all steps in each flowchart, based on the actual implementation scenario, may include multiple sub-steps or multiple stages. Some or all of these sub-steps or stages can be executed at the same time, and each sub-step or stage can also be executed at different times. In scenarios where execution times differ, the execution order of these sub-steps or stages can be flexibly configured according to requirements, and this application's embodiments do not limit this.

[0136] The above description is only an optional implementation method for some implementation scenarios of this application. It should be noted that for those skilled in the art, other similar implementation methods based on the technical concept of this application without departing from the technical concept of this application also fall within the protection scope of the embodiments of this application.

Claims

1. A page processing method, characterized in that, The method includes: In response to the opening operation of the target function page of the target product, the page configuration information of the target function page of the target product is obtained, and the page configuration information includes the structural information of each functional component in the target function page; Obtain the configuration data for each of the functional components corresponding to the target product; Based on the page configuration information and the configuration data corresponding to each functional component, the target functional page of the target product is rendered and displayed.

2. The method according to claim 1, characterized in that, For each functional page, the functional components in the page configuration information of the functional page are configured in the following way: The configuration page for the aforementioned function page is displayed, and the configuration page includes a component selection control; In response to a trigger operation on the component selection control, a candidate component list is displayed, the candidate component list including multiple candidate components; In response to the selection operation for the plurality of candidate components, the various functional components of the functional page are obtained.

3. The method according to claim 2, characterized in that, The structural information of each functional component includes the structural information of each configuration item in the functional component; The step of obtaining the configuration data corresponding to each of the functional components for the target product includes: For each of the aforementioned functional components, obtain the configuration data of the target product corresponding to each configuration item in the functional component; Each configuration item in each of the candidate components is configured in the following way: The component configuration page of the candidate component is displayed, and the component configuration page includes a configuration item setting area; The configuration item setting area receives configuration item setting operations for the candidate component, thereby obtaining each configuration item in the candidate component.

4. The method according to claim 3, characterized in that, For each product in the e-commerce marketplace, the configuration data for each of the configuration items is configured in the following manner: The product configuration page for the product is displayed, and the product configuration page includes a product addition control; In response to a trigger operation that adds a control to the product, the product configuration area of ​​the newly added product is displayed; The basic data of newly added products is received through the product configuration area. The basic data includes the configuration data of each product corresponding to each configuration item.

5. The method according to claim 1, characterized in that, The step of obtaining the page configuration information of the target function page of the target product includes: Based on the product identifier of the target product and the mapping relationship between each product identifier and product type in the e-commerce platform, the target product type to which the target product belongs is determined; Based on the target product type and the page identifier of the target function page, the page configuration information of the target function page of the target product type is determined from the local database; wherein, the local database stores the page configuration information of multiple function pages of multiple product types; The step of obtaining the configuration data for each functional component corresponding to the target product includes: Based on the product identifier of the target product and the page identifier of the target function page, a configuration data retrieval request is sent to the server; Receive configuration data returned by the server for each functional component in the target functional page corresponding to the target product; The step of displaying the target function page of the target product based on the page configuration information and the configuration data corresponding to each functional component includes: Based on the page configuration information, each functional component in the target functional page is pre-rendered; Add the configuration data corresponding to each of the aforementioned functional components to the pre-rendered corresponding functional component.

6. The method according to claim 1, characterized in that, The step of obtaining the configuration data corresponding to each of the functional components for the target product includes: For each of the aforementioned functional components, the component logic corresponding to the functional component is invoked to obtain the configuration data of the target product corresponding to the functional component.

7. The method according to claim 3, characterized in that, The step of obtaining the configuration data corresponding to each of the functional components for the target product includes: For each of the aforementioned functional components, determine the configuration items within that functional component; For each configuration item in the functional component, the data acquisition logic of the configuration item is invoked to obtain the configuration data of the target product corresponding to the configuration item.

8. The method according to claim 5, characterized in that, The step of determining the page configuration information of the target function page of the target product type from the local database based on the target product type and the page identifier of the target function page includes: Determine if the current runtime environment is a development environment; If the current operating environment is a development environment, a page configuration information retrieval request is sent to the server; the page configuration information returned by the server based on the target product type and the page identifier of the target function page is received. If the current operating environment is not a development environment, the page configuration information of the target function page of the target product type is determined from the local database based on the target product type and the page identifier of the target function page.

9. The method according to claim 1, characterized in that, The step of obtaining the configuration data corresponding to each of the functional components for the target product includes: Based on the product identifier of the target product, determine whether the target product is a configurable display product; If so, obtain the configuration data for each of the functional components corresponding to the target product.

10. A page processing apparatus, characterized in that, The device includes: The page configuration acquisition module is used to acquire the page configuration information of the target function page of the target product in response to the opening operation of the target function page of the target product. The page configuration information includes the structural information of each functional component in the target function page. A configuration data acquisition module is used to acquire configuration data for each of the functional components corresponding to the target product; The page display module is used to render and display the target function page of the target product based on the page configuration information and the configuration data corresponding to each of the functional components.

11. An electronic device, characterized in that, The electronic device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method according to any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements the method described in any one of claims 1 to 9.

13. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 9.