Network configuration version management method, device and electronic device

Abstract

The present application relates to a method, device and electronic device for managing network configuration versions, including obtaining a CPE configuration version, determining a branch position of the CPE configuration version according to a parent branch position of the CPE configuration version, receiving an instruction to switch the CPE configuration version, and executing the corresponding CPE configuration version according to the instruction to switch the CPE configuration version. Through this method, in scenarios where past configurations need to be loaded repeatedly, the centralized management server only needs to notify the CPE to load a specific CPE configuration version, without wasting network resources and time to repeatedly send down the CPE configuration version. And based on the distributed characteristics of Git, it can allow operators to bypass the centralized management server and directly operate the configuration on the CPE, which is extremely convenient.

Description

Technical Field

[0001] The present application relates to the field of computer science and technology, and in particular to a method, device and electronic device for managing network configuration versions. Background Art

[0002] In SD-WAN, CPE configuration is generally managed centrally, that is, the configuration of each CPE is stored in a centralized management server. More advanced systems also have configuration version management, such as Figure 1 As shown, the database of the centralized management server stores multiple configuration versions of each CPE. The operator can send configurations to each CPE as needed.

[0003] But this also brings some problems. The centralized management server does not have branch management. Figure 2 The advantage of branch management is that when a version is used as a blueprint and inherited to the next version, two parallel and different modification methods are allowed, that is, it is intuitively split into two parallel branches for version management. The two branches have their own inheritance routes, and each branch can continue to have its own branches. Even if multiple versions are managed in a more advanced way, and each version can be inherited, the management cannot cope with complex configuration scenarios, such as Figure 3 Branch management as shown.

[0004] Since all configuration versions are stored in the centralized management server, and there is only one current version on the CPE, when the business needs to frequently change the CPE configuration for trial and error, such as Figure 4 As shown in the figure, the configuration needs to be sent repeatedly from the centralized management server. Since the CPE configuration files are generally large, and considering the management bandwidth and network delay, the work efficiency in this scenario is extremely low. Summary of the invention

[0005] In view of this, the present application proposes a method for managing network configuration versions to solve the problems embodied in the above-mentioned background technology.

[0006] According to one aspect of the present application, a method for managing a network configuration version is provided, comprising:

[0007] Get the CPE configuration version;

[0008] Determining a branch position of the CPE configuration version according to a parent branch position of the CPE configuration version;

[0009] Receive an instruction to switch the CPE configuration version;

[0010] According to the CPE configuration version switching instruction, the corresponding CPE configuration version is executed.

[0011] As an optional implementation scheme of the present application, determining the branch position of the CPE configuration version according to the parent branch position of the CPE configuration version includes:

[0012] Determine a previous CPE configuration version according to the logical relationship of the CPE configuration versions;

[0013] A branch of the CPE configuration version is added under the branch position of the previous CPE configuration version to determine the branch position of the CPE configuration version.

[0014] As an optional implementation scheme of the present application, adding a branch of the CPE configuration version under the branch position of the previous CPE configuration version, and after determining the branch position of the CPE configuration version, further comprising:

[0015] The branch where the CPE configuration version is located is set as an active branch, and the branch status of the version branch is obtained.

[0016] As an optional implementation scheme of the present application, before receiving the instruction to switch the CPE configuration version, the method further includes:

[0017] Preset synchronization information nodes,

[0018] According to the synchronization information node, the branch state of the version branch is synchronized to the end that issues the initial CPE configuration version.

[0019] As an optional implementation scheme of the present application, according to the instruction to switch the CPE configuration version, executing the corresponding CPE configuration version includes:

[0020] Determine the CPE configuration version to be executed in the version branch, and set the branch where the CPE configuration version is located as the active branch;

[0021] The CPE configuration version in the active branch is executed.

[0022] As an optional implementation scheme of the present application, after setting the branch where the CPE configuration version is located as the active branch, the method further includes:

[0023] After setting the branch where the CPE configuration version is located as an active branch, the branch status of the version branch is updated.

[0024] As an optional implementation scheme of the present application, it also includes:

[0025] The initial CPE configuration version serves as the root node in the version branch.

[0026] As an optional implementation scheme of the present application, it also includes:

[0027] The logical relationship between each CPE configuration version and the logical relationship between each branch with the initial CPE configuration version as the root node are obtained according to the version branch.

[0028] The present application also provides a network configuration version management device, including:

[0029] Get configuration module, used to get CPE configuration version;

[0030] A configuration location determination module, configured to determine a branch location of the CPE configuration version according to a parent branch location of the CPE configuration version;

[0031] A command receiving module, used for receiving a command for switching a CPE configuration version;

[0032] The configuration execution module is used to execute the corresponding CPE configuration version according to the switching CPE configuration version instruction.

[0033] The present application also provides an electronic device, comprising:

[0034] processor;

[0035] a memory for storing processor-executable instructions;

[0036] Wherein, the processor is configured to implement the above-mentioned network configuration version management method when executing the executable instructions.

[0037] Beneficial effects of this application:

[0038] The present invention obtains the CPE configuration version, determines the branch position of the CPE configuration version according to the parent branch position of the CPE configuration version, receives the CPE configuration version switching instruction, and executes the corresponding CPE configuration version according to the CPE configuration version switching instruction. In the scenario where the past configuration needs to be loaded repeatedly, the centralized management server only needs to notify the CPE to load a specific CPE configuration version, without wasting network resources and time to repeatedly send down the CPE configuration version. And based on the distributed characteristics of Git, it can allow operators to bypass the centralized management server and directly operate the configuration on the CPE, and then Git synchronizes the new version of the CPE configuration version generated by this operation to the centralized management server, which is extremely convenient.

[0039] Other features and aspects of the present application will become apparent from the following detailed description of exemplary embodiments with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate exemplary embodiments, features, and aspects of the present application and, together with the description, serve to explain the principles of the present application.

[0041] Figure 1 A diagram showing a centralized management server management configuration version of the present application;

[0042] Figure 2 A diagram showing a linear management configuration version of the present application is shown;

[0043] Figure 3 Shows the branch management configuration version diagram of this application;

[0044] Figure 4 A flowchart showing a CPE configuration version change of the present application;

[0045] Figure 5 A flowchart showing a method for managing a network configuration version according to an embodiment of the present application;

[0046] Figure 6 A flow chart of a CPE receiving a configuration version according to an embodiment of the present application is shown;

[0047] Figure 7 A diagram showing a branch state a of a CPE configuration version of an embodiment of the present application;

[0048] Figure 8 A branch state diagram b of a CPE configuration version according to an embodiment of the present application is shown;

[0049] Fig. 9 A branch state diagram c of a CPE configuration version according to an embodiment of the present application is shown;

[0050] Fig.10 A branch state diagram d showing a CPE configuration version of an embodiment of the present application;

[0051] Fig.11 A branch state e diagram showing a CPE configuration version of an embodiment of the present application;

[0052] Fig.12 A block diagram of a management device for a network configuration version of an embodiment of the present application is shown. DETAILED DESCRIPTION

[0053] Various exemplary embodiments, features and aspects of the present application will be described in detail below with reference to the accompanying drawings. The same reference numerals in the accompanying drawings represent elements with the same or similar functions. Although various aspects of the embodiments are shown in the accompanying drawings, the drawings are not necessarily drawn to scale unless otherwise specified.

[0054] Among them, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", "clockwise", "counterclockwise", "axial", "radial", "circumferential" and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present application or simplifying the description, and do not indicate or imply that the referred device or element must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present application.

[0055] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0056] The word “exemplary” is used exclusively herein to mean “serving as an example, example, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0057] In addition, in order to better illustrate the present application, numerous specific details are given in the following specific embodiments. It should be understood by those skilled in the art that the present application can also be implemented without certain specific details. In some examples, methods, means, components and circuits well known to those skilled in the art are not described in detail in order to highlight the subject matter of the present application.

[0058] In an SD-WAN environment, CPE is the bridge between the user end and the SD-WAN platform, ensuring that users can access remote resources securely and efficiently.

[0059] Git is an open source distributed version control system. Unlike traditional centralized version control systems (such as SVN), Git is distributed. This means that each Git user can completely clone the entire repository including the history on his or her own machine. In this way, even if the server fails, the local repository of any client can be used as a recovery point.

[0060] Example 1

[0061] Figure 5 FIG. 1 is a flow chart showing a method for managing a network configuration version according to an embodiment of the present application. Figure 5 As shown, the flow chart includes:

[0062] S100, obtain the CPE configuration version;

[0063] In this embodiment, Figure 6 , using Git technology, CPE acts as the local end of Git, and the centralized management server acts as the remote end of Git. When the centralized management server sends the CPE configuration version, the CPE pulls the CPE configuration version from the remote end of Git. In actual application, there will be multiple CPEs. To facilitate distinction, the remote end of Git assigns a version number to each CPE configuration version to distinguish the CPE configuration version that can be used in each CPE.

[0064] On the other hand, the existing CPE configuration version can also be modified by logging into the CPE through the terminal. Compared with the CPE configuration version before the modification, the new CPE configuration version will also be assigned a version number.

[0065] It should be noted that the modification in this embodiment refers to using Git technology to modify the content of the CPE configuration version until it is submitted. The content of the CPE configuration version can be content written according to user needs, including narrow configuration files, script codes, pictures, images and other binary files.

[0066] S200, determining a branch position of the CPE configuration version according to a parent branch position of the CPE configuration version;

[0067] The CPE configuration version is modified based on the existing CPE configuration version. Therefore, when there is a new CPE configuration version, it is necessary to determine which CPE configuration version it is modified from, such as Fig. 9 When receiving CPE configuration version 10002, using Git technology, when creating CPE configuration version 10002, it is known that it is a modification based on CPE configuration version 10001, then CPE configuration version 10001 is the parent node for CPE configuration version 10002, and the branch where it is located is called the parent branch. Therefore, in the case of CPE configuration version 10001 and CPE configuration version 10011, it is necessary to determine the branch position of CPE configuration version 10001, and then determine the branch position of CPE configuration version 10002.

[0068] S300, receiving an instruction to switch a CPE configuration version;

[0069] In this embodiment, the CPE receives an instruction to switch the CPE configuration version from the centralized management server. The centralized management server stores all CPE configuration versions on the CPE and information on branch management thereof. The operator of the centralized management server determines the CPE configuration version that is more suitable for the current business based on the branch management situation and business situation, and sends an instruction to switch the CPE configuration version to the CPE.

[0070] S400: Execute the corresponding CPE configuration version according to the CPE configuration version switching instruction.

[0071] After receiving the instruction, the CPE switches to the CPE configuration version that needs to be executed. There is no need for the centralized management server to resend the CPE configuration version to the CPE, saving network resources and time.

[0072] As an optional implementation scheme of the present application, determining the branch position of the CPE configuration version according to the parent branch position of the CPE configuration version includes: determining the previous CPE configuration version according to the logical relationship of the CPE configuration version; adding a branch of the CPE configuration version under the branch position of the previous CPE configuration version to determine the branch position of the CPE configuration version.

[0073] The ways in which CPE obtains CPE configuration versions include the initial CPE configuration version pulled from the remote end of Git for the first time and the CPE configuration version modified based on the existing CPE configuration version; among them, the modification based on the existing CPE configuration version can be modified and issued by the centralized management server or modified and submitted by the modification personnel when logging into the CPE at the terminal.

[0074] When modifying, not only the initial CPE configuration version 10001 as the root node can be modified, but also the CPE configuration version as a branch, that is, the branch of the branch, can be modified. For example Figure 3 The CPE configuration version 10021 is a modification of the CPE configuration version 10012, and the CPE configuration version 10012 is a branch of the CPE configuration version 10011, and the CPE configuration version 10011 is a branch of the CPE configuration version 10002, and the CPE configuration version 10002 is a branch of the root node CPE configuration version 10001.

[0075] Therefore, when obtaining the CPE configuration version, based on the characteristics of Git technology, according to the logical relationship, it can be known that the CPE configuration version is modified based on one of the existing CPE configuration versions, so a branch is added under one of the existing CPE configuration versions, so that the obtained CPE configuration version becomes its branch, thereby determining the branch position of the CPE configuration version.

[0076] As an optional implementation scheme of the present application, adding a branch of the CPE configuration version under the branch position of the previous CPE configuration version, and after determining the branch position of the CPE configuration version, it also includes: setting the branch where the CPE configuration version is located as an active branch to obtain the branch status of the version branch.

[0077] like Figure 6-Figure 11When a new CPE configuration version is added, the CPE determines the branch location of the new CPE configuration version based on the logical relationship, and sets the branch where the received CPE configuration version is located as the active branch. For example, when the initial CPE configuration version 10001 is received, Figure 7 As shown, at this time, it is the only branch in the CPE. The branch is taken as the active branch, that is, the effective CPE configuration version. At this time, the status of the version branch is branch status a.

[0078] Due to the distributed nature of the Git system, the centralized management server is not the only node that can issue CPE configuration versions. Figure 8 As shown, it is also feasible for operator A to log in to the CPE directly from the terminal to modify the initial CPE configuration version 10001, and obtain the modified CPE configuration version 10011 branch, which exists based on the initial CPE configuration version 10001 branch. The CPE configuration version 10011 branch is used as the active branch. At this time, the status of the version branch is branch status b.

[0079] Since the centralized management server may not have received the information about the CPE synchronization of the CPE configuration version 10011 branch, it has issued the CPE configuration version 10002 branch based on the initial CPE configuration version 10001 branch. Fig. 9 As shown, at this time, there are parallel CPE configuration version 10011 branch and CPE configuration version 10002 branch on the CPE, and the CPE configuration version 10002 branch is used as the effective active branch. At this time, the status of the version branch is branch status c.

[0080] As an optional implementation scheme of the present application, before receiving the instruction to switch the CPE configuration version, it also includes: presetting a synchronization information node, and synchronizing the branch state of the version branch to the end that issues the initial CPE configuration version according to the synchronization information node.

[0081] In this embodiment, the synchronization information node may be before receiving the CPE configuration version sent by the centralized management server, or before each CPE attempts to switch branches, or may be set to once every hour.

[0082] According to the set synchronization information node, the CPE synchronizes the version branch information containing all CPE configuration versions to the centralized management server. The centralized management server can know from the version branch which previous CPE configuration version each CPE configuration version is modified. This achieves the purpose of CPE local management of all CPE configuration version branches and synchronization with the centralized management server at a lower frequency.

[0083] As an optional implementation scheme of the present application, according to the instruction to switch the CPE configuration version, the corresponding CPE configuration version is executed, including: determining the CPE configuration version to be executed in the version branch, setting the branch where the CPE configuration version is located as the active branch; and executing the CPE configuration version in the active branch.

[0084] After receiving the instruction, the CPE determines the branch where the CPE configuration version to be executed is located from the version branch information, and sets the branch as the active branch, so that the CPE executes the better CPE configuration version.

[0085] As an optional implementation scheme of the present application, after setting the branch where the CPE configuration version is located as an active branch, it also includes: after setting the branch where the CPE configuration version is located as an active branch, updating the branch status of the version branch.

[0086] like Figure 7 -like Fig. 9 When the CPE obtains a new CPE configuration version, it uses the new CPE configuration version as the effective active branch and obtains the branch status of the version branch at this time.

[0087] There is also a situation where, when a CPE configuration version is reset to an active branch, the branch status will also change. Fig. 9 , set CPE configuration version 10002 as the active branch. At this time, the version branch status is branch status c. Fig.10 , the CPE configuration version 10021 obtained after operator B's modification is set as the effective active branch. At this time, the status of the version branch is branch status d.

[0088] After the CPE synchronizes the version branch with the centralized management server, the operator of the centralized management server obtains the complete branch information and believes that the previously issued CPE configuration version 10002 is better, so the operator asks the CPE to switch from CPE configuration version 10021 to CPE configuration version 10002. At this time, the centralized management server does not need to issue CPE configuration version 10002 again, and can directly notify the CPE to switch. After the CPE receives the instruction, Fig.11 , immediately set the branch where CPE configuration version 10002 is located as the effective active branch again. At this time, the status of the version branch is branch status e.

[0089] like Fig. 9 He Ru Fig.11 , although the active branches all correspond to CPE configuration version 10002, Fig.11 Compare Fig. 9Zhongduo added CPE configuration version 10021. Therefore, although CPE configuration version 10002 is set as the active branch again, the branch status corresponding to the version branch is different.

[0090] As an optional implementation scheme of the present application, it also includes: the initial CPE configuration version serves as the root node in the version branch.

[0091] The initial CPE configuration version is the first CPE configuration version of the CPE, and it is used as the root node to facilitate branch management of subsequent configuration versions that are continuously modified based on the initial CPE configuration version.

[0092] As an optional implementation scheme of the present application, the logical relationship between each CPE configuration version and the logical relationship of each branch with the initial CPE configuration version as the root node are obtained according to the version branch.

[0093] The logical relationship between different CPE configuration versions can be clearly obtained from the version branch. According to the logic of Git technology branch management, the relationship between each branch can be obtained.

[0094] Through the above method, in the scenario where the past configuration needs to be loaded repeatedly, the centralized management server only needs to notify the CPE to load a specific CPE configuration version, without wasting network resources and time to repeatedly send the CPE configuration version. And based on the distributed characteristics of Git, it can allow operators to bypass the centralized management server and directly operate the CPE configuration version on the CPE, and then the new version of the CPE configuration version generated by this operation is synchronized to the centralized management server by Git, which is extremely convenient.

[0095] Example 2

[0096] Based on the same principle as the above method, a network configuration version management device is also proposed, see Fig.12 , a network configuration version management device 100 of an embodiment of the present disclosure includes:

[0097] A configuration acquisition module 110 is used to acquire a CPE configuration version;

[0098] A configuration location determination module 120, configured to determine a branch location of the CPE configuration version according to a parent branch location of the CPE configuration version;

[0099] The instruction receiving module 130 is used to receive an instruction to switch the CPE configuration version;

[0100] The configuration execution module 140 is used to execute the corresponding CPE configuration version according to the CPE configuration version switching instruction.

[0101] Obviously, those skilled in the art should understand that all or part of the processes in the above-mentioned embodiment method can be implemented by instructing the relevant hardware through a computer program. The program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned control methods. The modules or steps of the present invention can be implemented by a general-purpose computing device. They can be concentrated on a single computing device or distributed on a network composed of multiple computing devices. Optionally, they can be implemented by program codes executable by computing devices, so that they can be stored in a storage device and executed by the computing device, or they can be made into individual integrated circuit modules respectively, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. In this way, the present invention is not limited to any specific combination of hardware and software.

[0102] Those skilled in the art can understand that the implementation of all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned control methods. Among them, the storage medium can be a disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), a flash memory (Flash Memory), a hard disk (Hard Disk Drive, abbreviated as: HDD) or a solid-state drive (SSD), etc.; the storage medium can also include a combination of the above-mentioned types of memory.

[0103] Example 3

[0104] Furthermore, an electronic device is proposed, comprising:

[0105] processor;

[0106] a memory for storing processor-executable instructions;

[0107] Wherein, the processor is configured to implement the network configuration version management method described in Example 1 when executing the executable instructions.

[0108] The electronic device of the embodiment of the present disclosure includes a processor and a memory for storing processor executable instructions, wherein the processor is configured to implement any of the above-mentioned network configuration version management methods when executing the executable instructions.

[0109] It should be noted that the number of processors may be one or more. At the same time, the electronic device of the embodiment of the present disclosure may also include an input device and an output device. The processor, memory, input device, and output device may be connected via a bus or in other ways, which are not specifically limited here.

[0110] The memory is a computer-readable storage medium for the method for managing network configuration versions, and can be used to store software programs, computer executable programs, and various modules, such as the program or module corresponding to the method for managing network configuration versions of the embodiment of the present disclosure. The processor executes various functional applications and data processing of the electronic device by running the software programs or modules stored in the memory.

[0111] The input device can be used to receive input numbers or signals. The signal can be a key signal related to user settings and function control of the device / terminal / server. The output device can include a display device such as a display screen.

[0112] The embodiments of the present application have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A method for managing network configuration versions, characterized in that: Introducing the existing mature Git system into CPE configuration management, the method includes: Get the CPE configuration version; Determine the branch position of the CPE configuration version according to the parent branch position of the CPE configuration version; Receive an instruction to switch the CPE configuration version; According to the CPE configuration version switching instruction, execute the corresponding CPE configuration version; When obtaining the CPE configuration version, by introducing Git technology, the CPE pulls the CPE configuration version from the remote end of Git to the local end; When the corresponding CPE configuration version is executed, based on the characteristics of Git technology, when the CPE configuration version is obtained, it can be known from the logical relationship that the CPE configuration version is modified based on one of the existing CPE configuration versions.

2. The method for managing network configuration versions according to claim 1, characterized in that: Determining the branch position of the CPE configuration version according to the parent branch position of the CPE configuration version includes: Determine a previous CPE configuration version according to the logical relationship of the CPE configuration versions; A branch of the CPE configuration version is added under the branch position of the previous CPE configuration version to determine the branch position of the CPE configuration version.

3. The method for managing network configuration versions according to claim 2, characterized in that: Adding a branch of the CPE configuration version under the branch position of the previous CPE configuration version, and after determining the branch position of the CPE configuration version, further comprising: The branch where the CPE configuration version is located is set as an active branch, and the branch status of the version branch is obtained.

4. The method for managing network configuration versions according to claim 3, characterized in that: Before receiving the instruction to switch the CPE configuration version, the method further includes: Preset synchronization information nodes, According to the synchronization information node, the branch state of the version branch is synchronized to the end that issues the initial CPE configuration version.

5. The method for managing network configuration versions according to claim 4, characterized in that: According to the CPE configuration version switching instruction, executing the corresponding CPE configuration version includes: Determine the CPE configuration version to be executed in the version branch, and set the branch where the CPE configuration version is located as the active branch; The CPE configuration version in the active branch is executed.

6. The method for managing network configuration versions according to claim 5, characterized in that: After setting the branch where the CPE configuration version is located as the active branch, the method further includes: After setting the branch where the CPE configuration version is located as an active branch, the branch status of the version branch is updated.

7. The method for managing network configuration versions according to claim 4, characterized in that: Also includes: The initial CPE configuration version serves as the root node in the version branch.

8. The method for managing network configuration versions according to claim 6, characterized in that: Also includes: The logical relationship between each CPE configuration version and the logical relationship between each branch with the initial CPE configuration version as the root node are obtained according to the version branch.

9. A network configuration version management device, characterized in that: include: Get configuration module, used to get CPE configuration version; A configuration location determination module, configured to determine a branch location of the CPE configuration version according to a parent branch location of the CPE configuration version; A command receiving module, used for receiving a command for switching a CPE configuration version; The configuration execution module is used to execute the corresponding CPE configuration version according to the CPE configuration version switching instruction.

10. An electronic device, characterized in that: include processor; a memory for storing processor-executable instructions; Wherein, the processor is configured to implement the network configuration version management method described in any one of claims 1-8 when executing the executable instructions.

Images