Distributed management system and method thereof, computer readable storage medium

Abstract

This disclosure provides a distributed management system and method thereof, and a computer-readable storage medium. The distributed management system includes: a multi-branch management module for establishing multiple types of branches based on the characteristics of different network states, each branch serving as a carrier of network states; and a planning engine module for performing network state attribute customization and network state operation functions based on the characteristics of each branch in the multi-branch management module. This disclosure implements storage based on the characteristics of network state data.

Description

Technical Field

[0001] This disclosure relates to the field of data communication technology, and in particular to a distributed management system and method thereof, and a computer-readable storage medium. Background Technology

[0002] Network planning has two requirements for data storage: (1) the comprehensiveness and traceability of network status data; and (2) based on requirement (1), it can realize automated data operation of dynamic network status mapping logical relationship based on time series.

[0003] Network states exhibit strong and weak correlations across multiple dimensions and levels. Besides the real-time changes in network state, the internal mapping logic and relationships are also dynamic. Analyzing the dynamic mapping logic of network states is of great significance for multi-granularity traffic prediction.

[0004] Traditional database storage methods can only store network state sample data for a specific granularity time series (e.g., daily). However, sample data at a certain point in time is highly likely to be integrated from multiple intermediate data. Since there is only one time series and the granularity is fixed, traditional database storage methods cannot fully cover all intermediate data and cannot meet the requirements of (1). In addition to failing to provide the correct data samples for requirement (2), it is also impossible to trace back to intermediate versions to check for problems. Therefore, traditional database storage methods cannot meet the needs of current network planning for real-time multi-granularity network state analysis and prediction.

[0005] Git Flow approach: Git Flow is a tool for project code version management. It provides integration and splitting services for different code modules of a project through a main chain and multiple branches, and comprehensively covers all intermediate module code in the project process through multiple time series. Compared with the traditional database model, its advantage lies in providing multi-dimensional data storage based on parallel time series, providing more comprehensive and accurate data for subsequent structural analysis of the data internally and between data, meeting the requirements (1). However, Git Flow has the following disadvantages:

[0006] a. It is only applicable to general data storage and cannot be stored according to the characteristics of network status data; b. Its data integration and splitting are based on single text, and the modules in the text cannot achieve arbitrary granular data operations; c. The integration process is entirely based on manual operation and cannot provide automated integration and splitting based on data mapping logic algorithms, which cannot meet the requirements (2). Summary of the Invention

[0007] The inventors of this disclosure have discovered problems in the prior art described above, and therefore propose a new technical solution to address at least one of the problems.

[0008] One technical problem addressed by this disclosure is to provide a distributed management system for storing network state data based on its characteristics.

[0009] According to one aspect of this disclosure, a distributed management system is provided, comprising: a multi-branch management module for establishing multiple types of branches according to the characteristics of different network states, each branch serving as a carrier of network states; and a planning engine module for performing network state attribute customization functions and network state operation functions based on the characteristics of each branch in the multi-branch management module.

[0010] In some embodiments, the multiple types of branches include: an engineering status branch, used to carry the network status from formal release to the engineering stage; and a planning status branch, used to take a certain engineering network status as the branch starting point, and calculate a new network status through the planning engine module based on a custom adjustment strategy for the comparison and analysis of the solutions.

[0011] In some embodiments, the plurality of planning state branches are used to generate a plurality of new planning network states for the engineering network state, wherein each planning state branch generates a new planning network state; the engineering state branch is also used to select the optimal planning network state from the plurality of new planning network states of the plurality of planning state branches, integrate the optimal planning network state with the current network state on the engineering state branch, and generate a new network state on the engineering state branch.

[0012] In some embodiments, the multiple types of branches further include: a planning scheme design branch, which is created based on the intermediate network state of the planning state branch and performs multi-scheme comparisons on multiple decisions; wherein, after the planning scheme design branch is selected, it is merged into the planning state branch and deleted.

[0013] In some embodiments, the plurality of branches further include: an emergency state branch, which is established starting from an intermediate network state on the engineering state branch to make temporary adjustments to the network.

[0014] In some embodiments, the network state attribute customization function includes: an automated generation function for network state label attributes; the network state operation function includes: jumping between branches of network state, customization and / or splitting of a single network state, and comparison and / or integration of multiple network states.

[0015] In some embodiments, the distributed management system further includes: a distributed management module for managing network status, containing all operation commands of the distributed version control system Git; wherein, the planning engine module executes the network status attribute customization function and the network status operation function by calling the operation commands of Git in the distributed management module.

[0016] According to another aspect of this disclosure, a distributed management method based on the distributed management system described above is provided, comprising: establishing multiple types of branches according to the characteristics of different network states, each branch serving as a carrier of network states; and performing network state attribute customization functions and network state operation functions based on the characteristics of each branch.

[0017] In some embodiments, the multiple types of branches include: engineering status branches and planning status branches; the steps of performing network status attribute customization functions and network status operation functions based on the characteristics of each branch include: jumping the engineering network status on the engineering status branch to the planning status branch; using the planning status branch with the engineering network status as the branch starting point, calculating a new network status based on a customized adjustment strategy for comparison and analysis of schemes; and jumping the new network status to the engineering status branch.

[0018] In some embodiments, the steps of performing network state attribute customization and network state operation functions based on the characteristics of each branch further include: jumping the engineering network state on the engineering state branch to multiple planning state branches; generating multiple new planning network states for the engineering network state using the multiple planning state branches, wherein each planning state branch generates a new planning network state; and selecting the optimal planning network state from the multiple new planning network states of the multiple planning state branches, integrating the optimal planning network state with the current network state on the engineering state branch, and generating a new network state on the engineering state branch.

[0019] In some embodiments, the multiple types of branches further include planning scheme design branches; the steps of performing network state attribute customization function and network state operation function based on the characteristics of each branch further include: creating the planning scheme design branch with the intermediate network state of the planning state branch as the base point, comparing multiple schemes for multiple decisions; and merging the planning scheme design branch into the planning state branch after it is determined to be selected, and deleting the planning scheme design branch.

[0020] In some embodiments, the multiple types of branches further include emergency state branches; based on the characteristics of each branch, the steps of performing network state attribute customization functions and network state operation functions further include: establishing the emergency state branch starting from the intermediate network state on the engineering state branch, and making temporary adjustments to the network.

[0021] In some embodiments, the network status attribute customization function and network status operation function are executed by invoking Git operation instructions in the distributed management module, wherein the distributed management module contains all Git operation instructions.

[0022] According to another aspect of this disclosure, a distributed management system is provided, comprising: a memory; and a processor coupled to the memory, the processor being configured to perform the method as described above based on instructions stored in the memory.

[0023] According to another aspect of this disclosure, a computer-readable storage medium is provided that stores computer program instructions thereon, which, when executed by a processor, implement the method described above.

[0024] In the aforementioned distributed management system, the multi-branch management module establishes multiple types of branches based on the characteristics of different network states, with each branch serving as a carrier of network states. The planning engine module, based on the characteristics of each branch in the multi-branch management module, executes network state attribute customization and network state operation functions. This achieves storage based on the characteristics of network state data, which can largely solve the problem that Git Flow cannot customize network data storage structures.

[0025] Other features and advantages of this disclosure will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0026] The accompanying drawings, which form part of this specification, illustrate embodiments of this disclosure and, together with the specification, serve to explain the principles of this disclosure.

[0027] This disclosure will become clearer with reference to the accompanying drawings and the following detailed description, wherein:

[0028] Figure 1 This is a structural block diagram illustrating a distributed management system according to some embodiments of the present disclosure;

[0029] Figure 2 This is a structural block diagram illustrating a distributed management system according to other embodiments of the present disclosure;

[0030] Figure 3 This is a flowchart illustrating a distributed management method according to some embodiments of the present disclosure;

[0031] Figure 4 This is a flowchart illustrating a distributed management method according to other embodiments of the present disclosure;

[0032] Figure 5 This is a flowchart illustrating a distributed management method according to other embodiments of the present disclosure;

[0033] Figure 6 This is a flowchart illustrating a distributed management method according to other embodiments of the present disclosure;

[0034] Figure 7 This is a structural block diagram illustrating a distributed management system according to other embodiments of the present disclosure;

[0035] Figure 8 This is a structural block diagram illustrating a distributed management system according to other embodiments of the present disclosure;

[0036] Figure 9 This is a schematic diagram illustrating the comparison results between the prior art and the methods of the embodiments of this disclosure. Detailed Implementation

[0037] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.

[0038] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0039] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use.

[0040] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0041] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0042] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0043] Figure 1This is a structural block diagram illustrating a distributed management system according to some embodiments of the present disclosure. For example... Figure 1 As shown, the distributed management system includes a multi-branch management module 110 and a planning engine module 120.

[0044] The multi-branch management module 110 is used to establish multiple types of branches according to the characteristics of different network states, with each branch serving as a carrier of the network state.

[0045] The planning engine module 120 is used to perform network status attribute customization and network status operation functions based on the characteristics of each branch in the multi-branch management module.

[0046] In some embodiments, the network state attribute customization function includes: an automated generation function for network state label attributes. This can standardize network state labels, improve the recognizability of states, and facilitate transitions between states.

[0047] In some embodiments, network state operation functions include: switching network states between branches, customizing and / or splitting individual network states, and comparing and / or integrating multiple network states.

[0048] In some embodiments, the planning engine module, based on the characteristics of each branch in the multi-branch management module, establishes an encapsulation layer on top of the git-python library in Python, mainly implementing functions for customizing network state attributes and manipulating network state. Here, the multi-branch management module and the planning engine module can form an encapsulation layer. This planning engine module can directly perform functions such as network state transitions, flexible integration, and splitting based on the planning engine module.

[0049] Thus, a distributed management system according to some embodiments of this disclosure is provided. In this distributed management system, a multi-branch management module establishes multiple types of branches based on the characteristics of different network states, with each branch serving as a carrier of network states; the planning engine module executes network state attribute customization functions and network state operation functions based on the characteristics of each branch in the multi-branch management module. This achieves storage based on the characteristics of network state data, which can largely solve the problem that Git Flow cannot customize network data storage structures.

[0050] In the aforementioned system, by adding a multi-branch management module and a planning engine module to the distributed management system Git Flow, modular network state elements and initial data structures can be customized. This allows for flexible splitting and integration of network state data at a finer granularity from top to bottom, and dynamic mapping logic abstraction from bottom to top. This solves the problems of Git Flow's inability to customize network data storage structures, large-granularity data operations on single files, and entirely manual data integration and splitting.

[0051] Figure 2 This is a structural block diagram illustrating a distributed management system according to other embodiments of the present disclosure. For example... Figure 2 As shown, the distributed management system includes a multi-branch management module 110 and a planning engine module 120. Additionally, Figure 2 The network status 260 is also shown.

[0052] The multi-branch management module 110 is used to create multiple types of branches based on the characteristics of different network states, with each branch serving as a carrier of network states. The multi-branch management module can utilize the planning engine module 120 to customize network states on the branches.

[0053] The planning engine module 120 is used to perform network status attribute customization function 121 and network status operation function 122 based on the characteristics of each branch in the multi-branch management module.

[0054] In some embodiments, such as Figure 2 As shown, the above-mentioned multiple types of branches include engineering state branch 111 and planning state branch 112.

[0055] Project status branch 111 is used to carry the network status from the formal release to the project phase.

[0056] Planning state branch 112 is used to calculate a new network state (e.g., the second network state) based on a custom adjustment strategy, starting from a certain engineering network state (e.g., the first network state), through the planning engine module, for comparison and analysis of the schemes.

[0057] For example, the planning engine module can be used to jump the engineering network state on engineering state branch 111 to planning state branch 112; using the engineering network state as the starting point of the planning state branch, a new network state can be calculated based on a custom adjustment strategy for comparison and analysis of solutions; and the planning engine module can then jump the new network state to the engineering state branch. This enables automated integration or splitting of Git Flow data.

[0058] In some embodiments, multiple planning state branches 112 are used to generate multiple new planning network states for the engineering network state, wherein each planning state branch generates a new planning network state. The engineering state branch 111 can also be used to select the optimal planning network state from the multiple new planning network states of the multiple planning state branches, integrate the optimal planning network state with the current network state on the engineering state branch, and generate a new network state on the engineering state branch.

[0059] For example, an engineering state branch, acting as the main chain, can derive multiple planning state branches. The engineering network state on an engineering state branch can be jumped to multiple planning state branches; multiple planning state branches can be used to generate multiple new planning network states for the engineering network state, with each planning state branch generating a new planning network state; and the optimal planning network state can be selected from the multiple new planning network states from the multiple planning state branches. This optimal planning network state is then integrated with the current network state on the engineering state branch, generating a new network state on the engineering state branch. This achieves the goal of obtaining the optimal integration result.

[0060] In some embodiments, the planning state branch can submit a new planning state as the starting point after the planning decision is clear. After all planning schemes within a phase are completed, they are integrated with the current network state on the engineering state branch, and a new network state is generated on the engineering state branch.

[0061] In some embodiments, such as Figure 2 As shown, the aforementioned branches of various types may also include a planning scheme design branch 113. The planning scheme design branch 113 is created based on the intermediate network state of the planning state branch, and performs multi-scheme comparisons for multiple decisions. After a selection is determined, the planning scheme design branch 113 is merged into the planning state branch, and then deleted.

[0062] For example, an engineering state branch, acting as the main chain, can derive multiple planning state branches, and each planning state branch can also derive multiple independent planning scheme design branches. When a network state on an engineering state branch jumps to multiple planning state branches, for each planning state branch, that network state can generate multiple intermediate network states. For each intermediate network state, multiple independent planning scheme design branches can be created. Through various decision-making processes and comparisons of multiple schemes, the optimal planning scheme design branch can be selected and merged into the planning state branch. Then, all intermediate network states can select their corresponding optimal planning scheme design branch. This ensures that the network state of the current planning state branch represents the optimal result for that planning state branch. Then, from the optimal results of multiple planning state branches, a further optimal network state is selected and jumps to the engineering state branch, integrating with the current network state on the engineering state branch, and generating a new network state on the engineering state branch. This achieves the goal of obtaining a more optimal integration result.

[0063] In some embodiments, such as Figure 2As shown, the aforementioned types of branches can also include an emergency state branch 114. The emergency state branch 114 is used to establish a temporary network adjustment starting from an intermediate network state (or network intermediate state) on the engineering state branch. This allows for temporary adjustments to the intermediate network state on the engineering state branch. This temporary adjustment can be set according to actual needs.

[0064] In some embodiments, such as Figure 2 As shown, the distributed management system may further include a distributed management module 230. This distributed management module 230 manages the network state 260 and contains all the operation commands of Git (a distributed version control system). The planning engine module executes network state attribute customization and network state operation functions by calling the Git operation commands in the distributed management module.

[0065] In this embodiment, the distributed management module manages the network state and is the foundation for flexible state integration and splitting, as well as network customization, encompassing all Git operations. This distributed management module is implemented using modules known to those skilled in the art. The planning engine module executes corresponding operations by calling multiple Git operation commands within the distributed management module.

[0066] In the above embodiments, the distributed management system includes a multi-branch management module 110, a planning engine module 120, and a distributed management module 230. Here, the multi-branch management module 110 and the planning engine module 120 form an encapsulation layer, that is, the multi-branch management module 110 and the planning engine module 120 are the basic elements of the encapsulation layer. In this embodiment, by adding an encapsulation layer to the distributed management system Git Flow, modular network state elements and initial data structures can be customized. From top to bottom, more granular network state data can be flexibly split and integrated, and from bottom to top, dynamic mapping logic abstraction can be achieved. The addition of this encapsulation layer can solve, as much as possible, the problems of existing Git Flow's inability to customize network data storage structures, large-granularity data operations on single files, and entirely manual data integration and splitting.

[0067] Figure 3 This is a flowchart illustrating a distributed management method according to some embodiments of the present disclosure. For example... Figure 3 As shown, the method includes steps S302 to S304.

[0068] In step S302, multiple types of branches are established according to the characteristics of different network states, and each branch is a carrier of the network state.

[0069] In step S304, based on the characteristics of each branch, network state attribute customization and network state operation functions are executed. For example, these functions are executed by calling Git operation commands in the distributed management module, which contains all Git operation commands.

[0070] Thus, a distributed management method according to some embodiments of this disclosure is provided. This method enables storage based on the characteristics of network state data, and can largely solve the problem that existing Git Flow cannot customize network data storage structures.

[0071] The following are combined with Figures 4 to 6 Describe in detail the specific operation of step S304 above.

[0072] In some embodiments, the multiple types of branches include: engineering status branches and planning status branches.

[0073] Figure 4 This is a flowchart illustrating a distributed management method according to other embodiments of the present disclosure. The method is... Figure 3 A specific implementation of step S304 in the above. For example... Figure 4 As shown, the method includes steps S402 to S406.

[0074] In step S402, the engineering network state on the engineering state branch is switched to the planning state branch.

[0075] In step S404, a new network state is calculated using the planning state branch with the engineering network state as the branch starting point and based on a custom adjustment strategy, for comparison and analysis of the schemes.

[0076] In step S406, the new network state is switched to the engineering state branch.

[0077] Thus, a distributed management method according to other embodiments of this disclosure is provided. This enables the automated integration or splitting of GitFlow data.

[0078] Figure 5 This is a flowchart illustrating a distributed management method according to other embodiments of the present disclosure. The method is... Figure 3 Another specific implementation of step S304 in the above. For example... Figure 5 As shown, the method includes steps S502 to S506.

[0079] In step S502, the engineering network state on the engineering state branch is jumped to multiple planning state branches.

[0080] In step S504, multiple new planning network states are generated for the project network state using multiple planning state branches, wherein each planning state branch generates a new planning network state.

[0081] In step S506, the optimal planning network state is selected from multiple new planning network states of multiple planning state branches, the optimal planning network state is integrated with the current network state on the engineering state branch, and a new network state is generated on the engineering state branch.

[0082] Thus, a distributed management method according to other embodiments of this disclosure is provided. This achieves the objective of obtaining optimal integration results.

[0083] In some embodiments, the multiple types of branches may also include planning scheme design branches.

[0084] Figure 6 This is a flowchart illustrating a distributed management method according to other embodiments of the present disclosure. The method is... Figure 3 Another specific implementation of step S304 in the above. For example... Figure 6 As shown, the method includes steps S602 to S604.

[0085] In step S602, a planning scheme design branch is created based on the intermediate network state of the planning state branch, and multiple schemes are compared for various decisions.

[0086] In step S604, after the planning scheme design branch is selected, it is merged into the planning status branch and the planning scheme design branch is deleted.

[0087] Thus, a distributed management method according to other embodiments of this disclosure is provided. This achieves the goal of obtaining a more optimal integration result.

[0088] In some embodiments, the multiple types of branches may further include emergency state branches. Step S304 may further include: establishing an emergency state branch starting from an intermediate network state on the engineering state branch, and making temporary adjustments to the network. This allows for temporary adjustments to the intermediate network state on the engineering state branch.

[0089] Figure 7 This is a structural block diagram illustrating a distributed management system according to other embodiments of the present disclosure. The distributed management system includes a memory 710 and a processor 720. Wherein:

[0090] The memory 710 can be a disk, flash memory, or any other non-volatile storage medium. The memory is used for storage. Figures 3 to 6 At least one of the instructions in the corresponding embodiment.

[0091] Processor 720 is coupled to memory 710 and can be implemented as one or more integrated circuits, such as a microprocessor or microcontroller. Processor 720 executes instructions stored in memory, enabling storage based on the characteristics of network state data, thus addressing the limitation of existing Git Flow's inability to customize network data storage structures.

[0092] In some embodiments, it may also be as follows Figure 8 As shown, the distributed management system 800 includes a memory 810 and a processor 820. The processor 820 is coupled to the memory 810 via a BUS bus 830. The distributed management system 800 can also be connected to an external storage device 850 via a storage interface 840 to access external data, and can also be connected to a network or another computer system (not shown) via a network interface 860, which will not be described in detail here.

[0093] In this embodiment, data instructions are stored in a memory and then processed by a processor, which enables storage based on the characteristics of network state data. This can solve the problem that existing Git Flow cannot customize network data storage structures as much as possible.

[0094] Figure 9 This is a schematic diagram illustrating the comparison results between the prior art and the methods of the embodiments of this disclosure.

[0095] like Figure 9 As shown, traditional database storage methods can only store network status sample data at a specific granularity time series (e.g., daily). However, sample data at a certain point in time is highly likely to be integrated from multiple intermediate data. Since there is only one time series and the granularity is fixed, traditional database storage methods cannot fully cover all intermediate data. Existing Git Flow provides integration and splitting services for different code modules of a project through a main chain and multiple branches, and comprehensively covers all intermediate module code in the project process through multiple time series.

[0096] Figure 9 The innovative Git Flow pattern based on encapsulation, as described in this disclosure, is the method of this embodiment. For example... Figure 9 As shown, in the embodiments of this disclosure, the main chain is the engineering status branch, and other branches (such as branch 1 or branch 2) are planning status branches or emergency status branches, etc. When branch 1 is a planning status branch, a planning scheme design branch can also be created ( Figure 9(Not shown in the image). Through the methods described in this embodiment, modular network state elements and initial data structures can be customized. From a top-down perspective, more fine-grained splitting and integration of network state data can be achieved, while from a bottom-up perspective, dynamic mapping logic abstraction can be implemented. This method solves the problems of existing Git Flow's inability to customize network data storage structures, large-granularity data operations on single files, and entirely manual data integration and splitting.

[0097] In some embodiments, this disclosure also provides a computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, implement... Figures 3 to 6 The disclosure includes at least one step of the method in a corresponding embodiment. Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, apparatus, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0098] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0099] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0100] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0101] This concludes the detailed description of the present disclosure. To avoid obscuring the concept of the disclosure, some details known in the art have not been described. Those skilled in the art will fully understand how to implement the technical solutions disclosed herein based on the above description.

[0102] While specific embodiments of this disclosure have been described in detail by way of example, those skilled in the art should understand that the examples are for illustrative purposes only and not intended to limit the scope of this disclosure. Those skilled in the art should understand that modifications can be made to the above embodiments without departing from the scope and spirit of this disclosure. The scope of this disclosure is defined by the appended claims.

Claims

1. A distributed management system, comprising: The multi-branch management module is used to create multiple types of branches based on the characteristics of different network states, with each branch serving as a carrier of network states. as well as The planning engine module is used to perform network status attribute customization and network status operation functions based on the characteristics of each branch in the multi-branch management module. The various types of branches include: an engineering status branch, which carries the network status from the formal release to the engineering stage; and a planning status branch, which uses a certain engineering network status as the starting point and, based on a custom adjustment strategy, calculates a new network status through the planning engine module for comparison and analysis of the solutions. The multiple planning state branches are used to generate multiple new planning network states for the engineering network state, wherein each planning state branch generates a new planning network state. The engineering state branch is also used to select the optimal planning network state from multiple new planning network states of multiple planning state branches, integrate the optimal planning network state with the current network state on the engineering state branch, and generate a new network state on the engineering state branch. The multiple types of branches also include: The planning scheme design branch is created based on the intermediate network state of the planning state branch, and multiple schemes are compared for various decisions; In this process, the planning scheme design branch is merged into the planning status branch after it is selected, and the planning scheme design branch is deleted.

2. The distributed management system according to claim 1, wherein, The multiple types of branches also include: An emergency state branch is established starting from an intermediate network state on the engineering state branch to make temporary adjustments to the network.

3. The distributed management system according to claim 1, wherein, The network status attribute customization function includes: the function of automatically generating network status label attributes; The network state operation functions include: switching between branches of the network state, customizing and / or splitting a single network state, and comparing and / or integrating multiple network states.

4. The distributed management system according to claim 1 further includes: The distributed management module is used to manage network status and contains all the operation commands for the distributed version control system Git. The planning engine module executes the network status attribute customization function and network status operation function by calling the Git operation instructions in the distributed management module.

5. A distributed management method based on the distributed management system as described in claim 1, comprising: Based on the characteristics of different network states, multiple types of branches are established, with each branch serving as a carrier of the network state. as well as Based on the characteristics of each branch, perform network state attribute customization and network state operation functions; Among them, the multiple types of branches include: engineering status branches and planning status branches; Based on the characteristics of each branch, the steps for performing network state attribute customization and network state operation functions include: jumping the engineering network state on the engineering state branch to the planning state branch; using the planning state branch with the engineering network state as the branch starting point, and based on a customized adjustment strategy, calculating a new network state for comparison and analysis of the schemes; and jumping the new network state to the engineering state branch. Based on the characteristics of each branch, the steps of performing network state attribute customization and network state operation functions further include: jumping the engineering network state on the engineering state branch to multiple planning state branches; using multiple planning state branches to generate multiple new planning network states for the engineering network state, wherein each planning state branch generates a new planning network state; and selecting the optimal planning network state from the multiple new planning network states of the multiple planning state branches, integrating the optimal planning network state with the current network state on the engineering state branch, and generating a new network state on the engineering state branch. The multiple types of branches also include planning scheme design branches; Based on the characteristics of each branch, the steps of performing network state attribute customization and network state operation functions further include: creating the planning scheme design branch with the intermediate network state of the planning state branch as the base point, comparing multiple schemes for various decisions; and merging the planning scheme design branch into the planning state branch after it is determined to be selected, and deleting the planning scheme design branch.

6. The distributed management method according to claim 5, wherein, The multiple types of branches also include emergency status branches; Based on the characteristics of each branch, the steps for performing network status attribute customization and network status operation functions also include: establishing the emergency status branch starting from the intermediate network status on the engineering status branch, and making temporary adjustments to the network.

7. The distributed management method according to claim 5, wherein, The network status attribute customization function and network status operation function are executed by calling the Git operation commands in the distributed management module, wherein the distributed management module contains all Git operation commands.

8. A distributed management system, comprising: Memory; as well as A processor coupled to the memory, the processor being configured to perform the method as described in any one of claims 5 to 7 based on instructions stored in the memory.

9. A computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, implement the method as claimed in any one of claims 5 to 7.

Images