Micro-front-end integrated configuration method, device and equipment for reinsurance system

Abstract

The invention discloses a micro-front-end integrated configuration method, device and equipment for a reinsurance system, and the method comprises the steps: registering a sub-application in a base entrance file of a business micro-service through configuring sub-application parameters of a charge and payment micro-service and an interest account micro-service; in a component directory folder of the business micro-service, newly creating page files corresponding to the charge and payment micro-service and the interest account micro-service; adding a logical judgment rule for independent operation of the charge and payment micro-service and the interest account micro-service or operation in a preset environment in the sub-application entry file, and defining a basic access path of the packaged sub-application resources in a browser; and based on the base entry file, the component directory file and the sub-application entry file, in the front-end application of the business micro-service, integrating sub-application interfaces of the charge and payment micro-service and the interest account micro-service. According to the invention, the business system, the charging and paying system and the interest account micro-service which are independently deployed and run can be integrated, and unified access of the three is realized.

Description

Technical Field

[0001] The present application relates to the field of insurance technology, specifically to the field of reinsurance system management technology, and in particular to a micro-front-end integrated configuration method, device, equipment and medium for a reinsurance system. Background Art

[0002] The reinsurance system is a specialized electronic processing system used by insurance companies to carry out reinsurance business, which mostly includes core business operation systems, customer service systems, information security and operation and maintenance and other basic systems. With the continuous changes in the competitive environment and customer needs, the reinsurance business is constantly expanding. Insurance companies need to complete many new reinsurance businesses through the reinsurance system. Therefore, they need to rely on computer technology to continuously optimize the architecture and functions of the reinsurance system, so that the reinsurance system has better security, operability and scalability.

[0003] Regarding reinsurance business, insurance business in which the insured and the insurer directly enter into an insurance contract is usually regarded as the original insurance, and the business behavior of the insurer signing a reinsurance contract with other insurers on the basis of the original insurance is called reinsurance. Through the reinsurance business, part of the risks and responsibilities underwritten by the insurer itself can be shared with other insurers. In practice, practitioners realize the functions and services required in the reinsurance business based on the insurance business data of the original insurance and the information data of the reinsurance contract through the various subsystems and system modules provided by the reinsurance system platform.

[0004] In the existing reinsurance system, the subsystems frequently used by staff mainly include the business subsystem, the payment and collection subsystem, and the interest account subsystem. However, due to technical limitations, the business subsystem, the payment and collection subsystem, and the interest account subsystem have always been logged in through their respective login addresses. After successful login, their respective menus are displayed, and the data processing processes are independent of each other. It is difficult for users to quickly understand the relationship between different types of data (such as parallel management of business data, the overall relationship between business bills and settlement statements and payment and collection statements), and it is necessary to log in and jump multiple times between these subsystems during business processing. People are often required to repeat operations and confirm repeatedly, which makes the business process, which is already highly complex, more cumbersome, the business processing efficiency is low, and it is prone to errors, and it is highly dependent on the subsequent business data verification. Summary of the invention

[0005] In view of this, the embodiments of the present application provide a micro-front-end integrated configuration method, device, equipment, medium and product for a reinsurance system, which can build a unified platform management interface, integrate independently deployed and independently operated business systems, payment and collection systems, and interest account microservice systems, achieve unified access to the three, and improve business processing efficiency.

[0006] In a first aspect, an embodiment of the present application provides a micro-front-end integration configuration method for a reinsurance system, which is applied to a reinsurance system. The reinsurance system includes a business microservice, a payment and collection microservice, and an interest account microservice. The method includes: using the business microservice as a base application, and the payment and collection microservice and the interest account microservice as sub-applications, and registering the sub-applications by configuring the sub-application parameters of the payment and collection microservice and the interest account microservice in the base entry file of the business microservice; creating page files corresponding to the payment and collection microservice and the interest account microservice in the component directory folder of the business microservice, wherein the page files are used to undertake the sub-application interfaces; in the sub-application entry files of the payment and collection microservice and the interest account microservice, respectively adding logical judgment rules for the payment and collection microservice and the interest account microservice to run independently or in a preset environment, and defining the basic access paths of the sub-application resources of the packaged payment and collection microservice and the interest account microservice in the browser; based on the base entry file, the component directory file, and the sub-application entry file, integrating the sub-application interfaces of the payment and collection microservice and the interest account microservice in the front-end application of the business microservice.

[0007] In some implementable methods of the first aspect, based on the base entry file, the component directory file and the sub-application entry file, the sub-application interfaces of the payment and collection microservice and the interest account microservice are integrated in the front-end application of the business microservice, including: based on the sub-application parameters of the payment and collection microservice and the interest account microservice, a first menu module and a second menu module are added to the front-end application of the business microservice, wherein the first menu module is associated with the payment and collection microservice, and the second menu module is associated with the interest account microservice; in response to an access operation to the first menu module, based on the first configuration parameters for the payment and collection microservice in the base entry file, the component directory file and the sub-application entry file, the static resources of the payment and collection microservice are loaded, and the sub-application interface corresponding to the payment and collection microservice is displayed; in response to an access operation to the second menu module, based on the second configuration parameters for the interest account microservice in the base entry file, the component directory file and the sub-application entry file, the static resources of the interest account microservice are loaded, and the sub-application interface corresponding to the interest account microservice is displayed.

[0008] In some implementable methods of the first aspect, based on the base entry file, the component directory file and the sub-application entry file, in the front-end application of the business microservice, the sub-application interfaces of the payment and collection microservice and the interest account microservice are integrated, including: based on the application parameters of the business microservice, and the sub-application parameters of the payment and collection microservice and the interest account microservice, a to-do reminder management module is added to the front-end application of the business microservice, wherein the to-do reminder management module integrates the business data of the business microservice, the payment and collection data of the payment and collection microservice, and the interest account data of the interest account microservice; in response to the access operation to the to-do reminder management module, the sub-menu modules associated with each microservice are displayed; in response to the access operation to the sub-menu module of a single microservice, based on the configuration parameters for the single microservice in the base entry file, the component directory file and the sub-application entry file, the corresponding data of the single microservice is loaded in the sub-application interface of the single microservice.

[0009] In some possible implementations of the first aspect, the business microservice is used to generate billing data based on business data, and data association is achieved between the business microservice, the payment and collection microservice, and the interest account microservice through the billing data. The business microservice transmits the billing data to the payment and collection microservice through the API interface provided by the payment and collection microservice to realize bill settlement management and tax bill management.

[0010] In some implementable methods of the first aspect, in the base entry file of the business microservice, the sub-application is registered by configuring the sub-application parameters of the payment and collection microservice and the interest account microservice, including: passing in the sub-application parameters of the payment and collection microservice and the interest account microservice by calling the registration microservice method of the target micro-front-end architecture; wherein the sub-application parameters include the sub-application name, the sub-application startup address, the base-hosted sub-application container name, and the basic routing address.

[0011] In some implementable methods of the first aspect, the method also includes: in the sub-application entry files of the payment and collection microservice and the interest account microservice, adding a mount function method and an unmount function method, wherein the mount function method and the unmount function method are used to implement sub-application rendering and sub-application uninstallation; adjusting the routing processing method of the business microservice, the payment and collection microservice, and the interest account microservice from the hash mode to the history mode; adjusting the method for obtaining user permissions for the payment and collection microservice and the interest account microservice, and if it is determined that the current operation is in a preset environment, obtaining user permissions from the cookie of the business microservice.

[0012] In some possible implementations of the first aspect, data is exchanged between the microservices through a REST API, and the front-end application includes a first menu module associated with the payment and collection microservice, and a second menu module associated with the interest account microservice. Based on the base entry file, the component directory file, and the sub-application entry file, the sub-application interfaces of the payment and collection microservice and the interest account microservice are integrated in the front-end application of the business microservice, including: in response to an access operation to the first menu module, the URL changes, and the matching logic corresponding to the target micro-front-end architecture is automatically triggered, and the corresponding payment and collection microservice is activated by matching the basic routing address configured by the base entry file; the HTML entry of the payment and collection microservice is loaded through the target micro-front-end architecture, and the page is jumped to the sub-application interface of the payment and collection microservice based on the HTML entry, and the publicPath attribute of the webpack is dynamically configured according to the global variables injected by the target micro-front-end architecture to load the static resources of the payment and collection microservice.

[0013] In a second aspect, an embodiment of the present application provides a micro-front-end integrated configuration device for a reinsurance system, which is applied to a reinsurance system. The reinsurance system includes a business microservice, a payment and collection microservice, and an interest account microservice. The device includes: a registration module, which is used to use the business microservice as a base application, and the payment and collection microservice and the interest account microservice as sub-applications. In the base entry file of the business microservice, the sub-application is registered by configuring the sub-application parameters of the payment and collection microservice and the interest account microservice; a new creation module, which is used to create page files corresponding to the payment and collection microservice and the interest account microservice in the component directory folder of the business microservice, wherein the page file is used to undertake the sub-application interface; a sub-application configuration module, which is used to add logical judgment rules for the payment and collection microservice and the interest account microservice to run independently or in a preset environment in the sub-application entry files of the payment and collection microservice and the interest account microservice, and define the basic access path of the sub-application resources of the packaged payment and collection microservice and the interest account microservice in the browser; an integration module, which is used to integrate the sub-application interfaces of the payment and collection microservice and the interest account microservice in the front-end application of the business microservice based on the base entry file, the component directory file, and the sub-application entry file.

[0014] In some implementable methods of the second aspect, the integration module is specifically used to: based on the sub-application parameters of the payment and collection microservice and the interest account microservice, add a first menu module and a second menu module in the front-end application of the business microservice, wherein the first menu module is associated with the payment and collection microservice, and the second menu module is associated with the interest account microservice; in response to an access operation to the first menu module, based on the first configuration parameters for the payment and collection microservice in the base entry file, the component directory file, and the sub-application entry file, load the static resources of the payment and collection microservice, and display the sub-application interface corresponding to the payment and collection microservice; in response to an access operation to the second menu module, based on the second configuration parameters for the interest account microservice in the base entry file, the component directory file, and the sub-application entry file, load the static resources of the interest account microservice, and display the sub-application interface corresponding to the interest account microservice.

[0015] In some implementable methods of the second aspect, the integration module is specifically used to: based on the application parameters of the business microservice, and the sub-application parameters of the payment and collection microservice and the interest account microservice, add a to-do reminder management module in the front-end application of the business microservice, wherein the to-do reminder management module integrates the business data of the business microservice, the payment and collection data of the payment and collection microservice, and the interest account data of the interest account microservice; in response to an access operation to the to-do reminder management module, display the sub-menu modules associated with each microservice; in response to an access operation to the sub-menu module of a single microservice, load the corresponding data of the single microservice in the sub-application interface of the single microservice based on the configuration parameters for the single microservice in the base entry file, the component directory file, and the sub-application entry file.

[0016] In some possible implementation methods of the second aspect, the business microservice is used to generate billing data based on business data, and data association is achieved between the business microservice, the payment and collection microservice, and the interest account microservice through the billing data. The business microservice transmits the billing data to the payment and collection microservice through the API interface provided by the payment and collection microservice to realize bill settlement management and tax bill management.

[0017] In some implementation methods of the second aspect, the registration module is specifically used to: pass in the sub-application parameters of the payment and collection microservice and the interest account microservice by calling the registration microservice method of the target micro-frontend architecture; wherein the sub-application parameters include the sub-application name, the sub-application startup address, the base-hosted sub-application container name and the basic routing address.

[0018] In some implementable methods of the second aspect, the device also includes: a sub-application configuration module, which is also used to add a mount function method and an unmount function method in the sub-application entry files of the payment and collection microservice and the interest account microservice, wherein the mount function method and the unmount function method are used to implement sub-application rendering and sub-application uninstallation; a routing configuration module, which is used to adjust the routing processing method of the business microservice, the payment and collection microservice, and the interest account microservice from the hash mode to the history mode; the sub-application configuration module is also used to adjust the method for obtaining user permissions for the payment and collection microservice and the interest account microservice, and if it is determined that the current operation is in a preset environment, the user permissions are obtained from the cookie of the business microservice.

[0019] In some implementable methods of the second aspect, each microservice interacts with data through a REST API, and the front-end application includes a first menu module associated with the payment and collection microservice, and a second menu module associated with the interest account microservice. The integration module is specifically used to: in response to an access operation to the first menu module, the URL changes, and the matching logic corresponding to the target micro-front-end architecture is automatically triggered, and the corresponding payment and collection microservice is activated by matching the basic routing address configured by the base entry file; the HTML entry of the payment and collection microservice is loaded through the target micro-front-end architecture, and based on the HTML entry, it jumps to the sub-application interface of the payment and collection microservice, and dynamically configures the publicPath attribute of the webpack according to the global variables injected by the target micro-front-end architecture to load the static resources of the payment and collection microservice.

[0020] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the steps of the micro-front-end integration configuration method for a reinsurance system as in the first aspect are implemented.

[0021] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the steps of the micro-frontend integration configuration method for a reinsurance system according to the first aspect are implemented.

[0022] In a fifth aspect, an embodiment of the present application provides a computer program product, which is stored in a non-volatile storage medium. When the computer program product is executed by a processor, it implements the steps of the micro-front-end integration configuration method for a reinsurance system as in the first aspect.

[0023] In a sixth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface and the processor are coupled, and the processor is used to run a program or instruction to implement the steps of the micro-front-end integrated configuration method for a reinsurance system as in the first aspect.

[0024] The present application provides a micro-front-end integrated configuration method, apparatus, equipment, medium and product for a reinsurance system, which takes a business microservice as a base application, and a payment and collection microservice and an interest account microservice as sub-applications. In the base entry file of the business microservice, the payment and collection microservice and the interest account microservice are registered as sub-applications in the business microservice by configuring the sub-application parameters of the payment and collection microservice and the interest account microservice; in the component directory folder of the business microservice, a page file corresponding to the payment and collection microservice and the interest account microservice is newly created to undertake the sub-application interface in the front-end application of the business microservice; in the sub-application entry file of the payment and collection microservice and the interest account microservice, the processing logic before loading the sub-application is configured by adding logical judgment rules for the payment and collection microservice and the interest account microservice to run independently or in a preset environment, and the basic access path of the sub-application resources of the packaged payment and collection microservice and the interest account microservice in the browser is defined to load the sub-application static resources in the front-end application of the business microservice. Through the above configuration operations, with the business microservice as the base application, the payment and collection microservice and the interest account microservice as sub-applications, the sub-application interfaces of the payment and collection microservice and the interest account microservice are integrated in the front-end application of the business microservice, so as to transform the front-end application interface of the business microservice into a unified platform interface. Based on this, operators can uniformly access the business microservices, payment and collection microservices, and interest account microservices, reduce repeated operations, and can easily confirm and operate different types of data information, improve the fluency of business processes, improve the efficiency of personnel business processing, and optimize the overall performance of the reinsurance system. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the technical solution of the embodiments of the present application, the following briefly introduces the drawings in the embodiments of the present application.

[0026] Figure 1 It is a flowchart of a micro-frontend integration configuration method for a reinsurance system provided by an embodiment of the present application; Figure 2 is a flowchart of a micro-frontend integration configuration method for a reinsurance system provided by another embodiment of the present application; Figure 3 is a flowchart of a micro-frontend integration configuration method for a reinsurance system provided by yet another embodiment of the present application; Figure 4 is an exemplary schematic diagram of an application interface of a front-end application provided in an embodiment of the present application; Figure 5 is a flowchart of a micro-frontend integration configuration method for a reinsurance system provided by yet another embodiment of the present application; Figure 6 is an exemplary schematic diagram of an application interface of a front-end application provided by another embodiment of the present application; Figure 7 is a flowchart of a micro-frontend integration configuration method for a reinsurance system provided by yet another embodiment of the present application; Figure 8 is a flowchart of a micro-frontend integration configuration method for a reinsurance system provided by yet another embodiment of the present application; Fig. 9 is a flowchart of a micro-frontend integration configuration method for a reinsurance system provided by yet another embodiment of the present application; Fig.10 is a structural schematic diagram of a reinsurance system provided in an embodiment of the present application; Fig.11 It is a structural schematic diagram of a micro-front-end integrated configuration device for a reinsurance system provided in an embodiment of the present application; Fig.12 It is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] The principles and spirit of the present application will be described below with reference to several exemplary embodiments. It should be understood that the purpose of providing these embodiments is to make the principles and spirit of the present application clearer and more thorough, so that those skilled in the art can better understand and implement the principles and spirit of the present application. The exemplary embodiments provided herein are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments herein, all other embodiments obtained by ordinary technicians of the art without creative work are within the scope of protection of this application.

[0028] In this document, terms such as first, second, third, etc. are only used to distinguish one entity (or operation) from another entity (or operation), but not to require or imply any order or relationship between these entities (or operations).

[0029] The following is a brief description of the concepts and technical terms that may be involved in the embodiments of the present application.

[0030] Application architecture: Application architecture refers to the relationship and interaction between the various parts that make up an application. Application architecture usually includes components at different levels such as the front-end, back-end, and database. Common application architecture patterns include MVC (Model-View-Controller), MVP (Model-View-Presenter), MVVM (Model-View-ViewModel), etc. When designing an application architecture, factors such as application requirements, performance, maintainability, and scalability need to be considered. A reasonable application architecture can reduce development costs, improve development efficiency, and is also conducive to the subsequent maintenance and expansion of the application.

[0031] Micro frontend: Micro frontend is an architectural design method that splits the front-end application into smaller, more independent parts, each of which can be independently developed, deployed, and maintained. This architectural design allows multiple teams to independently develop their own front-end modules and then combine them into a unified application.

[0032] VUE: Vue (commonly known as Vue.js) is a popular front-end JavaScript framework for building interactive web interfaces. The goal of Vue.js is to make it easier to build modern web applications through simple and easy-to-use APIs and responsive data binding.

[0033] JS: JavaScript (JS for short) is a scripting language widely used in Web front-end development, mainly used to implement interactive functions, dynamic effects and data processing of web pages. JavaScript is an advanced, interpreted language, which together with HTML and CSS constitutes the three basic technologies of Web development.

[0034] H5: "H5" is usually the abbreviation of HTML5 (HyperText Markup Language). HTML5 is the latest version of HTML, which introduces many new features and APIs for implementing richer and more interactive web applications.

[0035] ElementUI: Element UI is a component library based on Vue.js for quickly building modern web applications. Element UI provides a set of rich and flexible UI components, allowing developers to quickly build various interfaces with rich functions and good user experience.

[0036] In the following, in conjunction with the accompanying drawings, the micro-frontend integration configuration method for the reinsurance system provided by the embodiment of the present application is described in detail through specific embodiments and application scenarios.

[0037] Figure 1 1 is a flow chart of a micro-frontend integrated configuration method for a reinsurance system provided by an embodiment of the present application. The execution subject of the micro-frontend integrated configuration method for a reinsurance system may be a reinsurance system, and the reinsurance system may be a processing system for reinsurance business. The reinsurance system is designed to be divided into a front-end and back-end separation architecture, which is composed of a front-end web application and a middle and back-end service application. The middle and back-end service application may include a business microservice, a payment and collection microservice, and an interest account microservice.

[0038] The following uses the reinsurance system as an example of the execution subject of the micro-frontend integration configuration method for the reinsurance system to illustrate the micro-frontend integration configuration method for the reinsurance system of the present application. It should be noted that the above execution subjects and application scenarios do not constitute a limitation on the present application.

[0039] like Figure 1 As shown, the micro-frontend integration configuration method for a reinsurance system provided in an embodiment of the present application may include steps 110 to 140.

[0040] Step 110, use the business microservice as the base application, the payment and collection microservice and the interest account microservice as sub-applications, and register the sub-applications by configuring the sub-application parameters of the payment and collection microservice and the interest account microservice in the base entry file of the business microservice; Step 120: Create new page files corresponding to the payment and collection microservice and the interest account microservice in the component directory folder of the business microservice; Step 130, in the sub-application entry files of the payment and collection microservice and the interest account microservice, respectively add the logic judgment rules for the payment and collection microservice and the interest account microservice to run independently or in a preset environment, and define the basic access path of the sub-application resources of the packaged payment and collection microservice and the interest account microservice in the browser; Step 140, based on the base entry file, the component directory file and the sub-application entry file, the sub-application interfaces of the payment and collection microservice and the interest account microservice are integrated in the front-end application of the business microservice.

[0041] The micro-frontend integration configuration method for the reinsurance system provided in the embodiment of the present application uses the business microservice as the base application, and the payment and collection microservice and the interest account microservice as sub-applications. In the base entry file of the business microservice, the payment and collection microservice and the interest account microservice are registered as sub-applications in the business microservice by configuring the sub-application parameters of the payment and collection microservice and the interest account microservice; in the component directory folder of the business microservice, a page file corresponding to the payment and collection microservice and the interest account microservice is newly created to host the sub-application interface in the front-end application of the business microservice; in the sub-application entry file of the payment and collection microservice and the interest account microservice, the processing logic before loading the sub-application is configured by adding logical judgment rules for the payment and collection microservice and the interest account microservice to run independently or in a preset environment, and the basic access path of the sub-application resources of the packaged payment and collection microservice and the interest account microservice in the browser is defined to load the sub-application static resources in the front-end application of the business microservice. Based on this, through the above configuration operations, with the business microservice as the base application, the payment and collection microservice and the interest account microservice as sub-applications, the sub-application interfaces of the payment and collection microservice and the interest account microservice are integrated in the front-end application of the business microservice. That is, the front-end application interface of the business microservice is transformed into a unified platform management interface to achieve unified access to the business microservice, the payment and collection microservice, and the interest account microservice, meeting the requirements of user system integration and user experience consistency.

[0042] The specific implementation of the above steps will be described in detail below in conjunction with specific embodiments.

[0043] Involving step 110, the business microservice is used as the base application, and the payment and collection microservice and the interest account microservice are used as sub-applications. In the base entry file of the business microservice, the sub-applications are registered by configuring the sub-application parameters of the payment and collection microservice and the interest account microservice.

[0044] In step 110, the business system is an insurance core system, so the business microservice is used as the base application (i.e., the main application), and by introducing the target micro-frontend architecture, the base entry file (main.js) is modified. On the basis of the business microservice as the base application, the payment microservice and the interest account microservice are registered as sub-applications, wherein the target micro-frontend architecture can be the qiankun architecture. The database in the reinsurance system can use postgresql.

[0045] In some embodiments of the present application, the above step 110 may specifically include: passing in the sub-application parameters of the payment and collection microservice and the interest account microservice by calling the registration microservice method of the target micro-frontend architecture.

[0046] Among them, the registration microservice method can be registerMicroApps; the sub-application parameters include the sub-application name name, the sub-application startup address entry, the base hosting sub-application container name container and the basic routing address activeRule, and the basic routing address is the unique basic routing address that matches the sub-application.

[0047] For example, for the sub-application name field, the payment and collection microservice can be configured as / applyRzsf, and the interest account microservice can be configured as / rbzproj.

[0048] Involving step 120, in the component directory folder of the business microservice, new page files corresponding to the payment and collection microservice and the interest account microservice are created.

[0049] In step 120, the page file is used to undertake the sub-application interface, wherein the component directory folder may be the src / components folder, the page file corresponding to the payment microservice is the applyRzsf.vue page, and the page file corresponding to the interest account microservice is the rbzproj.vue page.

[0050] In some embodiments of the present application, step 120 may also include: configuring the node ID on which the page files of the payment and collection microservice and the interest account microservice need to be mounted.

[0051] Specifically, it is to mount a file system or data storage to a specific node or location so that it can be accessed in the operating system. This process involves mounting a remote file system or storage resource to a directory on the local system, so that users can access these remote resources through the local file system interface. The setting of the mount point includes specifying a name (i.e., node ID), which is used to identify the mount point for reference and management in the system. The process of creating and configuring a mount point varies depending on the file system and mounting requirements, but the basic steps are roughly the same, including selecting the mount point location, configuring network access permissions, and specifying the mount point name.

[0052] Exemplarily, the configuration operation of the node ID that needs to be mounted may specifically include: Configure the sub-application page hidden routing component:()=>import("@ / components / @ / views / applyRzsf.vue") and component: () =>import("@ / components / @ / views / rbzproj.vue") in the index.js file under the src / router folder; Configure the dom node for inserting the sub - application in App.vue. The node id is the same as the container value during registration, <!-- Sub - application location -->.

[0053] Involve step 130. In the sub - application entry files of the payment and collection microservice and the interest account microservice, add the logical judgment rules for the independent operation of the payment and collection microservice and the interest account microservice or their operation in a pre - set environment, and define the basic access paths of the sub - application resources of the payment and collection microservice and the interest account microservice in the browser after packaging.

[0054] In step 130, in the sub - application entry file of the payment and collection microservice, configure the logical judgment rules for the independent operation of the payment and collection microservice or its operation in a pre - set environment; in the sub - application entry file of the interest account microservice, configure the logical judgment rules for the independent operation of the interest account microservice or its operation in a pre - set environment; the logical judgment rules are used to indicate the loading logic or processing logic of the microservice, and the pre - set environment can be the qiankun environment.

[0055] Specifically, by adding a public - path.js file to the sub - application entry files of both the payment and collection microservice and the interest account microservice, adding a runtime publicPath method, dynamically setting the publicPath property of Webpack, and setting the basic access path of the resources after Webpack packaging in the browser to: webpack_public_path = window.INJECTED_PUBLIC_PATH_BY_QIANKUN.

[0056] In this way, the configuration of the basic access paths of the sub - application resources of the payment and collection microservice and the interest account microservice in the browser can be completed, and the common paths of the sub - application resources of the payment and collection microservice and the interest account microservice can be defined, so that the sub - application can correctly load static resources in the pre - set environment.

[0057] The public path of sub-application resources refers to a resource access path provided for sub-applications in the micro-frontend architecture, which allows resources to be shared between the main application and the sub-application, ensuring that the sub-application can correctly load and access the static resources it needs. The setting of this path is crucial to the normal operation of the micro-frontend architecture, because it involves how the sub-application loads necessary resources from the main application, such as JavaScript files, CSS style sheets, pictures, etc. In the micro-frontend architecture, sub-applications are usually designed as units that can be deployed and run independently, but they still need to load some shared resources from the main application. These resources may include style sheets, script files, pictures, etc., which are essential for the correct display and functional implementation of the sub-application. By defining the public path of sub-application resources, it is possible to ensure that these resources are correctly loaded into the sub-application, thereby achieving the flexibility and scalability of the micro-frontend architecture. Specifically, this usually involves configuring the routing and resource loading mechanism of the main application to correctly point to the resources of the sub-application. For example, by configuring the routing rules of the main application, the entry point of the sub-application can be specified, and then the resources of the sub-application can be loaded. In addition, specific techniques or tools can be used to manage the loading and caching of these resources to ensure efficient resource utilization and optimized performance.

[0058] In some embodiments of the present application, Figure 2 is a flow chart of a micro-frontend integrated configuration method for a reinsurance system provided by another embodiment of the present application. Before the above step 140, the method may also include Figure 2 Steps 210 to 230 are shown.

[0059] Step 210: Add a mount function method and an unmount function method in the sub-application entry files of the payment and collection microservice and the interest account microservice, wherein the mount function method and the unmount function method are used to implement sub-application rendering and sub-application uninstallation; Step 220: adjust the routing processing mode of the business microservice, the payment and collection microservice, and the interest account microservice from the hash mode to the history mode; Step 230, adjust the method of obtaining user permissions for the payment and collection microservice and the interest account microservice. If it is determined that the current operation is in the preset environment, obtain the user permissions from the cookie of the business microservice.

[0060] Specifically, an instance of a sub-application is created through the mount function, and the instance is mounted at a corresponding location. The newly added mount function method may include: executing the render() method, which is executed each time the sub-application is mounted on a page; the newly added unmount function method may include: uninstalling the sub-application instance, and leaving the sub-application page route when the page url changes. The mount function method and the unmount function method are used to implement sub-application rendering and sub-application uninstallation.

[0061] In front-end development, Vue.js provides two modes for processing routes: hash mode and history mode. Hash mode: Use the hash part of the URL (the part after the # mark) to simulate a complete URL. Therefore, in hash mode, the path will not change, but JavaScript can be used to monitor hash changes and process accordingly. History mode: Using the HTML5 History API, you can change the browser history without the # mark, making the URL look neater.

[0062] This application is applicable to the qiankun micro-front-end architecture. The preset environment can be the qiankun environment. The method of obtaining user permissions for the payment and collection microservice and the interest account microservice is specifically adjusted as follows: if the sub-application is currently running in the qiankun environment, user permissions are obtained from the cookie of the business microservice.

[0063] It should be noted that the present application does not specifically limit the execution order between the above steps 210 to 230. For example, step 230 may be before step 210 or after step 210.

[0064] In some embodiments of the present application, before the above step 140, the following may also be included: adjusting the sub-application page style, removing the left menu bar and the top user login information, and removing the sub-application interface scroll bar.

[0065] Involving step 140, based on the base entry file, component directory file and sub-application entry file, the sub-application interface of the payment and collection microservice and the interest account microservice is integrated in the front-end application of the business microservice.

[0066] In step 140, the target micro-frontend architecture can be the Qiankun micro-frontend architecture, and the business microservices, payment and collection microservices, and interest account microservices are integrated through the Qiankun micro-frontend architecture; the front-end application mainly adopts VUE.JS and H5, ElementUI combined development mode to provide customers with a rich and convenient operation experience.

[0067] In this way, through Qiankun's powerful routing, state sharing and sandbox isolation functions, different sub-applications can communicate and collaborate efficiently and be isolated from each other, achieving the requirements of different system integration and user experience consistency. By logging in to a single access address, the same user can achieve cross-system seamless access to different sub-application data related to the core reinsurance business and core payment and collection business.

[0068] In some embodiments of the present application, the business microservice is used to generate billing data based on business data. The business microservice, the payment and collection microservice, and the interest account microservice can achieve data association through the billing data. The business microservice can transmit the billing data to the payment and collection microservice through the API interface provided by the payment and collection microservice to realize bill settlement management and tax bill management.

[0069] In some embodiments of the present application, Figure 3 is a flow chart of a micro-frontend integration configuration method for a reinsurance system provided by another embodiment of the present application. The above step 140 may include Figure 3 Steps 310 to 330 are shown.

[0070] Step 310: based on the sub-application parameters of the payment and collection microservice and the interest account microservice, a first menu module and a second menu module are added to the front-end application of the business microservice, wherein the first menu module is associated with the payment and collection microservice, and the second menu module is associated with the interest account microservice; Step 320, in response to the access operation to the first menu module, based on the first configuration parameter for the payment and collection microservice in the base entry file, the component directory file, and the sub-application entry file, the static resource of the payment and collection microservice is loaded, and the sub-application interface corresponding to the payment and collection microservice is displayed; Step 330, in response to the access operation to the second menu module, based on the second configuration parameters for the interest account microservice in the base entry file, the component directory file, and the sub-application entry file, load the static resources of the interest account microservice, and display the sub-application interface corresponding to the interest account microservice.

[0071] The first configuration parameter may include configuration parameters related to the payment microservice in the base entry file, component directory file, and sub-application entry file; the second configuration parameter may include configuration parameters related to the interest account microservice in the base entry file, component directory file, and sub-application entry file. The first menu module is a service module corresponding to the payment microservice set in the front-end application, and the second menu module is a service module corresponding to the interest account microservice set in the front-end application.

[0072] In some embodiments of the present application, the menu modules included in the front-end application may include but are not limited to: to-do reminder management module, customer management module, underwriting management module, claims management module, estimate management module, bill management module, settlement management module, tax bill management module, configuration management module, query statistics module and interest transfer account module.

[0073] Among them, the to-do reminder management module is used to uniformly provide to-do reminder functions for business microservices, payment and collection microservices, and interest account microservices; the settlement management module and the tax bill management module are used to provide services for payment and collection microservices; the interest account transfer module is used to provide services for the interest account microservice; the customer management module, underwriting management module, claims management module, estimate management module, bill management module, configuration management module, and query statistics module are used to provide services for business microservices.

[0074] For example, Figure 4 It is the application interface of the front-end application, which is the unified login page for the integrated business microservice, payment and collection microservice, and interest account microservice. The left column contains the menu modules included in the front-end application. Among them, settlement management (module) and tax bill management (module) are both the first menu modules, so the payment and collection system (i.e. payment and collection microservice) can be directly accessed through these two menu modules, and the to-do items and reminders related to bill settlement will also appear on the unified login page; interest account transfer (module) is the second menu module, so the interest account microservice can be directly accessed through this menu module.

[0075] In an embodiment of the present application, a target micro-front-end architecture is used in the front-end application of the business microservice to register a sub-application in the main application, integrate multiple sub-applications in the main application interface, and implement the main application loading the sub-application menu. By logging in to a single access address, the same user can achieve seamless access to different sub-application data.

[0076] In some embodiments of the present application, the backend data processing mainly obtains the settlement pending data of the payment module through the REST API provided by the payment service ( / api / workflow / findUncommitPage) and pushes business data to the payment module for review ( / api / account / accountManage / saveAccount).

[0077] In the related technologies, the business microservice, payment and collection microservice, and interest account microservice each perform their own to-do, approval, and reminder functions, requiring login and logout, and each process generates to-do, approval, and reminder related processes separately, making the process lengthy and unclear.

[0078] In some embodiments of the present application, Figure 5is a flowchart of a micro-frontend integration configuration method for a reinsurance system provided by another embodiment of the present application. The above step 140 may include Figure 5 Steps 510 - 530 are shown.

[0079] Step 510, based on the application parameters of the business microservice, and the sub-application parameters of the payment and collection microservice and the interest account microservice, a to-do reminder management module is added to the front-end application of the business microservice; Step 520, in response to the access operation to the to-do reminder management module, displaying submenu modules associated with each microservice; Step 530, in response to the access operation to the sub-menu module of the single microservice, based on the configuration parameters for the single microservice in the base entry file, the component directory file, and the sub-application entry file, the corresponding data of the single microservice is loaded in the sub-application interface of the single microservice.

[0080] Specifically, the business microservice is the main application, so the application parameters of the business microservice are the main application parameters, and correspondingly, the application parameters of the payment and collection microservice and the interest account microservice are sub-application parameters. The to-do reminder management module integrates the business data of the business microservice, the payment and collection data of the payment and collection microservice, and the interest account data of the interest account microservice, so it can provide corresponding to-do reminder services for the three microservices. The corresponding data of different microservices are different. Business data can be loaded in the sub-application interface of the business microservice, payment and collection data can be loaded in the sub-application interface of the payment and collection microservice, and interest account data can be loaded in the sub-application interface of the interest account microservice.

[0081] For example, see Figure 6 The application interface of the front-end application shown in the figure, the above-mentioned to-do reminder management module can be divided into Figure 6 The "To-do" and "Reminders" shown. Among them, the "To-do" function module can be divided into 8 sub-menu modules, namely, "Customer pending", "Underwriting pending", "Revision pending", "Claims pending", "Bill pending", "Settlement pending", "Rolling budget pending", and "Interest account pending". "Bill pending" and "Settlement pending" can be associated with the payment and collection microservices, "Interest account pending" can be associated with the interest account microservice, and the remaining 5 sub-menu modules are all associated with the business microservice. The "Reminders" function module can be divided into 6 sub-menu modules, namely, "Customer-related reminders", "Underwriting-related reminders", "Revision-related reminders", "Claims-related reminders", "Bill-related reminders", and "Interest account-related reminders". "Bill-related reminders" can be associated with the payment and collection microservices, "Interest account-related reminders" can be associated with the interest account microservice, and the remaining 4 sub-menu modules are all associated with the business microservices.

[0082] Continue to see Figure 6 In response to the access operation to the sub-menu module "Settlement Pending" of the payment and collection microservice, the payment and collection data such as temporary storage of payment and collection orders, review of payment and collection orders, processing of claim lists, review of temporary collection transfers, and review of temporary collection refunds can be loaded in the sub-application interface of the payment and collection microservice; similarly, in response to the access operation to the sub-menu module "Settlement Related Reminders" of the payment and collection microservice, the payment and collection data such as review reminders of payment and collection orders, review reminders of temporary collection refunds, cash compensation settlement reminders, and new customer settlement reminders can be loaded in the sub-application interface of the payment and collection microservice.

[0083] In the embodiment of the present application, compared with the prior art in which the same functional module can only provide support for one microservice, and the same functional module cannot integrate multiple microservices, the present application develops a new to-do reminder management module, so that the same functional module can simultaneously connect to the business microservice, the payment and collection microservice, and the interest account microservice, and provide to-do, approval, and reminder functions for the three. Therefore, through the to-do reminder management module, data access operations for multiple microservices can be realized, and business personnel can process the to-do, approval, and reminder business of the business microservice, the payment and collection microservice, and the interest account microservice through the same functional module, unifying the to-do, approval, and reminder processes of different microservices, facilitating business tracking and business progress, and improving work efficiency.

[0084] In some embodiments of the present application, a to-do reminder management module includes a to-do module and a reminder module; the sub-menu modules corresponding to the to-do module include: a customer pending module, an underwriting pending module, a correction pending module, a claims pending module, a bill pending module, a settlement pending module, a rolling budget pending module and an interest account pending module, wherein the bill pending module and the settlement pending module are associated with the receipt and payment microservice, the interest account pending module is associated with the interest account microservice, and the remaining sub-menu modules are associated with the business microservice; the sub-menu modules corresponding to the reminder module include: a customer-related reminder module, an underwriting-related reminder module, a correction-related reminder module, a claims-related reminder module, a bill-related reminder module and an interest account-related reminder module, wherein the bill-related reminder module is associated with the receipt and payment microservice, the interest account-related reminder module is associated with the interest account microservice, and the remaining sub-menu modules are associated with the business microservice.

[0085] In some embodiments of the present application, data can be exchanged between microservices through REST API. The front-end application includes a first menu module associated with the payment microservice and a second menu module associated with the interest account microservice. Figure 7 is a flow chart of a micro-frontend integration configuration method for a reinsurance system provided by another embodiment of the present application. The above step 140 may include Figure 7 Step 710 and step 720 are shown.

[0086] Step 710: In response to the access operation to the first menu module, the URL changes, automatically triggering the matching logic corresponding to the target micro-frontend architecture, and activating the corresponding payment microservice through matching the basic routing address (associated with the payment microservice) configured in the base entry file; Step 720, load the HTML entry of the payment microservice through the target micro-frontend architecture, jump to the sub-application interface of the payment microservice based on the HTML entry, and dynamically configure the publicPath attribute of webpack according to the global variables injected by the target micro-frontend architecture to load the static resources of the payment microservice.

[0087] Specifically, the target micro-frontend architecture is the qiankun micro-frontend structure. Check the window.__POWERED_BY_QIANKUN__ global variable. If it exists, configure the publicPath property of webpack and set __webpack_public_path__ to window.__INJECTED_PUBLIC_PATH_BY_QIANKUN__ to ensure that the payment and collection microservice can correctly load its static resources, which may include but are not limited to the application address, dynamic path, css files and pictures of the payment and collection microservice.

[0088] In the embodiment of the present application, the reinsurance system introduces the Qiankun micro-front-end architecture, builds a unified platform management interface, integrates the independently deployed and independently operated business system, payment and collection system, and interest account microservices, takes the business system as the base application, and adopts a routing configuration method (applicable to route-based scenarios) to associate the sub-application with some URL rules, so as to realize the function of automatically loading the corresponding sub-application when the browser URL changes.

[0089] In some embodiments of the present application, the above step 140 may also include the following steps: In response to the access operation to the second menu module, the URL changes, automatically triggering the matching logic corresponding to the target micro-frontend architecture, and activating the corresponding interest account microservice through the basic routing address (associated with the interest account microservice) configured in the base entry file; The HTML entry of the interest account microservice is loaded through the target micro-frontend architecture, and based on the HTML entry, it jumps to the sub-application interface of the interest account microservice. The publicPath property of webpack is dynamically configured according to the global variables injected by the target micro-frontend architecture to load the static resources of the interest account microservice.

[0090] In some embodiments of the present application, the backend data processing mainly obtains the settlement to-do of the payment module ( / api / workflow / findUncommitPage) and pushes business data to the payment module for review ( / api / account / accountManage / saveAccount) through the REST API provided by the payment module.

[0091] In some embodiments of the present application, each microservice can interact with each other through REST API, message queue and view VIEW to realize the flow of billing data.

[0092] Specifically, for public and infrequently changing data, such as institutions, exchange rates, insurance categories and types of insurance, you can Figure 8 As shown, the message queue (RocketMq) is used for regular updates. When the data such as the core system organization and exchange rate changes, the data is synchronized to the payment and collection through MQ; the view VIEW, the display fields of the account query and statistics function include core business and payment fields, and involve joint queries of multiple million-level data tables. The REST API method cannot meet the customer's efficiency requirements for query statistics, so the cross-database query and statistics function is implemented by creating a view.

[0093] In some embodiments of the present application, in order to solve the problem of data consistency between microservices, a TCC (Try-Confirm-Cancel) compensation mechanism can be added during batch review of bills.

[0094] like Fig. 9 As shown in the figure, when business data is submitted for review in batches, a corresponding confirmation and compensation (cancellation) operation is registered. When the coordinator passes the verification of the try data of the core business in the first phase and the try data of payment and collection, the second phase data submission Confirm or rollback cancel operation is executed.

[0095] As a specific example, Fig.10 Schematic diagram of a reinsurance system provided in an embodiment of the present application. Fig.10 As shown, the reinsurance system is aimed at internal employees of the enterprise and is specifically divided into a unified login platform, front-end server, middle-end microservices, data storage, peripheral systems and third-party service components. Each microservice in the reinsurance system is independently deployed, data is independently stored, and each peripheral system is independently connected.

[0096] Among them, the front-end service includes login authentication, data channel, routing management and Redis cache; the middle-end microservices can include business microservices and payment microservices. The functional modules included in the business microservices may include to-do items, customer management, underwriting management, claims management, estimate management, bill management, configuration management and query statistics; the functional modules included in the payment microservices may include settlement management and tax bill management; the data storage consists of both the business pg library and the business disaster recovery library; the peripheral systems include public services, data exchange, actuarial pricing, unified files, compliance management, data application, reserves and mail systems; third-party service components may include registration center, Redis, MQ, XXL-job, apollo and TongWeb.

[0097] In other examples of the present application, the above-mentioned middle-office microservices may include business microservices, payment and collection microservices, and interest account microservices, and the interest account microservices may include a functional module for transferring interest accounts.

[0098] Corresponding to the method embodiment of the present application, the present application also provides a micro-front-end integrated configuration device for a reinsurance system, which can be applied to the reinsurance system, and the reinsurance system includes a business microservice, a payment and collection microservice, and an interest account microservice.

[0099] Fig.11 Schematic diagram of a micro-front-end integrated configuration device for a reinsurance system provided in an embodiment of the present application. Fig.11 As shown, the micro-frontend integrated configuration device 1100 for the reinsurance system may include: a registration module 1110, a new creation module 1120, a sub-application configuration module 1130, and an integration module 1140.

[0100] Among them, the registration module 1110 is used to use the business microservice as the base application, the payment and collection microservice and the interest account microservice as sub-applications, and register the sub-application by configuring the sub-application parameters of the payment and collection microservice and the interest account microservice in the base entry file of the business microservice; the new creation module 1120 is used to create page files corresponding to the payment and collection microservice and the interest account microservice in the component directory folder of the business microservice, wherein the page file is used to undertake the sub-application interface; the sub-application configuration module 1130 is used to add logical judgment rules for the payment and collection microservice and the interest account microservice to run independently or in a preset environment in the sub-application entry files of the payment and collection microservice and the interest account microservice, and define the basic access path of the sub-application resources of the packaged payment and collection microservice and the interest account microservice in the browser; the integration module 1140 is used to integrate the sub-application interfaces of the payment and collection microservice and the interest account microservice in the front-end application of the business microservice based on the base entry file, the component directory file and the sub-application entry file.

[0101] The micro-front-end integrated configuration device for a reinsurance system provided in an embodiment of the present application registers the payment and collection microservice and the interest account microservice as sub-applications in the business microservice by configuring the sub-application parameters of the payment and collection microservice and the interest account microservice in the base entry file of the business microservice; creates page files corresponding to the payment and collection microservice and the interest account microservice in the component directory folder of the business microservice to host the sub-application interface in the front-end application of the business microservice; configures the processing logic before loading the sub-application by adding logical judgment rules for the payment and collection microservice and the interest account microservice to run independently or in a preset environment in the sub-application entry files, and loads the sub-application static resources in the front-end application of the business microservice by defining the basic access path of the sub-application resources of the packaged payment and collection microservice and the interest account microservice in the browser. Based on this, through the above configuration operations, with the business microservice as the base application, the payment and collection microservice and the interest account microservice as sub-applications, the sub-application interfaces of the payment and collection microservice and the interest account microservice are integrated in the front-end application of the business microservice. That is, the front-end application interface of the business microservice is transformed into a unified platform management interface to achieve unified access to the business microservice, the payment and collection microservice, and the interest account microservice, meet the requirements of user system integration and user experience consistency, and improve business processing efficiency.

[0102] In some embodiments of the present application, the integration module 1140 is specifically used to: based on the sub-application parameters of the payment and collection microservice and the interest account microservice, add a first menu module and a second menu module in the front-end application of the business microservice, wherein the first menu module is associated with the payment and collection microservice, and the second menu module is associated with the interest account microservice; in response to an access operation to the first menu module, based on the first configuration parameters for the payment and collection microservice in the base entry file, the component directory file, and the sub-application entry file, load the static resources of the payment and collection microservice, and display the sub-application interface corresponding to the payment and collection microservice; in response to an access operation to the second menu module, based on the second configuration parameters for the interest account microservice in the base entry file, the component directory file, and the sub-application entry file, load the static resources of the interest account microservice, and display the sub-application interface corresponding to the interest account microservice.

[0103] In some embodiments of the present application, the integration module 1140 is specifically used to: based on the application parameters of the business microservice, and the sub-application parameters of the payment and collection microservice and the interest account microservice, add a to-do reminder management module in the front-end application of the business microservice, wherein the to-do reminder management module integrates the business data of the business microservice, the payment and collection data of the payment and collection microservice, and the interest account data of the interest account microservice; in response to an access operation to the to-do reminder management module, display sub-menu modules associated with each microservice; in response to an access operation to the sub-menu module of a single microservice, load the corresponding data of the single microservice in the sub-application interface of the single microservice based on the configuration parameters for the single microservice in the base entry file, the component directory file, and the sub-application entry file.

[0104] In some embodiments of the present application, the business microservice is used to generate billing data based on business data. The business microservice, the payment and collection microservice, and the interest account microservice are associated with each other through the billing data. The business microservice transmits the billing data to the payment and collection microservice through the API interface provided by the payment and collection microservice to realize bill settlement management and tax bill management.

[0105] In some embodiments of the present application, the registration module 1110 is specifically used to: pass in the sub-application parameters of the payment and collection microservice and the interest account microservice by calling the registration microservice method of the target micro-frontend architecture; wherein the sub-application parameters include the sub-application name, the sub-application startup address, the base-hosted sub-application container name and the basic routing address.

[0106] In some embodiments of the present application, the device also includes: a sub-application configuration module 1130, which is also used to add a mount function method and an unmount function method in the sub-application entry file of the payment and collection microservice and the interest account microservice, wherein the mount function method and the unmount function method are used to implement sub-application rendering and sub-application uninstallation; a routing configuration module, which is used to adjust the routing processing method of the business microservice, the payment and collection microservice, and the interest account microservice from the hash mode to the history mode; the sub-application configuration module 1130 is also used to adjust the method for obtaining user permissions for the payment and collection microservice and the interest account microservice. If it is determined that the current environment is in a preset environment, the user permissions are obtained from the cookie of the business microservice.

[0107] In some embodiments of the present application, data is exchanged between the various microservices through the REST API, and the front-end application includes a first menu module associated with the payment and collection microservice, and a second menu module associated with the interest account microservice. The integration module 1140 is specifically used for: in response to the access operation to the first menu module, the URL changes, and the matching logic corresponding to the target micro-front-end architecture is automatically triggered, and the corresponding payment and collection microservice is activated by matching the basic routing address configured by the base entry file; the HTML entry of the payment and collection microservice is loaded through the target micro-front-end architecture, and based on the HTML entry, it jumps to the sub-application interface of the payment and collection microservice, and dynamically configures the publicPath attribute of the webpack according to the global variables injected by the target micro-front-end architecture to load the static resources of the payment and collection microservice.

[0108] The micro-front-end integrated configuration device for the reinsurance system provided in the embodiment of the present application can achieve Figure 1-10 The various processes implemented by the service platform in the method embodiment can achieve the same technical effect. To avoid repetition, they will not be described here.

[0109] Fig.12 It is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application.

[0110] like Fig.12 As shown, the electronic device 1200 includes a memory 1201 , a processor 1202 , and a computer program stored in the memory 1201 and executable on the processor 1202 .

[0111] In an example, the processor 1202 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0112] The memory 1201 may include a read-only memory (ROM), a random access memory (RAM), a disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Therefore, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software including computer executable instructions, and when the software is executed (e.g., by one or more processors), it can be operated to perform the operations described with reference to the card opening method in the embodiment according to the first aspect of the present application.

[0113] The processor 1202 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 1201, so as to implement the card activation method in the embodiment of the first aspect.

[0114] In some examples, the electronic device 1200 may further include a communication interface 1203 and a bus 1210. Fig.12 As shown, the memory 1201, the processor 1202, and the communication interface 1203 are connected via a bus 1210 and communicate with each other.

[0115] The communication interface 1203 is mainly used to realize the communication between the modules, devices, units and / or equipment in the embodiment of the present application. The communication interface 1203 can also be used to access input devices and / or output devices.

[0116] The bus 1210 includes hardware, software, or both, coupling the components of the electronic device 1200 to each other. By way of example and not limitation, the bus 1210 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a Memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses or a combination of two or more of these. Where appropriate, the bus 1210 may include one or more buses. Although embodiments of the present application describe and illustrate a particular bus, the present application contemplates any suitable bus or interconnect.

[0117] The electronic device provided in the embodiment of the present application can realize Figure 1-10 The various processes implemented by the electronic device in the method embodiment can achieve the same technical effect, and to avoid repetition, they will not be described here.

[0118] In combination with the micro-frontend integrated configuration method for a reinsurance system in the above embodiments, the present application embodiment may provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when the computer program instructions are executed by a processor, the steps of any one of the micro-frontend integrated configuration methods for a reinsurance system in the above embodiments are implemented.

[0119] In combination with the micro-frontend integrated configuration method for a reinsurance system in the above embodiment, the present application embodiment may provide a computer program product for implementation. The (computer) program product is stored in a non-volatile storage medium, and when the program product is executed by at least one processor, the steps of any one of the micro-frontend integrated configuration methods for a reinsurance system in the above embodiment are implemented.

[0120] The embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run a program or instruction, implement the various processes of the above-mentioned micro-front-end integrated configuration method embodiment for a reinsurance system, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0121] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0122] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.

[0123] The functional blocks shown in the structural block diagram described above can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application-specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present application are programs or code segments used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link via a data signal carried in a carrier. "Machine-readable medium" may include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROMs, flash memories, erasable ROMs (EROMs), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0124] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.

[0125] Aspects of the present disclosure are described above with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the functions / actions specified in one or more boxes of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each box in the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can also be implemented by dedicated hardware that performs the specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

[0126] The above is only a specific implementation of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.

Claims

1. A micro-frontend integrated configuration method for a reinsurance system, characterized in that: Applied to a reinsurance system, the reinsurance system includes a business microservice, a payment and collection microservice, and an interest account microservice, and the method includes: Use the business microservice as the base application, the payment and collection microservice and the interest account microservice as sub-applications, and register the sub-applications by configuring the sub-application parameters of the payment and collection microservice and the interest account microservice in the base entry file of the business microservice; In the component directory folder of the business microservice, create new page files corresponding to the payment and collection microservice and the interest account microservice, wherein the page files are used to undertake the sub-application interface; In the sub-application entry files of the payment and collection microservice and the interest account microservice, add the logic judgment rules for the payment and collection microservice and the interest account microservice to run independently or in a preset environment, and define the basic access paths of the sub-application resources of the packaged payment and collection microservice and the interest account microservice in the browser; Based on the base entry file, the component directory file and the sub-application entry file, the sub-application interfaces of the payment and collection microservice and the interest account microservice are integrated in the front-end application of the business microservice.

2. The method according to claim 1, characterized in that The sub-application interface of integrating the payment and collection microservice and the interest account microservice in the front-end application of the business microservice based on the base entry file, the component directory file and the sub-application entry file includes: Based on the sub-application parameters of the payment and collection microservice and the interest account microservice, a first menu module and a second menu module are added to the front-end application of the business microservice, wherein the first menu module is associated with the payment and collection microservice, and the second menu module is associated with the interest account microservice; In response to the access operation to the first menu module, based on the first configuration parameter for the payment microservice in the base entry file, the component directory file, and the sub-application entry file, the static resources of the payment microservice are loaded, and the sub-application interface corresponding to the payment microservice is displayed; In response to the access operation to the second menu module, based on the second configuration parameters for the interest account microservice in the base entry file, the component directory file and the sub-application entry file, the static resources of the interest account microservice are loaded, and the sub-application interface corresponding to the interest account microservice is displayed.

3. The method according to claim 1 or 2, characterized in that: The sub-application interface of integrating the payment and collection microservice and the interest account microservice in the front-end application of the business microservice based on the base entry file, the component directory file and the sub-application entry file includes: Based on the application parameters of the business microservice, and the sub-application parameters of the payment and collection microservice and the interest account microservice, a to-do reminder management module is added to the front-end application of the business microservice, wherein the to-do reminder management module integrates the business data of the business microservice, the payment and collection data of the payment and collection microservice, and the interest account data of the interest account microservice; In response to an access operation to the to-do reminder management module, a submenu module associated with each microservice is displayed; In response to an access operation to a sub-menu module of a single microservice, corresponding data of the single microservice is loaded in the sub-application interface of the single microservice based on the base entry file, the component directory file, and the configuration parameters for the single microservice in the sub-application entry file.

4. The method according to claim 1, characterized in that: The business microservice is used to generate billing data based on business data. The business microservice, the payment and collection microservice, and the interest account microservice are associated with each other through the billing data. The business microservice transmits the billing data to the payment and collection microservice through the API interface provided by the payment and collection microservice to realize bill settlement management and tax bill management.

5. The method according to claim 1, characterized in that In the base entry file of the business microservice, registering the sub-application by configuring the sub-application parameters of the payment and collection microservice and the interest account microservice includes: By calling the registration microservice method of the target micro-frontend architecture, the sub-application parameters of the payment and collection microservice and the interest account microservice are passed in; The sub-application parameters include the sub-application name, the sub-application startup address, the base-carrying sub-application container name and the basic routing address.

6. The method according to claim 1, characterized in that The method further comprises: In the sub-application entry files of the payment and collection microservice and the interest account microservice, a mount function method and an unmount function method are added, wherein the mount function method and the unmount function method are used to implement sub-application rendering and sub-application uninstallation; Adjust the routing processing mode of the business microservice, the payment and collection microservice, and the interest account microservice from hash mode to history mode; Adjust the method of obtaining user permissions for the payment and collection microservice and the interest account microservice. If it is determined that the current operation is in a preset environment, obtain user permissions from the cookie of the business microservice.

7. The method according to claim 1, characterized in that The microservices interact with each other through the REST API. The front-end application includes a first menu module associated with the payment microservice and a second menu module associated with the interest account microservice. Based on the base entry file, the component directory file and the sub-application entry file, the sub-application interface of the payment microservice and the interest account microservice is integrated in the front-end application of the business microservice, including: In response to the access operation to the first menu module, the URL changes, automatically triggering the matching logic corresponding to the target micro-frontend architecture, and activating the corresponding payment microservice through the basic routing address matching configured in the base entry file; The HTML entry of the payment microservice is loaded through the target micro-front-end architecture, and based on the HTML entry, it jumps to the sub-application interface of the payment microservice, and dynamically configures the publicPath attribute of webpack according to the global variables injected by the target micro-front-end architecture to load the static resources of the payment microservice.

8. A micro-front-end integrated configuration device for a reinsurance system, characterized in that: Applied to a reinsurance system, the reinsurance system includes a business microservice, a payment and collection microservice, and an interest account microservice, and the device includes: A registration module, used to use the business microservice as a base application, the payment and collection microservice and the interest account microservice as sub-applications, and register the sub-applications by configuring the sub-application parameters of the payment and collection microservice and the interest account microservice in the base entry file of the business microservice; A new module is used to create a new page file corresponding to the payment and collection microservice and the interest account microservice in the component directory folder of the business microservice, wherein the page file is used to undertake the sub-application interface; A sub-application configuration module, used to add logic judgment rules for the payment collection microservice and the interest account microservice to run independently or in a preset environment in the sub-application entry files of the payment collection microservice and the interest account microservice, respectively, and define the basic access paths of the packaged sub-application resources of the payment collection microservice and the interest account microservice in the browser; An integration module is used to integrate the sub-application interfaces of the payment and collection microservice and the interest account microservice in the front-end application of the business microservice based on the base entry file, the component directory file and the sub-application entry file.

9. An electronic device, characterized in that: The electronic device comprises: a processor and a memory storing computer program instructions; when the electronic device executes the computer program instructions, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images