Component template creation, page configuration, and page presentation schemes

Abstract

Provided are component template creation, page configuration, and page display solutions. A method for creating a component template can include the following steps: obtaining a component description, the component description including information of a data structure of a component to be created; parsing the component description to obtain the data structure of the component to be created, wherein the parsed data structure of the component to be created is used to determine whether the component to be created is a static component or a dynamic component, in the case of the component to be created being a static component, creating a static component template based on the parsed data structure of the component to be created; or in the case of the component to be created being a dynamic component, generating auxiliary configuration according to the type of the dynamic component and based on the parsed data structure of the component to be created, and creating a dynamic component template based on the auxiliary configuration.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method for creating page component templates, a page configuration method, a page display method, related devices, computer equipment, computer-readable storage media, and computer program products. Background Technology

[0002] Currently, when displaying a page in a business application (such as a promotional activity page, the homepage of a news application, etc.), the content to be displayed on the page is usually divided into multiple components (e.g., component modularization) according to the page layout to improve component reusability. Each component can be obtained by selecting a component template from an existing set of component templates and populating it with entity data. Multiple components with different content can be output at once, facilitating data management and location.

[0003] Since the requirements for page components are constantly changing depending on the content being displayed, if the required component template is not in the component template collection, a new component template needs to be created. In the current method, developers need to write a completely new code for that component template every time a new component template is created, which requires additional development. Therefore, there is redundant code and development cost, which reduces the efficiency of component development iteration.

[0004] Therefore, a solution is needed that can simplify the component template creation process, thereby reducing component development costs and improving component development iteration efficiency. Summary of the Invention

[0005] The various embodiments of the present invention provide a method for creating page component templates, a page configuration method, a page display method, related devices, as well as computer equipment, computer-readable storage media, and computer program products, which can simplify the component template creation process, thereby reducing component development costs and improving component development iteration efficiency.

[0006] According to one aspect of this application, a method for creating a component template is provided, comprising: obtaining a component description, the component description including information on the data structure of the component to be created; parsing the component description to obtain the data structure of the component to be created, wherein the parsed data structure of the component to be created is used to determine whether the component to be created is a static component or a dynamic component; if the component to be created is a static component, creating a static component template based on the parsed data structure of the component to be created; or if the component to be created is a dynamic component, generating an auxiliary configuration based on the type of the dynamic component and the parsed data structure of the component to be created, and creating a dynamic component template based on the auxiliary configuration.

[0007] According to another aspect of this application, a page configuration method is also provided, comprising: obtaining at least one component identifier, wherein each component identifier is used to indicate a component template of a component to be displayed on the page; selecting a component template from a set of component templates based on at least one component identifier, wherein each component template in the set of component templates is created based on the method described above; obtaining configuration data of the component template for each selected component template, wherein the configuration data is used to obtain entity data of the component template; and associating and saving the selected component template and its configuration data with the identifier of the page.

[0008] According to another aspect of this application, a page display method is also provided, comprising: obtaining an identifier of a page; determining, based on the identifier of the page, component templates and their configuration data to be displayed on the page, wherein the page is configured according to the page configuration method described above; obtaining entity data of each component template and its configuration data, and forming a component instance with the component template; and sending each component instance to a page rendering module for display on the page.

[0009] According to another aspect of this application, an apparatus for creating a component template is also provided, comprising: an acquisition module, a parsing module, and a creation module. The acquisition module is configured to acquire a component description, the component description including information about the data structure of the component to be created; the parsing module is configured to parse the component description to obtain the data structure of the component to be created, wherein the parsed data structure of the component to be created is used to determine whether the component to be created is a static component or a dynamic component; and the creation module is configured to: if the component to be created is a static component, create a static component template based on the data structure of the component to be created; or, if the component to be created is a dynamic component, generate an auxiliary configuration based on the type of the dynamic component and the data structure of the component to be created, and create a dynamic component template based on the auxiliary configuration.

[0010] According to another aspect of this application, a page configuration apparatus is also provided, comprising: an acquisition module, a selection module, and an association module. The acquisition module is configured to acquire at least one component identifier, wherein each component identifier is used to indicate a component template of a component to be displayed on the page; the selection module is configured to select a component template from a set of component templates based on at least one component identifier, wherein the component templates in the set of component templates are created based on the method described above; the acquisition module is further configured to acquire configuration data of the selected component template for each selected component template, wherein the configuration data is used to acquire entity data of the component template; and the association module is configured to associate and save the selected component template and its configuration data with the identifiers of the page.

[0011] According to another aspect of this application, a page display apparatus is also provided, comprising: an acquisition module, a determination module, a sending module, and a display module. The acquisition module is configured to acquire an identifier of a page; the determination module is configured to determine, based on the page identifier, component templates and their configuration data to be displayed on the page, wherein the page is configured according to the page configuration method described above; the acquisition module is further configured to acquire entity data of each component template based on its configuration data, and to form component instances with the component templates; the sending module is configured to send each component instance to the display module; and the display module is configured to render the component instances for display on the page.

[0012] According to another aspect of this application, a page management platform is also provided, including an access end and a server end. The server end includes an interactive access backend and a management configuration backend. The access end is configured to send a data acquisition request to the interactive access backend of the server end in response to a user accessing a page. The data acquisition request includes the page identifier. The interactive access backend is configured to send a component configuration acquisition request to the management configuration backend based on the page identifier. The component configuration acquisition request includes the page identifier. The management configuration backend is configured to determine and return the component template and its configuration data corresponding to the page identifier to the interactive access backend based on the page identifier. The page is configured according to the above-described page configuration method, and each component template is created according to the above-described method. The configuration data of the component template is used to obtain the entity data of the component template. The interactive access backend is also configured to obtain the entity data associated with the component template corresponding to the page identifier from the management configuration backend or an external data source based on the component template and its configuration data corresponding to the page identifier, process the obtained entity data to obtain a component instance, and return it to the access end. The access end is also configured to render and display the returned component instance.

[0013] According to another aspect of this application, a computer device is provided, comprising: one or more processors; and one or more memories storing a computer program thereon, which, when executed by the processor, causes one or more processing units to perform the steps of the method described above.

[0014] According to another aspect of this application, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, causes the processor to perform the steps of the method described above.

[0015] According to another aspect of this application, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the various steps of the method described above.

[0016] The method for creating page component templates in this application allows for the creation of templates for static and dynamic components in a differentiated manner. For example, static component templates can be directly generated based on the parsed data structure of the component to be created. Since the parsing module used for parsing can be preset, static component templates can be easily generated without the need for re-developing code. The creation process of dynamic component templates does not require excessive code development by introducing auxiliary configuration, thus simplifying the component template creation process, reducing component development costs, and improving component development iteration efficiency. Attached Figure Description

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

[0018] Figure 1 A schematic diagram of a management platform is shown.

[0019] Figure 2 The image shows a page displayed on a mobile device, which is the financial column page of a news channel.

[0020] Figure 3A A flowchart illustrating a method for creating a component template according to an embodiment of this application is shown.

[0021] Figure 3B This illustrates the process performed by the parsing module in the management configuration backend.

[0022] Figure 4 The various sub-steps of step S330 when creating a dynamic component template for a database source component are shown.

[0023] Figure 5A The various sub-steps of step S330 when creating a dynamic component template for a third-party data source interface component are shown.

[0024] Figure 5B The process of generating and using general configuration functions is illustrated.

[0025] Figure 6 For reference Figure 3A-5B A diagram illustrating the specific process of creating the described page component template.

[0026] Figure 7A A flowchart illustrating a page configuration method according to an embodiment of this application is shown.

[0027] Figure 7BThis illustrates the process performed by the field mapping module in the management configuration backend.

[0028] Figure 8 A flowchart illustrating a page display method according to an embodiment of this application is shown.

[0029] Figure 9 A structural block diagram of an apparatus for creating a component template according to an embodiment of this application is shown.

[0030] Figure 10 A structural block diagram of a page configuration apparatus according to an embodiment of this application is shown.

[0031] Figure 11 A structural block diagram of a page display device according to an embodiment of this application is shown.

[0032] Figure 12 This illustration shows an interaction diagram between the access end and the server end (including the interactive access backend and the management configuration backend) of the page management platform according to an embodiment of this application.

[0033] Figure 13 A structural block diagram of a computer device according to an embodiment of this application is shown. Detailed Implementation

[0034] To make the objectives, technical solutions, and advantages of this application more apparent, exemplary embodiments according to this application will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this application, and not all embodiments of this application. It should be understood that this application is not limited to the exemplary embodiments described herein.

[0035] In this specification and accompanying drawings, substantially identical or similar steps and elements are indicated by the same or similar reference numerals, and repeated descriptions of these steps and elements will be omitted. Furthermore, in the description of this application, terms such as "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance or order.

[0036] Before describing this application, the relevant terms used in the description are explained as follows.

[0037] Management platform: A platform used for managing, configuring, and querying various services. In this application, the management platform may include an access terminal, a server terminal, and a development terminal. The server terminal may include an interactive access backend and a management configuration backend.

[0038] Development side: This section is used by developers to configure relevant configuration information for the management platform, and it works in conjunction with the server side.

[0039] Access point: This refers to the front-end of the website, which can also be considered as the front end. It displays pages for users to browse and enables interactive functions with users.

[0040] Interactive access backend: Also known as the C-end access backend, it is part of the management platform's backend. It can be used to interact with the access end and users, and acts as a bridge between the access end and the management configuration backend. It can obtain user requests from the access end, obtain information or data from the management configuration backend, pull data from external data sources based on specific configurations, process the pulled data, and return it to the access end for use by the user.

[0041] Management Configuration Backend: Part of the management platform, it can be used to read configuration data and information from the development side, interact with the access side, save and read data, implement underlying business logic, maintain the stability and performance of the platform, etc., but does not directly interact with the access side or external data sources.

[0042] JSON: A lightweight data-interchange language that uses a text format that is completely independent of programming languages ​​to store and represent data. This language is easy for humans to read and can be used to transmit data objects consisting of attribute values ​​or sequential values.

[0043] HTTP, TCP, and UDP are all communication protocols that can be used by management platforms to obtain data from external data sources with specific access methods.

[0044] TRPC: A remote procedure call framework that can also be used to manage platforms to retrieve data from external data sources with specific access methods.

[0045] like Figure 1 As shown, in one embodiment, a management platform is provided, including a server (which can be a server) 102, an access terminal (also called a client-side) 104, and a development terminal 106. The server 102 stores various data implementing the management platform, executes various logical operations, and provides a public gateway interface for implementing the management platform. The access terminal 104 requests access to pages of the management platform from the server 102. The development terminal 106 is used by developers to configure relevant configuration information of the management platform. The server 102 can be a standalone physical server or a cluster of physical servers. When the server 102 is a server and connected to a display and input devices, the server 102 can also implement the functions of the access terminal 104 and / or the development terminal 106. The number of access terminals 102 and development terminals 106 can be one or more.

[0046] The access terminal 102 and the development terminal 106 can be the same or different terminals. These terminals can include desktop computers and mobile terminals, such as mobile phones, tablets, laptops, and personal digital assistants. Both the access terminal 102 and the development terminal 106 have displays and input devices. Input devices include keyboards, mice, or touchpads.

[0047] As mentioned earlier, when displaying a page of a business application (such as a promotional activity page, the homepage of a news application, etc.), the content to be displayed on the page is usually divided into multiple components according to the page layout (e.g., component modularization).

[0048] Based on this, when configuring a page, developers can determine the component template for each component to be displayed on the page, and then input at least one component identifier, with each component identifier corresponding to a component template, such as... Figure 1 After obtaining at least one component identifier, the server 102 can select a component template for the component to be displayed on the page from the component template set based on the at least one component identifier, and then obtain a component instance by filling entity data into these component templates, and then display it on the page after rendering.

[0049] Components on a webpage can generally be divided into static components and dynamic components. Dynamic components can be further divided into third-party data source interface components and database source components.

[0050] For example, Figure 2 The image shows a page displayed on a mobile phone as an example of a mobile terminal, specifically a financial column page for a news channel. Of course, this page could also be other pages depending on the specific needs, such as a promotional page or a game page. Furthermore, this page could also be displayed on other mobile terminals (such as tablets, personal digital assistants, etc.) or terminals (such as desktop computers).

[0051] like Figure 2 As shown, the block within the solid box at the top is a static "banner component," whose entity data mainly consists of images and text, and it remains unchanged once configured until the images and text are reconfigured. The block within the dashed box in the middle is a dynamic "stock index component," whose entity data is obtained from a third-party data source, and developers cannot directly configure the entity data. The block within the dashed box at the bottom is a dynamic database source component, which can be an advertising space used to place images of a merchant's products. Therefore, the merchant provides a database of images to be displayed, and the entity data included in the component is obtained from the database.

[0052] However, in some cases, the existing set of component templates may not contain the required template, necessitating its creation. In the current modular component configuration, for new component template requirements, developers create new code for each new template, resulting in significant code development effort, potentially leading to redundant code and increased development costs.

[0053] Therefore, this application proposes a solution that simplifies the component template creation process, thereby reducing component development costs and improving component development iteration efficiency.

[0054] Figure 3A A flowchart illustrating a method for creating a component template according to an embodiment of this application is shown. This method can, for example, be... Figure 1 The server-side 102 and the development-side 106 in the process execute collaboratively.

[0055] like Figure 3A As shown, in step S310, a component description is obtained, which includes information about the data structure of the component to be created.

[0056] For example, a component description can be a data structure of the component expressed in JSON format. Optionally, the JSON format can be in the form of key-value pairs. Alternatively, the data structure can also be expressed in XML or YAML formats.

[0057] In step S320, the component description is parsed to obtain the data structure of the component to be created, wherein the parsed data structure of the component to be created is used to determine whether the component to be created is a static component or a dynamic component.

[0058] Optionally, Figure 1 The interactive access backend of server 102 is generally used for interaction with the outside world. Most management and configuration operations can be executed by the management and configuration backend. Therefore, after the JSON format data structure is entered on the development side, it can be submitted to the management and configuration backend. Then, after the management and configuration backend obtains the JSON format data structure, it parses it to obtain a data structure in a preset code format (such as JavaScript) that the management and configuration backend can recognize and process.

[0059] The parsing module can be pre-configured in the management settings to perform the parsing process, for example, ... Figure 3BAs shown, the parsing module can obtain the component's data structure expressed in JSON format (referred to as JSON data structure), and then parse the JSON data structure by traversing each field to obtain the field name and field type of each field. Then, based on the field name and field type of each field obtained from the parsing, it generates or reflects a data structure in a preset code format (such as JavaScript).

[0060] Optionally, the system can determine whether the component to be created is a static or dynamic component based on a data structure in a preset code format (e.g., JavaScript). Optionally, it can also determine whether the data structure in the preset code format (e.g., JavaScript) conforms to predefined specifications. If it is determined that the data structure does not conform to the predefined specifications, subsequent component template creation operations can be prevented; if it is determined that the data structure conforms to the predefined specifications, subsequent component template creation operations can continue. Optionally, the process of determining whether the component to be created is a static or dynamic component and whether its data structure conforms to predefined specifications can be performed manually by the developers or executed by the management configuration backend according to preset logic.

[0061] In step S330, if the component to be created is a static component, a static component template is created based on the parsed data structure of the component to be created; or if the component to be created is a dynamic component, an auxiliary configuration is generated based on the type of the dynamic component and the parsed data structure of the component to be created, and a dynamic component template is created based on the auxiliary configuration.

[0062] For example, when creating a static component template, the field names and field types of the fields included in the parsed data structure of the component to be created can be determined; and the static component template can be generated based on the determined field names and field types. For example, the data structure of the static component template includes the fields of the component to be created, and has corresponding field names and field types.

[0063] For creating dynamic component templates, the auxiliary configuration can be related to the external data source (mainly including database sources and third-party data sources in this application) from which to obtain the entity data of the components. This auxiliary configuration generates the corresponding dynamic component template without requiring extensive code development, which will be discussed below. Figure 4-6 Detailed description.

[0064] By reference Figure 3AThe described method for creating page component templates can parse component descriptions, including information about the data structure of the component to be created, and create templates differently for static and dynamic components. For example, static component templates can be directly generated based on the parsed data structure of the component to be created. Since the parsing module used for parsing can be preset (e.g., configured by developers and saved in the management configuration backend), static component templates can be easily generated without rewriting code. The creation process of dynamic component templates does not require much code development by introducing auxiliary configuration, thus simplifying the component template creation process, reducing component development costs, and improving component development iteration efficiency.

[0065] The following combination Figure 4 This describes the process of creating a dynamic component template when the type of the dynamic component is a database source component used to retrieve data from a database.

[0066] As mentioned earlier, the entity data of components on the page can come from a database. For example, an ad space is used to place images of a merchant's products, so the merchant provides a database of images to be displayed and its tables.

[0067] Figure 4 The various sub-steps of step S330 when creating a dynamic component template for a database source component are shown.

[0068] In sub-step S330-1, an input module for field mapping is generated based on the data structure of the database source component. The input module for field mapping is used to configure the field mapping between the data structure of the component to be created and the tables in the database.

[0069] Since the associated databases can be different or multiple each time, it's desirable to develop a unified template for different databases to avoid secondary development. Then, the template's configuration data can be configured differently for each database. Furthermore, the database source component needs to retrieve entity data from the database, and the fields of the data structure of the database source component (which is the component to be created) have already been parsed. Therefore, an input module can be generated based on these fields to map the fields of the database source component to the fields of the database tables. For example, the input module can provide a configuration entry point for the field mappings, and the specific field mappings will be provided in the subsequent configuration data after template creation. In this way, the configuration data during the configuration phase after template creation can be the mapping relationship between the fields of the database source component's data structure and the fields of the database tables.

[0070] In sub-step S330-2, an address input module is generated according to the preset address format of the database associated with the database source component as needed. The address input module is used to configure the address of the database.

[0071] Similarly, the database address indicates where to obtain the entity data of the database source component and has a preset address format. Therefore, an input module can be generated to configure this address with the preset address format, providing a configuration entry point for the address. After obtaining the address during the configuration phase, it can point to the database. In this way, the database source component is associated with the database, and the configuration data during the configuration phase after template creation can be the address of the database that needs to be associated with the database source component.

[0072] In sub-step S330-3, a dynamic component template for the database source component is created based on the configuration of the input module for the database address and the configuration of the input module for the field mapping.

[0073] Optionally, after parsing the data structure of the database source component (the component to be created) (as described in step S320), it can be determined which fields exist (the content corresponding to the fields can be filled with the entity data obtained later) to obtain the initial template. After configuring the input module for the database address and the input module for the field mapping, the initial template is associated with the auxiliary configuration to obtain the template for the created dynamic component.

[0074] The created dynamic component template includes an address input module and a field mapping input module. Specific database-related information (e.g., field mapping and address) is provided in the configuration data after the template is created.

[0075] By reference Figure 4 The described process involves creating a component template for a database source component. By providing specific database-related information (e.g., field mappings and addresses) in the configuration data after template creation, the template creation process only requires configuring the input modules for the addresses and field mappings. Therefore, unlike existing technologies, there is no need to configure specific database-related details in the template. As a result, the template has greater versatility and can avoid secondary development.

[0076] The following combination Figure 5A This describes the process of creating a dynamic component template when the type of the dynamic component is a third-party data source interface component used to obtain data from a third-party data source.

[0077] As mentioned earlier, the entity data of components on the page can come from third-party data sources. This means that third-party data source interfaces can be called to retrieve data from them. For example, the entity data of a stock index component could come from a stock exchange's server. Figure 1 The management platform shown can be viewed as a client requesting data from an external server.

[0078] Figure 5AThe various sub-steps of step S330 when creating a dynamic component template for a third-party data source interface component are shown.

[0079] In step S330-A, the address and interface method of the third-party data source are obtained.

[0080] Optionally, the address is used to indicate, for example... Figure 1 The management platform shown obtains data from various sources, including destination IPs, domain names, and paths; the interface method can be... Figure 1 The management platform shown relates to the methods by which it retrieves (requests) data from third-party data sources. Different third-party data sources can have the same or different interface methods. Optionally, the interface method can be based on HTTP, TCP, UDP, TRPC, etc. For example, after determining the third-party data source from which to retrieve data, the developer can input the address and interface method information into the management platform (e.g., ...). Figure 1 The developer and server sides of the application obtain the address and interface method of the third-party data source.

[0081] In step S330-B, the service configuration corresponding to the interface method of the third-party data source is obtained according to the interface method of the third-party data source, and third-party data is obtained from the third-party data source based on the obtained service configuration.

[0082] Different interface methods correspond to different service configurations; for example, the service configurations for HTTP-based interfaces are different from those for UDP-based interfaces. For a specific third-party data source, different service configurations are required based on the interface method of that third-party data source, and the correspondence between different interface methods and different service configurations is pre-set.

[0083] Optionally, each service configuration includes all the details of the configuration through which data can be obtained. For example, it may include the service invocation method configuration, service parameter passing method configuration, and service addressing configuration corresponding to that service configuration. For instance, the service invocation method configuration includes specific configurations for interface methods such as HTTP, TCP, UDP, or TPRC; the service parameter passing method configuration includes timeout settings; and the service addressing configuration includes domain name lookup or IP address lookup settings.

[0084] Optionally, the service configuration corresponding to the interface method with the third-party data source can be obtained through the following operations.

[0085] Operation i retrieves the configuration identifier of the service configuration corresponding to the interface method of the third-party data source.

[0086] For example, after developers determine the interface method for obtaining data from a third-party data source, they can input the configuration identifier of the service configuration corresponding to that interface method as the interface method information mentioned in sub-step S330-A into the management platform. That is, the management platform, for example, obtains this configuration identifier.

[0087] The configuration file includes multiple service configurations, each corresponding to different interface methods, and each service configuration has a configuration identifier. Optionally, this configuration file is... Figure 1 The server-side configuration file shown can be in text, ini, or xml format. In this configuration file, the developers predefine different service configurations for the various known interface methods, and each service configuration is assigned a configuration identifier (e.g., given an alias) for easy reading or referencing.

[0088] Operation ii: Based on the configuration identifier and general configuration function of the service configuration corresponding to the interface method with the third-party data source, retrieve the service configuration corresponding to the interface method with the third-party data source from the configuration file. The general configuration function is an abstract configuration function used for multiple service configurations.

[0089] Optionally, after the management platform's development and server sides obtain the configuration identifier of the service configuration corresponding to the interface method of the third-party data source, since the general configuration function is an abstraction of multiple service configurations, the corresponding service configuration can be retrieved from the configuration file after passing the configuration identifier into the general configuration function (i.e., passing parameters).

[0090] Subsequently, the management platform, such as the server, can use the retrieved service configuration to obtain third-party data from the third-party data source with the aforementioned address. Specifically, since the interactive access backend is generally used for external interaction, it can obtain third-party data from the third-party data source. For example, such as... Figure 5B As shown, the different service configurations corresponding to different interface methods can be abstracted into a general configuration function at the interactive access backend. Then, the general configuration function uses the obtained configuration identifier (alias) as a parameter to pull the corresponding service configuration from the configuration file, and requests data from a third-party data source based on the service configuration.

[0091] In step S330-C, the field relationship configuration of the parsing result of the data structure based on third-party data is obtained, wherein the field relationship configuration is the correspondence between the fields of the parsed third-party data structure and the fields of the data structure of the third-party data source interface component.

[0092] When first interfaced with a third-party data source, the management platform cannot know the fields of the third-party data returned by that source, thus preventing the component from populating its entity data. Therefore, it is necessary to map the fields in the third-party data's data structure to the fields in the component's data structure. For example, the field DF in the third-party data structure should correspond to the field AC in the component's data structure.

[0093] Developers can manually parse third-party data and configure the field relationships based on the fields of the parsed third-party data structure and the fields of the third-party data source interface component's data structure. They can then save the field relationship configuration indicating this relationship, which the management platform can then access. Alternatively, third-party data can be parsed using pre-defined logic (e.g., a pre-compiled field parsing module) to obtain the field relationship configuration.

[0094] In step S330-D, a dynamic component template for the third-party data source interface component is created based on the service configuration and field relationship configuration corresponding to the interface method with the third-party data source.

[0095] In this way, the service configuration and field relationship configuration corresponding to the above interface method with the third-party data source can be regarded as auxiliary configuration for creating dynamic component templates.

[0096] Optionally, after parsing the data structure of the third-party data source interface component (the component to be created) (as described in step S320), it can be determined which fields exist, obtain the initial template, and after configuring the service and field relationships corresponding to the interface method with the third-party data source, associate the initial template with the auxiliary configuration to obtain the template for the created dynamic component.

[0097] By reference Figure 5A The described process of creating component templates for third-party data source interface components, although the interface methods and data structures of different third-party data sources may differ, requiring developers to perform some code development for different third-party data sources, such as configuring configuration files and designing code for obtaining parameters (e.g., address, configuration identifier, etc.), can efficiently retrieve the service configuration corresponding to the interface method of the third-party data source by pre-setting service configurations for different interface methods and using parameters passed to a general configuration function. Therefore, it is not necessary to configure the specific details of the service configuration every time a template is created, as in existing technologies, which can reduce code development to a certain extent.

[0098] Furthermore, according to other implementation methods, a corresponding interface parsing module can be customized for each interface method. This module encapsulates pre-set service configurations and common field relationship configurations. After obtaining the interface method of the third-party data source, the corresponding service configuration is used to retrieve third-party data from the third-party data source and obtain the field relationship configuration (if a field with an unconfigured relationship is encountered, an error is reported and subsequently configured manually). In this way, completely code-free configuration can be achieved, further reducing code development costs.

[0099] The above is for reference only. Figure 3A-5B This describes the process of creating component templates for static or dynamic components. After a component template is created, its configuration data is needed to obtain the entity data used for that component template. For example, for a static component consisting of an image and text, the configuration data for the static component template includes the image's address data (e.g., a URL or local address) and the text data.

[0100] The following combination Figure 6 For the above reference Figure 3A-5B The process of creating the described page component template is described in an example scenario. This example scenario is, for instance, a promotional activity scenario, where operations personnel need to determine the components to be displayed on the page. If no component template exists for that component, they can request a new component template, as shown in step S601.

[0101] First, as shown in step S602, the operator defines the data structure of the required components, which can be provided to, for example... Figure 1 The server-side management configuration backend allows, for example, operations personnel to specify and submit the data structure of a component on the management configuration platform. This includes specifying the field names and corresponding field types of the data structure, using JSON format as the carrier. Then, in step S603, after obtaining the data structure specified by the operations personnel, the management configuration backend parses the data structure (using a preset parsing module). For example, it iterates through each field (field name / field type) to ultimately convert or reflect the JSON-formatted data structure into a data structure corresponding to a code type that can be processed (e.g., JavaScript). Then, in step S604, the parsed data structure is reviewed to determine if it conforms to predefined specifications. If it does not conform to the predefined specifications, subsequent component template creation operations can be prevented; if it conforms to the predefined specifications, subsequent component template creation operations can continue.

[0102] If the component to be created is determined to be a static component based on the parsing result (No in step S605), in step S606, the management configuration backend can determine the field names and field types of each field included in the data structure of the component to be created; and generate the static component template based on the determined field names and field types of each field.

[0103] If the parsing results determine that the component to be created is a dynamic component ("Yes" in step S605), the management configuration backend can create the template differently depending on whether the dynamic component is a database source component or a third-party data source interface component, as determined in step S607. Whether the dynamic component is a database source component or a third-party data source interface component can also be determined during the process of determining whether the component to be created is a static component or a dynamic component in the aforementioned step S605.

[0104] If the component to be created is determined to be a database source component based on the parsing results ("Yes" in step S607), in steps S608-609, the management configuration backend can generate a field mapping input module according to the data structure of the database source component for subsequent input configuration data, and generate an address input module according to a preset address format. In step S610, the settings of these two input modules are saved, and a dynamic template is created based on them. After the dynamic template is created, the field mapping input module can be used to configure the field mapping between the data structure of the component to be created and the data structure of the database (database tables), and the address input module is used to configure the address of the database to be associated with the component.

[0105] If the component to be created is determined to be a third-party data source interface component ("No" in step S607), different third-party data sources may have different interface methods (i.e., data request methods), such as HTTP, TCP, UDP, TRPC, etc., and the service configuration corresponding to each interface method is also different. Therefore, it is necessary to select the appropriate service configuration for the specific third-party data source. In addition, the fields of data from different third-party data sources are also different. Therefore, it is necessary to know the field relationship between the fields of the data structure of the component to be created and the fields of the data from the third-party data source.

[0106] Based on this, regarding the third-party data source interface component, in step S611, developers can first perform backend development, including: in step S612, writing the service configurations corresponding to different interface methods into the configuration file, and assigning a configuration identifier to each service configuration; in step S613, abstracting the different service configurations corresponding to different interface methods into a general configuration function (i.e., generating an abstract configuration function), so that for a specific interface method, the service configuration corresponding to that specific interface method can be obtained by passing the configuration identifier into the general configuration function (parameter passing process). Therefore, various service configurations only need to be configured once, thereby reducing code development; that is, after configuring the configuration file and abstracting the general configuration function, developers can save it and configure... The file includes different service configurations and corresponding configuration identifiers. The interactive access backend (generally used for external data source interaction) can obtain the configuration identifier and address of the interface method for a specific third-party data source from which data is to be obtained. This obtained identifier is used to retrieve the service configuration corresponding to the specific third-party data source's interface method from the configuration file via a general configuration function. This allows the third-party data, also known as the return packet data, to be obtained from the specific third-party data source with that address using the obtained service configuration, as shown in step S614. In step S615, the return packet data is parsed to obtain its data structure. The correspondence between the fields in the return packet data structure and the fields in the data structure of the third-party data source interface component is configured as the field relationship configuration. The obtained service configuration and field relationship configuration corresponding to the specific third-party data source's interface method are saved, and a dynamic template is created based on them.

[0107] In summary, the component template creation method of this application can parse the component description, including the data structure of the component to be created, and create templates separately for static and dynamic components. It also simplifies the component template creation process, thereby reducing component development costs and improving component development iteration efficiency. For example, static component templates can be directly generated based on the parsed data structure of the component to be created. Since the parsing module is pre-defined, static component templates can be easily generated without re-developing code. The creation process of dynamic component templates requires less development through auxiliary configuration related to external data sources. For example, by providing specific database information in the configuration data after template creation, there is no need to configure specific database details in the template as in existing technologies. The template has greater versatility, thus avoiding secondary development. By pre-setting service configurations for different third-party data source interface methods and using the parameter passing process of a general configuration function to retrieve the corresponding service configuration, there is no need to configure specific service configuration details every time a template is created, as in existing technologies, which can reduce code development to a certain extent.

[0108] After the component template is created, it will be used in the page configuration. For example... Figure 2 The example page is composed of at least one component. Therefore, when configuring a new page, it is necessary to select the component templates for the at least one component from the existing set of component templates, obtain the configuration data corresponding to each component template, obtain the entity data based on the configuration data, and finally display the obtained entity data of each component on the page.

[0109] The following will combine Figure 7A-8 The page configuration method and the page display method are described separately.

[0110] Figure 7A A flowchart illustrating a page configuration method according to an embodiment of this application is shown. This method can be... Figure 1 The server and development teams are shown working together.

[0111] like Figure 7A As shown, in step S710, at least one component identifier is obtained, wherein each component identifier is used to indicate a component template of a component to be displayed on the page.

[0112] Optionally, when creating component templates as described above, a component identifier is assigned to each created template. Therefore, once page configurers (e.g., developers) determine the components to be displayed on the page, they can enter at least one component identifier, enabling the display of components on the page. Figure 1 The server shown or its management configuration platform obtains the identifier of at least one component.

[0113] In step S720, a component template is selected from a set of component templates based on at least one component identifier, wherein the component templates in the set of component templates are based on the aforementioned reference. Figure 3A-5B The method described is used for creation.

[0114] In other words, since each component identifies at least one component template, the component template for the component to be displayed can be obtained based on these identifiers.

[0115] In step S730, for each selected component template, the configuration data of the component template is obtained, wherein the configuration data is used to obtain the entity data of the component template.

[0116] Optionally, when the selected component template is a static component template for static components, if the data structure of the static component includes at least one of text and image fields, the text data or the image address data is obtained as configuration data. In this case, the obtained text data is also the entity data of the component template, and the corresponding image can be obtained based on the image address data, also as entity data.

[0117] Optionally, if the selected component template is a dynamic component template for the database source component, the field mapping between the data structure fields of the database source component and the fields of the database table, as well as the database address, are obtained as configuration data. For example, developers can perform these configurations on the development side to provide configuration data to both the development and server sides.

[0118] For example, a database table has three fields: ID, data, and title. A dynamic component's data structure has two fields: imageData and imageTitle. When configuring field mapping, data is associated with imageData, and title is associated with imageTitle. Since the database address is A, these configurations are saved together as configuration data. In this case, after configuration, image data and titles can be retrieved from the database based on the configuration data.

[0119] Furthermore, to ensure data retrieval from the database, after obtaining the field mappings configured for the component template and the database address, it's necessary to check if the database is accessible, for example, by checking if it can be accessed by the server, such as using a database query. If the database is accessible, and the data structure fields of the database source component are inconsistent with the mapped fields in the database, a field type conversion is performed. For example, if the parsed data structure field type of the database source component (the component to be created) is string, but the mapped field type in the database is number, a field type conversion is required. The converted field mappings and the database address are then used as the configuration data. Conversely, if the database is inaccessible, the configuration data is deleted. This operation can be performed, for example, by configuring a field mapping module in a management platform (e.g., the server's management configuration backend). Figure 7B As shown.

[0120] In some implementations, there may be more than two databases. For example, if both Merchant A and Merchant B want to display their product images in the ad space, the component to be created needs to be associated with more than two databases, and correspondingly configured with more than two field mappings and more than two database addresses.

[0121] Optionally, if the selected component template is a dynamic component template for a third-party data source interface component, the service configuration and field relationship configuration corresponding to the third-party data source are obtained as configuration data. The field relationship configuration defines the correspondence between the fields of the data structure of the third-party data source interface component and the fields of the data structure of the third-party data obtained from the third-party data source based on the service configuration. It should be noted that the service configuration and field relationship configuration are already obtained during the template creation process, as referenced above. Figure 5A Steps S330-B and S330-C describe steps that do not require additional configuration. In this case, third-party data (entity data) can be obtained from a third-party data source based on the configuration data and the corresponding service configuration. The fields of the third-party data can then be transformed to populate the corresponding fields in the data structure of the third-party data source interface component.

[0122] In step S740, the selected component template and its configuration data are associated with the identifier of the page and saved.

[0123] For example, an identifier can be assigned to a configured page, and then the selected component template and its configuration data can be associated with the page identifier, so that the associated component template and its configuration data can be obtained through the page identifier and ultimately used to obtain entity data.

[0124] By reference Figure 7A The described page configuration method configures the corresponding configuration data (e.g., entity data content or address) for each component template, such that, for example... Figure 1 After obtaining the corresponding configuration data, the server can generate or retrieve the entity data of the component template based on this configuration data, obtain each component, and render and display it on the page. Furthermore, specifically for database-source components, configuring field mapping and database address during page configuration improves template versatility, reduces code overhead during template creation, and allows detection of database accessibility and field type conversion, further enhancing configuration reliability and versatility. For third-party data source interface components, no additional configuration is required during page configuration. For static components, only simple field content configuration is needed, simplifying configuration operations after template creation.

[0125] Figure 8 A flowchart illustrating a page display method according to an embodiment of this application is shown. This method can, for example, be... Figure 1 The server-side 102 and the development-side 106 in the process execute collaboratively.

[0126] In step S810, the identifier of the page is obtained.

[0127] For example, each page is assigned a unique identifier.

[0128] In step S820, the component templates and their configuration data to be displayed on the page are determined based on the page's identifier, wherein the page is based on, as referenced... Figure 7A The page configuration method is described.

[0129] As mentioned above Figure 7A As described in step S740, the selected component template and its configuration data are associated with the page identifier, so the associated component template and its configuration data can be obtained through the page identifier.

[0130] In step S830, entity data of the component template is obtained based on each component template and its configuration data, and the entity data is formed with the component template to constitute a component entity.

[0131] For example, the acquired entity data is populated into the fields of the data structure on which the component template is based to form the component entity.

[0132] In step S840, each component instance is sent to the page rendering module for display on the page.

[0133] For example, send each component instance to Figure 1The access point shown is rendered by the access point's page rendering module and then displayed on the page.

[0134] By reference Figure 8 The described page display method can generate or obtain entity data of component templates based on configuration data, obtain each component instance, and render and display it on the page. In addition to the benefits of the page configuration method mentioned above, it can also display multiple component instances on the same page at one time, which is convenient for data management and positioning.

[0135] According to another aspect of this application, an apparatus for creating page component templates is also provided.

[0136] Figure 9 A structural block diagram of an apparatus 900 for creating component templates according to an embodiment of this application is shown.

[0137] like Figure 9 As shown, the device 900 includes an acquisition module 910, a parsing module 920, and a template creation module 930.

[0138] The acquisition module 910 is configured to acquire a component description, which includes information about the data structure of the component to be created.

[0139] The parsing module 920 is configured to parse the component description to obtain the data structure of the component to be created, wherein the parsed data structure of the component to be created is used to determine whether the component to be created is a static component or a dynamic component.

[0140] The template creation module 930 is configured to: create a static component template based on the data structure of the component to be created when the component to be created is a static component; or, generate an auxiliary configuration based on the type of the dynamic component and the data structure of the component to be created when the component to be created is a dynamic component, and create a dynamic component template based on the auxiliary configuration.

[0141] Optionally, the template creation module 930 may include one or more of the input module configuration unit, the acquisition unit, and the creation unit.

[0142] The input module configuration unit can be used to generate the configuration of the field mapping input module according to the data structure of the database source component when the component to be created is a database source component, and to generate the address input module according to the preset address format of the database associated with the database source component as needed. The field mapping input module is used to configure the field mapping between the data structure of the component to be created and the tables of the database, and the address input module is used to configure the address of the database.

[0143] The creation unit can be used to create a dynamic component template for a database source component when the component to be created is a database source component. This is based on the configuration of the input module for the database address and the input module for field mapping. For example, after the parsing module parses the data structure of the database source component (the component to be created), it can determine which fields exist and obtain an initial template. After configuring the input modules for the database address and field mapping, the initial template is associated with auxiliary configurations to obtain the created dynamic component template.

[0144] The retrieval unit can be used to obtain the address and interface method of a third-party data source when the component to be created is a third-party data source interface component.

[0145] The acquisition unit can also be used to obtain the service configuration corresponding to the interface method of the third-party data source when the component to be created is a third-party data source interface component, and obtain third-party data from the third-party data source based on the service configuration.

[0146] Optionally, the acquisition unit can be configured to: acquire the configuration identifier of the service configuration corresponding to the interface method of the third-party data source; and acquire the service configuration corresponding to the interface method of the third-party data source from the configuration file based on the configuration identifier of the service configuration corresponding to the interface method of the third-party data source and a general configuration function, wherein the configuration file includes multiple service configurations, each service configuration corresponds to a different interface method, and each service configuration has a configuration identifier, and the general configuration function is an abstract configuration function for multiple service configurations.

[0147] The acquisition unit is also used to acquire the field relationship configuration of the parsing result of the data structure based on the third-party data when the component to be created is a third-party data source interface component. The field relationship configuration is the correspondence between the fields of the parsed data structure of the third-party data and the fields of the data structure of the third-party data source interface component.

[0148] The creation unit can also be used to create dynamic component templates for third-party data source interface components by configuring service settings and field relationships based on the interface method of a third-party data source. For example, after the parsing module parses the data structure of the third-party data source interface component (the component to be created), it can determine which fields exist and obtain an initial template. After configuring the service settings and field relationships corresponding to the interface method of the third-party data source, the initial template is associated with auxiliary configurations to obtain the created dynamic component template.

[0149] More details about each module can be found in the reference. Figure 3A-6The method for creating page component templates is described in the description, so it will not be repeated here. Furthermore, the device 900 can be divided into more or fewer modules depending on the required functions, and each module can be further divided into multiple units to achieve its respective functions.

[0150] In summary, the component template creation device of this application can parse the component description, including the data structure of the component to be created, and create templates separately for static and dynamic components. It simplifies the component template creation process, thereby reducing component development costs and improving component development iteration efficiency. For example, static component templates can be directly generated based on the parsed data structure of the component to be created. Since the parsing module is pre-defined, static component templates can be easily generated without re-developing code. The creation process of dynamic component templates requires less development through auxiliary configuration related to external data sources. For example, by providing specific database information in the configuration data after template creation, there is no need to configure specific database details in the template as in existing technologies. The template has greater versatility, thus avoiding secondary development. By pre-setting service configurations for different third-party data source interface methods and using the parameters of a general configuration function to retrieve the corresponding service configuration, there is no need to configure specific service configuration details every time a template is created, as in existing technologies, which can reduce code development to a certain extent.

[0151] According to another aspect of this application, a page configuration device is also provided.

[0152] Figure 10 A structural block diagram of a page configuration apparatus 1000 according to an embodiment of this application is shown.

[0153] The page configuration device 1000 may include an acquisition module 1010, a selection module 1020, and an association module 1030.

[0154] The acquisition module 1010 is configured to acquire at least one component identifier, wherein each component identifier is used to indicate a component template of a component to be displayed on the page.

[0155] The selection module 1020 is configured to select a component template from a set of component templates based on the at least one component identifier, wherein the component templates in the set of component templates are based on a reference. Figure 3A-6 The method described is used for creation.

[0156] The acquisition module 1010 is also configured to acquire configuration data for each selected component template, wherein the configuration data is used to acquire entity data related to the component template.

[0157] Optionally, the acquisition module 1010 may include an acquisition unit and a field mapping unit.

[0158] The acquisition unit can be used to: 1) When the selected component template is a static component template, and the static component's data structure includes at least one of text and image fields, acquire text data and image address data as configuration data; 2) When the selected component template is a dynamic component template for a third-party data source interface component, acquire service configuration and field relationship configuration corresponding to the third-party data source as configuration data, wherein the field relationship configuration is the correspondence between fields of the third-party data source interface component's data structure and fields of the third-party data structure obtained from the third-party data source based on the service configuration; 3) When the selected component template is a dynamic component template for a database source component, acquire the field mapping between fields of the database source component's data structure and fields of the database table, as well as the database address, as configuration data.

[0159] The field mapping unit can be used to detect whether the database can be accessed after obtaining the field mapping and the address of the database; and if it is determined that the database can be accessed, and if the fields of the data structure of the database source component are inconsistent with the types of the mapped fields of the determined database, perform field type conversion and return the field mapping after field type conversion to the acquisition unit to obtain the configuration data; or if it is determined that the database cannot be accessed, delete the configuration data.

[0160] The association module 1030 is configured to associate and save the selected component template and its configuration data with the page's identifier.

[0161] More details about each module can be found in the reference. Figure 7A The page configuration method is described in the description, so it will not be repeated here. Furthermore, it should be understood that the device 1000 can be divided into more or fewer modules depending on the different functions required, and each module can be further divided into multiple sub-modules to implement their respective functions.

[0162] By reference Figure 10The described page configuration device configures corresponding configuration data (e.g., entity data content or address) for each component template. Specifically, for database source components, field mapping and database address configuration are performed during page configuration, improving template versatility, reducing code overhead during template creation, and enabling detection of successful database association with the component and field type conversion, further enhancing configuration reliability and versatility. For third-party data source interface components, no additional configuration is required during page configuration. For static components, only simple field content configuration is needed, facilitating configuration operations after template creation.

[0163] According to another aspect of this application, a page display device is also provided.

[0164] Figure 11 A structural block diagram of a page display device 1100 according to an embodiment of this application is shown.

[0165] The device 1100 may include: an acquisition module 1110, a determination module 1120, a sending module 1130, and a display module 1140.

[0166] The retrieval module 1110 can be configured to retrieve the identifier of the page.

[0167] The determination module 1120 can be configured to determine the component template and its configuration data to be displayed on the page based on the page's identifier, wherein the page is configured based on the page configuration method described above.

[0168] The acquisition module 1110 can also be configured to acquire the entity data of the component template based on each component template and its configuration data, and form a component instance with the component template.

[0169] Sending module 1130 is configured to send each component instance to display module 1140.

[0170] The display module 1140 is configured to render component instances for display on the page.

[0171] More details about each module can be found in the reference. Figure 8 The page display method is described in the description, so it will not be repeated here. Furthermore, it should be understood that the device 1100 can be divided into more or fewer modules depending on the different functions required, and each module can be further divided into multiple sub-modules to achieve their respective functions.

[0172] According to another aspect of this application, a page management platform is also disclosed, which can be integrated with the referenced... Figure 1The management platforms described have the same or similar structures, for example, including an access terminal and a server terminal, wherein the server terminal includes an interactive access backend and a management configuration backend.

[0173] Figure 12 This diagram illustrates the interaction between the access end and the server end (including the interactive access backend and the management configuration backend) of a page management platform according to an embodiment of this application. The page management platform can return page content to the user based on the user's access.

[0174] like Figure 12 As shown, in process A, the user accesses the page, that is, the access terminal receives the user's access request for the page.

[0175] In process B, the accessing end responds to the user's access to the page by sending a data retrieval request to the interactive access backend of the server. The data retrieval request may include the page's identifier.

[0176] In process C, the interactive access backend sends a component configuration retrieval request to the management configuration backend based on the page's identifier. The component configuration retrieval request includes the page's identifier.

[0177] In process D, the management configuration backend, based on the page's identifier, determines and returns the component template and its configuration data corresponding to the page's identifier to the interaction access backend. The page is based on, as shown in the reference... Figure 7A The page configuration method described above configures and saves the configuration data for each component template, with each component template based on a reference. Figure 3A-6 The described method is used to create the component template, and the configuration data of the component template is used to obtain the entity data of the component template.

[0178] In the process of EF, the interactive access backend retrieves entity data associated with the component template corresponding to the page's identifier from the management configuration backend or an external data source, based on the component template and its configuration data. For example, for static component templates, entity data (e.g., text and image data) will be returned from the management configuration backend; for database source components and third-party data source interface components, data will be pulled from the external data source based on the configuration data.

[0179] In the process GH, the interactive access backend processes the acquired entity data and returns it to the accessing client. For example, the acquired entity data is populated into the various fields of the data structure on which the corresponding component template is based to form the corresponding component entity.

[0180] In process I, the client renders and displays the processed entity data.

[0181] In this way, when a user visits a page (for example, in response to a user click), the templates of each component on that page and their configuration data can be determined. Then, based on each component template and its configuration data, the entity data of that component template can be generated or obtained to obtain each component instance. After rendering it on the page, it can be displayed. This allows multiple component instances to be displayed on the same page at once, which is convenient for data management and location.

[0182] According to another aspect of this application, a computer device is also provided. This computer device can be... Figure 1 The description includes the server-side and development-side components.

[0183] Figure 13 A structural block diagram of a computer device 1300 according to an embodiment of this application is shown. The computer device includes: one or more processors; and one or more memories storing a computer program thereon, the computer program, when executed by the one or more processors, causing the one or more processors to perform as described in the reference... Figure 3A-5B The various steps and references of the component template creation method described above Figure 7A The page configuration method and reference described above Figure 8 The steps of the page display method described above.

[0184] The processor can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor, and can be based on an x84 architecture or an ARM architecture.

[0185] Memory can be the computer's internal memory or a non-volatile storage medium used to store computer programs. Internal memory generally uses semiconductor memory cells, such as random access memory (RAM), read-only memory (ROM), and cache. Non-volatile storage media can be such as read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. It should be noted that the memory used in the methods described in this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0186] A computer device's network interface can be used to connect to external devices. The computer device's display screen can be an LCD screen or an e-ink screen. Input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad on the terminal casing, or an external keyboard, touchpad, or mouse. A computer device's camera can be used to capture information about the surrounding environment or people.

[0187] According to another aspect of this application, a computer-readable storage medium is also provided, storing a computer program that, when executed by a processor, causes the processor to perform the actions described in the referenced document. Figure 3A-5B The various steps and references of the component template creation method described above Figure 7A The page configuration method and reference described above Figure 8 The steps of the page display method described above.

[0188] According to another aspect of this application, a computer program product is also provided, comprising a computer program that, when executed by a processor, implements as described in the reference. Figure 3A-5B The various steps and references of the component template creation method described above Figure 7A The page configuration method and reference described above Figure 8 The steps of the page display method described above.

[0189] It should be noted that the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains at least one executable instruction for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0190] Generally, the various exemplary embodiments of this application can be implemented in hardware or dedicated circuitry, software, firmware, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computer device. When aspects of the embodiments of this application are illustrated or described as block diagrams, flowcharts, or using some other graphical representation, it will be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented as non-limiting examples in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computer devices, or some combination thereof.

[0191] The exemplary embodiments of this application described in detail above are merely illustrative and not restrictive. Those skilled in the art should understand that various modifications and combinations can be made to these embodiments or their features without departing from the principles and spirit of this application, and such modifications should fall within the scope of this application.

Claims

1. A method for creating a component template, comprising: Obtain the component description, which includes information about the data structure of the component to be created; The component description is parsed to obtain the data structure of the component to be created, wherein the parsed data structure of the component to be created is used to determine whether the component to be created is a static component or a dynamic component. If the component to be created is a static component, a static component template is created based on the parsed data structure of the component to be created. or When the component to be created is a dynamic component, an auxiliary configuration is generated based on the type of the dynamic component and the parsed data structure of the component to be created. A dynamic component template is then created based on this auxiliary configuration. The auxiliary configuration is a configuration related to an external data source for the entity data of the dynamic component to be acquired. The type of the dynamic component includes at least one of a database source component and a third-party data source component, and the external data source includes at least one of a database source and a third-party data source. Specifically, during page display, static components on the page are generated by filling the static component entity data into the created static component template, and dynamic components on the page are generated by filling the dynamic component entity data into the created dynamic component template.

2. The method according to claim 1, wherein, The dynamic component is a database source component for retrieving data from a database, and the auxiliary configuration includes the configuration of the input module for the address of the database and the configuration of the input module for field mapping. This includes generating auxiliary configurations based on the type of the dynamic component and the parsed data structure of the component to be created, and creating a dynamic component template based on the auxiliary configurations, including: The field mapping input module is generated based on the data structure of the database source component, wherein the field mapping input module is used to configure the field mapping between the data structure of the component to be created and the tables of the database; An input module for generating the address is configured to configure the address of the database, based on a preset address format of the database associated with the database source component. Based on the configuration of the input module for the address of the database and the configuration of the input module for the field mapping, a dynamic component template for the database source component is created.

3. The method according to claim 1, wherein the type of the dynamic component is a third-party data source interface component for obtaining third-party data from a third-party data source, and the auxiliary configuration includes service configuration and field relationship configuration; in, Based on the type of the dynamic component and the parsed data structure of the component to be created, an auxiliary configuration is generated, and a dynamic component template is created based on the auxiliary configuration, including: Obtain the address and API method of the third-party data source; According to the interface method of the third-party data source, obtain the service configuration corresponding to the interface method of the third-party data source, and obtain third-party data from the third-party data source based on the service configuration; The field relationship configuration for obtaining the parsed data structure based on third-party data is configured, wherein the field relationship configuration is the correspondence between the fields of the parsed data structure of the third-party data and the fields of the data structure of the third-party data source interface component; and Based on the service configuration corresponding to the interface method of the third-party data source and the field relationship configuration, a dynamic component template for the interface component of the third-party data source is created.

4. The method according to claim 3, wherein, The correspondence between different interface methods and different service configurations is pre-set.

5. The method according to claim 3, wherein, Obtain the service configuration corresponding to the interface method of the third-party data source, including: Obtain the configuration identifier of the service configuration corresponding to the interface method of the third-party data source; and Based on the configuration identifier and general configuration function of the service configuration corresponding to the interface method of the third-party data source, the service configuration corresponding to the interface method of the third-party data source is obtained from the configuration file. The configuration file includes multiple service configurations, each corresponding to a different interface method, and each service configuration has a configuration identifier. The general configuration function is an abstract configuration function used for the multiple service configurations.

6. The method according to any one of claims 3-5, wherein, Each of the service configurations includes a service invocation method configuration, a service parameter input method configuration, and a service addressing configuration corresponding to the service configuration.

7. The method according to claim 1, wherein, If the component to be created is a static component, a static component template is generated based on the parsed data structure of the component to be created, including: Determine the field names and field types of the fields included in the data structure of the component to be created obtained through parsing; and The static component template is generated based on the determined field names and field types.

8. A page configuration method, comprising: Obtain at least one component identifier, where each component identifier is used to indicate a component template to be displayed on the page; Based on the at least one component identifier, a component template is selected from a set of component templates, wherein each component template in the set of component templates is created based on the method of any one of claims 1-7; For each selected component template, obtain the configuration data of the component template, wherein the configuration data is used to obtain the entity data of the component template; as well as Associate the selected component template and its configuration data with the page's identifier and save them.

9. The page configuration method according to claim 8, wherein, For each selected component template, obtain the configuration data of the component template, including: if the selected component template is a component template for static components, When the data structure of the static component includes at least one of text and image fields, the text data or the address data of the image is obtained as the configuration data.

10. The page configuration method according to claim 8, wherein, For each selected component template, obtain the configuration data of the component template, including: in the case that the selected component template is a dynamic component template for a third-party data source interface component, Obtain the service configuration and field relationship configuration corresponding to the interface method of the third-party data source, and use them as the configuration data. The field relationship configuration is the correspondence between the fields of the data structure of the third-party data source interface component and the fields of the data structure of the third-party data obtained from the third-party data source based on the service configuration.

11. The page configuration method according to claim 8, wherein, For each selected component template, obtain the configuration data of the component template, including: in the case that the selected component template is a dynamic component template for database source components, Obtain the field mapping between the fields of the data structure of the database source component and the fields of the table in the database, as well as the address of the database, and use it as the configuration data.

12. The page configuration method according to claim 11, further comprising: After obtaining the field mappings that serve as the configuration data and the address of the database, it is determined whether the database can be accessed; If it is determined that the database can be accessed, and if the fields of the data structure of the database source component are inconsistent with the types of the mapped fields of the database, a field type conversion is performed, and the field mapping after field type conversion and the address of the database are used as the configuration data; as well as If it is determined that the database cannot be accessed, delete the configuration data.

13. A method for displaying a page, comprising: Get the page's identifier; The component template and its configuration data to be displayed on the page are determined based on the page identifier, wherein the page is configured based on the page configuration method as described in any one of claims 9-12; The entity data of the component template is obtained based on each component template and its configuration data, and a component instance is formed by combining the component template with the component template. Each component instance is sent to the page rendering module for display on the page.

14. An apparatus for creating a component template, comprising: The modules include module acquisition, module parsing, and module creation. The acquisition module is configured to acquire a component description, which includes information about the data structure of the component to be created. The parsing module is configured to: parse the component description to obtain the data structure of the component to be created, wherein the parsed data structure of the component to be created is used to determine whether the component to be created is a static component or a dynamic component; and The creation module is configured to: create a static component template based on the data structure of the component to be created if the component to be created is a static component; or, generate an auxiliary configuration based on the type of the dynamic component and the data structure of the component to be created, and create a dynamic component template based on the auxiliary configuration, wherein the auxiliary configuration is a configuration related to an external data source of the entity data of the dynamic component to be acquired, the type of the dynamic component includes at least one of a database source component and a third-party data source component, and the external data source includes at least one of a database source and a third-party data source. Specifically, during page display, static components on the page are generated by filling the static component entity data into the created static component template, and dynamic components on the page are generated by filling the dynamic component entity data into the created dynamic component template.

15. A page configuration device, comprising: Get module, select module, and associate module, among which, The acquisition module is configured to acquire at least one component identifier, wherein each component identifier is used to indicate a component template of a component to be displayed on the page; The selection module is configured to select a component template from a set of component templates based on the at least one component identifier, wherein the component templates in the set of component templates are created based on the method of any one of claims 1-7; The acquisition module is further configured to acquire configuration data of each selected component template, wherein the configuration data is used to acquire entity data of the component template; and The association module is configured to associate and save the selected component template and its configuration data with the page's identifier.

16. A page management system, comprising an access terminal and a server, wherein the server includes an interactive access backend and a management configuration backend. The access terminal is configured to send a data acquisition request to the interactive access backend of the server in response to a user accessing a page. The data acquisition request includes the identifier of the page. The interactive access backend is configured to send a component configuration retrieval request to the management configuration backend based on the identifier of the page, and the component configuration retrieval request includes the identifier of the page; The management configuration backend is configured to determine and return the component template and its configuration data corresponding to the page identifier to the interaction access backend based on the page identifier, wherein, The page is configured based on the page configuration method as described in any one of claims 9-12, and each component template is created based on the method as described in any one of claims 1-7. The configuration data of the component template is used to obtain the entity data of the component template. The interactive access backend is also configured to obtain entity data associated with the component template corresponding to the identifier of the page from the management configuration backend or an external data source based on the component template and its configuration data corresponding to the identifier of the page, process the obtained entity data to obtain a component instance, and return it to the access terminal. The access point is also configured to render and display the returned component instance.

17. A computer device, comprising: One or more processors; and One or more memories having a computer program stored thereon, which, when executed by the processor, causes the one or more processing units to perform the steps of the method as described in any one of claims 1-13.

18. A computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to perform the steps of the method according to any one of claims 1-13.

19. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the method as described in any one of claims 1-13.

Images