Landing page processing method and device, equipment and medium
Automatic floor query and API interface query are realized through API gateways, which solves the problem of insufficient flexibility in creating landing pages, and realizes efficient and flexible landing page management to adapt to frequently changing business needs.
Patent Information
- Application Number
- CN202510244834.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-03
- Publication Date
- 2025-06-20
Smart Images
Figure CN120179948A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of development technologies, and in particular, to a landing page processing method, apparatus, device, and medium. Background Art
[0002] A landing page (also known as a landing page or lead page) is a specific user interface (UI) designed specifically for clients such as applications or websites. For example, in the field of healthcare, there are specific pages designed for specific businesses, such as health consultation promotion pages, chronic disease management pages, and health assessment pages, aiming to guide users to complete specific conversion behaviors such as registration, purchase, or download. Through the landing page, more users can access the application or website, improving the conversion rate.
[0003] Currently, landing pages are usually developed in a hard-coded manner, where the logic for creating the landing page is directly written in the code. Once the landing page needs to be changed, such as updating or expanding the page content, invasive modifications need to be made to the existing code, lacking flexibility, maintainability, and timeliness, and it is difficult to adapt to the frequently changing business requirements.
[0004] Therefore, how to effectively improve the flexibility, maintainability, and timeliness of creating landing pages to adapt to the frequently changing business requirements has become a technical problem to be solved urgently. Summary of the Invention
[0005] The present invention provides an artificial intelligence-based landing page processing method, apparatus, computer device, and medium, aiming to effectively improve the flexibility, maintainability, and timeliness of creating landing pages to adapt to the frequently changing business requirements.
[0006] In a first aspect, a landing page processing method is provided, including:
[0007] In response to a landing page acquisition request, perform floor query processing on the landing page through an API gateway to obtain the floor of the landing page;
[0008] Perform API interface query processing on the floor through the API gateway to obtain the API interface of the floor;
[0009] Based on the API interface, obtain the required business data of the floor through the API gateway;
[0010] Fill and process the floor according to the required business data to obtain the landing page.
[0011] In a second aspect, a landing page processing apparatus is provided, including:
[0012] The floor query module is used to respond to the landing page acquisition request, perform floor query processing on the landing page through the API gateway, and obtain the floor of the landing page;
[0013] The interface query module is used to perform API interface query processing on the floor through the API gateway to obtain the API interface of the floor;
[0014] The data acquisition module is used to obtain the required service data of the floor through the API gateway based on the API interface;
[0015] The floor filling module is used to perform filling processing on the floor according to the required service data to obtain the landing page.
[0016] In a third aspect, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the above-mentioned landing page processing method are implemented.
[0017] In a fourth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above-mentioned landing page processing method are implemented.
[0018] In the solution implemented by the above-mentioned landing page processing method, device, computer device, and storage medium, in response to the landing page acquisition request, floor query processing is performed on the landing page through the API gateway to obtain the floor of the landing page; API interface query processing is performed on the floor through the API gateway to obtain the API interface of the floor; based on the API interface, the required service data of the floor is obtained through the API gateway; filling processing is performed on the floor according to the required service data to obtain the landing page. In the present invention, flexible and automated floor query and API interface query of the floor are realized through the API gateway, so as to quickly and accurately obtain the required service data to be displayed on the floor depending on the API interface. When the business requirements change, it is only necessary to adjust the API gateway without invasive modification of the existing code, and it is possible to quickly respond to the change of business requirements, switch and update the required service data to be displayed on the floor quickly and flexibly according to the actual business requirements, realize dynamic adjustment of the display content of the landing page, effectively improve the flexibility, maintainability, and timeliness of creating the landing page, and be able to adapt to frequently changing business requirements. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] To more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments of the present invention. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.
[0020] Figure 1 It is a schematic diagram of an application environment of the landing page processing method in an embodiment of the present invention;
[0021] Figure 2 It is a schematic flowchart of the landing page processing method in an embodiment of the present invention;
[0022] Figure 3 It is another schematic flowchart of the landing page processing method in an embodiment of the present invention;
[0023] Figure 4 It is a schematic structural diagram of the landing page processing device in an embodiment of the present invention;
[0024] Figure 5 It is a schematic structural diagram of a computer device in an embodiment of the present invention;
[0025] Figure 6 It is another schematic structural diagram of a computer device in an embodiment of the present invention. Specific embodiments
[0026] The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts fall within the protection scope of the present invention.
[0027] The landing page processing method provided by the embodiments of the present invention can be applied in, for example Figure 1In the application environment, the client communicates with the server through the network. The server can receive a landing page acquisition request through the client. In response to the landing page acquisition request, the server performs floor query processing on the landing page through the API gateway to obtain the floor of the landing page; performs API interface query processing on the floor through the API gateway to obtain the API interface of the floor; through the API gateway, obtains the required business data of the floor based on the API interface; and performs filling processing on the floor according to the required business data to obtain the landing page. In the present invention, flexible and automated floor query and API interface query of the floor are realized through the API gateway, so as to quickly and accurately obtain the required business data to be displayed on the floor depending on the API interface. When the business requirements change, it is only necessary to adjust the API gateway without invasive modification of the existing code, and it is possible to quickly respond to the change of business requirements, quickly and flexibly switch and update the required business data to be displayed on the floor according to the actual business requirements, realize dynamic adjustment of the display content of the landing page, effectively improve the flexibility, maintainability and timeliness of creating the landing page, and be able to adapt to the frequently changing business requirements. Among them, the client can be, but is not limited to, various personal computers, laptop computers, smart phones, tablet computers and portable wearable devices. The server can be implemented by an independent server or a server cluster composed of multiple servers. The present invention will be described in detail below through specific embodiments.
[0028] Please refer to Figure 2 as shown in Figure 2 a flowchart of a landing page processing method provided by an embodiment of the present invention, Figure 2 and the method in
[0029] S10: In response to a landing page acquisition request, determine the floor of the landing page through the API gateway.
[0030] The landing page processing method provided by the present invention can be applied to a content management system (CMS) in various application scenarios, and the content management system is usually implemented through a server. For example, in the medical and health business application scenario, a user can request the server through the client to obtain a landing page in the medical and health field created by the content management system, such as a medical product discount activity page, a member health consultation preferential activity page, a chronic disease management page, a health assessment page, a medical clinical trial subscription page and other medical and health management pages; in the financial business application scenario, a user can request the server through the client to obtain a landing page in the financial field created by the content management system, such as a financial insurance product introduction page, a financial insurance product claim settlement process page, a financial insurance product recommendation page, etc.
[0031] Since the logic of creating a landing page in the hard - coding method is to directly call the underlying interface to obtain relevant business data for creating the landing page, and this logic is directly written in the code. Once the underlying interface changes or the business data is updated, iterated, and expanded, it is necessary to invasively modify the existing code and republish it. To solve the problems of insufficient flexibility, poor maintainability, and timeliness brought by the hard - coding method, the present invention introduces an API Gateway to shield the details of the underlying interface, so that the content management system does not need to be coupled with the underlying interface, and can support dynamically adjusting the display content of the landing page according to actual business needs without modifying the existing code. Thus, while ensuring the flexibility of creating the landing page, the maintainability and response speed are improved, and the ability to quickly respond to frequently changing business needs is realized.
[0032] For ease of understanding, first, several terms related to the present invention are explained:
[0033] Floor: A floor is the basic unit that constitutes a landing page. As a stackable and dynamically loadable unit, it allows flexibly configuring information such as its data source according to actual business needs to display the required business data provided by the specified data source for the floor. It can be understood that a landing page can include one floor or multiple floors. For example, one floor is used to display medical product list data, another floor is used to display medical product order data, and yet another floor is used to display user comment data, etc. The required business data can be provided by a Data Model, and the data structure of the Data Model conforms to the data structure required for floor display, so that the required business data can be directly embedded into the floor and directly used by the floor.
[0034] API Gateway: It is a server - side middleware, such as the ShenYu gateway. As a bridge between the client and the server, it is used to centrally manage and process landing page acquisition requests. It acts as the only entry point for the content management system, encapsulating the acquisition channels of the data sources of the floors, thus supporting flexibly selecting and switching the data sources of the floors at any time according to actual business needs without modifying the existing code, and realizing the quick switching and adjustment of the display content of the landing page.
[0035] Based on this, the following details the landing page processing method provided by the present invention.
[0036] Please refer to Figure 2 , before step S10 of some embodiments, steps S50 to S60 may also be included.
[0037] S50: Obtain the configuration file of the floor.
[0038] S60: Based on the configuration file, configure the API interface of the floor and the SQL of the API interface in the API Gateway.
[0039] You can obtain the floor configuration file customized by the developer according to the actual business needs, so that the API gateway can generate and configure the API interface for the floor based on the floor configuration file. The floor API interface is used to provide the API gateway with the floor's required business data. The API gateway also generates and configures SQL for the floor's API interface, which is used to obtain the floor's required business data from the specified data source.
[0040] In this way, the acquisition channel of the floor's data source is encapsulated in the API gateway, so that the API gateway supports centralized management of the floor's API interface and the SQL of the API interface, and realizes complete decoupling between the content management system and the floor's API interface.
[0041] In step S60 of some embodiments, the configuration file includes the API generation parameters of the floor, the data source of the demand business data of the floor, and the query parameters of the demand business data. The API interface of the floor can be configured in the API gateway according to the API generation parameters; and SQL can be configured in the API gateway according to the data source and query parameters.
[0042] The API generation parameters clearly specify the basic properties and access methods of the API interface. The API generation parameters may include but are not limited to:
[0043] API name: the name of the API interface, used to identify and describe the API interface;
[0044] API group: The group to which the API interface belongs, used to organize and classify the API interface;
[0045] API path: the access path of the API interface;
[0046] API protocol: specifies the communication protocol used by the API interface, such as HTTP, HTTPS, etc.
[0047] Request method: specifies the method by which the client initiates the request, such as GET, POST, PUT, DELETE, etc.
[0048] Return type: the data format returned by the API interface, such as JSON, XML, etc.
[0049] Description: A brief description of the API interface function;
[0050] API tags: tags that can be added to API interfaces to mark and categorize API interfaces for easier management.
[0051] API authentication: whether authentication is required to access the interface, such as OAuth authentication, API Key, etc.
[0052] Thus, the API gateway can generate parameters based on the API and generate and configure the API interfaces for the floors. For example, at the API gateway, API interface 1 is generated and configured for floor 1, and API interface 2 is generated and configured for floor 2.
[0053] Among them, the data sources of the demand business data of the floors can be different databases, such as MySQL, Doris, Hive, etc. used to store the demand business data of the floors. The data sources of the demand business data of the floors clearly specify which database to query and obtain the demand business data of the floors from.
[0054] The query parameters of the demand business data clearly specify the query logic of the demand business data, which can be the specific fields for querying the demand business data, such as chronic disease types (such as diabetes, hypertension), patient age groups (such as 18 - 35 years old, 36 - 55 years old, over 56 years old), chronic disease management plan types (such as daily monitoring, long-term drug treatment, diet guidance, psychological support), health consultation types (such as internal medicine, surgery, mental health, nutrition consultation), the name, price, inventory, etc. of medical products; the query parameters of the demand business data can also be the specific conditions for querying the demand business data, such as filtering by the category of medical products, time range, etc., filtering by the available health consultation service scope (such as online consultation, phone consultation, in-person consultation), etc.
[0055] In this way, the API gateway can generate and configure SQL for the API interfaces of the floors according to the data sources of the demand business data of the floors and the query parameters of the demand business data, ensuring that when the API interfaces of the floors are called, the configured SQL will be automatically executed. For example, SQL1 is generated for API interface 1 of floor 1 to obtain medical product data from MySQL, and SQL2 is generated for the API interface of floor 2 to obtain user comment data from Hive.
[0056] It should be noted that the API gateway also supports the use of dynamic input parameters in SQL, that is, the query logic for the required business data can change dynamically according to the dynamic query parameters passed in the landing page acquisition request. For example, if the landing page acquisition request initiated by the user on the client is assumed to be a chronic disease management page acquisition request, and the dynamic query parameter passed in this request is diabetes in the chronic disease type, the SQL can be adjusted through the dynamic query parameter to obtain the diabetes management detail data that meets the dynamic query parameter. The diabetes management detail data includes, for example, blood glucose monitoring data (such as fasting blood glucose, postprandial blood glucose, glycated hemoglobin, and blood glucose monitoring time), drug management data (such as drug name, drug dose), the risk level of the patient's diabetes control (such as low, medium, high risk), and follow-up and diabetes management plans (such as the date of the next follow-up, diet management plan, exercise plan, drug adjustment plan), etc.
[0057] In this way, flexibly configuring the API interfaces of the floors and the SQL of the API interfaces in the API gateway according to the actual business requirements can support the timely realization of dynamic switching and updating of the data sources of the floors without modifying the existing code.
[0058] After step S60 of some embodiments, the API interfaces and SQL can also be debugged through the API gateway.
[0059] To ensure that the API interfaces of the floors are correctly called, the API gateway can debug the API interfaces. Specifically, it can determine whether the API interfaces can correctly return the required business data of the floors required for debugging. When the API interfaces can correctly return the required business data of the floors required for debugging, it is determined that the API interfaces pass the debugging and the API interfaces become effective, indicating that the API interfaces can be officially called by the API gateway.
[0060] Through the above method, the content management system can flexibly manage the landing pages, floors, and data sources. In this way, when the business requirements change, only a simple adjustment to the API gateway is required to achieve the switching and updating of the data sources and business data, avoiding invasive modification of the existing code and greatly improving the maintainability.
[0061] Based on this, the user can click on the text, icon, picture, or uniform resource locator (URL) of the hyperlink on the client to trigger the landing page acquisition request. The server can receive the landing page acquisition request triggered by the user on the client in real time, and in response to the landing page acquisition request, determine the floor of the landing page through the API gateway.
[0062] In step S10 of some embodiments, the floor parsing process can be performed on the pre-stored configuration information of the landing page in the API gateway to obtain the floor.
[0063] Among them, the configuration information of the landing page custom-written by developers according to actual business requirements can be obtained in advance. The configuration information of the landing page clearly specifies which floors the landing page includes. The configuration information of the landing page is pre-stored in the API gateway.
[0064] In this way, in response to the landing page acquisition request, through the API gateway, the floor parsing process can be performed on the pre-stored configuration information of the landing page, and the floors of the landing page can be obtained quickly and accurately. For example:
[0065] Suppose the requested landing page is a health assessment page, which includes Floor 1 (Health assessment item display area, used to display health assessment items, such as physical health assessment, mental health assessment, nutritional assessment), Floor 2 (Health assessment time display area, used to display the date or cycle of health assessment, such as quarterly assessment, annual assessment), Floor 3 (User health assessment result display area, used to display the user's basic information and health risk level), and Floor 4 (Health management recommended plan display area, used to display personalized health management plans recommended according to the user's health assessment results), etc.
[0066] Suppose the requested landing page is a medical clinical trial subscription page, which includes Floor 1 (Clinical trial type display area, used to display clinical trial types, such as drug trials, device trials, vaccine trials), Floor 2 (Clinical trial phase display area, used to display clinical trial phases, such as Phase I, Phase II, Phase III), Floor 3 (Clinical trial indication display area, used to display clinical trial indications, such as cancer, hypertension, heart disease, etc.), Floor 4 (Clinical trial area display area, used to display the geographical area where the clinical trial is located, such as a certain city or country), Floor 5 (Registration time display area, used to display the start and end times of the clinical trial), Floor 6 (Clinical trial subject recruitment condition display area, used to display the specific conditions that the subjects who can participate in the clinical trial need to meet), and Floor 7 (Recruitment status display area, used to display the recruitment status, such as whether recruitment is in progress, full, or on hold).
[0067] Suppose the requested landing page is a medical product discount activity page, which includes Floor 1 (Medical product display area, used to display a list of medical products), Floor 2 (User review display area, used to display user reviews), and Floor 3 (Medical product recommendation display area, used to display recommended related medical products).
[0068] S20: Perform API interface query processing on the floors through the API gateway to obtain the API interfaces of the floors.
[0069] The API interfaces pre-configured for the floors can be quickly queried in the API gateway.
[0070] S30: Obtain the required business data of the floor based on the API interface through the API gateway.
[0071] It is possible to quickly and accurately obtain the required business data of the floor based on the API interface of the floor in the API gateway. For example, the health assessment items required for Floor 1 of the health assessment page, the health assessment time required for Floor 2, the user health assessment results required for Floor 3, and the health management recommendation plan required for Floor 4; the clinical trial types required for Floor 1 of the medical clinical trial subscription page, the clinical trial phases required for Floor 2, the clinical trial indications required for Floor 3, the clinical trial regions required for Floor 4, the registration time required for Floor 5, the recruitment conditions for clinical trial subjects required for Floor 6, and the recruitment status required for Floor 7; the list of medical products required for Floor 1 of the medical product discount activity page, the user review content required for Floor 2, and the list of medical product recommendations required for Floor 3.
[0072] In step S30 of some embodiments, the API gateway can perform SQL query processing on the API interface to obtain SQL; through the API gateway, call the API interface to execute SQL to obtain the required business data from the data source.
[0073] It is possible to quickly query and obtain the SQL pre-configured for the API interface of the floor in the API gateway.
[0074] It is possible to perform parameter parsing processing on the landing page acquisition request. When the landing page acquisition request does not pass dynamic query parameters, the API gateway can call the API interface of the floor to directly and automatically execute the SQL associated with the API interface, quickly and accurately obtaining the required business data of the floor.
[0075] In this way, the API gateway exposes the required business data to be displayed on the floor through the API interface, enabling the content management system not to directly contact the API interface, realizing decoupling between the content management system and the API interface, and thus being able to flexibly and dynamically adjust the required business data to be displayed on the floor according to actual business needs without modifying the existing code.
[0076] In some embodiments, after performing SQL query processing on the API interface through the API gateway to obtain SQL, it is also possible to perform parameter parsing processing on the landing page acquisition request through the API gateway to obtain the dynamic query parameters passed by the landing page acquisition request; through the API gateway, adjust the SQL according to the dynamic query parameters to obtain the adjusted SQL; through the API gateway, call the API interface to execute the adjusted SQL to obtain the required business data from the data source.
[0077] Parameter parsing and processing can be performed on the landing page acquisition request. When the landing page acquisition request passes dynamic query parameters, the API gateway can adjust the SQL according to the dynamic query parameters to obtain the adjusted SQL, and then call the API interface of the floor to automatically execute the adjusted SQL to obtain the business data that meets the requirements of the adjusted SQL.
[0078] For example, the query parameter corresponding to the SQL of the API interface is the category of medical products, and the dynamic query parameter passed by the landing page acquisition request is the price range of medical products. The price range of medical products can be added to the SQL of the API interface. In this way, when the API gateway calls the API interface of the floor to automatically execute the adjusted SQL, it can obtain the medical product data that meets the "category of medical products + price range".
[0079] In this way, by dynamically adjusting the API gateway, it is possible to flexibly and dynamically adjust the business data to be displayed on the floor according to the actual business requirements based on the API gateway.
[0080] S40: Fill and process the floor according to the business data required to obtain the landing page.
[0081] The business data required can be filled into the floor to obtain the landing page. For example:
[0082] Floor 1 is the display area for health assessment items. Fill the health assessment items required for Floor 1 into Floor 1; Floor 2 is the display area for health assessment time. Fill the health assessment time required for Floor 2 into Floor 2; Floor 3 is the display area for the user's health assessment results. Fill the basic information and health risk level of the users required for Floor 3 into Floor 3; Floor 4 is the display area for health management recommended solutions. Fill the health management recommended solutions required for Floor 4 into Floor 4, thus obtaining the health assessment page.
[0083] Floor 1 is the display area for clinical trial types. Fill the clinical trial types required for Floor 1 into Floor 1; Floor 2 is the display area for clinical trial phases. Fill the clinical trial phases required for Floor 2 into Floor 2; Floor 3 is the display area for clinical trial indications. Fill the clinical trial indications required for Floor 3 into Floor 3; Floor 4 is the display area for clinical trial regions. Fill the geographical regions where the clinical trials are located required for Floor 4 into Floor 4; Floor 5 is the display area for registration time. Fill the start and end times of the clinical trials required for Floor 5 into Floor 5; Floor 6 is the display area for the recruitment conditions of clinical trial subjects. Fill the specific conditions that the subjects who can participate in the clinical trials need to meet required for Floor 6 into Floor 6; Floor 7 is the display area for the recruitment status floor. Fill the recruitment status required for Floor 7 into Floor 7, thus obtaining the medical clinical trial subscription page.
[0084] Floor 1 is the medical product display area, and the list of medical products required for Floor 1 is filled into Floor 1; Floor 2 is the user comment area, and the user comment content required for Floor 2 is filled into Floor 2; Floor 3 is the recommended medical product display area, and the recommended medical products required for Floor 3 are filled into Floor 3, thus obtaining the medical product discount activity page.
[0085] Finally, the landing page is returned to the client for the client to render the landing page for users to view, improving the accuracy of customizing dynamic landing pages for different users and facilitating increasing user stickiness.
[0086] It can be seen that in the above solution, by centrally configuring and managing the API interfaces of the floors and the SQL of the API interfaces through the API gateway, on the one hand, it is possible to dynamically obtain the accurate demand business data of the floors, realize the dynamic adjustment of the display content of the landing page, improve the flexibility of creating the landing page, and facilitate coping with frequently changing business requirements; on the other hand, when the business requirements change, only a simple adjustment to the configuration of the API gateway is required to achieve the switching and updating of the data source and business data, avoiding invasive modification of the existing code, and greatly improving the maintainability; on the one hand, relying on the API interface to obtain the demand business data of the floors not only simplifies and standardizes the process of obtaining the demand business data, but also improves the reliability and response speed of the content management system in creating the landing page, and reduces the complexity of updating the landing page.
[0087] The landing page processing method provided in the above embodiment, in response to a landing page acquisition request, performs floor query processing on the landing page through the API gateway to obtain the floors of the landing page; performs API interface query processing on the floors through the API gateway to obtain the API interfaces of the floors; through the API gateway, obtains the demand business data of the floors based on the API interfaces; performs filling processing on the floors according to the demand business data to obtain the landing page. In this way, through the API gateway, flexible and automated floor query and API interface query of the floors are realized, so as to quickly and accurately obtain the demand business data to be displayed on the floors depending on the API interface, facilitating only adjusting the API gateway when the business requirements change, without invasive modification of the existing code, being able to quickly respond to changes in business requirements, quickly and flexibly switch and update the demand business data to be displayed on the floors according to the actual business requirements, realize the dynamic adjustment of the display content of the landing page, and effectively improve the flexibility, maintainability and timeliness of creating the landing page, and can adapt to frequently changing business requirements.
[0088] It should be understood that the magnitudes of the sequence numbers of the steps in the above embodiments do not mean the order of execution is prior or posterior, and the execution order of each process should be determined according to its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
[0089] In one embodiment, a landing page processing device is provided, which corresponds one-to-one with the landing page processing method in the above embodiment. As Figure 4 shown, the landing page processing device includes a floor query module 101, an interface query module 102, a data acquisition module 103, and a floor filling module 104. The detailed description of each functional module is as follows:
[0090] The floor query module 101 is configured to, in response to a landing page acquisition request, perform floor query processing on the landing page through an API gateway to obtain the floors of the landing page;
[0091] The interface query module 102 is configured to perform API interface query processing on the floor through the API gateway to obtain the API interfaces of the floor;
[0092] The data acquisition module 103 is configured to, through the API gateway, obtain the required service data of the floor based on the API interface;
[0093] The floor filling module 104 is configured to perform filling processing on the floor according to the required service data to obtain the landing page.
[0094] In one embodiment, the landing page processing device further includes a floor configuration module, and the floor configuration module is configured to:
[0095] Obtain the configuration file of the floor;
[0096] Based on the configuration file, configure the API interface of the floor and the SQL of the API interface in the API gateway.
[0097] In one embodiment, the configuration file includes the API generation parameters of the floor, the data source of the required service data of the floor, and the query parameters of the required service data. The floor configuration module is specifically configured to:
[0098] Configure the API interface of the floor in the API gateway according to the API generation parameters;
[0099] Configure the SQL in the API gateway according to the data source and the query parameters.
[0100] In one embodiment, the floor configuration module is further configured to:
[0101] Debug the API interface through the API gateway.
[0102] In one embodiment, the data acquisition module 103 is specifically configured to:
[0103] Perform SQL query processing on the API interface through the API gateway to obtain the SQL;
[0104] Through the API gateway, the API interface is called to execute the SQL to obtain the required service data from the data source.
[0105] In one embodiment, the data acquisition module 103 is further configured to:
[0106] Perform parameter parsing processing on the landing page acquisition request through the API gateway to obtain the dynamic query parameters passed by the landing page acquisition request;
[0107] Through the API gateway, adjust the SQL according to the dynamic query parameters to obtain an adjusted SQL;
[0108] Through the API gateway, call the API interface to execute the adjusted SQL to obtain the required service data from the data source.
[0109] In one embodiment, the floor query module 101 is specifically configured to:
[0110] Perform floor parsing processing on the pre-stored configuration information of the landing page in the API gateway to obtain the floor.
[0111] The present invention provides a landing page processing device, which realizes flexible and automated floor query and query of the API interface of the floor through the API gateway, so as to quickly and accurately obtain the required service data to be displayed on the floor depending on the API interface. When the business requirements change, it is only necessary to adjust the API gateway without invasive modification of the existing code, and it can quickly respond to the change of business requirements, quickly and flexibly switch and update the required service data to be displayed on the floor according to the actual business requirements, realize dynamic adjustment of the display content of the landing page, effectively improve the flexibility, maintainability and timeliness of creating the landing page, and can adapt to the frequently changing business requirements.
[0112] For the specific limitations on the landing page processing device, reference can be made to the limitations on the intelligent question answering method in the above text, which will not be elaborated here. Each module in the above landing page processing device can be implemented in whole or in part by software, hardware and their combination. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.
[0113] In one embodiment, a computer device is provided. The computer device can be a server, and its internal structure diagram can be as Figure 5As shown in the figure. The computer device includes a processor, a memory, a network interface, and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile and / or volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external client through a network connection. When the computer program is executed by the processor, it realizes the functions or steps on the server side of a landing page processing method.
[0114] In one embodiment, a computer device is provided. The computer device can be a client, and its internal structure diagram can be as Figure 6 shown in the figure. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external server through a network connection. When the computer program is executed by the processor, it realizes the functions or steps on the client side of a landing page processing method
[0115] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the following steps are implemented:
[0116] In response to a landing page acquisition request, perform floor query processing on the landing page through an API gateway to obtain the floor of the landing page;
[0117] Perform API interface query processing on the floor through the API gateway to obtain the API interface of the floor;
[0118] Through the API gateway, obtain the required service data of the floor based on the API interface;
[0119] Perform filling processing on the floor according to the required service data to obtain the landing page.
[0120] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:
[0121] In response to the landing page acquisition request, the floor of the landing page is obtained by performing floor query processing on the landing page through the API gateway;
[0122] The API interface of the floor is obtained by performing API interface query processing on the floor through the API gateway;
[0123] Based on the API interface, the required service data of the floor is obtained through the API gateway;
[0124] The floor is filled according to the required service data to obtain the landing page.
[0125] It should be noted that for the functions or steps that can be achieved by the above computer-readable storage medium or computer device, reference can be made to the relevant descriptions on the server side and the client side in the foregoing method embodiments. To avoid repetition, they will not be described in detail here.
[0126] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the above method embodiments. Among them, any reference to a memory, storage, database, or other medium used in the various embodiments provided in the present application can include non-volatile and / or volatile memories. Non-volatile memories can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memories can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.
[0127] Those skilled in the art can clearly understand that for the convenience and brevity of description, only the above division of each functional unit and module is used as an example. In actual applications, the above functions can be allocated to different functional units and modules according to needs, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above.
[0128] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention, and should all be included within the protection scope of the present invention.
Claims
1. A landing page processing method, characterized in that: include: In response to the landing page acquisition request, the floor query processing of the landing page is performed through the API gateway to obtain the floor of the landing page; Performing API interface query processing on the floor through the API gateway to obtain the API interface of the floor; Obtaining demand business data of the floor based on the API interface through the API gateway; The floor is filled in according to the demand business data to obtain the landing page.
2. The landing page processing method according to claim 1, characterized in that: In response to the landing page acquisition request, performing floor query processing on the landing page through the API gateway to obtain the floor of the landing page also includes: Obtaining a configuration file of the floor; Based on the configuration file, the API interface of the floor and the SQL of the API interface are configured in the API gateway.
3. The landing page processing method according to claim 2, characterized in that: The configuration file includes the API generation parameters of the floor, the data source of the demand business data of the floor, and the query parameters of the demand business data. The configuration of the API interface of the floor and the SQL of the API interface in the API gateway based on the configuration file includes: According to the API generation parameters, the API interface of the floor is configured in the API gateway; The SQL is configured in the API gateway according to the data source and the query parameters.
4. The landing page processing method according to claim 2, characterized in that: The configuration file further includes: after the API gateway configures the API interface of the floor and the SQL of the API interface. The API interface is debugged through the API gateway.
5. The landing page processing method according to claim 3, characterized in that: The acquiring the demand business data of the floor based on the API interface through the API gateway includes: Perform SQL query processing on the API interface through the API gateway to obtain the SQL; Through the API gateway, the API interface is called to execute the SQL to obtain the required business data from the data source.
6. The landing page processing method according to claim 3, characterized in that: After performing SQL query processing on the API interface through the API gateway to obtain the SQL, the method further includes: Perform parameter parsing on the landing page acquisition request through the API gateway to obtain dynamic query parameters passed by the landing page acquisition request; By means of the API gateway, the SQL is adjusted according to the dynamic query parameters to obtain an adjusted SQL; Through the API gateway, the API interface is called to execute the adjusted SQL to obtain the required business data from the data source.
7. The landing page processing method according to any one of claims 1 to 6, characterized in that: The step of performing floor query processing on the landing page through the API gateway to obtain the floor of the landing page includes: At the API gateway, the pre-stored configuration information of the landing page is parsed and processed for the floor to obtain the floor.
8. A landing page processing device, characterized in that: include: The floor query module is used to respond to the landing page acquisition request, perform floor query processing on the landing page through the API gateway, and obtain the floor of the landing page; An interface query module, used to perform API interface query processing on the floor through the API gateway to obtain the API interface of the floor; A data acquisition module, used to acquire the demand business data of the floor based on the API interface through the API gateway; The floor filling module is used to fill the floor according to the required business data to obtain the landing page.
9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the landing page processing method as described in any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the landing page processing method as described in any one of claims 1 to 7 are implemented.