A method for optimizing dynamic business acceptance response through incremental page refresh

Abstract

The present invention discloses a method for optimizing dynamic business acceptance responses through incremental page refresh, comprising the following steps: Step 1: processing the first change information of the target attribute of the target page sent by the front-end device; Step 2: based on the preset suite group request identifier, the front-end device controls the incremental response interaction to determine whether the first change information of the target attribute of the target page is sent; Step 3: based on the preset non-suite group control request identifier, the front-end device controls the incremental response interaction to determine whether the first change information of the target attribute of the target page is sent. The present invention solves the problems that the cloud product acceptance page cannot achieve a fast response, cannot control the number of interactions, and the page response is too long or even stuck due to multiple processing logics. This method significantly reduces the number of dynamic business acceptance responses, significantly improves the system performance of the acceptance page, and significantly improves user perception by controlling the incremental refresh of the page.

Description

Technical Field

[0001] The present invention relates to the technical field of cloud computing page refresh, and in particular to a method for optimizing dynamic business acceptance responses through incremental page refresh. Background Art

[0002] In the existing technology, a front-end operation is required every time the information is changed. Even if the changed information is a non-logical calculation operation, a front-end interaction is required, which leads to frequent interactions of incremental page changes and invalid front-end and back-end logical interactions. In addition, the existing technology is based on a preset attribute constraint configuration, and the first change information on the front-end is verified and processed. Each time the target page incrementally changes, the change information must be constrained and verified, and will respond to each incremental response of the target attribute page, and may even cause frequent page freezes.

[0003] To this end, we propose a method to optimize dynamic business acceptance response through incremental page refresh to solve the above problems. Summary of the Invention

[0004] The purpose of this section is to summarize some aspects of the embodiments of the present invention and briefly introduce some preferred embodiments. Some simplifications or omissions may be made in this section and the abstract and title of this application to avoid obscuring the purpose of this section, the abstract and the title of the invention, and such simplifications or omissions should not be used to limit the scope of the present invention.

[0005] In view of the problems existing in the above-mentioned existing methods for optimizing dynamic business acceptance responses through incremental page refresh, the present invention is proposed.

[0006] Therefore, the purpose of the present invention is to provide a method for optimizing dynamic business acceptance responses through incremental page refresh, which solves the problems that the cloud product acceptance page cannot respond quickly, the number of interactions cannot be controlled, and the page response is too long or even stuck due to multiple processing logic.

[0007] To solve the above technical problems, the present invention provides the following technical solution: a method for optimizing dynamic business acceptance response by incremental page refresh, comprising the following steps:

[0008] Step 1: Processing the first change information of the target attribute of the target page sent by the front-end device;

[0009] Step 2: Based on the preset suite group request identifier, the front-end device controls the incremental response interaction to determine whether to send the first change information of the target attribute of the target page;

[0010] Step 3: Based on the preset non-suite group control request identifier, the front-end device controls the incremental response interaction, determines whether to send the first change information of the target attribute of the target page, and the back-end device controls the response processing and processes the response interaction logic;

[0011] Step 4: The front-end device sends the full information of the target page, triggering a unified pre-verification.

[0012] As a preferred solution of the method for realizing dynamic business acceptance response optimization through incremental page refresh as described in the present invention, the first change information in the step one is generated by a front-end operation performed by the user on the target attribute of the target page, and the target attribute refers to a page attribute whose attribute value can change, such as page control and page control group input information.

[0013] As a preferred solution of the method for optimizing dynamic business acceptance response through incremental page refresh described in the present invention, step two is based on the NHIS protocol, which is used by the front end to control the frequency of interaction with the back end during interaction, and the incremental operation can call the background service once or zero times.

[0014] As a preferred solution of the method for optimizing dynamic business acceptance response by incremental page refresh according to the present invention, the suite group in step 2 includes an address information suite group, and the response identifier of each control is preset to control whether the front-end and back-end interact with each other. The specific steps include:

[0015] Step A1: preset a response identifier of a single control in the suite group;

[0016] Step A2: Preset the package group response identifier;

[0017] When the page is performing incremental operations, the front-end triggers the NHIS protocol according to the preset control response identifier, and controls one or zero interactions with the back-end.

[0018] As a preferred solution of the method for optimizing dynamic business acceptance response by incremental page refresh of the present invention, the method includes the following steps:

[0019] Step B1: preset a single control front-end response identifier;

[0020] Step B2: Preset the backend logic identifier of a single control.

[0021] If the front-end response of the incremental information submission control indicates that the system does not perform any interaction, no front-end interaction will be performed for this incremental operation.

[0022] If the front-end response of the incremental information submission control is interactive and the back-end logic is near cache, the incremental operation is directly recorded in the change information cache object without any additional calculation logic processing.

[0023] As a preferred solution of the method for optimizing dynamic business acceptance response by incremental page refresh according to the present invention, in step 4, after the incremental page information is accepted, the full incremental page information is uniformly submitted to the back-end device for unified pre-verification processing. The specific operation steps are as follows:

[0024] Step C01: The user selects the cloud product to be processed on the business processing interface displayed on the front end, and then proceeds to step C02;

[0025] Step C02: triggering backend unified verification;

[0026] Step C03: back-end processing verification;

[0027] Step C04: The backend converts the verification complete JSON request into a string and stores the request content and verification result in the cache;

[0028] Step C05: Cache return verification storage result;

[0029] Step C06: The backend returns the verification result;

[0030] Step C07: The front end returns the verification result;

[0031] Step C08: The user resubmits the accepted cloud product multiple times after modification;

[0032] Step C09: triggering backend unified verification;

[0033] Step C10: Obtain cache verification information;

[0034] Step C11: Cache return verification storage result.

[0035] As a preferred solution of the method for optimizing dynamic service acceptance response by incremental page refresh described in the present invention, the method is applied to interactive response control of front-end and back-end devices, including:

[0036] Develop a new front-end and back-end interaction protocol: The front-end and back-end develop a set of standard protocols for high-interaction between the front-end and back-end, using multiple interactions to call the back-end service once or zero times for each front-end operation;

[0037] Define new page suite groups: Based on the NHIS protocol, by defining new suite groups, multiple separate controls on the collection page within different suite groups are individually identified to control whether the front-end and back-end interact with each other, thus achieving controllable interaction of incremental changes to information of multiple separate suites within a suite group;

[0038] Build the initial cache object: Build the initial cache object AcceptOrderContextBo and the change information cache object PortalChangedContext to record the information required for the entire business acceptance and the change information;

[0039] Define new response request constraints and cache interaction strategies: Define new request constraint rules for non-suite group controls to identify front-end and back-end interaction processing logic.

[0040] As a preferred solution of the method for realizing dynamic business acceptance response optimization through incremental page refresh described in the present invention, the front-end and back-end interaction processing logic includes: 1. Whether to trigger back-end interaction; 2. Whether to trigger logic calculation if the interaction is triggered.

[0041] As a preferred solution of the method for optimizing dynamic business acceptance response through incremental page refresh described in the present invention, if the submission control of the incremental information is marked as not interactive, then the incremental operation will not perform front-end interactive operations, and the front-end will not send requests to the back-end, reducing unnecessary communication overhead; if it is marked as triggering interaction but not triggering logical calculation, then the incremental operation will be directly recorded in the change information cache object PortalChangedContext without performing other additional calculation logic processing, which can reduce unnecessary calculation and processing operations and improve the performance and efficiency of the system.

[0042] As a preferred solution of the method for optimizing dynamic business acceptance response by incremental page refresh of the present invention, wherein: the method is applied to optimize dynamic business backend verification processing response, and further includes:

[0043] The first sending module triggers a front-end verification processing interaction when submitting all incremental information of the page;

[0044] A second receiving module is used to send the incremental information to a back-end receiving device to process all incremental update information of the target page;

[0045] The third processing module, after the backend device receives all the incremental update information of the target page, uses it for logical verification and remote verification processing; if all the incremental updates have been stored in the cache locally, this module does not process it;

[0046] The fourth processing module, the backend device caches all incremental update information and verification results of the target page. If all local incremental updates have been stored in the storage, this module does not process them;

[0047] The page refresh module is used to refresh the page and respond based on the verification results of all incremental update information of the page.

[0048] The present invention addresses the issues of cloud product acceptance pages being unable to respond quickly, unable to control the number of interactions, and experiencing lengthy or even lag-prone page responses due to multiple processing logic. By controlling incremental page refreshes, this method significantly reduces the number of dynamic business acceptance responses, significantly improves acceptance page system performance, and significantly enhances user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for describing the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. Those skilled in the art can also derive other drawings based on these drawings without inventive effort. Among them:

[0050] Figure 1 The present invention is a flowchart of a method for optimizing dynamic business acceptance response through incremental page refresh. DETAILED DESCRIPTION

[0051] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the specific embodiments of the present invention are described in detail below with reference to the accompanying drawings.

[0052] In the following description, many specific details are set forth to facilitate a full understanding of the present invention. However, the present invention may also be implemented in other ways different from those described herein. Those skilled in the art may make similar generalizations without violating the connotation of the present invention. Therefore, the present invention is not limited to the specific embodiments disclosed below.

[0053] Secondly, the term "one embodiment" or "embodiment" herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in various places throughout this specification does not necessarily refer to the same embodiment, nor does it refer to a separate or selective embodiment that is mutually exclusive of other embodiments.

[0054] Furthermore, the present invention is described in detail with reference to schematic diagrams. For ease of illustration, when describing the embodiments of the present invention, cross-sectional views illustrating device structures may be partially enlarged and not to scale. Furthermore, the schematic diagrams are merely illustrative and should not limit the scope of protection of the present invention. Furthermore, in actual production, the three-dimensional dimensions of length, width, and depth should be included.

[0055] Reference Figure 1 , provides a method for optimizing dynamic business acceptance response by incremental page refresh, including the following steps:

[0056] Step 1: Processing the first change information of the target attribute of the target page sent by the front-end device;

[0057] Step 2: Based on the preset suite group request identifier, the front-end device controls the incremental response interaction to determine whether to send the first change information of the target attribute of the target page;

[0058] Step 3: Based on the preset non-suite group control request identifier, the front-end device controls the incremental response interaction, determines whether to send the first change information of the target attribute of the target page, and the back-end device controls the response processing and processes the response interaction logic;

[0059] Step 4: The front-end device sends the full information of the target page, triggering a unified pre-verification.

[0060] The first change information in step 1 is generated by a front-end operation performed by the user on a target attribute of the target page. The target attribute refers to a page attribute whose attribute value can be changed, such as page control or page control group input information.

[0061] Among them, the step 2 is based on the NHIS protocol, which is used by the front end to control the frequency of interaction with the back end during interaction. The incremental operation can call the back end service once or zero times.

[0062] Furthermore, the suite group in step 2 includes: an address information suite group, which controls whether to perform interactive operations between the front-end and the back-end by presetting a response identifier for each control. The specific steps include:

[0063] Step A1: preset a response identifier of a single control in the suite group;

[0064] Step A2: Preset the package group response identifier;

[0065] When the page is performing incremental operations, the front-end triggers the NHIS protocol according to the preset control response identifier, and controls one or zero interactions with the back-end.

[0066] The step 3 presetting the non-suite group control to define a new request constraint for identifying the front-end and back-end interaction processing operations includes the following steps:

[0067] Step B1: preset a single control front-end response identifier;

[0068] Step B2: Preset the backend logic identifier of a single control.

[0069] If the front-end response of the incremental information submission control indicates that the system does not perform any interaction, no front-end interaction will be performed for this incremental operation.

[0070] If the front-end response of the incremental information submission control is interactive and the back-end logic is near cache, the incremental operation is directly recorded in the change information cache object without any additional calculation logic processing.

[0071] Among them, in step 4, after the page incremental information is accepted, the full page incremental information is uniformly submitted to the back-end device for unified pre-verification processing. The specific operation steps are as follows:

[0072] Step C01: The user selects the cloud product to be processed on the business processing interface displayed on the front end, and then proceeds to step C02;

[0073] Step C02: triggering backend unified verification;

[0074] Step C03: back-end processing verification;

[0075] Step C04: The backend converts the verification complete JSON request into a string and stores the request content and verification result in the cache;

[0076] Step C05: Cache return verification storage result;

[0077] Step C06: The backend returns the verification result;

[0078] Step C07: The front end returns the verification result;

[0079] Step C08: The user resubmits the accepted cloud product multiple times after modification;

[0080] Step C09: triggering backend unified verification;

[0081] Step C10: Obtain cache verification information;

[0082] Step C11: Cache return verification storage result.

[0083] Specifically, the method is applied to the interactive response control of front-end and back-end devices, including:

[0084] Develop a new front-end and back-end interaction protocol: The front-end and back-end develop a set of standard protocols for high-interaction between the front-end and back-end, using multiple interactions to call the back-end service once or zero times for each front-end operation;

[0085] Define new page suite groups: Based on the NHIS protocol, by defining new suite groups, multiple separate controls on the collection page within different suite groups are individually identified to control whether the front-end and back-end interact with each other, thus achieving controllable interaction of incremental changes to information of multiple separate suites within a suite group;

[0086] Build the initial cache object: Build the initial cache object AcceptOrderContextBo and the change information cache object PortalChangedContext to record the information required for the entire business acceptance and the change information;

[0087] Define new response request constraints and cache interaction strategies: Define new request constraint rules for non-suite group controls to identify the front-end and back-end interaction processing logic. The front-end and back-end interaction processing logic includes: 1. Whether to trigger back-end interaction; 2. If the interaction is triggered, whether to trigger logic calculation.

[0088] If the submit control for incremental information is marked as non-interactive, then this incremental operation will not perform front-end interactive operations, and the front-end will not send requests to the back-end, reducing unnecessary communication overhead; if it is marked as triggering interaction but not triggering logical calculation, then this incremental operation will be directly recorded in the change information cache object PortalChangedContext without performing other additional calculation logic processing, which can reduce unnecessary calculation and processing operations and improve system performance and efficiency.

[0089] The method is applied to the optimization of dynamic business backend verification processing response, and further includes:

[0090] The first sending module triggers a front-end verification processing interaction when submitting all incremental information of the page;

[0091] A second receiving module is used to send the incremental information to a back-end receiving device to process all incremental update information of the target page;

[0092] The third processing module, after the backend device receives all the incremental update information of the target page, uses it for logical verification and remote verification processing; if all the incremental updates have been stored in the cache locally, this module does not process it;

[0093] The fourth processing module, the backend device caches all incremental update information and verification results of the target page. If all local incremental updates have been stored in the storage, this module does not process them;

[0094] The page refresh module is used to refresh the page and respond based on the verification results of all incremental update information of the page.

[0095] The present invention solves the problems of the cloud product acceptance page being unable to respond quickly, being unable to control the number of interactions, and the page response being too long or even stuck due to multiple processing logics.

[0096] This method significantly reduces the number of dynamic business acceptance responses, significantly improves the system performance of the acceptance page, and significantly enhances user perception by controlling the incremental refresh of the page.

[0097] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solutions of the present invention may be modified or replaced by equivalents without departing from the spirit and scope of the technical solutions of the present invention, which should all be included in the scope of the claims of the present invention.

Claims

1. A method for optimizing dynamic business acceptance response by incremental page refresh, characterized in that: The following steps are involved: Step 1: Processing first change information of a target attribute of a target page sent by a front-end device; the first change information in step 1 is generated by a front-end operation performed by a user on a target attribute of the target page, wherein the target attribute refers to a page attribute whose attribute value can be changed, such as page control or page control group input information; Step 2: Based on the preset package group request identifier, the front-end device controls the incremental response interaction and determines whether to send the first change information of the target attribute of the target page; Step 2 is based on the NHIS protocol, which is used by the front-end to control the frequency of interaction with the back-end during the interaction. The incremental operation can call the back-end service once or zero times; The suite group in step 2 includes: an address information suite group, which controls whether to perform interactive operations between the front-end and the back-end by presetting the response identifier of each control. The specific steps include: Step A1: preset a response identifier of a single control in the suite group; Step A2: Preset the package group response identifier; When the page is performing incremental operations, the front-end triggers the NHIS protocol based on the preset control response identifier, controlling one or zero interactions with the back-end; Step 3: Based on the preset non-suite group control request identifier, the front-end device controls the incremental response interaction, determines whether to send the first change information of the target attribute of the target page, and the back-end device controls the response processing and processes the response interaction logic; the preset non-suite group control in step 3 defines a new request constraint for identifying the front-end and back-end interaction processing operation, including the following steps: Step B1: preset a single control front-end response identifier; Step B2: Preset the backend logic identifier of a single control; If the front-end response of the incremental information submission control indicates that the system does not perform any interaction, no front-end interaction will be performed for this incremental operation. If the front-end response flag of the incremental information submission control is interactive and the back-end logic flag is near cache, the incremental operation is directly recorded in the change information cache object without any additional calculation logic processing; Step 4: The front-end device sends the full information of the target page, triggering a unified pre-verification.

2. The method for optimizing dynamic service acceptance response through incremental page refresh according to claim 1, characterized in that: In step 4, after the page incremental information is accepted, the full page incremental information is uniformly submitted to the backend device for unified pre-verification processing. The specific operation steps are as follows: Step C01: The user selects the cloud product to be processed on the business processing interface displayed on the front end, and then proceeds to step C02; Step C02: triggering backend unified verification; Step C03: back-end processing verification; Step C04: The backend converts the verification complete JSON request into a string and stores the request content and verification result in the cache; Step C05: Cache return verification storage result; Step C06: The backend returns the verification result; Step C07: The front end returns the verification result; Step C08: The user resubmits the accepted cloud product multiple times after modification; Step C09: triggering backend unified verification; Step C10: Obtain cache verification information; Step C11: Cache return verification storage result.

3. The method for optimizing dynamic business acceptance response by incremental page refresh according to claim 1, characterized in that: This method is applied to the interactive response control of front-end and back-end devices, including: Develop a new front-end and back-end interaction protocol: The front-end and back-end develop a set of standard protocols for high-interaction between the front-end and back-end, using multiple interactions to call the back-end service once or zero times for each front-end operation; Define new page suite groups: Based on the NHIS protocol, by defining new suite groups, multiple separate controls on the collection page within different suite groups are individually identified to control whether the front-end and back-end interact with each other, thus achieving controllable interaction of incremental changes to information of multiple separate suites within a suite group; Build the initial cache object: Build the initial cache object AcceptOrderContextBo and the change information cache object PortalChangedContext to record the information required for the entire business acceptance and the change information; Define new response request constraints and cache interaction strategies: Define new request constraint rules for non-suite group controls to identify front-end and back-end interaction processing logic.

4. The method for optimizing dynamic service acceptance response by incremental page refresh according to claim 3, characterized in that: The front-end and back-end interaction processing logic includes:

1. Whether to trigger back-end interaction; 2. If the interaction is triggered, whether to trigger logical calculation.

5. The method for optimizing dynamic business acceptance response by incremental page refresh according to claim 1, characterized in that: If the submit control for incremental information is marked as non-interactive, then this incremental operation will not perform front-end interactive operations, and the front-end will not send requests to the back-end; if it is marked as triggering interaction but not triggering logical calculation, then this incremental operation will be directly recorded in the change information cache object PortalChangedContext without any additional calculation logic processing.

6. The method for optimizing dynamic business acceptance response by incremental page refresh according to claim 1, characterized in that: This method is applied to dynamic business backend verification processing response optimization, and also includes: The first sending module triggers a front-end verification processing interaction when submitting all incremental information of the page; A second receiving module is used to send the incremental information to a back-end receiving device to process all incremental update information of the target page; The third processing module, after the backend device receives all the incremental update information of the target page, uses it for logical verification and remote verification processing; if all the incremental updates have been stored in the cache locally, this module does not process it; The fourth processing module, the backend device caches all incremental update information and verification results of the target page. If all local incremental updates have been stored in the storage, this module does not process them; The page refresh module is used to refresh the page and respond based on the verification results of all incremental update information of the page.

Images