Configuration management method, device, system, equipment, storage medium and program product

Abstract

The application provides a configuration management method, device, system, equipment, storage medium and program product, and relates to the technical field of satellite communication. The application sets an agent server between a NETCONF client and a plurality of devices, which is used for maintaining a model instance library of each device. When a target device needs to be configured, the agent server modifies a target configuration library, converts configuration content into a preset protocol format recognizable by the target device, and then delivers the configuration to the target device. In this way, the agent server can realize unified configuration management of the plurality of devices without installing a NETCONF Agent program in each device.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of satellite communication, in particular to a configuration management method, device, system, equipment, storage medium and program product. BACKGROUND

[0002] NETCONF protocol is one of the mainstream network management protocols at present, which is suitable for large-scale network, cloud environment and DevOps scene. The network device (i.e. switch or router) supporting NETCONF protocol usually runs a NETCONF Agent (protocol agent module) program inside, which is responsible for processing the request from the NETCONF Client and storing the configuration data into the model instance library (YANG DB), and meanwhile calling the related function module to complete the configuration management operation.

[0003] As Figure 1 It can be known that the NETCONF Agent program runs inside the network device, which is responsible for storing the configuration data, state data and the like of each module of the network device in the model instance library (YANG DB) based on YANG modeling, and is also responsible for updating the model instance library based on the configuration instruction of the configuration client and deploying the modified configuration to the corresponding module. However, this NETCONF Agent program is only suitable for the conventional network device, such as switch, router and the like.

[0004] In the field of satellite communication, the satellite communication management system usually needs to manage various baseband devices in the terminal device and satellite base station. Among them, the terminal device includes vehicle-mounted satellite terminal, ship-mounted satellite terminal, airborne satellite terminal, fixed station, IoT (Internet of Things) device and the like satellite communication device, and the baseband device includes clock device, modulator, demodulator, antenna, satellite gateway, satellite signaling control device and the like device.

[0005] Since various baseband devices and terminal devices are from different manufacturers respectively, supported configuration management protocols are different, for example, some devices support using SNMP (Simple Network Management Protocol), some devices support using CLI (Command-Line Interface), some devices support using gRPC (Google Remote Procedure Call), etc. In this case, if uniform configuration management of these devices is to be implemented based on the existing NETCONF Agent technology, these devices themselves need to be modified (invasive installation of Agent), but some devices are limited by hardware capability or security policy and do not have the ability to install and run the NETCONF Agent.

[0006] Therefore, in the field of satellite communication, it is currently impossible to install a conventional NETCONF Agent program in all terminal devices and all baseband devices to achieve uniform configuration. SUMMARY

[0007] The purpose of the present application is to provide a configuration management method, device, system, equipment, storage medium and program product to improve the problems existing in the prior art.

[0008] Embodiments of the present application can be implemented as follows:

[0009] In a first aspect, the present application provides a configuration management method applied to a proxy server, wherein the proxy server communicates with a NETCONF client and a plurality of devices; the proxy server maintains a model instance library of each device, and the method comprises the following steps:

[0010] receiving a configuration request sent by the NETCONF client;

[0011] analyzing the configuration request based on the NETCONF protocol to determine a target device and its device type, a target configuration library and configuration content; the target configuration library is any one of a candidate configuration library, a running configuration library and a startup configuration library included in the model instance library;

[0012] updating the target configuration library in the model instance library of the target device based on the configuration content;

[0013] sending the configuration content to the target device in a preset protocol format recognizable by the target device, so that the target device performs configuration modification based on the configuration content in the preset format.

[0014] In an optional embodiment, the proxy server further maintains a registration table reflecting a plurality of adapters and a plurality of registration paths associated with each device type in the satellite communication system, one of the adapters corresponding to one of the registration paths uniquely;

[0015] The storage structure of the target configuration library is a tree structure composed of a root node, a plurality of branch nodes and a plurality of leaf nodes, the root node representing the target device, the branch nodes representing a module or a sub-module of the target device, and the leaf nodes representing a configurable item in a module or a sub-module;

[0016] The step of converting the configuration content into a preset protocol format recognizable by the target device and sending the configuration content to the target device includes:

[0017] Obtaining a node path of each changed node in the target configuration library;

[0018] Based on the device type of the target device and the node path of each changed node, at least one target adapter matched from the registration table is found out;

[0019] Determining a sub-content responsible for each target adapter from the configuration content;

[0020] Respectively calling each target adapter to convert each sub-content into the preset protocol format and send the sub-content to the target device, so that the target device is configured and modified based on each sub-content in the preset format.

[0021] In an optional embodiment, the registration table includes a plurality of registration table entries, each of which represents the association relationship between a device type, an adapter and a registration path;

[0022] The step of finding out at least one target adapter matched from the registration table based on the device type of the target device and the node path of each changed node includes:

[0023] For each changed node, the changed node is taken as a current node;

[0024] Based on the node path of the current node and the device type of the target device, it is determined whether there is a target registration table entry matched from the registration table;

[0025] If there is, the adapter in the target registration table entry is taken as the target adapter;

[0026] If there is not, the parent node of the current node is taken as a new current node;

[0027] After the node path of the current node is obtained from the target configuration library, the step of searching the registry for a matching target registry entry based on the node path of the current node and the device type of the target device is executed until the target registry entry is found in the registry.

[0028] In an optional embodiment, the step of determining the sub-content responsible for each target adapter from the configuration content comprises:

[0029] For each target adapter, the target registration path corresponding to the target adapter is determined from the registry.

[0030] Each change node under the node of the target registration path is determined from the target configuration library to obtain all change nodes under the target registration path.

[0031] The part corresponding to all change nodes under the target registration path is obtained from the configuration content to obtain the sub-content responsible for the target adapter.

[0032] In an optional embodiment, the method further comprises:

[0033] After each adapter receives the configuration response in the preset protocol format returned by the target device, a configuration response in the NETCONF format is returned to the NETCONF client; the configuration response represents configuration success or configuration failure.

[0034] In a second aspect, the application provides a configuration management device applied to a proxy server, wherein the proxy server communicates with a NETCONF client and a plurality of devices; the proxy server maintains a model instance library of each device; the device comprises:

[0035] A receiving module is configured to receive a configuration request sent by the NETCONF client.

[0036] An analysis module is configured to analyze the configuration request based on the NETCONF protocol, determine a target device and its device type, a target configuration library, and configuration content; the target configuration library is any one of a candidate configuration library, a running configuration library, and a startup configuration library included in the model instance library.

[0037] An updating module is configured to update the target configuration library in the model instance library of the target device based on the configuration content.

[0038] An adaptation module is configured to convert the configuration content into a preset protocol format recognizable by the target device and send it to the target device, so that the target device performs configuration modification based on the configuration content in the preset format.

[0039] In a third aspect, the present application provides a satellite communication management system, comprising an agent server, a NETCONF client and a plurality of devices; the agent server is in communication connection with the NETCONF client and the plurality of devices, and the agent server maintains a model instance library of each device; wherein:

[0040] The NETCONF client is configured to send a configuration request to the agent server;

[0041] The agent server is configured to parse the configuration request based on the NETCONF protocol, determine a target device and its device type, a target configuration library and configuration content; the target configuration library is any one of a candidate configuration library, a running configuration library and a startup configuration library included in the model instance library;

[0042] The agent server is further configured to update the target configuration library in the model instance library of the target device based on the configuration content;

[0043] The agent server is further configured to convert the configuration content into a preset protocol format recognizable by the target device and send the configuration content to the target device;

[0044] The target device is configured to perform configuration modification based on the configuration content in the preset format.

[0045] In a fourth aspect, the present application provides an electronic device, comprising a memory and a processor, the memory stores a software program, and the processor executes the software program to implement the configuration management method of the first aspect.

[0046] In a fifth aspect, the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the configuration management method of the first aspect.

[0047] In a sixth aspect, the present application provides a program product, which is executed by a processor to implement the configuration management method of the first aspect.

[0048] Compared with the prior art, the embodiment of the application provides a configuration management method, device, system, equipment, storage medium and program product. In a satellite communication management system, a proxy server communicates with a NETCONF client and a plurality of devices. The proxy server maintains a model instance library of each device. The process of realizing unified configuration through the proxy server is as follows: based on a NETCONF protocol, a configuration request sent by the NETCONF client is parsed, a target device and a device type thereof, a target configuration library and configuration content are determined; the target configuration library is any one of a candidate configuration library, a running configuration library and a startup configuration library included in the model instance library; then, based on the configuration content, the target configuration library in the model instance library of the target device is updated; finally, the configuration content is converted into a preset protocol format recognizable by the target device and is sent to the target device, so that the target device is configured and modified based on the configuration content in the preset format. The proxy server is arranged between the NETCONF client and the plurality of devices, and is used for maintaining the model instance library of each device. When one of the target devices needs to be configured, the proxy server first modifies the target configuration library, and then converts the configuration content into the preset protocol format recognizable by the target device and issues the configuration to the target device. In this way, the NETCONF Agent program does not need to be installed in each device, and unified configuration management of the plurality of devices is realized through the proxy server. BRIEF DESCRIPTION OF DRAWINGS

[0049] In order to more clearly illustrate the technical solutions of the embodiments of the application, the following will briefly introduce the drawings needed to be used in the embodiments. It should be understood that the following drawings only show some of the embodiments of the application, and therefore should not be regarded as a limitation to the scope. For those skilled in the art, other related drawings can also be obtained without creative labor on the basis of these drawings.

[0050] Figure 1 A scene diagram for realizing configuration based on the NETCONF protocol in the prior art.

[0051] Figure 2 A scene diagram for the application of the embodiment of the application.

[0052] Figure 3 A flowchart of a configuration management method provided by the embodiment of the application.

[0053] Figure 4 A structure diagram of a model instance library provided by the embodiment of the application.

[0054] Figure 5 A tree structure diagram of a target configuration library in a model instance library of a clock device provided by the embodiment of the application.

[0055] Figure 6A structural schematic diagram of an electronic device is provided for an embodiment of the present application. DETAILED DESCRIPTION

[0056] In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. The components of the embodiments of the present application described and shown in the drawings can be arranged and designed in various different configurations.

[0057] Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of the application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0058] It should be noted that: similar reference numbers and letters represent similar items in the following drawings, therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings.

[0059] In the description of the present application, it should be noted that if the terms "upper", "lower", "inner", "outer" and the like indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, or the orientation or positional relationship when the product of the present application is used, which is only for the convenience of describing the present application and simplifying the description, and does not indicate or imply that the device or element must have a particular orientation, be constructed and operated in a particular orientation, therefore, it cannot be understood as a limitation on the present application.

[0060] In addition, if the terms "first", "second" and the like appear, they are only used to distinguish the description, and cannot be understood as indicating or implying relative importance.

[0061] It should be noted that the features in the embodiments of the present application can be combined with each other without conflict.

[0062] Here, first, the key words or key terms related to the present application are introduced:

[0063] 1. NETCONF (Network Configuration Protocol): a network management protocol, a network administrator or configuration center can connect the devices supporting the protocol through the NETCONF protocol to complete network configuration, state monitoring, alarm information collection and other related operations.

[0064] NETCONF protocol supports transactional operation (commit, rollback), configuration and state separation, model-driven data operation based on YANG (Yet Another Next Generation, a flexible modeling language) model.

[0065] 2、YANG: a data modeling language for network device configuration and management, designed for automated network operation and maintenance. It defines the standardized structure of device configuration, state data and remote operation, and is the key basis of SDN (Software Defined Network) and network programmability. YANG is used to describe the configuration, state, notification time, operation and maintenance data information of specific network elements and the constraint relationship between them.

[0066] First, the application scenario of the present application is introduced.

[0067] Please refer to Figure 2 The configuration management method provided by the embodiment of the present application is applied to the proxy server as shown in Figure 2 The proxy server communicates with the NETCONF client and multiple devices, and the proxy server maintains a model instance library of each device.

[0068] Optionally, the NETCONF client and the proxy server can be respectively deployed and run on two independent physical servers, or the NETCONF client and the proxy server can also be deployed and run on the same physical server.

[0069] The present application mainly relates to a satellite communication management system in the field of satellite communication, and the NETCONF client is responsible for unified configuration management of multiple devices. Therefore, part of the multiple devices is baseband equipment of a ground master station, such as clock equipment, modulators, demodulators, antennas, satellite gateways, satellite signaling control equipment and the like, and another part of the multiple devices is terminal equipment with satellite communication function, for example, satellite communication equipment including vehicle-mounted satellite terminal, ship-mounted satellite terminal, airborne satellite terminal, fixed station, IoT equipment and the like.

[0070] Please refer to Figure 3 The configuration management method provided by the embodiment of the present application includes the following steps S101-S104.

[0071] S101, receiving a configuration request sent by the NETCONF client.

[0072] When the staff needs to configure any one of the multiple devices, the NETCONF client can be started, and remote network configuration is realized by using the NETCONF client.

[0073] S102, based on the NETCONF protocol, the configuration request is parsed, and the target device and its device type, the target configuration library and the configuration content are determined.

[0074] In the embodiment, compared with the configuration request of the prior art, the target parameter is added in the configuration request of the application, the target parameter includes the IP address of the target device and the device type information. Therefore, the configuration request is parsed, and the target configuration library to which the current configuration operation is directed, the target device to be configured and the device type to which the target device belongs, the target configuration library to be updated and the configuration content are determined.

[0075] S103, based on the configuration content, the target configuration library in the model instance library of the target device is updated.

[0076] In the embodiment, the proxy server updates the corresponding target configuration library in the model instance library of the target device according to the configuration content.

[0077] S104, the configuration content is converted into a preset protocol format recognizable by the target device, and is sent to the target device, so that the target device is configured and modified based on the configuration content in the preset format.

[0078] In the embodiment, after the model instance library of the target device is updated, the proxy server also needs to convert the configuration content into a preset protocol format recognizable by the target device, and the preset protocol format is a configuration management protocol supported by the target device, such as an SNMP protocol, a CLI or other protocols.

[0079] Because different devices support different configuration management protocols in the field of satellite communication, the proxy server has the function of reorganizing the configuration content originally expressed based on the NETCONF protocol into a data structure conforming to the protocol specification of the target device. Then, the proxy server sends the configuration content after format conversion to the target device, so that the target device can correctly parse and apply the configuration content based on the protocol format supported by itself, thereby completing the configuration modification of itself.

[0080] The configuration management method provided by the embodiment of the application sets a proxy server between the NETCONF client and a plurality of devices, which is used to maintain the model instance library of each device. When one of the target devices needs to be configured, the proxy server first modifies the target configuration library, and then converts the configuration content into a preset protocol format recognizable by the target device, and then sends the configuration to the target device. In this way, it is not necessary to install the NETCONF Agent program into each device, but the unified configuration management of the plurality of devices is realized through the proxy server.

[0081] It should be understood that the above description should be combined with the accompanying drawings. Figure 4In the standard model instance library, the Schema definition and three data instances conforming to the Schema definition are included: candidate, running, startup, i.e. candidate configuration library (candidate), running configuration library (running) and startup configuration library (startup).

[0082] The Schema definition is modeled by using YANG syntax to specify the organization form, hierarchical structure and semantic constraints of each module, sub-module under the module and all configurable items of a device. The candidate configuration library is used to temporarily store the configuration modification which has not yet taken effect; the running configuration library records the current actual effective configuration state; and the startup configuration library saves the default configuration loaded after the device restarts.

[0083] In the optional example, the clock device of the ground master station is taken as an example, which includes a clock 1pps (pulse per second) transmission module (abbreviated as pps module), a clock master-slave module (abbreviated as cs-ms module); the pps module includes a clock source configuration module (abbreviated as ppscfg module) and a clock sending configuration module (abbreviated as timer module); and the cs-ms module includes a master-slave configuration module (abbreviated as mscfg module) and a master-slave state module (abbreviated as msinfo module).

[0084] Taking the pps module as an example, in the Schema definition of the model instance library of the clock device, the definition content of the pps module is as follows (the text after / / represents an annotation):

[0085] / / pps module

[0086] module pps {

[0087] yang-version 1.1;

[0088] namespace "coresat.com:yang:pps";

[0089] prefix "pps";

[0090] import types {

[0091] prefix types;

[0092] }

[0093] organization "Coresat Inc.";

[0094] contact "liguanghao";

[0095] description "1PPS signal generation model...";

[0096] revision 2025-01-14 {

[0097] description "init";

[0098] }

[0099] / / Information about 6 configurable items under ppscfg module

[0100] container ppscfg {

[0101] leaf pps_mux {type int32; description "PPS source";}

[0102] leaf pps_out_en {type int32;}

[0103] leaf lnb_pwr {type string {pattern "on|off";}}

[0104] leaf lnb_clk {type string {pattern "on|off";}}

[0105] leaf buc_clk {type string {pattern "on|off";}}

[0106] leaf lnb_22k {type string {pattern "on|off";}}

[0107] }

[0108] / / Information about 2 configurable items under timer module

[0109] container timer {

[0110] leaf group_ip {type types:ipv4_address;}

[0111] leaf group_port {type int32;}

[0112] }

[0113] }

[0114] For example, the ppscfg module and the timer module under the pps module, in the candidate configuration library of the model instance library of the clock device, the content about the ppscfg module and the timer module is as follows:

[0115] <ppscfg xmlns="coresat.com:yang:pps"> / / pending configuration for ppscfg module

[0116] <pps_mux>2< / pps_mux>

[0117] <pps_out_en>511< / pps_out_en>

[0118] <lnb_pwr>off< / lnb_pwr>

[0119] <lnb_clk>off< / lnb_clk>

[0120] <buc_clk>off< / buc_clk>

[0121] <lnb_22k>off< / lnb_22k>

[0122] < / ppscfg>

[0123] <timer xmlns="coresat.com:yang:pps"> / / pending configuration of timer module

[0124] <group_ip>239.0.0.1< / group_ip>

[0125] <group_port>1998< / group_port>

[0126] < / timer>

[0127] For example, the ppscfg module and the timer module under the pps module, in the running configuration library of the model instance library of the clock device, the content about the ppscfg module and the timer module is as follows:

[0128] <ppscfg xmlns="coresat.com:yang:pps"> / / current configuration of the ppscfg module

[0129] <pps_mux>2< / pps_mux>

[0130] <pps_out_en>511< / pps_out_en>

[0131] <lnb_pwr>off< / lnb_pwr>

[0132] <lnb_clk>off< / lnb_clk>

[0133] <buc_clk>off< / buc_clk>

[0134] <lnb_22k>on< / lnb_22k>

[0135] < / ppscfg>

[0136] <timer xmlns="coresat.com:yang:pps"> / / current configuration of the timer module

[0137] <group_ip>239.0.0.100< / group_ip>

[0138] <group_port>1998< / group_port>

[0139] < / timer>

[0140] For example, the ppscfg module and the timer module under the pps module, in the startup configuration library of the model instance library of the clock device, the content about the ppscfg module and the timer module is as follows:

[0141] <ppscfg xmlns="coresat.com:yang:pps"> / / startup run configuration for ppscfg module

[0142] <pps_mux>2< / pps_mux>

[0143] <pps_out_en>511< / pps_out_en>

[0144] <lnb_pwr>off< / lnb_pwr>

[0145] <lnb_clk>off< / lnb_clk>

[0146] <buc_clk>off< / buc_clk>

[0147] <lnb_22k>off< / lnb_22k>

[0148] < / ppscfg>

[0149] <timer xmlns="coresat.com:yang:pps"> / / start run configuration for timer module

[0150] <group_ip>239.0.0.1< / group_ip>

[0151] <group_port>1998< / group_port>

[0152] < / timer>

[0153] It can be seen from the above example that the Schema definition describes which data items are included in the ppscfg module and the timer module under the pps module respectively, and the data type of each configurable item and even some related information (such as description, state example, attribute, etc.), and the three configuration libraries respectively include the specific configuration of the configuration items of the ppscfg module and the timer module.

[0154] Correspondingly, it can be known from the above content that the content of the clock device in the configuration library can be abstracted into a tree structure as shown in Figure 5 In addition to the configuration items in the above example, the three configurable items under the mscfg module and the ten configuration items under the msinfo module are also shown in Figure 5 It should be noted that the above example is only an example, and the specific content in the three configuration libraries is not limited in the present application, and in actual situations, the content of the three configuration libraries in the model instance library can be different.

[0155]

[0156] ​Optionally, the target configuration library is any one of a candidate configuration library, a running configuration library and a startup configuration library included in the model instance library. The storage structure of the target configuration library is a tree structure composed of a root node, a plurality of branch nodes and a plurality of leaf nodes, the root node represents the target device, the branch node represents a module or a sub-module of the target device, and the leaf node represents a configurable item in the module or the sub-module.

[0157] In the field of satellite communication, the configuration management protocols supported by devices of the same type are usually the same. Therefore, in order to ensure that the proxy server can perform unified configuration management in a complex satellite communication environment with various device types and heterogeneous protocol interfaces, a plurality of groups of adapters (each group of adapters includes at least one adapter) are run in the proxy server, each group of adapters is responsible for configuration content conversion processing of a type of device, and the proxy server also maintains a registry.

[0158] The registry can reflect a plurality of adapters and a plurality of registration paths associated with each device type in the satellite communication system, and one adapter corresponds to one registration path. Therefore, the implementation of the above step S104 can include S1041-S1044:

[0159] S1041, obtaining a node path of each changed node in the target configuration library that has changed.

[0160] In this embodiment, the node path is a complete path string composed of nodes at each level from the root node to the changed node, which is used to uniquely identify the position of the changed node in the tree structure.

[0161] S1042, based on the device type of the target device and the node path of each changed node, finding at least one target adapter matched from the registry.

[0162] Since the functions of the modules of the target device are different, the configuration data can be quite different. Therefore, in a group of adapters corresponding to a type of device, each adapter can be responsible for configuration content conversion processing of different modules. Therefore, the proxy server needs to find at least one target adapter from the registry in combination with the device type of the target device and the node path of each changed node, and these target adapters can be responsible for converting the configuration data of all changed nodes.

[0163] Optionally, the registry includes a plurality of registry entries, and each registry entry represents the association relationship among a device type, an adapter and a registration path. Therefore, for each changed node, the process of finding a target adapter can include:

[0164] S1, taking the changed node as a current node;

[0165] S2, find whether there is a matched target registry item from the registry based on the node path of the current node and the device type of the target device;

[0166] S3, take the parent node of the current node as a new current node, and acquire the node path of the current node from the target configuration library;

[0167] S4, take the adapter in the target registry item as a target adapter.

[0168] Wherein, the registration path in the target registry item is the same as the node path of the current node. After performing S2, if there is no matched target registry item, after performing step S3, return to perform step S2 until the target registry item is found from the registry; if there is a matched target registry item, perform the following step S4 to determine the target adapter.

[0169] Exemplarily, assuming that the configuration personnel wants to configure 6 configuration items of the ppscfg module of the clock device into Figure 5 As shown, the content of the configuration request (edit-config request) initiated by the NETCONF client is:

[0170] <edit-config xmlns:nca="”coresat.com:yang:nms:cs-netconf-agent”">

[0171] <target>

[0172] <running / > / / Specified target configuration library

[0173] <nca:agent> / / added target parameters

[0174] <nca:device_id>192.168.1.1< / nca:device_id> / / IP address

[0175] <nca:device_type>CLOCK< / nca:device_type> / / device type

[0176] < / nca:agent>

[0177] < / target>

[0178] <config>

[0179] <ppscfg xmlns="coresat.com:yang:pps"> / / configure content

[0180] <pps_mux>2< / pps_mux>

[0181] <pps_out_en>511< / pps_out_en>

[0182] <lnb_pwr>on< / lnb_pwr>

[0183] <lnb_clk>off< / lnb_clk>

[0184] <buc_clk>off< / buc_clk>

[0185] <lnb_22k>off< / lnb_22k>

[0186] < / ppscfg>

[0187] < / config>

[0188] < / edit-config>

[0189] The proxy server parses the content of the above configuration request, that is, it can identify that the request is to configure the clock type device with the IP address of 192.168.1.1, and the target configuration library is the running configuration library. Then the proxy server stores the configuration parameters of the ppscfg module into the running configuration library based on the configuration content in the above configuration request, that is, the running configuration library becomes as shown in Figure 5 .

[0190] After the running configuration library is updated, the proxy server determines that the changed change node is the 6 nodes under the ppscfg module in Figure 5 , that is, the node path of the 6 nodes can be obtained, for example Figure 5 , the node path of the pps_mux node is: / pps:ppscfg:pps_mux.

[0191] As shown in Figure 5 , assuming that the device type of CLOK in the registry includes 4 adapters, and the corresponding 4 registration paths are the node paths of the 4 green nodes in Figure 2 : / pps:ppscfg, / pps:timer, / pps:mscfg, / pps:msinfo.

[0192] So based on the node path of the pps_mux node ( / pps:ppscfg:pps_mux ), no matching registry entry exists in the registry, then the node path of the parent node ( ppscfg module) of the pps_mux node ( / pps:ppscfg ) is used, i.e. the target adapter can be matched.

[0193] Similarly, for the other 5 variant nodes under the ppscfg module, the process of finding the target adapter is consistent, and the target adapters determined by the final 6 variant nodes are the same.

[0194] It should be noted that the example is only an example, and is not limited herein. In the case where the configuration attribute structure corresponding to the target device is complex and the configuration content is more, the number of target adapters determined can not be unique.

[0195] The search process of the above steps S1-S4 adopts a bottom-up path backtracking manner, i.e. starting from the variant node and searching the path of its parent node level by level upwards until a preset registration path in the registry is matched. In this way, even if a specific leaf node is not directly registered with a corresponding adapter, the corresponding adapter can still be matched through the path of its upper module, thereby enhancing the fault tolerance and adaptability of the system, and reducing the calling frequency of the adapter.

[0196] S1043, determining the sub-content responsible by each target adapter from the configuration content.

[0197] Further, after the screening of the target adapters is completed, the proxy server extracts the sub-content responsible by each target adapter from the overall configuration content. Since different adapters correspond to different registration paths, the configuration data range they are responsible for is also different, and the proxy server divides the configuration content into several subsets according to this, each subset corresponding to the input parameter of a target adapter. Correspondingly, for each target adapter, the way to determine the sub-content responsible by the target adapter is:

[0198] (1) determining the target registration path corresponding to the target adapter from the registry;

[0199] (2) determining each variant node under the node of the target registration path from the target configuration library, to obtain all variant nodes under the target registration path;

[0200] (3) obtaining the part corresponding to all variant nodes under the target registration path from the configuration content, to obtain the sub-content responsible by the target adapter.

[0201] Thus, the complete configuration is precisely assigned to each target adapter in combination with the registration path and the hierarchical structure of the tree structure, so that each target adapter only processes the sub-content corresponding to its functional domain, thereby avoiding redundant conversion and invalid processing, and improving the efficiency and accuracy of configuration management.

[0202] S1044, respectively calling each target adapter to convert each sub-content into a preset protocol format and send to the target device, so that the target device performs configuration modification based on each sub-content in the preset format.

[0203] In this embodiment, the proxy server respectively calls each target adapter to convert the respective sub-content into a preset protocol format recognizable by the target device, and sends the converted sub-content to the target device. Thus, the target device can perform configuration modification on the corresponding module or submodule based on the received sub-content in different protocol formats, thereby realizing an efficient and modular configuration update mechanism.

[0204] In an optional implementation, after completing the configuration modification, the target device returns a configuration response to the proxy server, and the proxy server needs to convert the configuration response into a NETCONF format and return it to the NETCONF client, thereby realizing a complete closed loop of the entire configuration management process. That is, the method further includes:

[0205] S105, after each adapter receives the configuration response in the preset protocol format returned by the target device, returns a configuration response in the NETCONF format to the NETCONF client.

[0206] In this embodiment, the configuration response represents configuration success or configuration failure.

[0207] For example, in combination with Figure 2 , assuming that the target device is device 1 and three target adapters are found, then the three sub-contents are respectively converted into SNMP protocol format by the three target adapters and sent to device 1, so that device 1 can directly recognize the three sub-contents in SNMP protocol format and then perform configuration modification. Device 1 returns an SNMP protocol format configuration response (indicating configuration success) to the video module of the proxy server. Then, the configuration response in SNMP protocol format is converted into a NETCONF format by the adaptation module, and then the NETCONF Agent module of the proxy server returns the configuration response in the NETCONF format to the NETCONF client. This example is only for illustration and is not limited herein.

[0208] Based on the same inventive concept as the above configuration management method, the embodiments of the present application also provide a satellite communication management system, which comprises a proxy server, a NETCONF client and a plurality of devices; the proxy server is in communication connection with the NETCONF client and the plurality of devices, and the proxy server maintains a model instance library of each device; wherein:

[0209] The NETCONF client is configured to send a configuration request to the proxy server;

[0210] The proxy server is configured to parse the configuration request based on the NETCONF protocol, determine a target device and a device type thereof, a target configuration library and configuration content; the target configuration library is any one of a candidate configuration library, a running configuration library and a startup configuration library included in the model instance library;

[0211] The proxy server is further configured to update the target configuration library in the model instance library of the target device based on the configuration content;

[0212] The proxy server is further configured to convert the configuration content into a preset protocol format recognizable by the target device and then send the configuration content to the target device;

[0213] The target device is configured to perform configuration modification based on the configuration content in the preset format.

[0214] In the satellite communication management system, the working cooperation principles of each part in a configuration process are described above and will not be repeated here.

[0215] In order to perform the corresponding steps in the above method embodiments and various possible implementation manners, the embodiments of the present application also provide a configuration management device, which is applied to a proxy server in communication with a NETCONF client and a plurality of devices; the proxy server maintains a model instance library of each device.

[0216] In combination Figure 6 The configuration management device comprises a NETCONF Agent module and an adaptation module, wherein the NETCONF Agent module is responsible for updating the model instance library of a target device based on a configuration request initiated by the NETCONF client; specifically, the NETCONF Agent module comprises a receiving module, a parsing module and an updating module.

[0217] The receiving module is configured to receive a configuration request sent by the NETCONF client;

[0218] The parsing module is configured to parse the configuration request based on the NETCONF protocol, determine a target device and a device type thereof, a target configuration library and configuration content; the target configuration library is any one of a candidate configuration library, a running configuration library and a startup configuration library included in the model instance library;

[0219] an updating module configured to update a target configuration library in a model instance library of the target device based on the configuration content;

[0220] an adapting module configured to convert the configuration content into a preset protocol format recognizable by the target device and send the configuration content in the preset protocol format to the target device, so that the target device performs configuration modification based on the configuration content in the preset format.

[0221] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the configuration management apparatus described above can refer to the corresponding process in the foregoing method embodiments, which will not be described herein.

[0222] Please refer to Figure 6 , Figure 6 A structural schematic diagram of an electronic device is provided in an embodiment of the present application. The electronic device 300 includes a processor 310, a memory 320 and a bus 330, and the processor 310 is connected with the memory 320 through the bus 330.

[0223] The memory 320 can be used to store software programs or firmware, for example, the software programs or firmware corresponding to the configuration management apparatus described above. The processor 310 performs various functional applications and data processing to realize the configuration management method provided in the embodiment of the present application by running the software programs stored in the memory 320.

[0224] The memory 320 can be, but is not limited to, a RAM (Random Access Memory), a ROM (Read Only Memory), a FLASH (FLASH memory), a PROM (Programmable Read-Only Memory), an EPROM (Erasable Programmable Read-Only Memory), an EEPROM (Electric Erasable Programmable Read-Only Memory) and the like.

[0225] The processor 310 can be an integrated circuit chip with a signal processing capability and can be used to execute software programs, for example, software programs corresponding to the configuration management apparatus 200 described above. The processor 310 can be a general-purpose processor, including a CPU (Central Processing Unit), a NP (Network Processor), a SoC (System on Chip), etc., and can also be a DSP (Digital Signal Processing), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0226] It can be understood that, Figure 6 The structure shown is only schematic, and the electronic device 300 can further include more or fewer components than those shown in the figures, or have a different configuration from that shown in the figures. Figure 6 The components shown in the figures can be implemented in hardware, software or a combination thereof. Figure 6 The components shown in the figures can be implemented in hardware, software or a combination thereof. ​ The components shown in the figures can be implemented in hardware, software or a combination thereof.

[0227] The embodiment of the present application further provides a computer readable storage medium, and the computer readable storage medium stores a computer program. When the computer program is run by a processor, the configuration management method disclosed in the above embodiment is implemented. The computer readable storage medium can be, but is not limited to, a U disk, a mobile hard disk, a ROM, a RAM, a PROM, an EPROM, an EEPROM, a FLASH disk or an optical disk and various storage medium capable of storing program codes.

[0228] The embodiment of the present application further provides a program product, and the program product is executed by a processor to implement the configuration management method disclosed in the above embodiment.

[0229] In summary, the embodiment of the present application provides a configuration management method, device, system, equipment, storage medium and program product. In a satellite communication management system, a proxy server communicates with a NETCONF client and a plurality of devices. The proxy server maintains a model instance library of each device. The process of realizing unified configuration through the proxy server is as follows: based on the NETCONF protocol, a configuration request sent by the NETCONF client is parsed to determine a target device and its device type, a target configuration library and configuration content. The target configuration library is any one of a candidate configuration library, a running configuration library and a startup configuration library included in the model instance library. Then, based on the configuration content, the target configuration library in the model instance library of the target device is updated. Finally, the configuration content is converted into a preset protocol format recognizable by the target device and is sent to the target device, so that the target device performs configuration modification based on the configuration content in the preset format. The proxy server is arranged between the NETCONF client and the plurality of devices, and is used to maintain the model instance library of each device. When one of the target devices needs to be configured, the proxy server modifies the target configuration library first, and then converts the configuration content into a preset protocol format recognizable by the target device and issues the configuration to the target device. In this way, the NETCONF Agent program does not need to be installed in each device, and unified configuration management of the plurality of devices is realized through the proxy server.

[0230] The above merely describes specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed by the present application, which should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A configuration management method, characterized in that: A proxy server used in a satellite communication management system, the satellite communication management system also including a NETCONF client, the proxy server communicating with the NETCONF client and multiple devices, the devices being baseband devices of a ground master station or terminal devices with satellite communication capabilities; The proxy server maintains a model instance library for each device, and further maintains a registry, wherein the registry reflects multiple adapters and multiple registration paths associated with each device type in the satellite communication system, and one adapter uniquely corresponds to one registration path; in the field of satellite communications, devices of the same device type support the same configuration management protocol, the proxy server runs multiple groups of adapters, and at least one adapter in each group of adapters is responsible for configuration content conversion processing for one device type; the method comprises: Receive a configuration request sent by the NETCONF client; The configuration request is parsed based on the NETCONF protocol to determine the target device and its device type, the target configuration library, and the configuration content; the target configuration library is any one of the candidate configuration library, the running configuration library, and the startup configuration library included in the model instance library; the storage structure of the target configuration library is a tree structure consisting of a root node, multiple branch nodes, and multiple leaf nodes, wherein the root node represents the target device, the branch node represents a module or a submodule of the target device, and the leaf node represents a configurable item in a module or a submodule; Based on the configuration content, updating the target configuration library in the model instance library of the target device; Obtaining a node path of each changed node in the target configuration repository; Based on the device type of the target device and the node path of each changed node, searching for at least one matching target adapter from the registration table by tracing back the path from each changed node upward to its parent node; the registration path of the target adapter is consistent with the node path of at least one changed node or its upper-level node; Determining from the configuration content the sub-content for which each target adapter is responsible; Each target adapter is called to convert each sub-content into a preset protocol format recognizable by the target device and then sent to the target device, so that the target device performs configuration modification based on each sub-content in the preset format.

2. The configuration management method according to claim 1, wherein: The registry includes a plurality of registry entries, each of which represents an association between a device type, an adapter, and a registration path; The step of searching for at least one matching target adapter from the registry table based on the device type of the target device and the node path of each changed node by tracing back the path from each changed node to the parent node step by step includes: For each changed node, the changed node is used as the current node; Based on the node path of the current node and the device type of the target device, searching the registry for a matching target registry entry; If it exists, the adapter in the target registry entry is used as the target adapter; If it does not exist, the parent node of the current node is used as the new current node; After obtaining the node path of the current node from the target configuration library, return to the step of searching the registry for a matching target registry entry based on the node path of the current node and the device type of the target device, until the target registry entry is found in the registry.

3. The configuration management method according to claim 2, characterized in that: The step of determining the sub-content for which each target adapter is responsible from the configuration content comprises: For each target adapter, determining a target registration path corresponding to the target adapter from the registration table; Determine each change node below the node where the target registration path is located from the target configuration library to obtain all change nodes under the target registration path; The parts corresponding to all the changed nodes under the target registration path are obtained from the configuration content to obtain the sub-content that the target adapter is responsible for.

4. The configuration management method according to claim 1, wherein: The method further comprises: After each of the adapters receives the configuration response in the preset protocol format returned by the target device, it returns a configuration response in the NETCONF format to the NETCONF client; the configuration response represents a configuration success or a configuration failure.

5. A configuration management device, characterized in that: A proxy server used in a satellite communication management system, the satellite communication management system also including a NETCONF client, the proxy server communicating with the NETCONF client and multiple devices, the devices being baseband devices of a ground master station or terminal devices with satellite communication capabilities; The proxy server maintains a model instance library for each device, and further maintains a registry, wherein the registry reflects multiple adapters and multiple registration paths associated with each device type in the satellite communication system, and one adapter uniquely corresponds to one registration path. In the field of satellite communications, devices of the same device type support the same configuration management protocol, and the proxy server runs multiple groups of adapters, with at least one adapter in each group responsible for configuration content conversion processing for one device type. The device comprises: A receiving module, configured to receive a configuration request sent by the NETCONF client; A parsing module is configured to parse the configuration request based on the NETCONF protocol to determine a target device and its device type, a target configuration library, and configuration content; the target configuration library is any one of the candidate configuration library, the running configuration library, and the startup configuration library included in the model instance library; the storage structure of the target configuration library is a tree structure consisting of a root node, multiple branch nodes, and multiple leaf nodes, wherein the root node represents the target device, the branch node represents a module or a submodule of the target device, and the leaf node represents a configurable item in a module or a submodule; An updating module, configured to update a target configuration library in a model instance library of the target device based on the configuration content; Adapter modules for: Obtaining a node path of each changed node in the target configuration repository; Based on the device type of the target device and the node path of each changed node, searching for at least one matching target adapter from the registration table by tracing back the path from each changed node upward to its parent node; the registration path of the target adapter is consistent with the node path of at least one changed node or its upper-level node; Determining from the configuration content the sub-content for which each target adapter is responsible; Each target adapter is called to convert each sub-content into a preset protocol format and then sent to the target device, so that the target device performs configuration modification based on each sub-content in the preset format.

6. A satellite communication management system, characterized in that: The satellite communication management system includes a proxy server, a NETCONF client, and multiple devices, wherein the devices are baseband devices of a ground master station or terminal devices with satellite communication functions; the proxy server is communicatively connected to the NETCONF client and multiple devices, and the proxy server maintains a model instance library for each device. The proxy server also maintains a registry, which reflects multiple adapters and multiple registration paths associated with each device type in the satellite communication system, and one adapter uniquely corresponds to one registration path; in the field of satellite communications, devices of the same device type support the same configuration management protocol, and the proxy server runs multiple groups of adapters, and at least one adapter in each group of adapters is responsible for configuration content conversion processing for one device type; wherein: The NETCONF client is used to send a configuration request to the proxy server; The proxy server is used to parse the configuration request based on the NETCONF protocol to determine the target device and its device type, the target configuration library and the configuration content; the target configuration library is any one of the candidate configuration library, the running configuration library and the startup configuration library included in the model instance library; The proxy server is further configured to update a target configuration library in a model instance library of the target device based on the configuration content; The proxy server is further configured to: obtain a node path of each changed node in the target configuration repository; based on the device type of the target device and the node path of each changed node, search the registry for at least one matching target adapter using a path backtracking method starting from each changed node and searching for a parent node step by step; the registration path of the target adapter is consistent with the node path of at least one changed node or its upper-level node; determine the sub-content that each target adapter is responsible for from the configuration content; and call each target adapter to convert each sub-content into a preset protocol format recognizable by the target device and then send the converted sub-content to the target device; The target device is used to perform configuration modification based on the sub-contents of each preset format.

7. An electronic device, characterized in that: include: A memory and a processor, wherein the memory stores a software program, and when the electronic device is running, the processor executes the software program to implement the configuration management method according to any one of claims 1 to 4.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the configuration management method according to any one of claims 1 to 4 is implemented.

9. A program product, characterized in that When the program product is executed by a processor, the configuration management method according to any one of claims 1 to 4 is implemented.

Images