Web system front-end page loading method and device, electronic equipment and storage medium

Abstract

The invention relates to the technical field of computers, and discloses a Web system front-end page loading method and device, electronic equipment and a storage medium. The method comprises the steps that when a loading request initiated by a user for a target Web system in a browser is received, a corresponding front-end main application is loaded in the browser through a guide module of the Web system; obtaining a front-end sub-application set corresponding to the front-end main application; obtaining a user role corresponding to the user and a user permission corresponding to the user role; when the loading of the front-end main application is finished, acquiring a corresponding first front-end sub-application from the front-end sub-application set according to the user role; and starting the first front-end sub-application, and loading a corresponding front-end page in the first front-end sub-application according to the user permission. According to the method, the first screen performance of the front-end page of the Web system is improved, and the loading time consumption of the front-end page of the Web system is reduced.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, device, electronic device and storage medium for loading a front-end page of a Web system. Background Art

[0002] In the field of financial technology, specifically in the field of property insurance claims, the process of property insurance claims is usually long, involving a series of links such as reporting, investigation, damage assessment, liability settlement, payment, etc., and corresponding to the insurance claims system are business subsystems supporting various businesses such as investigation risk control, rule engine, scheduling and dispatching, and damage assessment platform. In addition, it can also be other medium and large Web systems involving long business process links, such as bank credit systems and hospital digital medical systems. Therefore, general medium and large Web systems need to load a large number of Web pages when they are first started, which makes the system take a long time to load for the first time, and the loading is slow and stuck when opening each new sub-page in the system. And as the system functions increase, the number of Web pages that need to be loaded will also increase, which will further increase the time it takes to load the system for the first time and open the sub-pages. Summary of the invention

[0003] The main technical problem solved by the implementation method of the present application is that the front-end page loading of traditional medium and large-scale Web systems takes a long time, which reduces the user experience and operating efficiency of the Web system.

[0004] To solve the above technical problems, the first technical solution adopted in the implementation mode of the present application is: to provide a front-end page loading method of a Web system, comprising: when a loading request initiated by a user to a target Web system in a browser is received, loading the corresponding front-end main application through the boot module of the Web system in the browser; obtaining a front-end sub-application set corresponding to the front-end main application; obtaining a user role corresponding to the user, and user permissions corresponding to the user role; when the loading of the front-end main application is completed, obtaining a corresponding first front-end sub-application from the front-end sub-application set according to the user role; starting the first front-end sub-application, and loading the corresponding front-end page in the first front-end sub-application according to the user permissions.

[0005] Optionally, after the step of loading the corresponding front-end page in the first front-end sub-application according to the user's permissions, it also includes: starting the front-end tracking subsystem, front-end monitoring subsystem, and intelligent preloading subsystem corresponding to the target Web system; monitoring the corresponding page routing information from the user's browser through the front-end monitoring subsystem, and reporting the page routing information to the front-end tracking subsystem; storing the user information of the user and the corresponding page routing information to the intelligent preloading subsystem through the front-end tracking subsystem; and using a preset big data search and analysis engine through the intelligent preloading subsystem to process the user information and the corresponding page routing information to obtain the corresponding preloaded page.

[0006] Optionally, after the step of loading the corresponding front-end page in the first front-end sub-application according to the user permissions, the step also includes: monitoring whether the user role of the user changes, and if the user role changes, obtaining the new user role corresponding to the user and the corresponding new user permissions; according to the new user role, obtaining the corresponding second front-end sub-application from the front-end sub-application set; starting the second front-end sub-application, and loading the corresponding front-end page in the second front-end sub-application according to the new user permissions; controlling the corresponding first front-end sub-application to enter a dormant state, or uninstalling the corresponding first front-end sub-application.

[0007] Optionally, after the step of obtaining the corresponding preloading page, it also includes: obtaining the resource script path corresponding to the preloading page, and downloading the corresponding preloading resource file to the user's browser according to the resource script path; determining whether the preloading page belongs to the first front-end sub-application; if not, obtaining the corresponding third front-end sub-application from the front-end sub-application set according to the preloading page; starting the third front-end sub-application, and when receiving the user's loading request for the preloading page, loading the corresponding front-end page in the user's browser according to the preloading resource file.

[0008] Optionally, the step of using a preset big data search and analysis engine to process the user information and the corresponding page routing information to obtain a corresponding preloaded page includes: obtaining the corresponding user role and time interval based on the user information; setting the user information, the user role and the time interval as weight factors, performing aggregation analysis on the page routing information to obtain the next access probability of the user corresponding to the user information to different front-end pages of the Web system when in different user roles; and setting the front-end page with the highest next access probability as the preloaded page.

[0009] Optionally, the intelligent preloading subsystem also includes preset preloading rules. Before the step of setting the front-end page corresponding to the next access probability with the highest probability as the preloading page, it also includes: parsing the preloading rules to obtain the corresponding business process nodes; determining the first business process node corresponding to the current front-end page where the user stays in the browser; determining the second business process node corresponding to the different front-end pages; if the second business process node is the subsequent process node of the first business process node, and the second business process node is not an adjacent process node of the first business process node, then removing the different front-end pages corresponding to the second business process node.

[0010] Optionally, before the step of setting the front-end page corresponding to the highest probability of the next access as the preloaded page, the step also includes: clustering the page routing information according to the user role, and determining the page routing information to be analyzed corresponding to the current user role of the user according to the clustering result; counting the number of occurrences of different historical jump pages corresponding to the current front-end page where the user stays in the browser in the page routing information to be analyzed; and recalculating the next access probability according to the number of occurrences and a preset probability increase rule, wherein the largest number of occurrences corresponds to the largest probability increase value.

[0011] To solve the above technical problems, the second technical solution adopted in the implementation mode of the present application is: to provide a front-end page loading device of a Web system, including: a main application loading module, which is used to load the corresponding front-end main application through the boot module of the Web system in the browser when receiving a loading request initiated by a user to the target Web system in the browser; a sub-application collection module, which is used to obtain the front-end sub-application collection corresponding to the front-end main application; a user role and permission module, which is used to obtain the user role corresponding to the user, and the user permission corresponding to the user role; a sub-application loading module, which is used to obtain the corresponding first front-end sub-application from the front-end sub-application collection according to the user role when the loading of the front-end main application is completed; and a sub-application page module, which is used to start the first front-end sub-application and load the corresponding front-end page in the first front-end sub-application according to the user permission.

[0012] To solve the above technical problems, the third technical solution adopted in the implementation mode of the present application is: to provide an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the Web system front-end page loading method as described above.

[0013] In order to solve the above technical problems, the fourth technical solution adopted in the implementation mode of the present application is: providing a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are executed by an electronic device, the electronic device executes the Web system front-end page loading method as described above.

[0014] Different from the related technologies, this application partially loads the corresponding front-end sub-application according to the user role and user authority when the front-end page of the Web system is initially loaded, without loading all system resources, thereby improving the first screen performance of the front-end page of the Web system and reducing the loading time of the front-end page of the Web system. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] One or more embodiments are exemplarily described by corresponding drawings, which do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and the figures in the drawings do not constitute proportional limitations unless otherwise stated.

[0016] Figure 1 It is a schematic diagram of the application environment of the Web system front-end page loading method provided in the embodiment of the present application.

[0017] Figure 2 It is a schematic diagram of the execution flow of the Web system front-end page loading method provided in an embodiment of the present application.

[0018] Figure 3 It is a schematic diagram of the execution flow of the loading subsystem of the Web system front-end page loading method provided in an embodiment of the present application.

[0019] Figure 4 It is a schematic diagram of the execution flow of monitoring user roles in the Web system front-end page loading method provided in an embodiment of the present application.

[0020] Figure 5 It is a system structure diagram of the Web system front-end page loading device provided in an embodiment of the present application.

[0021] Figure 6 It is a hardware structure diagram of an electronic device for executing a Web system front-end page loading method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0023] It should be noted that, if there is no conflict, the various features in the embodiments of the present application can be combined with each other, all within the scope of protection of the present application. In addition, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flow chart, in some cases, the steps shown or described can be performed in a different order than the module division in the device schematic diagram or the order in the flow chart.

[0024] Unless otherwise defined, all technical and scientific terms used in this specification have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used in the specification of this application are only for the purpose of describing specific embodiments and are not intended to limit this application. The term "and / or" used in this specification includes any and all combinations of one or more of the related listed items.

[0025] To facilitate understanding of this embodiment, a Web system front-end page loading method disclosed in an embodiment of the present application is first introduced in detail. The executor of the Web system front-end page loading method provided in the embodiment of the present application is generally an electronic device with certain computing capabilities, such as a computer device. In some possible implementation methods, the Web system front-end page loading method can be implemented by a processor calling computer-readable instructions stored in a memory.

[0026] The following describes the Web system method provided by the embodiment of the present application by taking the execution subject as a computer device as an example. Figure 1 , Figure 1 Schematic diagram of the application environment of the Web system front-end page loading method provided in the embodiment of the present application. Figure 1 As shown, users of the Web system Figure 1 The client in the Web system (usually a browser on the client, or a client application based on browser kernel technology, such as a client application developed based on Electron technology) accesses the server of the Web system, and the client communicates with the server through the network. When the user of the Web system initiates a loading request to the server of the Web system through the network on the client, the server needs to return the corresponding resources required for loading, and the client then loads the corresponding front-end page based on the required resources obtained for loading. Among them, it should be specially noted that Figure 1The server can be an independent server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms. The client can be a general computer device or other electronic devices with network communication functions such as mobile phones and tablets. It is understandable that Figure 1 The number of clients, networks and servers in the figure is only indicative and can be expanded to any number according to actual needs.

[0027] Please continue reading Figure 2 , Figure 2 is a schematic diagram of the execution flow of the Web system front-end page loading method provided in the embodiment of the present application, such as Figure 2 As shown, the method comprises the following steps:

[0028] S1. When a loading request initiated by a user to a target Web system in a browser is received, a corresponding front-end main application is loaded in the browser through a boot module of the Web system.

[0029] Among them, for traditional medium and large Web systems with more complex business processes, the front end of the original Web system can be split into a front-end main application and at least one front-end sub-application according to the specific business processes and the original business modules. The front-end main application and the front-end sub-application can be independently developed, tested, deployed and maintained. The technical team can independently develop and release functions according to needs without affecting the overall system, and avoid problems such as duplicate loading by sharing components, styles, tool libraries, etc.

[0030] S2. Obtain a set of front-end sub-applications corresponding to the front-end main application.

[0031] Among them, the elements of the front-end sub-application set are the unique identification information of the above-mentioned front-end sub-applications, such as sub-application name, sub-application path, etc. The front-end sub-application is managed by a unified routing manager to ensure that users can navigate between different front-end sub-applications and maintain application consistency. The relevant front-end routing technology will not be repeated here.

[0032] S3. Obtain the user role corresponding to the user and the user permissions corresponding to the user role.

[0033] Among them, there are differences in the above front-end sub-applications corresponding to users with different user roles. For example, in some Web systems of insurance institutions, insurance consumers and insurance sales personnel are associated with front-end sub-applications such as user information and user settings, but insurance sales personnel can also be associated with insurance sales business sub-modules such as insurance plan generation. Furthermore, some front-end pages of front-end sub-applications corresponding to different user permissions will also be different. For example, in the front-end sub-application associated with insurance products, insurance consumers can only see the insurance products they have purchased, while insurance sales personnel can see the insurance products they have sold (the corresponding distinction can be made through customer information).

[0034] S4. When the loading of the front-end main application is completed, a corresponding first front-end sub-application is obtained from the front-end sub-application set according to the user role.

[0035] S5. Start the first front-end sub-application and load the corresponding front-end page in the first front-end sub-application according to the user's authority.

[0036] As a preferred implementation, please continue to refer to Figure 3 , Figure 3 : is a schematic diagram of the execution flow of the loading subsystem of the Web system front-end page loading method provided in the embodiment of the present application, such as Figure 3 As shown, after step S5, the following steps are also included:

[0037] S51. Start the front-end tracking subsystem, front-end monitoring subsystem, and intelligent preloading subsystem corresponding to the target Web system.

[0038] S52. Monitor the corresponding page routing information from the user's browser through the front-end monitoring subsystem, and report the page routing information to the front-end embedding subsystem.

[0039] As an example, in the front-end monitoring subsystem of an insurance claims Web system, the hashchange / history API of the user's browser is used to monitor the routing information before and after each page jump (such as app_id, previous_page, current_page, user_id, timestamp, etc.), and the monitored routing change information is reported to the corresponding tracking system.

[0040] S53. The front-end embedding subsystem stores the user's user information and the corresponding page routing information to the intelligent preloading subsystem.

[0041] Among them, the above-mentioned front-end tracking subsystem not only stores the user information and corresponding page routing information of the user, but also can store the user behavior information when the user operates the front-end page of the above-mentioned Web system. For example, in the front-end tracking subsystem of a certain insurance sales Web system, the user's stay time on the page of each type of insurance product and the corresponding next jump page information are stored.

[0042] S54. The intelligent preloading subsystem uses a preset big data search and analysis engine to process the user information and the corresponding page routing information to obtain a corresponding preloading page.

[0043] As another preferred embodiment, please continue to refer to Figure 4 , Figure 4 is a schematic diagram of the execution flow of monitoring user roles in the Web system front-end page loading method provided in the embodiment of the present application, such as Figure 4 As shown, after step S5, the following steps are also included:

[0044] S61. Monitor whether the user role of the user has changed. If the user role has changed, obtain a new user role corresponding to the user and corresponding new user permissions.

[0045] S62: Acquire a corresponding second front-end sub-application from the front-end sub-application set according to the new user role.

[0046] The new user role can correspond to different front-end sub-applications than the old user role, so when the user role of the user changes, if the corresponding front-end sub-application is not loaded, it is necessary to obtain the corresponding second front-end sub-application from the front-end sub-application set. At the same time, if the front-end sub-application corresponding to the new user role has the same part as the front-end sub-application corresponding to the old user role, it does not need to be loaded repeatedly.

[0047] S63: Start the second front-end sub-application, and load the corresponding front-end page in the second front-end sub-application according to the new user's authority.

[0048] S64: Control the corresponding first front-end sub-application to enter a dormant state, or uninstall the corresponding first front-end sub-application.

[0049] Among them, after the user role changes, if the corresponding change is reversible, for example, the user can switch between the new user role and the old user role, then the corresponding first front-end sub-application is controlled to enter a dormant state, which can avoid frequent initialization and loading of the front-end sub-application when the user role is switched, resulting in the freezing of the front page of the Web system. At the same time, if the above-mentioned user role change is temporarily irreversible (for example, the role of the manager in some financial systems has been downgraded, and the corresponding authority is reduced. If the original management authority needs to be restored, certain procedures or processing procedures are required), then the corresponding first front-end sub-application can be uninstalled, because the corresponding new user role is no longer associated with the corresponding front-end sub-application, and after uninstalling the corresponding front-end sub-application, system resources can be further released to reduce the front-end pressure of the Web system.

[0050] As an optional implementation, after the above step S54, it may also include: first, obtaining the resource script path corresponding to the preloaded page, for example, obtaining the corresponding resource script path from the Nginx server, and downloading the corresponding preloaded resource file to the user's browser according to the resource script path. Determine whether the preloaded page belongs to the first front-end sub-application. If not, obtain the corresponding third front-end sub-application from the front-end sub-application set according to the preloaded page, that is, when the front-end sub-application corresponding to the page to be preloaded is not started, it is necessary to start the corresponding front-end sub-application first. If the user's subsequent actual operation is to jump to the above-mentioned preloaded page, it is not necessary to start the corresponding front-end sub-application (already pre-started in advance) when the user initiates a jump request, further shortening the loading time of the front-end page of the Web system. Start the third front-end sub-application, and when receiving the user's loading request for the preloaded page, load the corresponding front-end page in the user's browser according to the preloaded resource file. For example, in a certain insurance sales Web system, when the user's stay time on a certain insurance product reaches a preset threshold, the corresponding insurance product purchase front-end sub-application can be loaded in advance. When the user clicks on the corresponding insurance product to purchase, the loading speed of the insurance purchase front-end page can be increased.

[0051] As an optional implementation, the above step S54 may specifically include: first, obtaining the corresponding user role and time interval according to the user information. Then, setting the user information, user role and time interval as weight factors, performing aggregate analysis on the page routing information, and obtaining the next access probability of the user corresponding to the user information to different front-end pages of the Web system when in different user roles, that is, the page that the user will visit next can be predicted, and the front-end page with the highest probability of next access can be preloaded in advance, and the above access probability analyst is based on the user information, user role, and historical page routing information. Finally, the front-end page with the highest probability of next access is set as the preloaded page.

[0052] As a preferred embodiment, the above-mentioned intelligent preloading subsystem also includes a preset preloading rule. Before the above-mentioned setting of the front-end page with the highest probability of access in the next step as the preloading page, it can also include: first, parsing the preloading rule to obtain the corresponding business process node. For example, in the business process of insurance claims, there may be different business process nodes such as reporting, investigation, damage assessment, and payment of claims. Then, determine the first business process node corresponding to the current front-end page where the user stays in the browser, and determine the second business process node corresponding to the different front-end pages. Finally, if the second business process node is a subsequent process node of the first business process node, and the second business process node is not an adjacent process node of the first business process node, then remove the different front-end pages corresponding to the second business process node. For example, in the above-mentioned insurance claims business process, when the user is in the business process node of reporting or investigating, the next step cannot jump to the business process node of paying the claim.

[0053] As another preferred implementation, before the step of setting the front-end page corresponding to the highest probability of next access as the preloaded page, it may also include: first, clustering the page routing information according to the user role, and determining the page routing information to be analyzed corresponding to the user's current user role according to the clustering result. Then, in the page routing information to be analyzed, the number of occurrences of the current front-end page where the user stays in the browser corresponding to different historical jump pages is counted. For example, in the above-mentioned insurance claim settlement business process, when the user is at the business process node of the loss assessment, statistics show that more than 70% of users will return to jump to the front-end subpage corresponding to the investigation process business node to verify the specific investigation details data. Finally, the next access probability is recalculated according to the number of occurrences and the preset probability increase rule, wherein the maximum number of occurrences corresponds to the maximum probability increase value, that is, the above-mentioned next access probability is adjusted according to the historical jump data of the same user role.

[0054] The Web system front-end page loading method provided in the embodiment of the present application partially loads the corresponding front-end sub-application according to the user role and user authority when the Web system front-end page is initially loaded, without loading all system resources, thereby improving the first screen performance of the Web system front-end page and reducing the loading time of the Web system front-end page. In addition, by predicting the user's subsequent page loading probability, the front-end page with a high access probability is preloaded, further reducing the loading time of subsequent pages, which not only improves the user experience, but also improves the operating efficiency of the Web system.

[0055] Please continue reading Figure 5 , Figure 5 : is a system structure diagram of a front-end page loading device of a Web system provided in an embodiment of the present application, such as Figure 5 As shown, the device includes: a main application loading module 51, a sub-application collection module 52, a user role and permission module 53, a sub-application loading module 54 and a sub-application page module 55.

[0056] The main application loading module 51 is used to load the corresponding front-end main application through the boot module of the Web system in the browser when receiving a loading request initiated by the user to the target Web system in the browser.

[0057] The sub-application set module 52 is used to obtain the front-end sub-application set corresponding to the front-end main application;

[0058] The user role and permission module 53 is used to obtain the user role corresponding to the user and the user permission corresponding to the user role.

[0059] The sub-application loading module 54 is used for acquiring a corresponding first front-end sub-application from the front-end sub-application set according to the user role when the front-end main application is loaded.

[0060] The sub-application page module 55 is used to start the first front-end sub-application and load the corresponding front-end page in the first front-end sub-application according to the user authority.

[0061] As an optional implementation, the front-end page loading device of the Web system also includes a subsystem module, which is used to start the front-end tracking subsystem, front-end monitoring subsystem, and intelligent preloading subsystem corresponding to the target Web system; monitor the corresponding page routing information from the user's browser through the front-end monitoring subsystem, and report the page routing information to the front-end tracking subsystem; store the user information of the user and the corresponding page routing information to the intelligent preloading subsystem through the front-end tracking subsystem; use a preset big data search and analysis engine through the intelligent preloading subsystem to process the user information and the corresponding page routing information to obtain the corresponding preloading page.

[0062] As an optional implementation, the Web system front-end page loading device also includes a user role module, which is used to monitor whether the user role of the user changes. If the user role changes, the new user role corresponding to the user and the corresponding new user permissions are obtained; according to the new user role, the corresponding second front-end sub-application is obtained from the front-end sub-application set; the second front-end sub-application is started, and the corresponding front-end page in the second front-end sub-application is loaded according to the new user permissions; the corresponding first front-end sub-application is controlled to enter a dormant state, or the corresponding first front-end sub-application is uninstalled.

[0063] As an optional implementation, the subsystem module is also used to obtain the resource script path corresponding to the preloaded page, download the corresponding preloaded resource file to the user's browser according to the resource script path; determine whether the preloaded page belongs to the first front-end sub-application; if not, obtain the corresponding third front-end sub-application from the front-end sub-application set according to the preloaded page; start the third front-end sub-application, and when receiving the user's loading request for the preloaded page, load the corresponding front-end page in the user's browser according to the preloaded resource file.

[0064] As an optional implementation, the subsystem module is also specifically used to obtain the corresponding user role and time interval based on the user information; set the user information, the user role and the time interval as weight factors, perform aggregation analysis on the page routing information, and obtain the next access probability of the user corresponding to the user information to different front-end pages of the Web system when the user has different user roles; set the front-end page with the highest next access probability as the preloaded page.

[0065] As an optional implementation, the intelligent preloading subsystem also includes preset preloading rules, and the subsystem module is also used to parse the preloading rules to obtain corresponding business process nodes; determine the first business process node corresponding to the current front-end page where the user stays in the browser; determine the second business process node corresponding to the different front-end page; if the second business process node is a subsequent process node of the first business process node, and the second business process node is not an adjacent process node of the first business process node, then remove the different front-end page corresponding to the second business process node.

[0066] As an optional implementation, the subsystem module is also used to cluster the page routing information according to the user role, and determine the page routing information to be analyzed corresponding to the user's current user role according to the clustering result; count the number of occurrences of different historical jump pages corresponding to the current front-end page where the user stays in the browser in the page routing information to be analyzed; recalculate the next access probability according to the number of occurrences and a preset probability increase rule, wherein the largest number of occurrences corresponds to the largest probability increase value.

[0067] It should be noted that the above-mentioned Web system front-end page loading device can execute the Web system front-end page loading method provided in the embodiment of the present application, and has the corresponding functional modules and beneficial effects of the execution method. For technical details not fully described in the embodiment of the Web system front-end page loading device, please refer to the Web system front-end page loading method provided in the embodiment of the present application.

[0068] Please continue reading Figure 6 , Figure 6 is a schematic diagram of the hardware structure of an electronic device 600 for executing a method for loading a front-end page of a Web system provided in an embodiment of the present application, such as Figure 6 As shown, the electronic device 600 includes:

[0069] One or more processors 610 and memory 620, Figure 6 A processor 610 is taken as an example.

[0070] The processor 610 and the memory 620 may be connected via a bus or other means. Figure 6 The example of connecting through bus is taken in the following.

[0071] The memory 620, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer executable programs and modules, such as program instructions / modules corresponding to the Web system front-end page loading method in the embodiment of the present application. The processor 610 executes various functional applications and data processing of the server by running the non-volatile software programs, instructions and modules stored in the memory 620, that is, the Web system front-end page loading method in the above method embodiment is implemented.

[0072] The memory 620 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application required by at least one function; the data storage area may store data created according to the use of the front-end page loading device of the Web system, etc. In addition, the memory 620 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 620 may optionally include a memory remotely arranged relative to the processor 610, and these remote memories may be connected to the front-end page loading device of the Web system via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0073] The one or more modules are stored in the memory 620, and when executed by the one or more processors 610, the Web system front-end page loading method in any of the above method embodiments is executed, for example, the above described Figure 2 Steps S1 to S5 of the method, Figure 3 Steps S51 to S54 of the method, Figure 4 Steps S61 to S64 of the method are implemented Figure 5 The functions of modules 51-55 in.

[0074] The above-mentioned product can execute the method provided in the embodiment of the present application, and has the functional modules and beneficial effects corresponding to the execution method. For technical details not fully described in this embodiment, please refer to the method provided in the embodiment of the present application.

[0075] The embodiment of the present application provides a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by one or more processors, such as Figure 6 A processor 610 in the embodiment may enable the one or more processors to execute the web system front-end page loading method in any of the above method embodiments, for example, executing the above described Figure 2 Steps S1 to S5 of the method, Figure 3 Steps S51 to S54 of the method, Figure 4 Steps S61 to S64 of the method are implemented Figure 5 The functions of modules 51-55 in.

[0076] The present application provides a computer program product, wherein the computer program product includes a computer program stored on a non-volatile computer-readable storage medium, wherein the computer program includes program instructions, and when the program instructions are executed by the electronic device, the electronic device is enabled to execute the Web system front-end page loading method in any of the above method embodiments, for example, to execute the above described Figure 2 Steps S1 to S5 of the method, Figure 3 Steps S51 to S54 of the method, Figure 4 Steps S61 to S64 of the method are implemented Figure 5 The functions of modules 51-55 in.

[0077] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0078] Through the description of the above implementation methods, ordinary technicians in this field can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, it can also be implemented by hardware. Ordinary technicians in this field can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the storage medium can be a disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.

[0079] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Under the concept of the present application, the technical features in the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other changes in different aspects of the present application as described above, which are not provided in detail for the sake of simplicity. Although the present application has been described in detail with reference to the aforementioned embodiments, a person of ordinary skill in the art should understand that the technical solutions described in the aforementioned embodiments can still be modified, or some of the technical features can be replaced by equivalents. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for loading a front-end page of a Web system, characterized in that: include: When receiving a loading request initiated by a user to a target Web system in a browser, loading a corresponding front-end main application through a boot module of the Web system in the browser; Obtain a front-end sub-application set corresponding to the front-end main application; Obtain the user role corresponding to the user and the user authority corresponding to the user role; When the front-end main application is loaded, acquiring a corresponding first front-end sub-application from the front-end sub-application set according to the user role; The first front-end sub-application is started, and a corresponding front-end page in the first front-end sub-application is loaded according to the user authority.

2. The method for loading a front-end page of a Web system according to claim 1, characterized in that: After the step of loading the corresponding front-end page of the first front-end sub-application according to the user authority, the method further includes: Start the front-end tracking subsystem, front-end monitoring subsystem, and intelligent preloading subsystem corresponding to the target Web system; Monitor the corresponding page routing information from the user's browser through the front-end monitoring subsystem, and report the page routing information to the front-end tracking subsystem; The user information of the user and the corresponding page routing information are stored in the intelligent preloading subsystem through the front-end embedding subsystem; The intelligent preloading subsystem uses a preset big data search and analysis engine to process the user information and the corresponding page routing information to obtain a corresponding preloading page.

3. The method for loading a front-end page of a Web system according to claim 1, characterized in that: After the step of loading the corresponding front-end page of the first front-end sub-application according to the user authority, the method further includes: Monitor whether the user role of the user has changed, and if so, obtain a new user role corresponding to the user and corresponding new user permissions; According to the new user role, acquiring a corresponding second front-end sub-application from the front-end sub-application set; Start the second front-end sub-application, and load the corresponding front-end page in the second front-end sub-application according to the new user authority; Control the corresponding first front-end sub-application to enter a dormant state, or uninstall the corresponding first front-end sub-application.

4. The method for loading a front-end page of a Web system according to claim 2, characterized in that: After the step of obtaining the corresponding preload page, the method further includes: Obtaining a resource script path corresponding to the preloaded page, and downloading a corresponding preloaded resource file to the user's browser according to the resource script path; Determining whether the preloaded page belongs to the first front-end sub-application; If not, acquiring a corresponding third front-end sub-application from the front-end sub-application set according to the preloaded page; The third front-end sub-application is started, and when a loading request for the preloaded page is received from the user, a corresponding front-end page is loaded in the browser of the user according to the preloaded resource file.

5. The method for loading a front-end page of a Web system according to claim 2, characterized in that: The step of using a preset big data search and analysis engine to process the user information and the corresponding page routing information to obtain a corresponding preloaded page includes: Acquire the corresponding user role and time interval according to the user information; The user information, the user role and the time interval are set as weight factors, and the page routing information is aggregated and analyzed to obtain the next access probability of the user corresponding to the user information to different front-end pages of the Web system when the user roles are different; The front-end page with the highest probability of being accessed next is set as the preloaded page.

6. The method for loading a front-end page of a Web system according to claim 5, characterized in that: The intelligent preloading subsystem further includes a preset preloading rule, and before the step of setting the front-end page with the highest probability of access in the next step as the preloading page, it also includes: Parse the preloaded rules to obtain corresponding business process nodes; Determine a first business process node corresponding to the current front-end page where the user stays in the browser; Determine the second business process node corresponding to the different front-end pages; If the second business process node is a subsequent process node of the first business process node, and the second business process node is not an adjacent process node of the first business process node, then the different front-end page corresponding to the second business process node is removed.

7. The method for loading a front-end page of a Web system according to claim 5, characterized in that: Before the step of setting the front-end page with the highest probability of being accessed in the next step as the preloaded page, the method further includes: Clustering the page routing information according to the user role, and determining the page routing information to be analyzed corresponding to the current user role of the user according to the clustering result; Counting the number of occurrences of different historical jump pages corresponding to the current front-end page where the user stays in the browser in the page routing information to be analyzed; The next access probability is recalculated according to the number of occurrences and a preset probability increase rule, wherein the maximum number of occurrences corresponds to the maximum probability increase value.

8. A web system front-end page loading device, characterized in that: include: The main application loading module is used to load the corresponding front-end main application through the boot module of the Web system in the browser when receiving a loading request initiated by the user to the target Web system in the browser; A sub-application set module, used to obtain a front-end sub-application set corresponding to the front-end main application; A user role and permission module, used to obtain the user role corresponding to the user, and the user permission corresponding to the user role; A sub-application loading module, configured to obtain a corresponding first front-end sub-application from the front-end sub-application set according to the user role when the front-end main application is loaded; The sub-application page module is used to start the first front-end sub-application and load the corresponding front-end page in the first front-end sub-application according to the user authority.

9. An electronic device, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the Web system front-end page loading method according to any one of claims 1 to 7.

10. A non-volatile computer-readable storage medium, characterized in that: The non-volatile computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are executed by an electronic device, the electronic device executes the Web system front-end page loading method according to any one of claims 1 to 7.

Images