Method and apparatus for updating site configuration data, and electronic device

Abstract

The present disclosure provides a method for updating site configuration data, which comprises: parsing site data based on a management object (MO) model file of a network management system to obtain site data information; parsing a physical device model of the site based on a physical device model file of the network management system to obtain physical device information of the site; determining MO instances of replaceable physical devices under a target physical device based on the target physical device selected by a user and the physical device information of the site; generating configuration data of the site based on the MO instances of the target physical device, the MO instances of the replaceable physical devices under the target physical device, and MO instances related to services of the physical devices; and updating the site by using the configuration data of the site. The method can update physical device data and service data, and has high configuration efficiency and is less prone to errors. The present disclosure also provides an apparatus for updating site configuration data and an electronic device.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a method, apparatus, and electronic device for updating site configuration data. Background Technology

[0002] To improve the performance of Long Term Evolution (LTE) wireless network systems, communication equipment providers and service providers are constantly launching base stations and related equipment with superior performance. Therefore, site upgrades are necessary, replacing existing equipment with new equipment and adjusting site resource allocation. Especially as 5G equipment gradually replaces existing LTE equipment, the workload of site upgrades is increasing significantly. Furthermore, the upgrade process not only requires updating the configuration data of the physical equipment but also inheriting optimized transmission and wireless service data.

[0003] Currently, site upgrades and modifications are performed on the network management side following the process of reactivating existing sites. For example, on the network management side, based on the new site type or equipment, the entire site's configuration data is created in a reactivation manner, and then network parameters are optimized. Since it takes time for network parameters to reach optimal performance, this results in a poor user experience. Alternatively, new physical configuration data is manually created on the network management side, and transmission and wireless service data are configured based on the existing configuration data. Due to the large volume of site data and the interrelationships among managed objects, this manual data configuration is inefficient and prone to errors.

[0004] Public content

[0005] This disclosure provides a method, apparatus, and electronic device for updating site configuration data, in order to solve the problems of long generation time, high error rate, low operation and maintenance efficiency, and high cost during site upgrades and renovations.

[0006] In a first aspect, embodiments of this disclosure provide a method for updating site configuration data, comprising:

[0007] The system parses site data based on the management object (MO) model file of the network management system to obtain site data information; wherein, the site data information includes all MOs and the parent-child relationships and reference relationships between the MOs;

[0008] The physical device model of a site is parsed based on the physical device model file of the network management system to obtain the physical device information of the site; wherein, the physical device information of the site includes all physical devices in the site, the hierarchy of the physical devices, and the MO instances of the physical devices at each layer;

[0009] Based on the target physical device selected by the user, the site data information, and the physical device information of the site, determine the MO instance of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the services of the physical device;

[0010] The configuration data of the site is generated based on the MO instance of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the services of the physical device.

[0011] Update the site using the site's configuration data.

[0012] Secondly, embodiments of this disclosure provide a site configuration data updating apparatus, comprising:

[0013] The first parsing module is used to parse site data based on the management object (MO) model file of the network management system to obtain site data information; wherein, the site data information includes all MOs and the parent-child relationships and reference relationships between the MOs;

[0014] The second parsing module is used to parse the physical device model of a site based on the physical device model file of the network management system, and obtain the physical device information of the site; wherein, the physical device information of the site includes all physical devices in the site, the hierarchy of the physical devices, and MO instances of the physical devices at each layer;

[0015] The physical device determination module is used to determine the MO instance of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the services of the physical device based on the target physical device selected by the user, the site data information, and the physical device information of the site.

[0016] The configuration data generation module is used to generate configuration data for the site based on the MO instance of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the services of the physical device.

[0017] A configuration data update module is used to update the site using the site's configuration data.

[0018] Thirdly, embodiments of this disclosure provide an electronic device, which includes:

[0019] One or more processors;

[0020] A memory having stored one or more programs that, when executed by one or more processors, cause the one or more processors to perform any of the above-described methods for updating site configuration data.

[0021] One or more I / O interfaces are connected between the processor and the memory and configured to enable information interaction between the processor and the memory.

[0022] Fourthly, embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements any of the methods described above for updating site configuration data.

[0023] The method for updating site configuration data provided in this embodiment involves parsing site data from the management object (MO) model file of the network management system to obtain the parent-child relationships and reference relationships between MOs in the site; parsing the physical device model of the site based on the physical device model file of the network management system to obtain the physical device information of the site; determining the MO instances of replaceable physical devices under the target physical device based on the target physical device selected by the user and the physical device information of the site; generating the site configuration data based on the MO instances of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the services of the physical device; and updating the site using the site configuration data. This allows users to update the site configuration data on the network management side in conjunction with the target physical device they expect. Moreover, the updated configuration data includes both physical device data and service data, improving the versatility of updating site configuration data and thus enhancing the user experience. In addition, the method for updating site configuration data provided in this embodiment can replace physical devices of various types and levels, allowing users to flexibly select replaceable target physical devices. This achieves the effect of using a single system to cover the replacement of various types of physical devices, and it is highly efficient and less prone to errors. Attached Figure Description

[0024] The accompanying drawings are provided to further illustrate the embodiments of this disclosure and form part of the specification. They are used together with the embodiments of this disclosure to explain the disclosure and do not constitute a limitation thereof. The above and other features and advantages will become more apparent to those skilled in the art from the detailed description of exemplary embodiments with reference to the accompanying drawings, in which:

[0025] Figure 1 A flowchart illustrating a method for updating site configuration data provided in this disclosure embodiment;

[0026] Figure 2 This is an MO model relationship diagram obtained by parsing site data from an MO model file in this embodiment of the disclosure;

[0027] Figure 3 A flowchart illustrating a method for updating site configuration data provided in this disclosure embodiment;

[0028] Figure 4 A flowchart of a method for updating site configuration data provided in embodiments of this disclosure;

[0029] Figure 5 A schematic diagram of an apparatus for updating site configuration data according to an embodiment of this disclosure;

[0030] Figure 6 A schematic diagram of another apparatus for updating site configuration data provided in an embodiment of this disclosure;

[0031] Figure 7 This is a block diagram of an electronic device provided in an embodiment of the present disclosure. Detailed Implementation

[0032] To enable those skilled in the art to better understand the technical solutions of this disclosure, the methods, apparatus, electronic devices, and computer-readable media for updating site configuration data provided in this disclosure will be described in detail below with reference to the accompanying drawings.

[0033] Exemplary embodiments will be described more fully below with reference to the accompanying drawings; however, these exemplary embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will enable those skilled in the art to fully understand the scope of this disclosure.

[0034] Where there is no conflict, the various embodiments of this disclosure and the features thereof in the embodiments may be combined with each other.

[0035] As used herein, the term “and / or” includes any and all combinations of one or more related enumerated entries.

[0036] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. As used herein, the singular forms “a” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising” and / or “made of” are used in this specification, the presence of the stated feature, integral, step, operation, element, and / or component is specified, but the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof is not excluded.

[0037] Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this disclosure, and will not be interpreted as having an idealized or overly formal meaning, unless expressly so defined herein.

[0038] The 3rd Generation Partnership Project (3GPP) protocol is a standard for wireless communication technology. Its network management and configuration component describes sites through Managed Objects (MOs). The 3GPP protocol provides modeling standards, and manufacturers extend these standards to create their own models. For base stations, the instance of the model is the site's configuration data, which is fundamental to site operation.

[0039] In the 3GPP modeling standard, each network element node in a site contains device sub-nodes, transport sub-nodes, and radio sub-nodes, and each sub-node has a corresponding service sub-node. The device sub-node, transport sub-node, radio sub-node, and service sub-node describe an MO (Mobile Operation). The site's configuration data is composed of instances of these MOs.

[0040] The network management system manages various types of sites; therefore, it includes configuration data for different types of sites. Site configuration data includes MO (Model Object) files and physical device model files, which are recorded in the gateway system. The gateway system's MO model file contains each MO and its attributes, as well as the parent-child relationships between MOs. For physical devices referenced in transmission or wireless applications, the MO model file can also describe the referenced physical devices. For example, in modeling an MO, the attribute "Related Physical Device MO" might take the value of the Distinguished Name (DN) of the referenced physical device.

[0041] The physical device model file describes the site type, the hierarchical relationship of the physical devices supported by the site, and the MO instance corresponding to each layer of physical devices. In each site, the physical devices, from highest to lowest, are: base station, cabinet, rack, chassis, slot, board, and board service capabilities. Each layer of physical device nodes has a corresponding MO. Although the layers and MOs of physical devices are relatively fixed, the MO instances of physical devices at each layer are different for each site type.

[0042] When users modify a site, it is usually necessary to update the MO instances of the target physical devices, the MO instances that reference the target physical devices, and the MO instances related to the services of the physical devices within the site. In other words, the site's configuration information needs to be updated.

[0043] When updating site configuration information, updates can be performed on the network element side or the network management side. Compared to the network element side, updating site configuration information on the network management side can effectively utilize network management resources and improve the efficiency of generating configuration information. Therefore, this embodiment focuses on the generation of site configuration information on the network management side and then updating the site.

[0044] In a first aspect, embodiments of this disclosure provide a method for updating site configuration data. Figure 1 A flowchart illustrating a method for updating site configuration data provided in an embodiment of this disclosure. (Refer to...) Figure 1 Methods for updating site configuration data include:

[0045] Step 101: Parse site data based on the management object (MO) model file of the network management system to obtain site data information.

[0046] The site data information includes all MOs and the parent-child relationships and reference relationships between them.

[0047] The management object (MO) model file of the network management system adopts, but is not limited to, XML, Excel, and Yang formats. The management object (MO) model file is stored in the gateway system. Using the MO model file, one can obtain information about each MO and its attributes within the site, as well as the parent-child relationships and reference relationships between MOs. MO attributes include MO name, value type, value range, default value, and whether it contains keywords.

[0048] In this context, the parent-child relationship of an MO refers to the master-slave relationship between MOs. For example, when a device root node MO includes device child nodes MO, the device root node MO and the device child nodes MO have a parent-child relationship, with the device root node MO being the parent node MO and the device child nodes MO being the child nodes MO.

[0049] The reference relationship between MOs refers to the reference relationship between MOs. For example, when a transport child node MO references a device child node MO, a reference relationship exists between the transport child node MO and the device child node MO.

[0050] In some embodiments, site data is parsed from the MO model file of the network management system, the site is divided into blocks, and the MO of each block and the parent-child relationship between MOs are obtained.

[0051] Figure 2 This is an MO model relationship diagram obtained by parsing site data from an MO model file in this embodiment of the disclosure. For example... Figure 2As shown, network element MO 2 in the site is divided into three parts: device root node MO 21, transmission root node MO 22, and wireless root node MO 23. Below device root node MO 21 are multiple device sub-nodes MO 211, 212, and 213. Each device sub-node MO 211 can also have one or more sub-nodes MO 2111, 2112, 2113, and 2114. Below transmission root node MO 22 are multiple transmission sub-nodes MO 221, 222, and 223. Each transmission sub-node MO 221, 222, and 223 can also have sub-nodes MO 2211 and 2212. Below wireless root node MO 23 are multiple wireless sub-nodes MO 231 and 232. Each transmission sub-node MO 221, 222, and 223 can also have sub-nodes MO 2311, 2312, and 2313.

[0052] Among them, device root node MO 21 has a parent-child relationship with device child nodes MO 211, 212, and 213; transmission root node MO22 has a parent-child relationship with transmission child nodes MO 221, 222, and 223; and wireless root node MO 23 has a parent-child relationship with wireless child nodes MO 231, 232, and 233.

[0053] When parsing site data based on the management object (MO) model file of the network management system to obtain the parent-child relationship between MOs in the site, the parent-child relationship between MOs in the site can be stored in a tree structure and displayed to the user.

[0054] In some embodiments, site data is parsed from the MO model file of the network management system to obtain reference relationship description keywords, and the MO instance of the physical device referenced by the MO is obtained based on the reference relationship description keywords.

[0055] The reference relationship description keyword is used to describe the reference relationship of an MO. Based on this reference relationship description keyword, the MO of the physical device referenced by the MO can be obtained, and thus the MO instance of the referenced physical device can be obtained. For example: Figure 2 As shown by the dashed line, based on the keyword describing the reference relationship, it can be seen that there is a reference relationship between the transmission sub-node MO 221 and the physical device sub-node MO 212, and that the transmission sub-node MO 221 references the physical device sub-node MO 212, and the physical device sub-node MO 212 references the physical device sub-node MO 211.

[0056] Step 102: Based on the physical device model file of the network management system, parse the physical device model of the site to obtain the physical device information of the site.

[0057] The site's physical device information includes all physical devices in the site, the hierarchy of physical devices, and the MO instances of physical devices at each layer.

[0058] The physical device model file of the network management system adopts, but is not limited to, XML, Excel, and Yang formats. The physical device model file of the network management system describes the site type, the hierarchical relationship of the physical devices at each layer supported by the site, and the MO instance corresponding to each layer of physical devices.

[0059] In some embodiments, the organizational hierarchy of physical devices in a site, from highest to lowest, is: base station, cabinet, rack, chassis, slot, board, and board service capabilities. Each level of physical device node has a corresponding MO (Mean Object), such as base station MO, cabinet MO, rack MO, chassis MO, slot MO, board MO, and board service capabilities MO. After parsing the site's physical device model based on the physical device model file of the network management system and obtaining the site's physical device information, the site's physical device information can be stored in a tree structure and displayed to the user.

[0060] It should be noted that although the physical device layer and MO are relatively fixed, the physical device MO instances at each layer under each type of station are not necessarily the same.

[0061] In some embodiments, the physical device model of a site can be parsed based on the physical device model file of the network management system to obtain the physical device information of the site, including the hierarchy of physical devices in the site and the MO instances of physical devices at each layer, that is, all physical devices under the site, the hierarchical relationship of physical devices, and the MO instances corresponding to each layer of physical devices.

[0062] In some embodiments, the MO model file and physical device model file of the network management system can be built into the gateway system, and site data and the site's physical device model can be used as input signals.

[0063] Step 103: Based on the target physical device selected by the user, site data information, and site physical device information, determine the MO instance of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the services of the physical device.

[0064] In this embodiment, the parent-child relationships and reference relationships between MOs in the site, as well as the physical device information of the site, are displayed in a tree structure. Users can select the target physical device in the network management system interface according to the site's modification status.

[0065] In some embodiments, based on the target physical device selected by the user and the physical device information of the site, the service types supported by each layer of physical devices under the target physical device are determined layer by layer; the type of physical device at the corresponding layer is determined based on the service types supported by each layer of physical devices; and the MO instance of the replaceable physical device under the target physical device is determined based on the type of the physical device at each layer.

[0066] For example, the network management system calculates the replaceable physical device types for each node. Specifically, based on the type of the current (current layer) physical device, it calculates the types of physical devices that can support the same service type. The type of the current physical device and the service type can be found in the MO model file or the physical device model file. More specifically, after a user selects the site type, the selectable replacement rack type is the rack type that supports the same service function under that site. In other words, once the site type is determined, the rack type under that site can be determined; after selecting the rack type, the user can select the replacement rack type that supports the same service function under that rack; and so on, down to the lowest level of single-board services. Therefore, after determining the physical devices at a certain level, the types of physical devices at each level under that level can be determined based on the type of the physical devices at that level, thus determining the corresponding MO instance.

[0067] In this embodiment, the target physical device can be arbitrarily selected according to the site's modification status. That is, a certain physical device in the site can be selected as the target physical device, and only the target physical device, the physical devices under the target physical device, and the related service data are updated. There is no need to update the configuration data of other physical devices outside the target physical device, which improves the flexibility of the site's configuration data and thus improves the efficiency of the update.

[0068] Step 104: Generate site configuration data based on the MO instance of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the services of the physical devices.

[0069] In some embodiments, MO instances of the target physical device are created or replaced based on the site's configuration data, MO instances of physical devices referencing the target physical device are replaced, and MO instances related to the services of the physical device are updated.

[0070] In some embodiments, the service MO instance under the physical device is updated; the MO referencing the physical device is obtained, and the attribute values ​​of the MO referencing the physical device are updated.

[0071] In this embodiment, the MO instance of the target physical device, the MO instance of the replaceable physical device under the target physical device, and the MO instance related to the services of the physical device generate the configuration data of the site.

[0072] Step 105: Update the site using the site's configuration data.

[0073] In step 105, the corresponding physical device MO instances are replaced using the site's configuration data; the MOs that reference these physical devices are located, and their "related attribute" values ​​are updated to the identifier of the new physical device MO instance; the changed physical device MO instances are passed to the extended interface, and the interface is called to complete the update of the corresponding business MO instances.

[0074] Figure 3 A flowchart illustrating a method for updating site configuration data provided in an embodiment of this disclosure. (Refer to...) Figure 3 Methods for updating site configuration data include:

[0075] Step 301: Parse site data based on the management object MO model file of the network management system to obtain site data information.

[0076] The site data information includes all MOs and the parent-child relationships and reference relationships between them.

[0077] Step 302: Based on the physical device model file of the network management system, parse the physical device model of the site to obtain the physical device information of the site.

[0078] The site's physical device information includes all physical devices in the site, the hierarchy of physical devices, and the MO instances of physical devices at each layer.

[0079] Step 303: Based on the target physical device selected by the user, site data information, and site physical device information, determine the MO instance of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the services of the physical device.

[0080] In this embodiment, steps 301 to 303 are the same as steps 101 to 103 in the above embodiment, and will not be described again here.

[0081] Step 304: Verify the legitimacy of the replaceable physical devices under the target physical device.

[0082] In some embodiments, the type, service type, and number of instances of each layer of physical devices under the target physical device are verified in sequence to determine the legitimacy of the target physical device.

[0083] Specifically, the network management system obtains the target physical device (MO) instances for each layer according to the user's selection. Legality verification begins with the site type. The verification process includes: verifying whether each rack in the site is a buildable rack type; verifying whether the rack's service type (e.g., primary, secondary, or auxiliary rack) is the same as the rack's service type before replacement; and verifying whether the number of rack instances supported by the site is greater than or equal to the number of rack instances configured for the site. For example, assuming the site has two secondary racks, if the updated site type supports two or more secondary racks, the verification passes. After the rack verification passes, the next layer of physical equipment is verified, i.e., rack verification. The rack verification content is the same as the rack verification, also based on rack type, rack service type, and the number of racks supported by the rack; until the last layer of the site is reached, i.e., single-board service MO instances. When verifying single-board service MO instances, the type of the single board is determined, whether the single-board MO instance is a service MO supported by the single board, and whether the number of single-board service MO instances is greater than or equal to the number of service MO instances for the corresponding single board in the site.

[0084] It should be noted that if the physical devices at a certain level under the target physical device are not replaced, the original physical devices will continue to be used.

[0085] If a replaceable physical device under the target physical device passes verification, proceed to step 305. If a replaceable physical device under the target physical device fails verification, the network management system can guide the user to replace the target physical device. For example, the network management system can recommend a suitable target physical device to the user. The network management system can also access data on the user's site modifications.

[0086] Step 305: Generate site configuration data based on the MO instance of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the services of the physical devices.

[0087] In this embodiment, step 305 is the same as step 104 in the above embodiment, and will not be described again here.

[0088] Step 306: Update the site using the site's configuration data.

[0089] In step 306, the MO instances of physical devices can be updated layer by layer. For example, first, the rack MO instances and service MO instances are updated, and then the physical device MO instances and service MO instances at different levels are updated layer by layer downwards. For a single board's service MO, it is a description of the board's capabilities; that is, for a given board, the number of services it supports and the number of MO instances are fixed. Therefore, after replacing a board, the service MO instances under that board will replace the service MO instances of the board at the site. Next, the MOs that reference these physical devices are found, and their "related physical device MO" attribute value is updated to the identifier name value of the new physical device MO instance. Finally, the changed physical device service MO instances are imported into the extension interface, and when this extension interface is called, the update of the corresponding physical device service MO instances is completed.

[0090] It should be noted that when the number of replaced physical device service MO instances is greater than the number of corresponding physical device service MO instances at the site, a single service MO instance can be created. For example, when the number of replaced single-board service MO instances is greater than the number of single-board service MO instances at the site, a single-board service MO instance can be created.

[0091] To better understand the method for updating site configuration data provided in the embodiments of this disclosure, the method for updating site configuration data is described in more detail below.

[0092] Figure 4 A flowchart illustrating a method for updating site configuration data provided in embodiments of this disclosure. Figure 4 As shown, the methods for updating site configuration data include:

[0093] Step 401: Parse site data based on the management object MO model file of the network management system to obtain site data information.

[0094] The site data information includes all MOs and the parent-child relationships and reference relationships between them.

[0095] In this embodiment, the MO model file of the network management system is an Excel file. In the MO model file of the network management system, the rows are MOs and their attribute names, and the columns are descriptions of MOs and their attributes, specifically including information such as the parent MO name, value type, value range, default value, and whether there are keywords.

[0096] After the network management system starts, it first loads the MO model file, then parses the site data input by the user, divides the site data into blocks according to device, transmission, and radio, and stores the MO instances of each block in a tree structure. Simultaneously, it searches for the referenced physical device MO instances based on the reference relationship description keywords to obtain the referenced physical device MO instances. The referenced physical device MO instances can be stored in physical, transmission, or radio MO instances.

[0097] Step 402: Based on the physical device model file of the network management system, parse the physical device model of the site to obtain the physical device information of the site.

[0098] The physical equipment model file is described using an Excel format file. The physical equipment model file describes the station type, the hierarchical relationship of physical equipment at each level, and the MO instance corresponding to each level of physical equipment.

[0099] In this embodiment, base stations, cabinets, racks, chassis, slots, and single boards can be described using independent pages. On each page, the rows are physical device (MO) instances, the columns are the MO attributes of the physical devices and their sub-device types, and the last column lists the sub-device types supported by the physical device. For example, on the single board page, the columns contain the single board's MO attributes and its service capability attributes, and the rows are the single board's MO instances and their supported service capability MO instances.

[0100] After the network management system starts, it loads and parses the physical device model file of the site to obtain all the physical device (MO) instances actually configured under the site, as well as the hierarchy of physical devices and the MO instances of physical devices at each layer.

[0101] After completing steps 401 and 402, the network management system can present the user with all MOs in the parsed site, the parent-child relationships and reference relationships between MOs, all physical device MO instances, as well as the hierarchy of physical devices and the MO instances of physical devices at each level, allowing the user to select replaceable physical device MO instances.

[0102] Step 403: Based on the target physical device selected by the user, site data information, and site physical device information, determine the MO instance of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the services of the physical device.

[0103] The network management system presents the physical devices configured at the site to the user in a tree structure, showing the physical devices at each level of the site and their corresponding MO instances. For example, in the user interface, different levels of nodes in the tree structure represent different levels of physical devices. When the user clicks on a tree node, the MO instances of the physical devices corresponding to each tree node are displayed in a table format. Based on the MO instances of physical devices supported by each level of physical devices, the user can find out the types of physical devices that can be replaced.

[0104] In step 403, after the user selects the target physical device, the tree node corresponding to the target physical device can be used to find out the types of physical devices that can be replaced, as well as the instances of physical devices (MO) that can be replaced under the target physical device.

[0105] In step 403, the network management system can also obtain the MO instance that references the physical device based on the relevant attributes of the physical device.

[0106] Step 404: Verify the legitimacy of the replaceable physical devices under the target physical device.

[0107] Based on the target physical device selected by the user, the network management system integrates the physical device hierarchy of the replaced site, obtains the physical device type and MO instance of each layer, and performs legality verification: the verification starts from the device root node (site type), and verifies whether the type of its first-level child node is the type of the child device that can be created; secondly, it verifies whether the service type of the child device is the same as the original device before replacement; thirdly, it verifies whether the number of instances of the child device is greater than or equal to the number of instances of the corresponding layer of the source site; if the verification passes, the next level of verification is performed, traversing to the last level of single-board service capability MO.

[0108] For example, the system verifies whether each rack in the site is a createable rack type, whether the service type of the rack (e.g., main rack, secondary rack, or auxiliary rack) is the same as the service type of the rack before replacement, and whether the number of rack instances supported by the site is greater than or equal to the number of rack instances configured for the site. For example, assuming the site has two secondary racks, if the updated site type supports more than or equal to two secondary racks, the verification passes. After the rack verification passes, the system continues to verify the next layer of physical equipment, i.e., rack verification. The rack verification content is the same as that of the rack, also according to rack type, rack service type, and the number of racks supported by the rack; until the last level of the site is reached, i.e., single-board service MO instances.

[0109] For physical devices that fail verification, the network management system can provide clear prompts, guiding users to replace the target device or modify the data at the original site.

[0110] Step 405: Generate site configuration data based on the MO instance of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the services of the physical devices.

[0111] Step 406: Update the site using the site's configuration data.

[0112] The system updates the original configuration data of the site using the configuration data, updates the physical device MO instance, finds the MO of the physical device, updates the relevant attribute value to the DN of the new physical device MO instance, and passes the updated physical device MO instance to the extension interface. When the extension interface is called, the corresponding business MO instance is updated, thereby completing the update of the site configuration data.

[0113] It is easy to understand that although this embodiment uses an Ecxel format MO model file as an example to introduce the generation and updating of site configuration data, the present invention is not limited to this. Other formats of MO model files can also update site configuration data according to the method provided in this embodiment, and can achieve the same technical effect.

[0114] The method for updating site configuration data provided in this embodiment involves parsing site data from the management object (MO) model file of the network management system to obtain the parent-child relationships and reference relationships between MOs in the site; parsing the physical device model of the site based on the physical device model file of the network management system to obtain the physical device information of the site; determining the MO instances of replaceable physical devices under the target physical device based on the target physical device selected by the user and the physical device information of the site; generating the site configuration data based on the MO instances of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the services of the physical device; and updating the site using the site configuration data. This allows users to update the site configuration data on the network management side in conjunction with the target physical device they expect. Moreover, the updated configuration data includes both physical device data and service data, improving the versatility of updating site configuration data and thus enhancing the user experience. In addition, the method for updating site configuration data provided in this embodiment can replace physical devices of various types and levels, allowing users to flexibly select replaceable target physical devices. This achieves the effect of using a single system to cover the replacement of various types of physical devices, and it is highly efficient and less prone to errors.

[0115] Secondly, embodiments of this disclosure provide an apparatus for updating site configuration data. Figure 5 A schematic diagram of an apparatus for updating site configuration data according to an embodiment of this disclosure. (Refer to...) Figure 5 The site configuration data updating device provided in this embodiment includes:

[0116] The first parsing module 501 is used to parse site data based on the management object MO model file of the network management system to obtain site data information.

[0117] The site data information includes all MOs and the parent-child relationships and reference relationships between them. The specific implementation of the first parsing module 501 is the same as step 101 in the above embodiments, and will not be repeated here.

[0118] The second parsing module 502 is used to parse the physical device model of the site based on the physical device model file of the network management system to obtain the physical device information of the site.

[0119] The site's physical device information includes all physical devices in the site, the hierarchy of physical devices, and the MO instances of physical devices at each layer.

[0120] The specific implementation of the second parsing module 502 is the same as step 102 in the above embodiment, and will not be repeated here.

[0121] The physical device determination module 503 is used to determine, based on the target physical device selected by the user, the site data information, and the physical device information of the site, the MO instance of the target physical device, the MO instance of the replaceable physical device under the target physical device, and the MO instance related to the service of the physical device.

[0122] The specific implementation of the physical device determination module 503 is the same as step 103 in the above embodiments, and will not be repeated here.

[0123] The configuration data generation module 504 is used to generate site configuration data based on the MO instance of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the services of the physical device.

[0124] The specific implementation of the configuration data generation module 504 is the same as step 103 in the above embodiment, and will not be repeated here.

[0125] The configuration data update module 505 is used to update the site using the site's configuration data.

[0126] Figure 6 A schematic diagram of another apparatus for updating site configuration data provided in an embodiment of this disclosure. (Refer to...) Figure 6 The apparatus for updating site configuration data provided in this embodiment includes:

[0127] The first parsing module 601 is used to parse site data based on the management object (MO) model file of the network management system to obtain site data information. The site data information includes all MOs and the parent-child relationships and reference relationships between them.

[0128] The second parsing module 602 is used to parse the physical device model of the site based on the physical device model file of the network management system to obtain the physical device information of the site.

[0129] The physical device determination module 603 is used to determine the MO instance of the target physical device, the MO instance of the replaceable physical device under the target physical device, and the MO instance related to the service of the physical device based on the target physical device selected by the user, the site data information, and the physical device information of the site.

[0130] Verification module 604 is used to verify the legitimacy of replaceable physical devices under the target physical device.

[0131] In some embodiments, the type, service type, and number of instances of each layer of physical devices under the target physical device are verified in sequence to determine the legitimacy of the target physical device.

[0132] The configuration data generation module 605 is used to generate site configuration data based on the MO instance of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the services of the physical device.

[0133] Configuration data update module 606 is used to update the site using the site's configuration data.

[0134] The device for updating site configuration data provided in this embodiment allows users to update site configuration data on the network management side, based on their desired target physical devices. The updated configuration data includes both physical device data and service data, improving the versatility of site configuration data updates and thus enhancing user experience. Furthermore, the device can replace various types and levels of physical devices, allowing users to flexibly select replaceable target physical devices. This achieves the effect of using a single system to cover the replacement of various types of physical devices, while also offering high configuration efficiency and reducing the likelihood of errors.

[0135] Thirdly, referring to Figure 7 This disclosure provides an electronic device, which includes:

[0136] One or more processors 701;

[0137] Memory 702, having stored one or more programs, which, when executed by one or more processors, cause the one or more processors to implement any of the above-mentioned methods for updating site configuration data;

[0138] One or more I / O interfaces 703 are connected between the processor and the memory and configured to enable information exchange between the processor and the memory.

[0139] The processor 701 is a device with data processing capabilities, including but not limited to a central processing unit (CPU); the memory 702 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH); the I / O interface (read / write interface) 703 is connected between the processor 701 and the memory 702, enabling information exchange between the processor 701 and the memory 702, including but not limited to a data bus (Bus).

[0140] In some embodiments, the processor 701, memory 702, and I / O interface 703 are interconnected via a bus, and thus connected to other components of the computing device.

[0141] Fourthly, embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements any of the methods described above for updating site configuration data.

[0142] It will be understood by those skilled in the art that all or some of the steps, systems, or apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0143] Example embodiments have been disclosed herein, and while specific terminology has been used, it is for illustrative purposes only and should be construed as such, and is not intended to be limiting. In some instances, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in connection with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in connection with other embodiments, unless otherwise expressly indicated. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of this disclosure as set forth by the appended claims.

Claims

1. A method for updating site configuration data, comprising: resolving site data based on a management object (MO) model file of a network management system to obtain site data information, wherein the site data information comprises all MOs and parent-child relationships and reference relationships between the MOs; resolving a physical device model of the site based on a physical device model file of the network management system to obtain physical device information of the site, wherein the physical device information of the site comprises all physical devices in the site, a hierarchy of the physical devices, and MO instances of the physical devices at each level; determining MO instances of a target physical device, MO instances of replaceable physical devices under the target physical device, and MO instances related to services of the physical devices based on the target physical device selected by a user, the site data information, and the physical device information of the site; generating configuration data of the site based on the MO instances of the target physical device, the MO instances of the replaceable physical devices under the target physical device, and the MO instances related to the services of the physical devices; updating the site by using the configuration data of the site; the determining the MO instances of the replaceable physical devices under the target physical device based on the target physical device selected by the user and the physical device information of the site comprises: determining service types supported by physical devices at each level under the target physical device based on the target physical device selected by the user and the physical device information of the site; determining types of the physical devices at corresponding levels based on the service types supported by the physical devices at each level; determining the MO instances of the replaceable physical devices under the target physical device based on the types of the physical devices at each level.

2. The method of claim 1, wherein, the resolving the site data based on the MO model file of the network management system to obtain the site data information comprises: performing block division on the site based on the site data resolved in the MO model file of the network management system to obtain MOs of each block and parent-child relationships between the MOs; obtaining a reference relationship description keyword based on the site data resolved in the MO model file of the network management system, and obtaining MO instances of physical devices referenced by the MOs according to the reference relationship description keyword.

3. The method of claim 1, wherein, before the generating the configuration data of the site based on the MO instances of the target physical device, the MO instances of the replaceable physical devices under the target physical device, and the MO instances related to the services of the physical devices, the method further comprises: performing legality verification on the replaceable physical devices under the target physical device; when the replaceable physical devices are legal, generating the configuration data of the site based on the MO instances of the target physical device, the MO instances of the replaceable physical devices under the target physical device, and the MO instances related to the services; when the replaceable physical devices are illegal, reminding the user.

4. The method of claim 3, wherein, the performing legality verification on the replaceable physical devices under the target physical device comprises: sequentially verifying types of physical devices at each level under the target physical device, service types, and instance numbers to determine legality of the target physical device.

5. The method of claim 3, wherein, The reminding the user when the alternative physical device is illegal further comprises: replacing the target physical device, or, modifying the site data.

6. The method of claim 1, wherein, The updating the site by using the configuration data of the site comprises: creating or replacing the MO instance of the target physical device, replacing the MO instance of the physical device referenced under the target physical device, and updating the MO instance related to the business of the physical device based on the configuration data of the site.

7. The method of claim 6, wherein, The updating the MO instance related to the business of the physical device comprises: updating the business MO instance of the physical device; obtaining the MO referencing the physical device, and updating the attribute value of the MO referencing the physical device to the attribute value of the newly configured physical device. 8.An apparatus for updating site configuration data, comprising: a first parsing module configured to parse site data based on a management object (MO) model file of a network management system to obtain site data information, wherein the site data information comprises all MOs and parent-child relationships and reference relationships between the MOs; a second parsing module configured to parse a physical device model of the site based on a physical device model file of the network management system to obtain physical device information of the site, wherein the physical device information of the site comprises all physical devices in the site, a hierarchy of the physical devices, and MO instances of the physical devices at each level; a physical device determining module configured to determine, based on a target physical device selected by a user, the MO instance of the target physical device, MO instances of replaceable physical devices under the target physical device, and MO instances related to the business of the physical devices; a configuration data generating module configured to generate configuration data of the site based on the MO instance of the target physical device, the MO instances of replaceable physical devices under the target physical device, and the MO instances related to the business of the physical devices; a configuration data updating module configured to update the site by using the configuration data of the site; the physical device determining module is specifically configured to determine, based on the target physical device selected by the user and the physical device information of the site, a type of business supported by each level of physical devices under the target physical device, a type of physical device corresponding to each level based on the type of business supported by the physical devices at each level, and the MO instances of replaceable physical devices under the target physical device based on the type of the physical devices at each level. 9.An electronic device, comprising: one or more processors; a storage device having one or more programs stored thereon, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method according to any one of claims 1-7; one or more I / O interfaces connected between the processor and the memory and configured to implement information interaction between the processor and the memory. 10.A computer readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method according to any one of claims 1-7.

Images