Hierarchical updating system and method

By updating the system at a hierarchy, detecting and matching the types and rules of the micro-application page layer, and dynamically adjusting the hierarchy structure, solving the complexity and hierarchical coverage of style management among micro-applications, achieving more efficient hierarchical management and user experience.

CN119088422APending Publication Date: 2024-12-06BEIJING BAILONG MAYUN TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411226736.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-02
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Different micro-applications use different technology stacks and component libraries, resulting in complex style management and consistency control, and there is a problem of mutual coverage of sub-application pages and main application levels.

Method used

Provide a hierarchical update system, through micro front-end modules, hierarchical management modules and collaboration modules, detect the matching of page layer types with preset rules, dynamically adjust the global hierarchical structure, ensure the display priority of each page layer, and register instances for precise management , and intelligently match rules in case of mismatch, dealing with hierarchical conflicts.

Benefits of technology

Effectively control page-level conflicts between different micro-applications, improve the accuracy and flexibility of hierarchical management, reduce code complexity, and improve user experience and system stability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119088422A_ABST
    Figure CN119088422A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of computers, and discloses a hierarchical updating system and method.The system comprises a micro-front-end module, a hierarchical management module and a first cooperation module; the micro front-end module is used for calling the first page layer in response to a first loading instruction of a target object; detecting whether the type of the first page layer corresponds to a first rule configured in the first cooperation module or not, and if the type of the first page layer corresponds to the first rule configured in the first cooperation module, sending the hierarchy of the first page layer to the first cooperation module; the first cooperation module is used for receiving the hierarchy of the first page layer, converting the initial hierarchy into the hierarchy of the first page layer according to a preset rule, and sending the hierarchy of the first page layer to the hierarchy management module; the hierarchy management module is used for receiving the hierarchy of the first page layer and updating the initial hierarchy into the hierarchy of the first page layer; and the first cooperation module is also used for covering the initial hierarchy with the hierarchy of the first page layer.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a hierarchical updating system and method. Background Art

[0002] As a modern software architecture pattern, micro frontends improve development efficiency and deployment flexibility by splitting large front-end applications into multiple small, independently deployable micro applications.

[0003] Currently, micro frontends use custom events, global state management (such as Redux, Vuex, etc.), or specialized micro frontend communication libraries (such as Single-SPA, Module Federation, etc.) to achieve data sharing and event triggering between micro applications.

[0004] However, different micro-applications use different technology stacks and component libraries, which makes style management and consistency control extremely complicated. There is a problem of mutual coverage and influence between the sub-application pages and the main application levels. Summary of the invention

[0005] In view of this, the present invention provides a hierarchical update system and method to solve the problem that different micro-applications use different technology stacks and different component libraries, which makes style management and consistency control extremely complicated, and the hierarchical levels of sub-application pages and main applications have mutual coverage and influence.

[0006] In a first aspect, the present invention provides a hierarchy update system, which includes: a micro-front-end module, a hierarchy management module and a first collaboration module; the micro-front-end module is used to call up a first page layer in response to a first loading instruction of a target object; detect whether the type of the first page layer corresponds to a first rule configured in the first collaboration module, and if the type of the first page layer corresponds to the first rule configured in the first collaboration module, send the hierarchy of the first page layer to the first collaboration module; the first collaboration module is used to receive the hierarchy of the first page layer, and convert the initial hierarchy into the hierarchy of the first page layer according to a preset rule, and send the hierarchy of the first page layer to the hierarchy management module; the hierarchy management module is used to receive the hierarchy of the first page layer, and update the initial hierarchy to the hierarchy of the first page layer; the first collaboration module is also used to overwrite the initial hierarchy with the hierarchy of the first page layer after the initial hierarchy is updated to the hierarchy of the first page layer.

[0007] The hierarchical update system provided in the present embodiment, when each micro-application is loaded, will check the type of its page layer through the first collaboration module and match it with the preset rules. In this way, it can be ensured that the page layer of each micro-application is correctly identified and classified, laying the foundation for subsequent hierarchical management. When the type of the first page layer corresponds to the first rule configured in the first collaboration module, the module will send its hierarchical information to the hierarchical management module. The hierarchical management module dynamically adjusts and maintains a global hierarchical structure according to the received hierarchical information. This means that if the page layer of a certain micro-application requires a higher display priority (i.e., a higher level), it can be adjusted accordingly to avoid being covered by other page layers. Through the above-mentioned hierarchical management mechanism, the page layer conflicts between different micro-applications can be minimized. Because the display priority of each page layer is determined according to the preset rules and the current global hierarchical structure, the mutual coverage problem between them can be effectively controlled.

[0008] In an optional implementation, the first collaboration module is further used to register an instance for the first page layer, and after the level of the first page layer covers the initial level, the first page layer is processed based on the instance.

[0009] The hierarchical update system provided in this embodiment, by registering instances, each first page layer is given a clear identity and management object. This allows developers to more accurately control and manage the behavior and style of the first page layer, reducing confusion and errors caused by anonymous or disorderly management. In addition, since each pop-up layer has a corresponding instance, the system can dynamically adjust the display level, size, position and other properties of the pop-up layer according to actual needs without worrying about the impact on other pop-up layers.

[0010] In an optional embodiment, the system also includes: a second collaboration module; the micro-front-end module is further used to send the type of the first page layer to the second collaboration module if the type of the first page layer does not correspond to the rule configured in the first collaboration module; the second collaboration module is used to determine the target rule information that matches the type of the first page layer from a preset rule library based on the type of the first page layer, and send the target rule information to the hierarchy management module; the hierarchy management module is used to convert the initial hierarchy into the hierarchy of the first page layer according to the target rule, and send the hierarchy to the second collaboration module; the second collaboration module is further used to update the initial hierarchy to the hierarchy of the first page layer.

[0011] In the hierarchical update system provided in this embodiment, when the type of the first page layer does not correspond to the predefined rule in the first collaboration module, the system can intelligently forward the type information to the second collaboration module. The second collaboration module matches based on the preset rule library to find the most suitable target rule information. This design enables the system to handle more diverse page layer types, improving the flexibility and scalability of the system.

[0012] In an optional embodiment, the system also includes: a second collaboration module; a micro-front-end module, which is used to respond to the second loading instruction of the target object, call up the second page layer, detect whether the second page layer type corresponds to the rules configured in the first collaboration module, and if the second page layer type does not correspond to the rules configured in the first collaboration module, send the level of the second page layer to the second collaboration module; a second collaboration module, which is used to receive the level of the second page layer, and detect whether the level of the second page layer is the same as the level of the first page layer; if the level of the second page layer is not the same as the level of the first page layer, match the second rule that matches the type of the second page layer from a preset rule library; a level management module, which is used to convert the level of the first page layer into the level of the second page layer according to the second rule that matches the type of the second page layer; a second collaboration module, which is used to overwrite the level of the first page layer with the level of the second page layer.

[0013] The hierarchical update system provided in this embodiment can respond to the second loading instruction of the target object, dynamically call up the second page layer, and intelligently adjust the page hierarchy according to the matching of the page layer type and the configuration rules. This dynamic adjustment mechanism enables the system to adapt to the hierarchical requirements between different page layers, improving the flexibility of the page and the user experience. Through the intervention of the second collaboration module, the system can detect and handle the hierarchical conflict between the second page layer and the first page layer. When the hierarchies of the two are different, the system can automatically match the corresponding rules from the preset rule library, and adjust the hierarchy of the first page layer to match the second page layer accordingly, thereby achieving coordination and unification across page hierarchies.

[0014] In an optional implementation, the first collaboration module is further used to receive the level of the first page layer, and increment the initial level to the level of the first page layer by a preset amount.

[0015] The level update system provided in this embodiment can significantly reduce the amount of code related to level management by encapsulating the level adjustment logic in the first collaboration module and adopting a preset quantity increment strategy. This not only reduces the complexity of the system, but also improves the readability and maintainability of the code.

[0016] In an optional embodiment, the system also includes: a monitoring module; a monitoring module, used to monitor whether the first rule and the type of the first page layer match, whether the second rule and the type of the second page layer match, if the first rule and the type of the first page layer do not match and / or the second rule and the type of the second page layer do not match, an alarm is issued in the form of a voice warning, an error prompt or a highlighted display.

[0017] The hierarchical update system provided in this embodiment can continuously monitor the type matching between the rules and page layers, and promptly detect and report mismatches. This helps to quickly locate and fix potential problems, thereby avoiding errors or crashes in the system due to type mismatches, and improving the overall stability of the system. When the data entered by the user does not match the rules, the monitoring module can immediately notify the user through voice warnings, error prompts, or highlighted displays. This instant feedback mechanism reduces user confusion and frustration, helps users quickly understand the problem and make corresponding adjustments, thereby improving the user experience.

[0018] In a second aspect, the present invention provides a hierarchical updating method, the method comprising: in response to a first loading instruction of a target object, calling up a first page layer; detecting whether the type of the first page layer corresponds to a first rule configured in a first collaboration module; if the type of the first page layer corresponds to the first rule configured in the first collaboration module, converting the initial hierarchy into the hierarchy of the first page layer according to a preset rule; updating the initial hierarchy to the hierarchy of the first page layer so that the hierarchy of the first page layer covers the initial hierarchy.

[0019] In a third aspect, the present invention provides a hierarchical updating device, which includes: a calling module, used to call up a first page layer in response to a first loading instruction of a target object; a detection module, used to detect whether the type of the first page layer corresponds to a first rule configured in the first collaboration module; a conversion module, used to convert the initial hierarchy into the hierarchy of the first page layer according to a preset rule if the type of the first page layer corresponds to the first rule configured in the first collaboration module; and an update coverage module, used to update the initial hierarchy to the hierarchy of the first page layer, so that the hierarchy of the first page layer covers the initial hierarchy.

[0020] In a fourth aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, computer instructions being stored in the memory, and the processor executing the hierarchical update method of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0021] In a fifth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the hierarchical updating method of the first aspect or any corresponding embodiment thereof.

[0022] In a sixth aspect, the present invention provides a computer program product, comprising computer instructions for causing a computer to execute the hierarchical updating method of the first aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0024] Figure 1 is a structural block diagram of a hierarchical updating system according to an embodiment of the present invention;

[0025] Figure 2 is a schematic diagram of a process flow of another hierarchical updating system according to an embodiment of the present invention;

[0026] Figure 3 is a flowchart of a hierarchical updating method according to an embodiment of the present invention;

[0027] Figure 4 is a structural block diagram of a hierarchical updating device according to an embodiment of the present invention;

[0028] Figure 5 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0029] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0030] Based on relevant technologies, micro front-end, as a modern software architecture pattern, improves development efficiency and deployment flexibility by splitting large front-end applications into multiple small, independently deployable micro applications.

[0031] Currently, micro frontends use custom events, global state management (such as Redux, Vuex, etc.), or specialized micro frontend communication libraries (such as Single-SPA, Module Federation, etc.) to achieve data sharing and event triggering between micro applications.

[0032] However, different micro-applications use different technology stacks and component libraries, which makes style management and consistency control extremely complicated. There is a problem of mutual coverage and influence between the sub-application pages and the main application levels.

[0033] Based on this, the present invention provides a hierarchical update system, and each micro-application, when loaded, will check the type of its page layer through the first collaboration module and match it with the preset rules. In this way, it can be ensured that the page layer of each micro-application is correctly identified and classified, laying the foundation for subsequent hierarchical management. When the type of the first page layer corresponds to the first rule configured in the first collaboration module, the module will send its hierarchical information to the hierarchical management module. The hierarchical management module dynamically adjusts and maintains a global hierarchical structure according to the received hierarchical information. This means that if the page layer of a certain micro-application requires a higher display priority (i.e., a higher level), it can be adjusted accordingly to avoid being covered by other page layers. Through the above-mentioned hierarchical management mechanism, the page layer conflicts between different micro-applications can be minimized. Because the display priority of each page layer is determined according to the preset rules and the current global hierarchical structure, the mutual coverage problem between them can be effectively controlled.

[0034] According to an embodiment of the present invention, a hierarchical updating system embodiment is provided, such as Figure 1 As shown, the system includes: a micro-front-end module 101, a hierarchy management module 103 and a first collaboration module 102; the micro-front-end module 101 is used to call up the first page layer in response to the first loading instruction of the target object; detect whether the type of the first page layer corresponds to the first rule configured in the first collaboration module 102, and if the type of the first page layer corresponds to the first rule configured in the first collaboration module 102, send the hierarchy of the first page layer to the first collaboration module 102; the first collaboration module 102 is used to receive the hierarchy of the first page layer, and convert the initial hierarchy into the hierarchy of the first page layer according to a preset rule, and send the hierarchy of the first page layer to the hierarchy management module 103; the hierarchy management module 103 is used to receive the hierarchy of the first page layer, and update the initial hierarchy to the hierarchy of the first page layer; the first collaboration module 102 is also used to overwrite the initial hierarchy with the hierarchy of the first page layer after the initial hierarchy is updated to the hierarchy of the first page layer.

[0035] The micro-front-end module 101 may be a module responsible for modular loading and management of front-end applications, and may call up corresponding page layers according to different loading instructions. The hierarchy management module 103 may be a module responsible for maintaining the hierarchical relationship of each page layer in the system, ensuring the correct display and interaction of the page layers. The first collaboration module 102 may be a module responsible for coordinating the work between the micro-front-end module 101 and the hierarchy management module 103 in the micro-front-end architecture, including functions such as hierarchy conversion and hierarchy overlay. Among them, the first collaboration module 102 may be an element pop center, and all original pop-up layers have been registered in this center. The parts for obtaining the hierarchy and setting the hierarchy are modified and uniformly managed by the hierarchy management module 103.

[0036] The hierarchical management module 103 can build a centralized hierarchical management service, including a multi-level management system of global styles, component library styles, technology stack-specific styles, and project-customized styles. It can perform initialization settings, data retrieval, information update, and value increase operations, and distribute them to each micro-application through an API to ensure a consistent visual experience for the entire micro-frontend application.

[0037] Specifically, responding to the loading instruction: When the user or system triggers the first loading instruction of the target object, the micro front-end module 101 starts working. Calling up the first page layer: According to the loading instruction, the micro front-end module 101 is responsible for loading and displaying the first page layer. The micro front-end module 101 detects the type of the first page layer and matches it with the first rule pre-configured in the first collaboration module 102. If the type matches the rule, the micro front-end module 101 sends the hierarchical information of the first page layer to the first collaboration module 102.

[0038] The first collaboration module 102: Receives the hierarchical information of the first page layer from the micro front-end module 101. According to the preset rules (such as increasing by a fixed number, calculated according to a specific algorithm, etc.), the initial hierarchy is converted into the hierarchy of the first page layer. The hierarchical information of the converted first page layer is sent to the hierarchy management module 103. After the hierarchy management module 103 completes the hierarchy update, the first collaboration module 102 is responsible for overwriting the initial hierarchy with the hierarchy of the first page layer to ensure the correctness of the page layer display. Hierarchy management module 103: Receives the hierarchical information of the first page layer from the first collaboration module 102. Updates the current initial hierarchy to the hierarchy of the first page layer. Ensure that the hierarchical relationship between the page layers within the system is correct for subsequent operations.

[0039] For example: an online shopping mall system, where the product details page is the first page layer.

[0040] Micro front-end module 101: When a user clicks a product link, the micro front-end module 101 receives an instruction to load the product details page and calls up the corresponding page layer.

[0041] Type detection and rule matching: The micro front-end module 101 detects that the type of the product details page is “product details” and matches it with the “product details” rule configured in the first collaboration module 102 .

[0042] Level conversion: The first collaboration module 102 converts the initial level to 5 according to a preset rule (eg, the level of the product details page is fixed at 5).

[0043] Sending the converted level: The first collaboration module 102 sends the converted level information (5) to the level management module 103.

[0044] Update level: The level management module 103 updates the current initial level to 5 to ensure that the product details page can be displayed correctly.

[0045] Layer override (if applicable): If there are multiple page layers in the system that need to be displayed at the same time and there is a layer conflict, the first collaboration module 102 may also be responsible for overriding the layer of the product details page to the highest level to ensure that it is displayed first. However, in this simple example, the layer override operation may not be required.

[0046] The hierarchical update system provided in the present embodiment, when each micro-application is loaded, will check the type of its page layer through the first collaboration module and match it with the preset rules. In this way, it can be ensured that the page layer of each micro-application is correctly identified and classified, laying the foundation for subsequent hierarchical management. When the type of the first page layer corresponds to the first rule configured in the first collaboration module, the module will send its hierarchical information to the hierarchical management module. The hierarchical management module dynamically adjusts and maintains a global hierarchical structure according to the received hierarchical information. This means that if the page layer of a certain micro-application requires a higher display priority (i.e., a higher level), it can be adjusted accordingly to avoid being covered by other page layers. Through the above-mentioned hierarchical management mechanism, the page layer conflicts between different micro-applications can be minimized. Because the display priority of each page layer is determined according to the preset rules and the current global hierarchical structure, the mutual coverage problem between them can be effectively controlled.

[0047] In an optional implementation, the first collaboration module 102 is further used to register an instance for the first page layer, and after the level of the first page layer covers the initial level, process the first page layer based on the instance.

[0048] The first page layer may be a page pop-up layer, which may include a main page pop-up layer and a sub-page pop-up layer. An instance refers to a specific object representing the first page layer, which includes all necessary information and behaviors of the page layer.

[0049] Specifically, after receiving the relevant information of the first page layer, the first collaboration module 102 creates a corresponding instance according to the type and content of the page layer. This instance may contain all necessary information of the page layer, such as the level, display content, interaction logic, etc. The created instance is registered in the instance management system of the system so that it can be managed later, such as updated, deleted or queried.

[0050] Layer Overlay: As before, after the first collaboration module 102 sends the layer information of the first page layer to the layer management module 103 and receives confirmation of the layer update completion, it will perform a layer overlay operation. This step ensures that the newly loaded page layer can be correctly displayed in the expected position.

[0051] Processing page pop-up layers: Based on the registered instances, the first collaboration module 102 is responsible for managing and controlling the pop-up layers on the page. This may include displaying, hiding, animation effects, interactive logic, etc. of the pop-up layers. If there are multiple pop-up layers that need to be displayed at the same time, the first collaboration module 102 also needs to determine the display order of the pop-up layers according to certain priority sorting rules (such as level, display time, etc.). Process user interaction events related to the pop-up layer, such as click, close, etc., and trigger corresponding logic processing according to the event type.

[0052] For example, in an online shopping mall system, when a user clicks on a shopping cart icon, a shopping cart details page layer will pop up. When a user clicks on the shopping cart icon, the first collaboration module 102 will create an instance of a shopping cart details page layer and register it with the instance management system of the system. This instance contains all necessary information of the shopping cart details page layer, such as a list of products, a total price, etc. If the shopping cart details page layer needs to cover other page layers (such as a product details page), the first collaboration module 102 will send the hierarchy information to the hierarchy management module 103, and after receiving the confirmation that the hierarchy update is complete, perform the hierarchy overwriting operation. The first collaboration module 102 is responsible for controlling the display and hiding of the shopping cart details page layer. When the user clicks on the close button, the first collaboration module 102 will trigger the corresponding logic processing to hide the shopping cart details page layer. At the same time, if there are multiple pop-up layers in the system that need to be displayed at the same time, the first collaboration module 102 will determine their display order according to certain priority sorting rules.

[0053] The hierarchical update system provided in this embodiment, by registering instances, each first page layer is given a clear identity and management object. This allows developers to more accurately control and manage the behavior and style of the first page layer, reducing confusion and errors caused by anonymous or disorderly management. In addition, since each pop-up layer has a corresponding instance, the system can dynamically adjust the display level, size, position and other properties of the pop-up layer according to actual needs without worrying about the impact on other pop-up layers.

[0054] In an optional embodiment, the system also includes: a second collaboration module; the micro-front-end module 101 is further used to send the type of the first page layer to the second collaboration module if the type of the first page layer does not correspond to the rule configured in the first collaboration module 102; the second collaboration module is used to determine the target rule information that matches the type of the first page layer from a preset rule library based on the type of the first page layer, and send the target rule information to the hierarchy management module 103; the hierarchy management module 103 is used to convert the initial hierarchy into the hierarchy of the first page layer according to the target rule, and send the hierarchy to the second collaboration module; the second collaboration module is further used to update the initial hierarchy to the hierarchy of the first page layer.

[0055] The second collaboration module refers to the system in which, when the first collaboration module 102 cannot process the hierarchical rules of a specific page layer type, the second collaboration module is responsible for finding and applying appropriate rules from a preset rule base. The rule base can be a data set that stores a variety of page layer types and their corresponding hierarchical rules. These rules define how to convert the initial level into the level required for a specific page layer. The target rule information can be the hierarchical rule information found in the rule base that matches the first page layer type.

[0056] When it is detected that the type of the first page layer does not correspond to the rule configured in the first collaboration module 102, the micro front-end module 101 sends the type information of the first page layer to the second collaboration module. The second collaboration module receives the type information of the first page layer from the micro front-end module 101. Based on the type information, search and determine the target rule information that matches the first page layer type in the preset rule library. Send the found target rule information to the hierarchy management module 103. The hierarchy management module 103 receives the target rule information from the second collaboration module. According to the target rule information, the current initial hierarchy is converted to the hierarchy required for the first page layer. The converted hierarchy information is sent back to the second collaboration module. The second collaboration module receives the converted hierarchy information from the hierarchy management module 103. Perform a hierarchy update operation to update the initialization hierarchy to the hierarchy of the first page layer.

[0057] Specifically, the implementation of the rule base can use a database, file, or in-memory data structure to store the rule base. The rules in the rule base can be statically configured or dynamically added through some mechanism (such as an administrator interface). The rule matching algorithm can use a simple key-value pair lookup algorithm, where the key is the page layer type and the value is the corresponding hierarchical rule. For more complex scenarios, more advanced matching algorithms can be used, such as regular expression matching, fuzzy matching, etc. The hierarchical transformation logic can be implemented based on the specific content of the target rule information. For example, it may be a simple numerical increment or decrement operation, or it may be a complex calculation expression. The hierarchical transformation logic can also be designed to be extensible so that new transformation logic can be added without modifying the existing code.

[0058] In the hierarchical update system provided in this embodiment, when the type of the first page layer does not correspond to the predefined rule in the first collaboration module, the system can intelligently forward the type information to the second collaboration module. The second collaboration module matches based on the preset rule library to find the most suitable target rule information. This design enables the system to handle more diverse page layer types, improving the flexibility and scalability of the system.

[0059] In an optional embodiment, the system also includes: a second collaboration module; a micro-front-end module 101, which is used to respond to the second loading instruction of the target object, call up the second page layer, detect whether the second page layer type corresponds to the rules configured in the first collaboration module 102, and if the second page layer type does not correspond to the rules configured in the first collaboration module 102, send the level of the second page layer to the second collaboration module; a second collaboration module, which is used to receive the level of the second page layer, and detect whether the level of the second page layer is the same as the level of the first page layer; if the level of the second page layer is not the same as the level of the first page layer, match the second rule that matches the type of the second page layer from a preset rule library; a level management module 103, which is used to convert the level of the first page layer into the level of the second page layer according to the second rule that matches the type of the second page layer; a second collaboration module, which is used to overwrite the level of the first page layer with the level of the second page layer.

[0060] The second rule may be a level conversion rule matching the second page layer type, and these rules define how to convert the level of one page layer into the level required by another page layer.

[0061] The micro front-end module 101 calls up the second page layer in response to the second loading instruction of the target object. Then, it is detected whether the type of the second page layer corresponds to the rule configured in the first collaboration module 102. If not, the level information of the second page layer (not just the type) is sent to the second collaboration module. The second collaboration module receives the level information of the second page layer. It is detected whether the level of the second page layer is the same as the level of the first page layer currently displayed. If not, a second rule matching the type of the second page layer is matched from a preset rule library. The found second rule information is sent to the level management module 103 (although in this process, the level management module 103 may operate directly according to the level information rather than the rule information, in order to maintain consistency with the description, it is assumed that the rule contains the level conversion logic). The level management module 103 receives the second rule (or actually just the indication of the level conversion) from the second collaboration module. According to the second rule (or level conversion logic) matching the type of the second page layer, the level of the first page layer is converted into the level required by the second page layer. The second collaboration module receives the result processed by the level management module 103 (if sent). The level of the second page layer covers the level of the first page layer, ensuring that the second page layer occupies a dominant position in display.

[0062] For example: In an online editor, the user clicks a button to insert a table, which causes the second page layer (table editing page layer) to be called up. The micro front-end module 101 detects that this is a request to load the table editing page layer, but finds that there is no matching rule in the first collaboration module 102. Therefore, it sends the level information of the table editing page layer to the second collaboration module. After receiving the level information, the second collaboration module checks and finds that the level of the table editing page layer (assuming it is level 3) is different from the level of the currently displayed first page layer (such as the text editing page layer, the level is level 2). Then, it matches the second rule that matches the table editing page layer type from the rule library (the rule may simply specify the level that the table editing page layer should have). The level management module 103 receives the information from the second collaboration module (which may be a rule, but in this example we assume that it is just an indication of the level conversion), and converts the level of the first page layer from level 2 to level 3 (or actually sets the newly loaded table editing page layer to level 3) so that the table editing page layer can cover the text editing page layer.

[0063] The hierarchical update system provided in this embodiment can respond to the second loading instruction of the target object, dynamically call up the second page layer, and intelligently adjust the page hierarchy according to the matching of the page layer type and the configuration rules. This dynamic adjustment mechanism enables the system to adapt to the hierarchical requirements between different page layers, improving the flexibility of the page and the user experience. Through the intervention of the second collaboration module, the system can detect and handle the hierarchical conflict between the second page layer and the first page layer. When the hierarchies of the two are different, the system can automatically match the corresponding rules from the preset rule library, and adjust the hierarchy of the first page layer to match the second page layer accordingly, thereby achieving coordination and unification across page hierarchies.

[0064] In an optional implementation, the first collaboration module 102 is further configured to receive the level of the first page layer, and increment the initial level by a preset amount to the level of the first page layer.

[0065] The preset number of increments can be a fixed or dynamically calculated value, which is used to increment the initial level to the target level. Specifically, the first collaboration module 102 receives the target level of the first page layer from the micro-front-end module 101 or other related modules. Before performing the increment operation, an initial level needs to be determined. This initial level may be the system default or dynamically determined based on the current context. According to the preset number (which may be a fixed value or a value calculated based on some logic), the initial level is incremented to match the target level of the first page layer. The incremented level information is stored for subsequent use, such as page rendering, permission control, etc.

[0066] The level update system provided in this embodiment can significantly reduce the amount of code related to level management by encapsulating the level adjustment logic in the first collaboration module and adopting a preset quantity increment strategy. This not only reduces the complexity of the system, but also improves the readability and maintainability of the code.

[0067] In an optional embodiment, the system also includes: a monitoring module; a monitoring module, used to monitor whether the first rule and the type of the first page layer match, whether the second rule and the type of the second page layer match, if the first rule and the type of the first page layer do not match and / or the second rule and the type of the second page layer do not match, an alarm is issued in the form of a voice warning, an error prompt or a highlighted display.

[0068] The monitoring module can be a component in the system that is responsible for continuously monitoring and checking the status or conditions within the system to ensure that they meet the predetermined rules or standards. Voice warning / error prompt / highlight display: These are the alarm methods that the monitoring module may take when it finds a mismatch, used to notify users or system administrators that there is a problem. Monitoring settings: First, the monitoring module needs to be configured to identify which rules are associated with which page layers, and determine the trigger conditions and frequency of monitoring. The monitoring module collects information about rules and page layer types from the system periodically or in real time. The collected rule types are compared with the corresponding page layer types to determine whether there is a mismatch. If a mismatch is found, the monitoring module needs to decide which alarm method to take (such as voice warning, error prompt or highlight display). Based on the decision result, the corresponding alarm operation is performed to notify relevant personnel.

[0069] The hierarchical update system provided in this embodiment can continuously monitor the type matching between the rules and page layers, and promptly detect and report mismatches. This helps to quickly locate and fix potential problems, thereby avoiding errors or crashes in the system due to type mismatches, and improving the overall stability of the system. When the data entered by the user does not match the rules, the monitoring module can immediately notify the user through voice warnings, error prompts, or highlighted displays. This instant feedback mechanism reduces user confusion and frustration, helps users quickly understand the problem and make corresponding adjustments, thereby improving the user experience.

[0070] Combination Figure 2 As shown, in an optional embodiment, the micro front-end module (ie Figure 2 The micro frontend in the system can load the page, and then the hierarchical management module (that is, Figure 2 The micro front-end module calls up the sub-page pop-up layer (that is, the first page layer), the element pop center is the sub-page pop-up layer registration instance, the level management module obtains the level of the sub-page pop-up layer, returns the level to the element pop center, the element pop center performs incremental level processing on the initial level, and then the level management module updates the level, and then the element pop center covers the component level.

[0071] The micro front-end module calls up the main page pop-up layer. After initializing the component, it determines whether to increment through the antdesign component or custom component or custom style (that is, the second collaboration module mentioned above). If so, the hierarchy management module increments the hierarchy; if not, the hierarchy management module obtains the hierarchy and sets the hierarchy through the second collaboration module, and ends.

[0072] According to an embodiment of the present invention, a hierarchical updating method embodiment is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0073] In this embodiment, a level updating method is provided, which can be used in the above-mentioned level updating system. Figure 3 is a flowchart of a hierarchical updating method according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0074] Step S301 , in response to a first loading instruction of a target object, calling up a first page layer.

[0075] Step S302: Detect whether the first page layer type corresponds to the first rule configured in the first collaboration module.

[0076] Step S303: if the type of the first page layer corresponds to the first rule configured in the first collaboration module, the initial level is converted into the level of the first page layer according to the preset rule.

[0077] Step S304: Update the initial level to the level of the first page layer, so that the level of the first page layer covers the initial level.

[0078] In this embodiment, a hierarchical updating device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0079] This embodiment provides a hierarchical updating device, such as Figure 4 As shown, including:

[0080] A calling module 401 is used to call up the first page layer in response to the first loading instruction of the target object; a detection module 402 is used to detect whether the type of the first page layer corresponds to the first rule configured in the first collaboration module; a conversion module 403 is used to convert the initial level into the level of the first page layer according to a preset rule if the type of the first page layer corresponds to the first rule configured in the first collaboration module; an update coverage module 404 is used to update the initial level to the level of the first page layer so that the level of the first page layer covers the initial level.

[0081] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0082] The hierarchical update device in this embodiment is presented in the form of a functional unit, where the functional unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0083] The embodiment of the present invention also provides a computer device having the above Figure 4 The level update device shown.

[0084] See also Figure 5 , Figure 5 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 5 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 5 A processor 10 is taken as an example.

[0085] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0086] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

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

[0088] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0089] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0090] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0091] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0092] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A hierarchical update system, It is characterized in that The system includes: a micro front-end module, a hierarchical management module and a first collaboration module; The micro front-end module is used to call up the first page layer in response to the first loading instruction of the target object; detect whether the type of the first page layer corresponds to the first rule configured in the first collaboration module, and if the type of the first page layer corresponds to the first rule configured in the first collaboration module, send the level of the first page layer to the first collaboration module; The first collaboration module is used to receive the level of the first page layer, convert the initial level into the level of the first page layer according to a preset rule, and send the level of the first page layer to the level management module; A level management module, configured to receive the level of the first page level and update the initial level to the level of the first page level; The first collaboration module is further configured to, after the initial level is updated to the level of the first page layer, overwrite the initial level with the level of the first page layer.

2. The hierarchical updating system according to claim 1, It is characterized in that The first collaboration module is further used to register an instance for the first page layer, and after the level of the first page layer covers the initial level, process the first page layer based on the instance.

3. The hierarchical updating system according to claim 1, It is characterized in that The system further comprises: a second collaboration module; The micro front-end module is further configured to send the type of the first page layer to the second collaboration module if the type of the first page layer does not correspond to the rule configured in the first collaboration module; The second collaboration module is used to determine target rule information matching the type of the first page layer from a preset rule library based on the type of the first page layer, and send the target rule information to the hierarchy management module; The hierarchy management module is used to convert the initial hierarchy into the hierarchy of the first page layer according to the target rule, and send the hierarchy to the second collaboration module; The second collaboration module is further configured to update the initialization level to the level of the first page layer.

4. The hierarchical updating system according to claim 2, It is characterized in that The system further comprises: a second collaboration module; The micro front-end module is used to call up the second page layer in response to the second loading instruction of the target object, detect whether the type of the second page layer corresponds to the rule configured in the first collaboration module, and if the type of the second page layer does not correspond to the rule configured in the first collaboration module, send the level of the second page layer to the second collaboration module; The second collaboration module is used to receive the level of the second page layer and detect whether the level of the second page layer is the same as the level of the first page layer; if the level of the second page layer is not the same as the level of the first page layer, match a second rule matching the type of the second page layer from a preset rule library; The level management module is used to convert the level of the first page layer into the level of the second page layer according to a second rule matching the type of the second page layer; The second collaboration module is used to overwrite the level of the first page layer with the level of the second page layer.

5. The hierarchical updating system according to claim 1, It is characterized in that The first collaboration module is further used to receive the level of the first page layer, and to increment the initial level to the level of the first page layer according to a preset number.

6. The hierarchical updating system according to claim 4, It is characterized in that The system further comprises: a monitoring module; The monitoring module is used to monitor whether the first rule and the type of the first page layer match, whether the second rule and the type of the second page layer match. If the first rule and the type of the first page layer do not match and / or the second rule and the type of the second page layer do not match, an alarm is issued in the form of a voice warning, an error prompt or a highlighted display.

7. A hierarchical updating method, It is characterized in that The method is applied to the level update according to any one of claims 1 to 6, and the method comprises: In response to a first load instruction of the target object, calling up a first page layer; Detecting whether the first page layer type corresponds to a first rule configured in the first collaboration module; If the type of the first page layer corresponds to the first rule configured in the first collaboration module, converting the initial level into the level of the first page layer according to the preset rule; The initial level is updated to the level of the first page level, so that the level of the first page level covers the initial level.

8. A computer device, It is characterized in that include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the hierarchical updating method according to claim 7 by executing the computer instructions.

9. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the hierarchy updating method according to claim 7.

10. A computer program product, It is characterized in that The method comprises computer instructions for causing a computer to execute the hierarchy updating method according to claim 7.