Page query method and device
By configuring information to determine the header data, content data, and paging data, the problem of difficult iterative maintenance of the asset securitization settlement query page is solved, and more efficient page maintenance is achieved.
Patent Information
- Application Number
- CN202011603526.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-12-29
- Publication Date
- 2025-09-16
- Estimated Expiration
- 2040-12-29
Smart Images

Figure CN114691764B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of information technology, and in particular to a page query method and device. Background Art
[0002] Asset-backed securitization (ABS) settlement refers to a settlement method based on the assets owned by the project and guaranteed by the expected returns that the project assets can bring. ABS settlement usually includes various business types such as repayment business, investment business, guarantee agency business, procurement business, etc.
[0003] In related technologies, because ABS settlement encompasses multiple business types, each new business type requires the addition of new code corresponding to that business type's business logic. This often requires a large amount of backend code to support the differences between different business types on the same page, making iterative maintenance of the query page difficult. Summary of the Invention
[0004] The embodiments of the present application provide a page query method and device, which can solve the problem of difficult iterative maintenance of query pages in the prior art.
[0005] In a first aspect, an embodiment of the present application provides a page query method, applied to a server, the method comprising:
[0006] Receive a request to obtain header data, content data, and page data of the page to be queried;
[0007] Determining the header configuration data of the page to be queried from a database according to the first query parameter in the header data acquisition request;
[0008] Determining, based on the second query parameter in the content data acquisition request, a first data service corresponding to the content data of the page to be queried, and determining, based on the third query parameter in the page data acquisition request, a second data service corresponding to the page data of the page to be queried;
[0009] determining the content data according to the first data service, and determining the paging data according to the second data service;
[0010] The page to be queried is generated according to the content data, the paging data and the header configuration data.
[0011] In an optional embodiment, the server further includes a background interface layer and a background routing configuration layer, and the method further includes:
[0012] Controlling the background interface layer to encapsulate the first query parameter, the second query parameter, and the third query parameter according to the interface parameter format of the background routing configuration layer;
[0013] The background interface layer is controlled to send the encapsulated first query parameter, the encapsulated second query parameter, and the encapsulated third query parameter to the background routing configuration layer.
[0014] In an optional implementation, before controlling the background interface layer to send the encapsulated first query parameter, the encapsulated second query parameter, and the encapsulated third query parameter to the background routing configuration layer, the method further includes:
[0015] The background interface layer is controlled to perform data mapping on the second query parameter according to the query parameter configuration information, wherein the data mapping is used to map the second query parameter into a parameter recognizable by the background data layer in the server.
[0016] In an optional implementation, determining the first data service corresponding to the content data of the page to be queried according to the second query parameter in the content data acquisition request includes:
[0017] controlling the background routing configuration layer to determine the service configuration information of the content data according to the second query parameter;
[0018] The background routing configuration layer is controlled to determine the first data service corresponding to the content data from the service management library of the server according to the service configuration information of the content data.
[0019] In an optional implementation manner, determining the content data according to the first data service includes:
[0020] Controlling the background routing configuration layer to send information of the first data service to the background data layer through the interface of the first data service;
[0021] The background data layer is controlled to determine the content data according to the information of the first data service.
[0022] In an optional implementation, after controlling the background data layer to determine the content data according to the information of the first data service, the method further includes:
[0023] Controlling the background data layer to send the content data to the background routing configuration layer;
[0024] The backend routing configuration layer is controlled to convert the format of the content data according to the data display rules of the front-end view layer of the server.
[0025] In an optional implementation, determining the second data service corresponding to the paging data of the page to be queried according to the third query parameter in the paging data acquisition request includes:
[0026] Controlling the background routing configuration layer to determine the service configuration information of the paging data according to the third query parameter;
[0027] The background routing configuration layer is controlled to determine the second data service corresponding to the paging data from the service management library of the server according to the service configuration information of the paging data.
[0028] In an optional implementation, determining the paging data according to the second data service includes:
[0029] Controlling the background routing configuration layer to send information of the second data service to the background data layer through the interface of the second data service;
[0030] The background data layer is controlled to determine the paging data according to the information of the second data service.
[0031] In an optional implementation, the service configuration information includes table information corresponding to the content data, an alias of the data service, and a service type corresponding to the table information.
[0032] In an optional embodiment, the server further includes a front-end view layer; generating the page to be queried according to the content data, the paging data, and the header configuration data includes:
[0033] The front-end view layer is controlled to fill the content data, the paging data and the header configuration data into a page template to generate the page to be queried.
[0034] In an optional implementation, the header configuration data includes service type data, display sequence data, header name data, and layout rule data.
[0035] In a second aspect, an embodiment of the present application provides a page query device, comprising:
[0036] A view module, configured to receive a request for obtaining header data, content data, and paging data of a page to be queried; and generate the page to be queried based on the content data, the paging data, and the header configuration data;
[0037] a routing module configured to determine, from a database, header configuration data of the page to be queried based on a first query parameter in the header data acquisition request; determine, based on a second query parameter in the content data acquisition request, a first data service corresponding to the content data of the page to be queried; and determine, based on a third query parameter in the paging data acquisition request, a second data service corresponding to the paging data of the page to be queried;
[0038] The data module is configured to determine the content data according to a first data service corresponding to the content data, and to determine the paging data according to a second data service corresponding to the paging data.
[0039] In an optional embodiment, the page query device further includes an interface module;
[0040] The interface module is used to encapsulate the first query parameter, the second query parameter, and the third query parameter according to the interface parameter format of the background routing configuration layer; and send the encapsulated first query parameter, the encapsulated second query parameter, and the encapsulated third query parameter to the background routing configuration layer.
[0041] In an optional implementation, the interface module is further configured to perform data mapping on the second query parameter according to the query parameter configuration information, wherein the data mapping is configured to map the second query parameter into a parameter recognizable by a data module in the server.
[0042] In an optional implementation, the routing module is specifically configured to determine service configuration information of the content data based on the second query parameter; and determine the first data service corresponding to the content data from the service management library of the server based on the service configuration information of the content data.
[0043] In an optional implementation, the routing module is specifically configured to send the information of the first data service to the data module through an interface of the first data service;
[0044] The data module is specifically configured to determine the content data according to the information of the first data service.
[0045] In an optional implementation, the data module is further configured to send the content data to the routing module;
[0046] The routing module is further configured to convert the format of the content data according to the data display rules of the front-end view layer of the server.
[0047] In an optional embodiment, the routing module is specifically used to determine the service configuration information of the paging data based on the third query parameter; and determine the second data service corresponding to the paging data from the service management library of the server based on the service configuration information of the paging data.
[0048] In an optional implementation, the routing module is specifically configured to send the information of the second data service to the data layer module through the interface of the second data service;
[0049] The data module is specifically configured to determine the paging data according to the information of the second data service.
[0050] In an optional implementation, the service configuration information includes table information corresponding to the content data, an alias of the data service, and a service type corresponding to the table information.
[0051] In an optional implementation, the view module is specifically configured to fill the content data, the paging data, and the header configuration data into a page template to generate the page to be queried.
[0052] In an optional implementation, the header configuration data includes service type data, display sequence data, header name data, and layout rule data.
[0053] According to a third aspect, a computer program product comprises computer instructions, which, when executed by a processor, implement the method described in any one of the first aspects.
[0054] In a fourth aspect, an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.
[0055] In a fifth aspect, an embodiment of the present application provides an electronic device, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.
[0056] The page query method and device provided by the embodiment of the present application receive a header data acquisition request, a content data acquisition request, and a paging data acquisition request of a page to be queried; determine the header configuration data of the page to be queried from a database according to the first query parameter in the header data acquisition request; determine the data service corresponding to the content data of the page to be queried according to the second query parameter in the content data acquisition request, and determine the data service corresponding to the paging data of the page to be queried according to the third query parameter in the paging data acquisition request; determine the content data according to the data service corresponding to the content data, and determine the paging data according to the data service corresponding to the paging data; generate the page to be queried according to the content data, the paging data, and the header configuration data. In this way, the configuration data, content data, and paging data of the header data can be determined separately. When iterative maintenance is performed, only the configuration information of the header data and the data services of the content data and paging data need to be updated, without changing the specific data, thereby reducing the difficulty of iterative maintenance of the query page. BRIEF DESCRIPTION OF THE DRAWINGS
[0057] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0058] Figure 1 An application scenario provided for the embodiments of the present application is a schematic diagram;
[0059] Figure 2 A signaling interaction diagram of a page query method provided in an embodiment of the present application;
[0060] Figure 3 Another signaling interaction diagram for page query provided in an embodiment of the present application;
[0061] Figure 4 A signaling interaction diagram for another page query provided in an embodiment of the present application;
[0062] Figure 5 A schematic diagram of a page query process provided in an embodiment of the present application;
[0063] Figure 6 A schematic diagram of the structure of a page query device provided in an embodiment of the present application;
[0064] Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0065] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.
[0066] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts shall fall within the scope of protection of the present invention.
[0067] The terms "first," "second," and the like in the description and claims of the present invention and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, such that the embodiments of the present invention described herein can be practiced in orders other than those illustrated or described herein.
[0068] It should be understood that in various embodiments of the present invention, the size of the sequence number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.
[0069] It should be understood that in the present invention, "include" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products or apparatuses.
[0070] It should be understood that, in the present invention, "B corresponding to A," "A corresponds to B," or "B corresponds to A" means that B is associated with A and B can be determined based on A. Determining B based on A does not mean determining B based solely on A; B can also be determined based on A and / or other information.
[0071] Depending on the context, "if" as used herein may be interpreted as "at the time" or "when" or "in response to a determination."
[0072] Asset-backed securitization (ABS) settlement refers to a settlement method based on the assets owned by the project and guaranteed by the expected returns that the project assets can bring. ABS settlement usually includes various business types such as repayment business, investment business, guarantee agency business, procurement business, etc.
[0073] In related technologies, because ABS settlement encompasses multiple business types, each new business type requires the addition of new code corresponding to that business type's business logic. This often requires a large amount of backend code to support the differences between different business types on the same page, making iterative maintenance of the query page difficult.
[0074] To address the above-mentioned issues, embodiments of the present application provide a page query method and apparatus to solve the problem of difficult iterative maintenance of query pages in the prior art. In embodiments of the present application, configuration information is used to separately determine the configuration data, content data, and paging data of the header data. In this manner, when performing iterative maintenance, only the data services for the configuration data, content data, and paging data of the header data in the routing module need to be modified, without requiring changes to the specific data, thereby reducing the difficulty of iterative maintenance of the query page.
[0075] The application scenarios of the embodiments of the present application are described below.
[0076] Figure 1 An application scenario provided for the embodiment of the present application is a schematic diagram, such as Figure 1 As shown, the application scenario of the embodiment of the present application includes a terminal device 101 and a server 102. When a user needs to query a certain query page, the terminal device 101 can send a query request to the server 102. After receiving the query request sent by the terminal device 101, the server 102 can generate a specific query page through the view module, routing module, and data module in the server, and send the query page to the terminal device 101.
[0077] Among them, the terminal device 101 can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in a smart home, etc. In the embodiment of the present application, the device for realizing the function of the terminal can be a terminal, or a device that can support the terminal to realize the function, such as a chip system, which can be installed in the terminal. In the embodiment of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.
[0078] The server 102 may be, but is not limited to, a single network server, a server group consisting of multiple network servers, or a cloud based on cloud computing consisting of a large number of computers or network servers. Cloud computing is a type of distributed computing, a super virtual computer composed of a group of loosely coupled computers.
[0079] It should be noted that the application scenario of the technical solution of this application can be Figure 1 The application scenario is not limited to this, and can also be applied to other scenarios that require page query.
[0080] It can be understood that the above-mentioned page query method can be implemented by the page query device provided in the embodiment of the present application, and the page query method can be part or all of a certain device, for example, the above-mentioned server 102 or the processor in the server 102.
[0081] The following uses a server integrated with or installed with relevant execution code as an example to describe the technical solutions of the embodiments of the present application in detail with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.
[0082] Figure 2 This is a signaling interaction diagram of a page query method provided in an embodiment of the present application. Figure 2 The execution subject of the query method is a server, which includes a front-end view layer, a back-end routing layer, and a back-end data layer. The embodiment of the present application relates to the specific process of how the server generates a query page. The page query method mainly includes steps S201 to S208, which are as follows:
[0083] S201. The front-end view layer sends a header data acquisition request, a content data acquisition request, and a paging data acquisition request of a page to be queried to the back-end routing layer.
[0084] In this application, when the server receives a page query request sent by the terminal device through the front-end view layer, it can send a header data acquisition request, a content data acquisition request, and a paging data acquisition request of the page to be queried to the routing module based on the identifier of the page to be queried in the page query request.
[0085] In some embodiments, the query page can be generated by the header, content data, and paging data. The header, content data, and paging data are not fixed and will change dynamically according to the configuration in the routing module root. Therefore, when generating the query page, it is necessary to obtain each of them through a get request.
[0086] The embodiments of the present application do not restrict how the front-end view layer sends a request to obtain header data, content data, and paging data for the page to be queried to the back-end routing layer. In some embodiments, the server further includes a back-end interface layer. The front-end view layer may first send a request to obtain header data, content data, and paging data to the back-end interface layer. Subsequently, the back-end interface layer sends the request to obtain header data, content data, and paging data to the back-end routing layer through corresponding interfaces.
[0087] The interface in the background interface layer is an application programming interface (API). Exemplarily, the background interface layer may include a first API interface, a second API interface, and a third API interface. The first API interface corresponds to a header data acquisition request, the second API interface corresponds to a content data acquisition request, and the third API interface corresponds to a page data acquisition request.
[0088] In some embodiments, after receiving a content data acquisition request, the backend interface layer performs data mapping on the second query parameter in the content data acquisition request based on the query parameter configuration information, and obtains the second query parameter in the processed content data acquisition request. The data mapping is used to map the second query parameter to a parameter that can be directly recognized by the backend data layer. Subsequently, the backend interface layer encapsulates the first query parameter in the header data acquisition request, the second query parameter in the processed content data acquisition request, and the third query parameter in the paging data acquisition request based on the interface parameter format of the backend routing layer.
[0089] For example, if the date field for both the repayment and refund page requests is the same as the createdDate field, and the backend routing layer is configured with the repayment table corresponding to the repayDate field and the refund table corresponding to the refundDate field, then the repayment page is mapped to the reapyDate field, and the refund page is mapped to the refundDate field.
[0090] S202: The backend routing layer obtains the first query parameter in the request based on the header data, and determines the header configuration data of the page to be queried from the database.
[0091] In this step, after receiving the header data acquisition request, content data acquisition request and paging data acquisition request of the page to be queried, the background routing layer can determine the header configuration data of the page to be queried from the database according to the first query parameter in the header data acquisition request.
[0092] In some embodiments, the background routing layer may determine the header configuration data of the page to be queried from the database based on a mapping relationship between the first query parameter in the header data acquisition request and the header configuration data.
[0093] It should be understood that the embodiment of the present application does not limit the first query parameter in the header data acquisition request, for example, it may include a page identifier, a business identifier, etc.
[0094] For example, if the page the user needs to query is a loan page, the first query parameter sent in the header data acquisition request may include the identifier of the loan page and the identifier of the loan business. Subsequently, the background routing layer determines the header configuration data of the page to be queried from the database based on the identifier of the loan page and the identifier of the loan business.
[0095] The header configuration data includes business type data, display order data, header name data and layout rule data.
[0096] In addition, header configuration data can also include header field configuration dimensions, specifically system dimensions, service type dimensions, service type group dimensions, and protocol dimensions. Similar to the ABS process, different service type protocols vary significantly. For different header configuration data, queries based on the above dimensions are supported, with the priority from highest to lowest being protocol dimensions, service type group dimensions, service type dimensions, and system dimensions.
[0097] For example, if the page to be queried is a daily summary page, if the rules for each business type are consistent, only one set of system-level configurations can be configured. If there are differences in the repayment business, a set of configurations unique to the repayment business needs to be configured, and other business types continue to use the system default configurations. If there is a special agreement under the repayment business, a separate configuration needs to be added for the agreement, and other agreements under the repayment business can use the default configuration of the white bar. It should be noted that in the embodiment of the present application, the amount of data in the header field configuration dimension is minimized.
[0098] S203. The background routing layer determines the first data service corresponding to the content data of the page to be queried according to the query parameters in the content data acquisition request, and determines the second data service corresponding to the paging data of the page to be queried according to the query parameters in the paging data acquisition request.
[0099] In this step, after the background routing layer obtains the query parameters in the request based on the header data and determines the header configuration data of the page to be queried from the database, it can determine the first data service corresponding to the content data of the page to be queried based on the query parameters in the request for content data, and determine the second data service corresponding to the paging data of the page to be queried based on the query parameters in the request for paging data.
[0100] Among them, the embodiment of the present application does not limit the second query parameter in the content data acquisition request and the third query parameter in the page data acquisition request, which may include a page identifier, a service identifier, etc.
[0101] In some embodiments, the background routing layer first determines the service configuration information of the content data based on the second query parameter in the content data acquisition request. Subsequently, the background routing layer determines the first data service corresponding to the content data from the service management library based on the service configuration information of the content data. Similarly, the background routing layer first determines the service configuration information of the paging data based on the third query parameter in the paging data acquisition request. Subsequently, the background routing layer determines the second data service corresponding to the paging data from the service management library based on the service configuration information of the paging data.
[0102] The service configuration information of content data and page data may include table information, aliases, and business types corresponding to the data, such as the table information and aliases corresponding to the daily asset summary page.
[0103] In some embodiments, the service management library may include multiple data services. The background routing layer may encapsulate all data services into the service management library. When determining the service configuration information for the content data and the service configuration information for the paging data, the service management library may determine, based on the configuration information, a first data service corresponding to the content data and a second data service corresponding to the paging data.
[0104] S204: The background routing layer sends the first data service corresponding to the content data and the second data service corresponding to the paging data to the background data layer.
[0105] In this step, after determining the first data service corresponding to the content data and the second data service corresponding to the paged data, the background routing layer may send the first data service corresponding to the content data and the second data service corresponding to the paged data to the background data layer.
[0106] It should be noted that the embodiments of the present application do not limit how to send the first data service corresponding to the content data and the second data service corresponding to the paging data. For example, the interface of the background data layer can also be uniformly defined in the background routing layer. The background routing layer sends the first data service corresponding to the content data to the background data layer through the interface of the first data service corresponding to the content data. The background routing layer sends the second data service corresponding to the paging data to the background data layer through the interface of the second data service corresponding to the paging data.
[0107] S205 : The background data layer determines the content data according to the first data service corresponding to the content data, and determines the paging data according to the second data service corresponding to the paging data.
[0108] In an embodiment of the present application, after receiving the first data service and the second data service, the background data layer can determine the content data according to the first data service corresponding to the content data, and determine the paging data according to the second data service corresponding to the paging data.
[0109] For example, through the unified standard interface provided by the background routing layer, after receiving the first data service corresponding to the content data and the second data service corresponding to the page data, the background data layer can distinguish different data services through the service aliases, and then determine the content data and paging data.
[0110] S206: The background data layer sends the content data and the paging data to the background routing layer.
[0111] It should be noted that after determining the content data and the paging data, the background data layer does not perform any processing on the content data and the paging data, and directly sends the content data and the paging data to the background routing layer.
[0112] In an optional implementation, after receiving the content data and the paging data, the background routing layer may convert the format of the content data according to the data display rules of the front-end view layer.
[0113] The data display rules of the front-end view layer may be included in the query parameters in the content data acquisition request.
[0114] In some embodiments, since the content data fed back in the background data layer is unprocessed atomic data, the background routing layer can parse the content data according to the data display rules of the front-end view layer, and then complete the format conversion, so that when the content data is fed back to the front-end view layer, the front-end view layer does not need to process the content data again.
[0115] The embodiment of the present application does not limit the data display rules, and can display calculations, dates, thousand separators, percentages, etc., for example.
[0116] For example, if the page to be queried is the daily asset summary page, the data in Table 1 is the content data fed back by the background data layer, and Table 2 is the header configuration information corresponding to the daily asset summary page, then the background routing layer can convert the content data into the following: Figure 3 The format shown is shown. The original value of the Status field is 3, which is converted to the corresponding Chinese enumeration: Recurring Period; the date 2020-10-16 08:00:00 is converted to the corresponding short date format 2020-10-16; the Yield field 0.08755 is converted to a percentage with two decimal places; the Balance field 10000 corresponds to the formula Balance-repay-refund, which is 10000-2000-1000=7000; and the Repayment and Refund field is converted to a field with a thousand separator.
[0117] In this way, for different business types, you only need to configure different data display rules. The front-end view layer no longer needs to process the content data and can display it directly, which further facilitates the iterative maintenance of the query page.
[0118] Table 1
[0119]
[0120] Table 2
[0121]
[0122] Table 3
[0123]
[0124] S207: The backend routing layer sends the content data, paging data, and header configuration data to the frontend view layer.
[0125] In the step, after receiving the content data and the paging data, the background routing layer may send the content data, the paging data and the header configuration data to the front-end view layer.
[0126] It should be noted that the embodiment of the present application does not limit how to send content data, paging data and header configuration data to the front-end view layer. For example, it can be sent through the API interface in the background interface layer.
[0127] S208. The front-end view layer generates a page to be queried based on the content data, the paging data, and the header configuration data.
[0128] The embodiment of the present application does not limit how to generate the page to be queried based on the content data, paging data and header configuration data, and a common page generation method can be used. For example, the front-end view layer can fill the content data, paging data and header configuration data into the page template to generate the page to be queried.
[0129] In this application, unified management is done for the entire page query process, which is handled by the front-end view layer, back-end interface layer, back-end routing layer and back-end data layer respectively, and standardized interfaces are set. Since each layer only needs to know the information of the adjacent layer, cross-layer processing is not required. As the core function, the back-end routing layer manages the configuration of each dimension and establishes a service management library so that the back-end routing layer can determine the data service. The back-end data layer only provides atomic data, and differentiated processing is handled uniformly in the back-end routing layer. If a new business type is connected, there is no need to develop the code at all. You only need to add a set of configurations to the routing, and the entire front-end page will appear. Subsequent field modifications only require modifying the configuration.
[0130] The page query method provided by the embodiment of the present application receives a header data acquisition request, a content data acquisition request, and a paging data acquisition request of a page to be queried; determines the header configuration data of the page to be queried from a database according to the first query parameter in the header data acquisition request; determines the data service corresponding to the content data of the page to be queried according to the second query parameter in the content data acquisition request, and determines the data service corresponding to the paging data of the page to be queried according to the third query parameter in the paging data acquisition request; determines the content data according to the data service corresponding to the content data, and determines the paging data according to the data service corresponding to the paging data; generates the page to be queried according to the content data, paging data, and header configuration data. In this way, the configuration data, content data, and paging data of the header data can be determined separately. When performing iterative maintenance, only the configuration information of the header data and the data services of the content data and paging data need to be updated, without changing the specific data, thereby reducing the difficulty of iterative maintenance of the query page.
[0131] On the basis of the above embodiment, the server may further include a background interface layer, which is used to provide a data interface between the front-end view layer and the background routing layer. Figure 3Another signaling interaction diagram for page query provided in this application embodiment is shown in FIG. Figure 3 The page query method mainly includes steps S301 to S312, which are as follows:
[0132] S301. The front-end view layer sends a header data acquisition request, a content data acquisition request, and a page data acquisition request to the back-end interface layer.
[0133] S302. The background interface layer performs data mapping on the second query parameter in the content data acquisition request according to the configuration information of the background routing layer to obtain the processed second query parameter. The data mapping is used to map the second query parameter into a parameter that can be directly recognized by the background data layer.
[0134] S303: The background interface layer encapsulates the first query parameter, the second query parameter, and the third query parameter in the header data acquisition request according to the interface parameter format of the background routing layer.
[0135] S304: The background interface layer sends the header data acquisition request, the content data acquisition request, and the page data acquisition request to the background routing layer through corresponding interfaces.
[0136] S305: The backend routing layer obtains the first query parameter in the header data request and determines the header configuration data of the page to be queried from the database.
[0137] S306. The background routing layer determines the first data service corresponding to the content data of the page to be queried based on the second query parameter in the content data acquisition request, and determines the second data service corresponding to the paging data of the page to be queried based on the third query parameter in the paging data acquisition request.
[0138] S307: The background routing layer sends the first data service corresponding to the content data and the second data service corresponding to the paging data to the background data layer.
[0139] S308: The background data layer determines the content data according to the data service corresponding to the content data, and determines the paging data according to the data service corresponding to the paging data.
[0140] S309: The background data layer sends the content data and the paging data to the background routing layer.
[0141] S310: The background routing layer sends the content data, paging data, and header configuration data to the background interface layer.
[0142] S311. The backend interface layer sends the content data, paging data, and header configuration data to the frontend view layer.
[0143] S312. The front-end view layer generates a page to be queried based on the content data, paging data, and header configuration data.
[0144] Based on the above embodiment, after the background routing layer receives the content data, it can also convert the format of the content data according to the data display rules of the front-end view layer, so that the view module does not need to process the content data again, which is more conducive to the later maintenance of the query page. Figure 4 For another signaling interaction diagram of page query provided in the embodiment of the present application, refer to Figure 4 The page query method mainly includes steps S401 to S409, which are as follows:
[0145] S401: The front-end view layer sends a header data acquisition request, a content data acquisition request, and a page data acquisition request of a page to be queried to the back-end routing layer.
[0146] S402: The backend routing layer obtains the first query parameter in the header data request and determines the header configuration data of the page to be queried from the database.
[0147] S403. The background routing layer determines the first data service corresponding to the content data of the page to be queried according to the second query parameter in the content data acquisition request, and determines the second data service corresponding to the paging data of the page to be queried according to the second query parameter in the paging data acquisition request.
[0148] S404: The background routing layer sends the first data service corresponding to the content data and the second data service corresponding to the paging data to the background data layer.
[0149] S405: The background data layer determines the content data according to the first data service corresponding to the content data, and determines the paging data according to the second data service corresponding to the paging data.
[0150] S406: The background data layer sends the content data and the paging data to the background routing layer.
[0151] S407: The backend routing layer converts the format of the content data according to the data display rules of the frontend view layer.
[0152] S408: The backend routing layer sends the content data, paging data, and header configuration data to the frontend view layer.
[0153] S409: The front-end view layer generates a page to be queried based on the content data, the paging data, and the header configuration data.
[0154] It should be noted that the above module is only an example and does not constitute a limitation on the page query method provided in the embodiment of the present application. Figure 5A schematic diagram of a page query process provided by an embodiment of the present application, refer to Figure 5 The page query method mainly includes steps S501 to S505, which are as follows:
[0155] S501: Receive a header data acquisition request, a content data acquisition request, and a page data acquisition request of a page to be queried.
[0156] S502: Determine the header configuration data of the page to be queried from a database according to the first query parameter in the header data acquisition request.
[0157] S503: Determine the first data service corresponding to the content data of the page to be queried according to the second query parameter in the content data acquisition request, and determine the second data service corresponding to the paging data of the page to be queried according to the third query parameter in the paging data acquisition request.
[0158] S504: Determine the content data according to the first data service corresponding to the content data, and determine the paging data according to the second data service corresponding to the paging data.
[0159] S505: Generate a page to be queried based on the content data, paging data, and header configuration data.
[0160] Those skilled in the art will understand that all or part of the steps of implementing the above-mentioned method embodiment can be completed by hardware related to program information, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above-mentioned method embodiment; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk, etc. Various media that can store program codes.
[0161] Figure 6 This is a schematic diagram of the structure of a page query device provided in an embodiment of the present application. The page query device can be implemented by software, hardware, or a combination of both, such as the above-mentioned server, and the settlement device is used to execute the page query method in the above-mentioned embodiment. Figure 6 As shown, the page query device 600 includes: a view module 601, a routing module 602, a data module 603 and an interface module 604.
[0162] The view module 601 is used to receive a request for obtaining header data, content data, and paging data of a page to be queried; and generate the page to be queried based on the content data, paging data, and header configuration data.
[0163] Routing module 602 is configured to determine, from a database, header configuration data of the page to be queried based on a first query parameter in a header data retrieval request; determine, based on a second query parameter in a content data retrieval request, a first data service corresponding to the content data of the page to be queried; and determine, based on a third query parameter in a paging data retrieval request, a second data service corresponding to the paging data of the page to be queried;
[0164] The data module 603 is configured to determine the content data according to the first data service corresponding to the content data, and determine the paging data according to the second data service corresponding to the paging data.
[0165] In an optional embodiment, the page query device further includes an interface module 604;
[0166] The interface module 604 is used to encapsulate the first query parameter, the second query parameter and the third query parameter according to the interface parameter format of the background routing configuration layer; and send the encapsulated first query parameter, the encapsulated second query parameter and the encapsulated third query parameter to the background routing configuration layer.
[0167] In an optional implementation, the interface module 604 is further configured to perform data mapping on the second query parameter according to the query parameter configuration information, where the data mapping is used to map the second query parameter into a parameter recognizable by the data module 603 in the server.
[0168] In an optional implementation, the routing module 602 is specifically configured to determine service configuration information of the content data according to the second query parameter; and determine the first data service corresponding to the content data from a service management library of the server according to the service configuration information of the content data.
[0169] In an optional implementation, the routing module 602 is specifically configured to send the information of the first data service to the data module 603 through the interface of the first data service;
[0170] The data module 603 is specifically configured to determine content data according to the information of the first data service.
[0171] In an optional embodiment, the data module 603 is further configured to send the content data to the routing module 602;
[0172] The routing module 602 is further configured to convert the format of the content data according to the data display rules of the front-end view layer of the server.
[0173] In an optional implementation, the routing module 602 is specifically configured to determine service configuration information of the paging data according to the third query parameter; and determine the second data service corresponding to the paging data from the service management library of the server according to the service configuration information of the paging data.
[0174] In an optional implementation, the routing module 602 is specifically configured to send the information of the second data service to the data module 603 through the interface of the second data service;
[0175] The data module 603 is specifically configured to determine paging data according to the information of the second data service.
[0176] In an optional implementation, the service configuration information includes table information corresponding to the content data, an alias of the data service, and a service type corresponding to the table information.
[0177] In an optional implementation, the view module 601 is specifically configured to fill the content data, paging data, and header configuration data into a page template to generate a page to be queried.
[0178] In an optional implementation, the header configuration data includes service type data, display sequence data, header name data, and layout rule data.
[0179] The page query device provided in the embodiment of the present application can execute the actions of the page query method in the above embodiment. Its implementation principle and technical effects are similar and will not be repeated here.
[0180] It should be noted that the page query device provided in the above embodiment, when executing the page query method, only uses the division of the above-mentioned functional modules as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the page query device provided in the above embodiment and the page query method embodiment are based on the same concept. The implementation process is detailed in the method embodiment and will not be repeated here.
[0181] The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.
[0182] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 7As shown, the electronic device may include: a processor 61 (such as a CPU), a memory 62, a receiver 63 and a transmitter 64; the receiver 63 and the transmitter 64 are coupled to the processor 61, and the processor 61 controls the receiving action of the receiver 63 and the transmitting action of the transmitter 64. The memory 62 may include a high-speed RAM memory, and may also include a non-volatile memory NVM, such as at least one disk memory. Various information can be stored in the memory 62 to complete various processing functions and implement the method steps of the embodiment of the present application. Optionally, the electronic device involved in the embodiment of the present application may also include: a power supply 65, a communication bus 66 and a communication port 63. The receiver 63 and the transmitter 64 can be integrated into the transceiver of the electronic device, or can be an independent transceiver antenna on the electronic device. The communication bus 66 is used to realize the communication connection between components. The above-mentioned communication port 63 is used to realize the connection and communication between the electronic device and other peripherals.
[0183] In an embodiment of the present application, the above-mentioned memory 62 is used to store computer-executable program code, and the program code includes information; when the processor 61 executes the information, the information enables the processor 61 to perform the processing action of the above-mentioned method embodiment, enables the transmitter 64 to perform the sending action in the above-mentioned method embodiment, and enables the receiver 73 to perform the receiving action in the above-mentioned method embodiment. The implementation principles and technical effects are similar and will not be repeated here.
[0184] The present application also provides a chip including a processor and an interface, wherein the interface is used to input and output data or instructions processed by the processor. The processor is used to execute the method provided in the above method embodiment.
[0185] The present invention also provides a computer-readable storage medium, which may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, and other media that can store program code. Specifically, the computer-readable storage medium stores program information, and the program information is used in the above method.
[0186] An embodiment of the present application also provides a program, which, when executed by a processor, is used to execute the method provided in the above method embodiment.
[0187] An embodiment of the present application also provides a program product, such as a computer-readable storage medium, which stores instructions. When the program product is run on a computer, it enables the computer to execute the method provided by the above method embodiment.
[0188] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions according to the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).
[0189] Finally, it should be noted that the above embodiments 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 above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.
[0190] The above are merely embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.
Claims
1. A page query method, characterized in that: Applied to a server, the method includes: Receive a request to obtain header data, content data, and page data of the page to be queried; Determining, from a database, header configuration data of the page to be queried based on a first query parameter in the header data acquisition request; the header configuration data including business type data, display order data, header name data, layout rule data, and header field configuration dimensions; Determining, based on the second query parameter in the content data acquisition request, a first data service corresponding to the content data of the page to be queried, and determining, based on the third query parameter in the page data acquisition request, a second data service corresponding to the page data of the page to be queried; determining the content data according to the first data service, and determining the paging data according to the second data service; The page to be queried is generated according to the content data, the paging data and the header configuration data.
2. The method according to claim 1, characterized in that The server further includes a background interface layer and a background routing configuration layer, and the method further includes: Controlling the background interface layer to encapsulate the first query parameter, the second query parameter, and the third query parameter according to the interface parameter format of the background routing configuration layer; The background interface layer is controlled to send the encapsulated first query parameter, the encapsulated second query parameter, and the encapsulated third query parameter to the background routing configuration layer.
3. The method according to claim 2, characterized in that Before controlling the background interface layer to send the encapsulated first query parameter, the encapsulated second query parameter, and the encapsulated third query parameter to the background routing configuration layer, the method further includes: The background interface layer is controlled to perform data mapping on the second query parameter according to the query parameter configuration information, wherein the data mapping is used to map the second query parameter into a parameter recognizable by the background data layer in the server.
4. The method according to claim 3, characterized in that The determining, according to the second query parameter in the content data acquisition request, the first data service corresponding to the content data of the to-be-queried page includes: controlling the background routing configuration layer to determine the service configuration information of the content data according to the second query parameter; The background routing configuration layer is controlled to determine the first data service corresponding to the content data from the service management library of the server according to the service configuration information of the content data.
5. The method according to claim 4, characterized in that The determining the content data according to the first data service includes: Controlling the background routing configuration layer to send information of the first data service to the background data layer through the interface of the first data service; The background data layer is controlled to determine the content data according to the information of the first data service.
6. The method according to claim 5, characterized in that After controlling the background data layer to determine the content data according to the information of the first data service, the method further includes: Controlling the background data layer to send the content data to the background routing configuration layer; The backend routing configuration layer is controlled to convert the format of the content data according to the data display rules of the front-end view layer of the server.
7. The method according to claim 3, characterized in that The determining, according to the third query parameter in the paging data acquisition request, the second data service corresponding to the paging data of the page to be queried includes: Controlling the background routing configuration layer to determine the service configuration information of the paging data according to the third query parameter; The background routing configuration layer is controlled to determine the second data service corresponding to the paging data from the service management library of the server according to the service configuration information of the paging data.
8. The method according to claim 7, characterized in that The determining the paging data according to the second data service includes: Controlling the background routing configuration layer to send information of the second data service to the background data layer through the interface of the second data service; The background data layer is controlled to determine the paging data according to the information of the second data service.
9. The method according to any one of claims 4 to 8, characterized in that The service configuration information includes table information corresponding to the content data, an alias of the data service, and a business type corresponding to the table information.
10. The method according to claim 1, characterized in that The server further includes a front-end view layer; generating the page to be queried according to the content data, the paging data and the header configuration data, including: The front-end view layer is controlled to fill the content data, the paging data and the header configuration data into a page template to generate the page to be queried.
11. A page query device, characterized in that: include: View module, routing module and data module; The view module is used to receive requests for obtaining header data, content data, and page data of the page to be queried; Generate the page to be queried according to the content data, the paging data and the header configuration data; a routing module configured to determine, from a database, header configuration data for the page to be queried based on a first query parameter in the header data acquisition request; the header configuration data including business type data, display order data, header name data, layout rule data, and header field configuration dimensions; determine, based on a second query parameter in the content data acquisition request, a data service corresponding to the content data of the page to be queried; and determine, based on a third query parameter in the paging data acquisition request, a data service corresponding to the paging data of the page to be queried; The data module is configured to determine the content data according to a data service corresponding to the content data, and to determine the paging data according to a data service corresponding to the paging data.
12. A computer program product comprising computer instructions, characterized in that When the computer instructions are executed by a processor, the method according to any one of claims 1 to 10 is implemented.
13. A computer storage medium, characterized in that The computer storage medium stores a plurality of instructions, which are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 10.
14. An electronic device, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method according to any one of claims 1 to 10.
Citation Information
Patent Citations
General paging query method and system based on SSH framework
CN103984549A
Page query request processing method and device, equipment and storage medium
CN112115338A