WO2021218503A1 - 更新站点配置数据的方法及装置、电子设备 - Google Patents

更新站点配置数据的方法及装置、电子设备 Download PDF

Info

Publication number
WO2021218503A1
WO2021218503A1 PCT/CN2021/082728 CN2021082728W WO2021218503A1 WO 2021218503 A1 WO2021218503 A1 WO 2021218503A1 CN 2021082728 W CN2021082728 W CN 2021082728W WO 2021218503 A1 WO2021218503 A1 WO 2021218503A1
Authority
WO
WIPO (PCT)
Prior art keywords
physical device
site
instance
replaceable
configuration data
Prior art date
Application number
PCT/CN2021/082728
Other languages
English (en)
French (fr)
Inventor
牟丹
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US18/014,646 priority Critical patent/US20230276262A1/en
Publication of WO2021218503A1 publication Critical patent/WO2021218503A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/12—Detection or prevention of fraud
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network

Definitions

  • the present disclosure relates to the field of communication technology, for example, to a method and device for updating site configuration data, and electronic equipment.
  • LTE Long Term Evolution
  • communication equipment providers and service providers continue to introduce better-performing base stations and related equipment. Therefore, it is necessary to upgrade the sites and replace existing equipment with new equipment.
  • 5G 5th Generation mobile communication system
  • the workload of upgrading and rebuilding sites is increasing.
  • the process of upgrading and rebuilding sites not only To update the configuration data of the physical equipment corresponding to the site, it is also necessary to inherit the optimized transmission and wireless service data.
  • the above-mentioned upgrading and reconstruction of the site refers to the upgrading and reconstruction of the site on the network management side in accordance with the process of re-opening the site.
  • the configuration data of the entire site is created in the form of reopening the site, and then the network parameters are optimized. Since it takes a certain amount of time for network parameters to achieve optimal results, the user experience is poor.
  • manually create new physical configuration data on the network management side and refer to the original configuration data to configure transmission and wireless service data. Due to the large amount of data on the site and the correlation between the management objects, this manual data configuration is inefficient and error-prone.
  • the present disclosure provides a method and device for updating site configuration data, and electronic equipment.
  • a method for updating site configuration data including: analyzing site data based on a Managed Object (MO) model file of a network management system to obtain site data information; wherein, the site data information includes all MOs and all MOs The parent-child relationship and the reference relationship between the network management system; the physical device model of the site is analyzed based on the physical device model file of the network management system, and the physical device information of the site is obtained; wherein, the physical device information of the site includes all the information in the site Physical equipment, the hierarchy of all physical equipment, and the MO instance of each layer of physical equipment; determine the target physical equipment based on the target physical equipment selected by the user, the site data information, and the site’s physical equipment information
  • An apparatus for updating site configuration data including: a first analysis module configured to analyze site data based on the MO model file of the network management system to obtain site data information; wherein, the site data information includes all MOs and all The parent-child relationship and the reference relationship between MOs; the second parsing module is configured to analyze 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; wherein, the physical device of the site The device information includes all the physical devices in the site, the levels of all the physical devices, and the MO instances of the physical devices in each layer; the physical device determination module is configured to be based on the target physical device selected by the user and the site The data information and the physical device information of the site determine the MO instance of the target physical device, the MO instance of the replaceable physical device at the level where the target physical device is located, and the service related to the replaceable physical device MO instance; configuration data generation module, configured to be based on the MO instance of the target physical device, the MO instance of the replaceable physical device at
  • An electronic device including: one or more processors; a memory, on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the The method for updating site configuration data by one or more processors; one or more input/output (Input/Output, I/O) interfaces, connected between the processor and the memory, and configured to implement the processing Information interaction between the device and the memory.
  • processors including: one or more processors; a memory, on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the The method for updating site configuration data by one or more processors; one or more input/output (Input/Output, I/O) interfaces, connected between the processor and the memory, and configured to implement the processing Information interaction between the device and the memory.
  • I/O input/output
  • a computer-readable medium is also provided, and a computer program is stored, and when the program is executed by a processor, the above method for updating site configuration data is realized.
  • FIG. 1 is a flowchart of a method for updating site configuration data provided by an embodiment of the disclosure
  • FIG. 2 is a MO model relationship diagram obtained by analyzing site data based on MO model files provided by an embodiment of the disclosure
  • FIG. 3 is a flowchart of another method for updating site configuration data provided by an embodiment of the present disclosure.
  • FIG. 4 is a flowchart of another method for updating site configuration data provided by an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of an apparatus for updating site configuration data provided by an embodiment of the disclosure.
  • FIG. 6 is a schematic diagram of another device for updating site configuration data provided by an embodiment of the disclosure.
  • FIG. 7 is a block diagram of an electronic device provided by an embodiment of the disclosure.
  • the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) protocol is a standard for wireless communication technology, in which the network management configuration part is to describe the site through the MO. Modeling standards are given in the 3GPP protocol, and manufacturers expand the modeling based on the 3GPP standards.
  • the instance of the model is the configuration data of the station, and the configuration data is the basis for the operation of the station.
  • each network element node of the site includes device sub-nodes, transmission sub-nodes, and wireless sub-nodes, and each sub-node is its corresponding service sub-node.
  • the device sub-node, transmission sub-node, wireless sub-node, and service sub-node describe an MO.
  • the configuration data of the site is composed of these MO instances.
  • the network management system manages multiple types of sites. Therefore, the network management system includes configuration data for different types of sites.
  • the configuration data of the site includes MO model files and physical device model files, which are recorded in the network management system.
  • the MO model file of the network management system contains multiple MOs and their attributes, and the parent-child relationship between multiple MOs.
  • the MO model file can also describe the referenced physical devices. For example, the attribute in the modeled MO is "Related Physical Device MO", and the value is the Distinguished Name (DN) of the referenced physical device.
  • DN Distinguished Name
  • the physical device model file is used to describe the site type of the site, the hierarchical relationship of the multi-layer physical devices supported by the site, and the MO instance corresponding to each layer of the physical device.
  • the physical equipment in each site is the base station, cabinet, rack, frame, slot, single board, and single board business capabilities from high to low.
  • Each level of physical equipment node has a corresponding MO. Although the level and MO of the physical equipment are relatively fixed, the MO instances of the physical equipment at multiple levels under each type of site are different.
  • the configuration information of the site When updating the configuration information of the site, it can be updated on the network element side or on the network management side. Compared with the network element side, the network management side updates the configuration information of the site, which can effectively utilize the resources of the network management side and improve the efficiency of production configuration information. Therefore, in the embodiments of the present disclosure, the focus is to introduce the configuration information of the site generated by the network management side, and then update the site.
  • Fig. 1 is a flowchart of a method for updating site configuration data provided by an embodiment of the present disclosure.
  • the method of updating site configuration data includes:
  • Step 101 Analyze site data based on the MO model file of the network management system to obtain site data information.
  • the site data information includes all MOs and parent-child relationships and reference relationships between all MOs.
  • the MO model file of the network management system adopts, but is not limited to, Extensible Markup Language (XML), Excel, and Yang format files.
  • the MO model file is stored in the network management system.
  • the MO model file can be used to obtain the attributes of multiple MOs and MOs in the site, as well as the parent-child relationship and reference relationship of multiple MOs.
  • MO attributes include information such as MO name, value type, value range, default value, and whether there are keywords.
  • the parent-child relationship of MO refers to the master-slave relationship between multiple MOs.
  • the device root node MO includes the device child node MO
  • the device root node MO and the device child node MO have a parent-child relationship
  • the device root node MO is the parent node MO
  • the device child node MO is the child node MO.
  • the reference relationship of MO refers to the reference relationship between multiple MOs. For example, when the transmission child node MO references the device child node MO, there is a reference relationship between the transmission child node MO and the device child node MO.
  • the site data is parsed based on the MO model file of the network management system, the sites are divided into blocks, and the MO in each block and the parent-child relationship between the obtained MO are obtained.
  • FIG. 2 is a MO model relationship diagram obtained by analyzing site data based on an MO model file provided by an embodiment of the disclosure.
  • the network element MO 2 in the site is divided into three blocks, namely, the device root node MO 21, the transmission root node MO 22, and the wireless root node MO 23.
  • the transmission root node MO 22 there are multiple transmission sub-nodes MO 221, MO 222, and MO 223, and the transmission sub-nodes MO 221, MO 222, and MO 223 may also have sub-nodes MO 2211 and MO 2212.
  • the wireless root node MO 23 there are multiple wireless sub-nodes MO 231 and MO 232, and the wireless sub-nodes MO 231 and MO 232 may also have sub-nodes MO 2311, MO 2312, MO 2313.
  • Device and node MO 21 and device child nodes MO 211, MO 212, MO 213 are parent-child relationships
  • transmission root node MO 22 and transmission child nodes MO 221, MO 222, MO 223 are parent-child relationships
  • wireless root node MO 23 and unlimited children Nodes MO 231, MO 232, and MO 233 have a parent-child relationship.
  • the parent-child relationship between multiple MOs in the site can be stored in a tree structure and displayed to users.
  • the site data is parsed based on the MO model file of the network management system to obtain a reference relationship description keyword, and the MO instance of the physical device referenced by the MO is obtained according to the reference relationship description keyword.
  • the reference relationship description keyword is a keyword used to describe the reference relationship of the MO.
  • the MO of the physical device referenced by the MO can be obtained, thereby obtaining the MO instance of the referenced physical device.
  • Step 102 Analyze the physical device model of the site based on the physical device model file of the network management system to obtain physical device information of the site.
  • the physical device information of the site includes all the physical devices in the site, the levels of the physical devices, and the MO instances of the physical devices at each layer.
  • the physical device model files of the network management system adopt but are not limited to XML, Excel, and Yang format files.
  • the physical device model file of the network management system describes the site type, the hierarchical relationship of the multi-layer physical devices supported by the site, and the MO instance corresponding to each layer of the physical device.
  • the organization level of multiple physical devices in the site from high to low is base station, cabinet, rack, machine frame, slot, single board, single board business capabilities, and physical device nodes at each level There are corresponding MOs, such as base station MO, cabinet MO, rack MO, shelf MO, slot MO, single board MO, and single board service capability MO.
  • the physical device information of the site can be stored in a tree structure and displayed to users.
  • the physical device model of the site is parsed based on the physical device model file of the network management system, and the physical device information of the site can be obtained.
  • the physical device information includes the level of the physical device in the site and the MO instance of each layer of the physical device, namely All physical devices under the site, the hierarchical relationship of the physical devices, and the MO instances corresponding to each layer of physical devices.
  • the MO model file and the physical device model file of the network management system can be built in the network management system, and the site data and the physical device model of the site can be used as input signals.
  • Step 103 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 related to the business 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. Instance.
  • the parent-child relationship, reference relationship between multiple MOs in the site, and physical device information of the site are displayed in a tree structure, and the user can select the target physical device on the interface of the network management system according to the modification of the site.
  • the service type supported by the multilayer physical device under the target physical device is determined layer by layer based on the target physical device selected by the user and the physical device information of the site; the service type supported by each layer of physical device is determined Corresponding to the type of the physical device at the level; determine the MO instance of the replaceable physical device under the target physical device based on the type of the physical device at each layer.
  • the network management system calculates the types of physical devices that can be replaced by each node.
  • the type of the current (current layer) physical device the type of physical device of the same service type that the current physical device can support is calculated.
  • the current physical device type and service type can be in the MO model file or the physical device model file.
  • the alternative cabinet type that can be selected is the cabinet type that supports the same business function under the site. In other words, after the station type of the site is determined, the type of the cabinet under the site can be determined; After the type is selected, the user can choose to replace the rack with the same service function supported by the cabinet; and so on, up to the lowest single board service. Therefore, after determining a level of physical device, the type of the multilayer physical device under the layer of physical device can be determined according to the type of the layer of physical device, so as to determine the corresponding MO instance.
  • the target physical device can be arbitrarily selected according to the reconstruction of the site, that is, a physical device in the site can be selected as the target physical device, and only the target physical device and the multi-layer physical device under the target physical device can be selected.
  • the equipment and related business data are updated without the need to update the configuration data of other physical equipment other than the target physical equipment, which improves the flexibility of the configuration data of the site, thereby improving the efficiency of the update.
  • Step 104 Generate configuration data of the site based on 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.
  • the MO instance of the target physical device is created or replaced based on the configuration data of the site, the MO instance that references the physical device under the target physical device is replaced, and the MO instance related to the service of the physical device is updated.
  • the service MO instance under the physical device is updated; the MO that refers to the physical device is obtained, and the attribute value of the MO that refers to the physical device is updated.
  • 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 generate configuration data of the site.
  • Step 105 Use the configuration data of the site to update the site.
  • step 105 use the configuration data of the site to replace the MO instances of the physical device at the corresponding level; find the MOs that refer to these physical devices, and update their "relevant attributes" to the identification name of the new physical device MO instance;
  • the MO instance of the physical device is passed into the extended interface, and the interface is called to complete the update of the corresponding business MO instance.
  • Fig. 3 is a flowchart of another method for updating site configuration data provided by an embodiment of the present disclosure.
  • the method of updating site configuration data includes:
  • Step 301 Analyze site data based on the MO model file of the network management system to obtain site data information.
  • the site data information includes all MOs and parent-child relationships and reference relationships between all MOs.
  • Step 302 Analyze the physical device model of the site based on the physical device model file of the network management system to obtain physical device information of the site.
  • the physical device information of the site includes all the physical devices in the site, the levels of the physical devices, and the MO instances of the physical devices at each layer.
  • Step 303 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 related to the business 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. Instance.
  • step 301 to step 303 are the same as step 101 to step 103 in the foregoing embodiment, and will not be repeated here.
  • Step 304 Perform legality verification on the replaceable physical device under the target physical device.
  • the type, service type, and number of instances of the multi-layer physical device under the target physical device are sequentially verified to determine the legitimacy of the target physical device.
  • the network management system obtains the MO instance of the target physical device at each level according to the user's choice.
  • the verification of legitimacy can start from the station type of the site.
  • the verification process includes: verifying whether the type of each cabinet in the site is a cabinet type that can be created, and verifying the service type of the cabinet (such as main cabinet, auxiliary cabinet or auxiliary cabinet). Whether the service type of the cabinet is the same as that of the cabinet before replacement; and check whether the number of cabinet instances supported by the site is greater than or equal to the number of cabinet instances configured on the site. For example: Suppose there are two auxiliary cabinets at the site. If the updated site support capacity is greater than or equal to two auxiliary cabinets, the verification will pass.
  • the next layer of physical equipment will continue to be verified, that is, the verification of the rack will be performed.
  • the verification content of the rack is the same as that of the cabinet, which is also carried out according to the rack type, the service type of the rack, and the number of racks supported by the rack; until the last level of the site is traversed, that is, the single board service MO instance.
  • verifying the service MO instance of the single board determine the type of the single board, determine whether the MO instance of the single board is a service MO supported by the single board, and whether the number of service MO instances of the single board can be greater than or equal to the number of service MO instances of the corresponding single board at the site .
  • the original physical device continues to be used.
  • step 305 is executed.
  • the network management system can guide the user to replace the target physical device. For example, the network management system can recommend suitable target physical devices to users. The network management system can also guide users to transform site data.
  • Step 305 Generate site configuration data based on 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.
  • step 305 is the same as step 104 in the foregoing embodiment, and will not be repeated here.
  • Step 306 Use the configuration data of the site to update the site.
  • the MO instance of the physical device may be updated layer by layer.
  • the cabinet MO instance and the business MO instance are first updated, and then the physical device MO instances and business MO instances of different levels are updated layer by layer.
  • the service MO of a single board it is a description of the capability of the single board, that is, for a certain single board, the number of services and MO instances it supports is determined. Therefore, after the single board is replaced, the business MO instance under the single board will replace the business MO instance of the single board at the site.
  • find the MOs that refer to these physical devices and update its "Related Physical Device MO" attribute value to the value of the identification name of the new physical device MO instance.
  • import the changed physical device service MO instance into the extended interface and complete the update of the corresponding physical device service MO instance when the extended interface is called.
  • a service MO instance can be created. For example, when the replaced single-board service MO instances are more than the site's single-board service MO instances, one single-board service MO instance can be created.
  • Fig. 4 is a flowchart of another method for updating site configuration data provided by an embodiment of the present disclosure. As shown in Figure 4, methods for updating site configuration data include:
  • Step 401 Analyze site data based on the MO model file of the network management system to obtain site data information.
  • the site data information includes all MOs and parent-child relationships and reference relationships between all MOs.
  • the MO model file of the network management system is an Excel format file.
  • the behavior MO and its attribute name are listed as the description of the MO and its attributes, including information such as the parent MO name, value type, value range, default value, and whether there are keywords.
  • the network management system When the network management system starts, it first loads the MO model file, then parses the site data entered by the user, divides the site data into blocks according to equipment, transmission and wireless, and stores each block of MO instances in a tree structure; at the same time, according to the reference relationship
  • the description keyword searches for the referenced physical device MO instance to obtain the referenced physical device MO instance.
  • the reference physical device MO instance can be stored in the physical, transmission, and wireless MO instances.
  • Step 402 Analyze the physical device model of the site based on the physical device model file of the network management system to obtain physical device information of the site.
  • the physical device model file uses an Excel format file description.
  • the physical device model file is used to describe the hierarchical relationship of the station type, multi-layer physical device, and the MO instance corresponding to each layer of physical device.
  • base stations, cabinets, racks, machine frames, slots, and boards can be described using separate pages.
  • the MO instance of the physical device is listed as the MO attribute of the physical device and its sub-device types, and the last column is filled with the sub-device types supported by the physical device.
  • the list contains the MO attributes of the veneer and its business capability attributes, the MO instances of the behavior veneer and the MO instances of the business capabilities supported by it.
  • the physical device model file of the site is loaded and analyzed to obtain all the MO instances of the physical devices actually configured under the site, as well as the level of the physical devices and the MO instances of the physical devices of each layer.
  • the network management system can parse all MOs in the site and parent-child relationships and reference relationships between all MOs, all physical device MO instances, and the level of physical devices and the MO instances of each layer of physical devices. Presented to the user for the user to select an alternative physical device MO instance.
  • Step 403 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 related to the business 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. Instance.
  • the network management system presents the physical devices and corresponding MO instances of each layer in the site to users according to a tree structure. For example, in the user interface, tree nodes at different levels in the tree structure represent physical devices at different levels. When the user clicks on the tree node, the MO instance of the physical device corresponding to each tree node will be presented in a table. According to the physical device MO instances supported by each layer of physical devices, the user can learn the types of physical devices that can be replaced.
  • step 403 after the user selects the target physical device, the tree node corresponding to the target physical device can learn the type of the replaceable physical device and the MO instance of the replaceable physical device under the target physical device.
  • the network management system may also obtain an MO instance that references the physical device according to the relevant attributes of the physical device.
  • Step 404 Perform legality verification on the replaceable physical device under the target physical device.
  • the network management system integrates the physical device level 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), Check whether the type of the first-level child node is the type of sub-device that can be created under it; secondly, check whether the service type of the sub-device is the same as the original device before replacement; third, check whether the number of instances of the sub-device is greater than Or equal to the number of instances of equipment at the corresponding level at the source site; if the verification passes, the next level of verification is performed, and the last level of single-board service capability MO is traversed.
  • site type the device root node
  • Check whether the type of the first-level child node is the type of sub-device that can be created under it
  • the service type of the sub-device is the same as the original device before replacement
  • third check whether the number of instances of the sub-device is greater than Or equal to the number of instances of equipment at the corresponding level
  • verify whether the types of multiple cabinets in the site are the cabinet types that can be created verify whether the service type of the cabinet (such as main cabinet, auxiliary cabinet or auxiliary cabinet) is the same as the service type of the cabinet before replacement; and check Whether the number of rack instances supported by the site is greater than or equal to the number of rack instances configured on the site. For example: Suppose there are two auxiliary cabinets at the site. If the updated site support capacity is greater than or equal to two auxiliary cabinets, the verification will pass. After the cabinet verification is passed, the next layer of physical equipment will continue to be verified, that is, the verification of the rack will be performed.
  • the service type of the cabinet such as main cabinet, auxiliary cabinet or auxiliary cabinet
  • the content of the rack verification is the same as that of the cabinet, which is also carried out according to the rack type, the service type of the rack, and the number of racks supported by the rack; until it traverses to the last level of the site, that is, the single-board service MO instance.
  • the network management system can give a clear reminder, knowing that the user replaces the target physical equipment or changes the data of the original site.
  • Step 405 Generate configuration data of the site based on 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.
  • Step 406 Update the site with the configuration data of the site.
  • MO model files in Ecxel format can also update the site configuration data according to the method provided in this embodiment, and the same technical effects can be obtained.
  • the MO model file of the network management system analyzes the site data to obtain the parent-child relationship and the reference relationship between multiple MOs in the site; the physical device model file of the network management system analyzes the physical of the site The device model obtains the physical device information of the site; determines the MO instance of the replaceable physical device under the target physical device based on the target physical device selected by the user and the physical device information of the site; based on the target physical device
  • 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 business of the physical device generate configuration data of the site; use the configuration data of the site to update the site , Which enables users to update the configuration data of the site on the network management side in combination with the target physical device desired by the user, and the updated configuration data includes not only physical device data, but also business data, which improves the versatility of updating site configuration data, thereby improving user experience.
  • the method for updating site configuration data provided by this embodiment can replace multiple types and multiple levels of physical devices, so that users can flexibly select replaceable target physical devices, achieving the use of one system to cover multiple types The effect of physical equipment replacement, and the configuration efficiency is high, and it is not easy to make mistakes.
  • Fig. 5 is a schematic diagram of an apparatus for updating site configuration data provided by an embodiment of the disclosure.
  • the apparatus for updating site configuration data provided by an embodiment of the present disclosure includes:
  • the first parsing module 501 is configured to analyze site data based on the MO model file of the network management system to obtain site data information.
  • the site data information includes all MOs and parent-child relationships and reference relationships between all MOs.
  • the specific implementation of the first parsing module 501 is the same as that of step 101 in the foregoing embodiment, and will not be repeated here.
  • the second parsing module 502 is configured to analyze the physical device model of the site based on the physical device model file of the network management system to obtain physical device information of the site.
  • the physical device information of the site includes all the physical devices in the site, the levels of the physical devices, and the MO instances of the physical devices at each layer.
  • the specific implementation of the second parsing module 502 is the same as that of step 102 in the foregoing embodiment, and will not be repeated here.
  • the physical device determining module 503 is configured to determine the MO instance of the target physical device and the replaceable physical device under the target physical device based on the target physical device selected by the user, the site data information, and the physical device information of the site.
  • the specific implementation of the physical device determining module 503 is the same as that of step 103 in the foregoing embodiment, and will not be repeated here.
  • the configuration data generating module 504 is configured to generate configuration data of the site based on 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 business of the physical device.
  • the specific implementation manner of the configuration data generating module 504 is the same as that of step 104 in the foregoing embodiment, and will not be repeated here.
  • the configuration data update module 505 is configured to update the site using the configuration data of the site.
  • Fig. 6 is a schematic diagram of another apparatus for updating site configuration data provided by an embodiment of the disclosure.
  • the apparatus for updating site configuration data provided by an embodiment of the present disclosure includes:
  • the first parsing module 601 is configured to analyze site data based on the MO model file of the network management system to obtain site data information.
  • the site data information includes all MOs and parent-child relationships and reference relationships between all MOs.
  • the second parsing module 602 is configured to analyze the physical device model of the site based on the physical device model file of the network management system to obtain physical device information of the site.
  • the physical device determining module 603 is configured to determine the MO instance of the target physical device and the replaceable physical device under the target physical device based on the target physical device selected by the user, the site data information, and the physical device information of the site.
  • the verification module 604 is configured to perform legality verification on the replaceable physical device under the target physical device.
  • the type, service type, and number of instances of the multi-layer physical device under the target physical device are sequentially verified to determine the legitimacy of the target physical device.
  • the configuration data generating module 605 is configured to generate configuration data of the site based on 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 business of the physical device.
  • the configuration data update module 606 is configured to update the site using the configuration data of the site.
  • the user can update the site configuration data on the network management side in combination with the target physical device desired by the user, and the updated configuration data includes both physical device data and business data, which improves The versatility of the update site configuration data is improved, thereby improving the user experience.
  • the device for updating site configuration data provided in this embodiment can replace multiple types and multiple levels of physical equipment, so that users can flexibly select replaceable target physical equipment, achieving the use of one system to cover multiple types The effect of physical equipment replacement, and the configuration efficiency is high, and it is not easy to make mistakes.
  • an electronic device which includes:
  • the processor 701 is a device with data processing capabilities, including but not limited to a central processing unit (CPU), etc.; the memory 702 is a device with data storage capabilities, including but not limited to random access memory (Random Access Memory).
  • Memory RAM
  • RAM Synchronous Dynamic RAM
  • DDR SDRAM Double Data Rate SDRAM
  • ROM Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • FLASH Flash memory
  • I/O interface (read and write interface) 703 is connected between the processor 701 and the memory 702, which can realize the processor 701 and the memory 702
  • the information exchange including but not limited to data bus (Bus), etc.
  • the processor 701, the memory 702, and the I/O interface 703 are connected to each other through a bus, and further connected to other components of the computing device.
  • the embodiment of the present disclosure provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, any one of the above-mentioned methods for updating site configuration data is realized.
  • the functional modules/units in the system, and the device can be implemented as software, firmware, hardware, and appropriate combinations thereof.
  • the division between functional modules/units mentioned in the above description 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 consist of multiple The physical components are executed cooperatively.
  • Some physical components or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit.
  • Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or a non-transitory medium) and a communication medium (or a transitory medium).
  • the term computer storage media includes volatile and nonvolatile implementations in any method or technology configured to store information (such as computer-readable instructions, data structures, program modules, or other data). Sexual, removable and non-removable media.
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technologies, compact disc read-only memory (Compact Disc ROM, CD-ROM), digital versatile disc (Digital Versatile Disc, DVD) or other optical disc storage, magnetic Cassette, magnetic tape, disk storage or other magnetic storage device, or any other medium that can be configured to store desired information and that can be accessed by a computer.
  • Communication media generally contain computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Computer And Data Communications (AREA)

Abstract

本文公开了一种更新站点配置数据的方法，包括：基于网管系统的MO模型文件解析站点数据，获得站点数据信息；基于网管系统的物理设备模型文件解析站点的物理设备模型，获得站点的物理设备信息；基于用户选定的目标物理设备、站点数据信息和站点的物理设备信息确定目标物理设备的MO实例、目标物理设备所在层次下的可替换的物理设备的MO实例以及与可替换的物理设备的业务相关的MO实例；基于目标物理设备的MO实例、目标物理设备所在层次下的可替换的物理设备的MO实例，以及与可替换的物理设备的业务相关的MO实例生成站点的配置数据；利用站点的配置数据更新站点。本文还公开了一种更新站点配置数据的装置和电子设备。

Description

更新站点配置数据的方法及装置、电子设备 技术领域
本公开涉及通信技术领域，例如涉及一种更新站点配置数据的方法及装置、电子设备。
背景技术
为了提高无线网络长期演进(Long Term Evolution，LTE)系统的性能，通讯设备提供商和服务提供商不断推出性能更优的基站及相关设备，因此，需要对站点进行升级改造，用新设备替换已有设备，并调整站点的资源分配。例如第五代移动通信系统(the 5th Generation mobile communication system，5G)设备逐渐替代LTE设备的过程中，升级改造站点的工作量越来越大，而且，在对站点的升级改造过程中，不仅要更新站点对应的物理设备的配置数据，还需继承已优化的传输、无线业务数据。
上述对站点进行升级改造是指在网络管理侧按照重新开通站点的流程对站点进行升级改造。如，在网络管理侧基于新的站型或者设备，按照重新开站的形式创建整个站点的配置数据，再优化网络参数。由于网络参数达到最优效果需要一定的时间，导致用户体验较差。或者，在网络管理侧人工创建新的物理配置数据，并参照原有配置数据，配置传输和无线业务数据。由于站点的数据量大且管理对象有关联关系，这种人工进行数据配置的效率低，且易出错。
发明内容
本公开提供一种更新站点配置数据的方法及装置、电子设备。
提供一种更新站点配置数据的方法，包括：基于网管系统的管理对象(Managed Object，MO)模型文件解析站点数据，获得站点数据信息；其中，所述站点数据信息包括所有MO及所述所有MO之间的父子关系和引用关系；基于所述网管系统的物理设备模型文件解析站点的物理设备模型，获得所述站点的物理设备信息；其中，所述站点的物理设备信息包括所述站点中所有的物理设备、所述所有的物理设备的层次和每层物理设备的MO实例；基于用户选定的目标物理设备、所述站点数据信息和所述站点的物理设备信息确定所述目标物理设备的MO实例、所述目标物理设备所在层次下的可替换的物理设备的MO实例以及与所述可替换的物理设备的业务相关的MO实例；基于所述目标物理设备的MO实例、所述目标物理设备所在层次下的所述可替换的物理设备 的MO实例，以及与所述可替换的物理设备的业务相关的MO实例生成所述站点的配置数据；利用所述站点的配置数据更新所述站点。
还提供一种更新站点配置数据的装置，包括：第一解析模块，配置为基于网管系统的MO模型文件解析站点数据，获得站点数据信息；其中，所述站点数据信息包括所有MO及所述所有MO之间的父子关系和引用关系；第二解析模块，配置为基于所述网管系统的物理设备模型文件解析站点的物理设备模型，获得所述站点的物理设备信息；其中，所述站点的物理设备信息包括所述站点中所有的物理设备、所述所有的物理设备的层次和每层所述物理设备的MO实例；物理设备确定模块，配置为基于用户选定的目标物理设备、所述站点数据信息和所述站点的物理设备信息确定所述目标物理设备的MO实例、所述目标物理设备所在层次下的可替换的物理设备的MO实例以及与所述可替换的物理设备的业务相关的MO实例；配置数据生成模块，配置为基于所述目标物理设备的MO实例、所述目标物理设备所在层次下的所述可替换的物理设备的MO实例，以及与所述可替换的物理设备的业务相关的MO实例生成所述站点的配置数据；配置数据更新模块，配置为利用所述站点的配置数据更新所述站点。
还提供一种电子设备，包括：一个或多个处理器；存储器，其上存储有一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器上述的更新站点配置数据的方法；一个或多个输入/输出(Input/Output，I/O)接口，连接在所述处理器与存储器之间，配置为实现所述处理器与存储器的信息交互。
还提供一种计算机可读介质，存储有计算机程序，所述程序被处理器执行时实现上述的更新站点配置数据的方法。
附图说明
图1为本公开实施例提供的一种更新站点配置数据的方法的流程图；
图2为本公开实施例提供的一种基于MO模型文件解析站点数据得到的MO模型关系图；
图3为本公开实施例提供的另一种更新站点配置数据的方法的流程图；
图4为本公开实施例提供的另一种更新站点配置数据的方法的流程图；
图5为本公开实施例提供的一种更新站点配置数据的装置的原理图；
图6为本公开实施例提供的另一种更新站点配置数据的装置的原理图；
图7为本公开实施例提供的一种电子设备的组成框图。
具体实施方式
下面结合附图对本公开提供的更新站点配置数据的方法及装置、电子设备、计算机可读介质进行描述。
在下文中将参考附图描述示例实施例，所述示例实施例可以以不同形式来体现且不应当被解释为限于本文阐述的实施例。
如本文所使用的，术语“和/或”包括一个或多个相关列举条目的任何和所有组合。
本文所使用的术语仅用于描述实施例，且不意欲限制本公开。如本文所使用的，单数形式“一个”和“该”也意欲包括复数形式，除非上下文另外指出。当本文中使用术语“包括”和/或“由……制成”时，指定存在所述特征、整体、步骤、操作、元件和/或组件，但不排除存在或添加一个或多个其它特征、整体、步骤、操作、元件、组件和/或其群组。
本文所用的所有术语(包括技术和科学术语)的含义与本领域普通技术人员通常理解的含义相同。诸如那些在常用字典中限定的那些术语应当被解释为具有与其在相关技术以及本公开的背景下的含义一致的含义，且将不解释为具有理想化或过度形式上的含义，除非本文如此限定。
第三代合作计划(3rd Generation Partnership Project，3GPP)协议是无线通讯技术的标准，其中，网络管理配置部分是通过MO对站点进行描述。在3GPP协议中给出了建模标准，厂家基于3GPP标准进行建模的扩充。对于基站，模型的实例就是站点的配置数据，配置数据是站点运行的基础。
在3GPP的建模标准中，站点的每个网元节点下包含设备子节点、传输子节点和无线子节点，每个子节点下为其对应的业务子节点。设备子节点、传输子节点、无线子节点和业务子节点描述一个MO。站点的配置数据，就是由这些MO的实例组成。
网络管理系统管理着多种类型的站点，因此，网络管理系统包括不同类型的站点的配置数据。站点的配置数据包括MO模型文件和物理设备模型文件，这些模型文件记录在网管系统中。其中，网管系统的MO模型文件包含多个MO及其属性，多个MO间的父子关系。对于传输或者无线引用的物理设备，MO模型文件还可以对引用的物理设备进行描述。例如，在建模MO中的属性为“相关物理设备MO”，取值为引用的物理设备的标识名(Distinguished Name，DN)。
物理设备模型文件用于描述站点的站型，该站点支持的多层物理设备的层次关系，以及每层物理设备对应的MO实例。每个站点中物理设备从高到低依次为基站、机柜、机架、机框、槽位、单板、单板的业务能力，每个层次的物 理设备节点都有对应的MO。虽然物理设备的层次和MO是相对固定的，但每种站型下多个层次的物理设备MO实例是不同的。
当用户改造站点时，通常需要对站点内目标物理设备的MO实例、引用该目标物理设备的MO实例以及与该目标物理设备的业务相关的MO实例进行更新，即需要更新站点的配置信息。
在更新站点的配置信息时，可以在网元侧进行更新，也可以在网管侧进行更新。相对于网元侧，网管侧更新站点的配置信息，可以有效地利用网管侧的资源，提高生产配置信息的效率。因此，在本公开实施例中，重点介绍网管侧生成站点的配置信息，然后对站点进行更新。
本公开实施例提供一种更新站点配置数据的方法。图1为本公开实施例提供的一种更新站点配置数据的方法的流程图。参照图1，更新站点配置数据的方法包括：
步骤101，基于网管系统的MO模型文件解析站点数据，获得站点数据信息。
站点数据信息包括所有MO及所述所有MO之间的父子关系和引用关系。
网管系统的MO模型文件采用但不限于可扩展标记语言(Extensible Markup Language，XML)、Excel、Yang格式的文件。MO模型文件存储在网管系统中，利用MO模型文件可以获得站点中多个MO及MO的属性，以及多个MO的父子关系和引用关系。其中，MO属性包括MO名称、取值类型、取值范围、默认值、是否有关键字等信息。
MO的父子关系是指多个MO之间的主从关系。例如，当设备根节点MO下包括设备子节点MO时，设备根节点MO和设备子节点MO存在父子关系，设备根节点MO为父节点MO，设备子节点MO为子节点MO。
MO的引用关系是指多个MO之间的引用关系。例如，当传输子节点MO引用设备子节点MO时，传输子节点MO和设备子节点MO之间存在引用关系。
在一些实施例中，基于网管系统的MO模型文件中解析站点数据，对站点进行分块，获得每个分块中的MO及获得的MO之间的父子关系。
图2为本公开实施例提供的一种基于MO模型文件解析站点数据得到的MO模型关系图。如图2所示，站点中的网元MO 2被分为三块，即设备根节点MO 21、传输根节点MO 22和无线根节点MO 23。在设备根节点MO 21以下有多个设备子节点MO 211、MO 212、MO 213，每个设备子节点以下还可以设置一个或多个子节点，例如，设备子节点MO 211、MO 212、MO 213以下设置子节点MO 2111、MO 2112、MO 2113、MO 2114。在传输根节点MO 22以下有多个传输子节点MO 221、MO 222、MO 223，传输子节点MO 221、MO 222、MO 223 以下还可以设置有子节点MO 2211、MO 2212。在无线根节点MO 23以下有多个无线子节点MO 231、MO 232，无线子节点MO 231、MO 232以下还可以设置有子节点MO 2311、MO 2312、MO 2313。
设备跟节点MO 21与设备子节点MO 211、MO 212、MO 213为父子关系，传输根节点MO 22与传输子节点MO 221、MO 222、MO 223为父子关系，无线根节点MO 23与无限子节点MO 231、MO 232、MO 233为父子关系。
当基于网管系统的MO模型文件解析站点数据，获得站点中多个MO之间的父子关系时，可以将站点中的多个MO之间的父子关系按照树状结构存储并向用户展示。
在一些实施例中，基于网管系统的MO模型文件中解析站点数据，获得引用关系描述关键字，依据引用关系描述关键字获得MO引用的物理设备的MO实例。
引用关系描述关键字是用于描述MO的引用关系的关键字，依据该引用关系描述关键字可以获得MO引用的物理设备的MO，从而获得引用的物理设备的MO实例。例如：如图2中的虚线所示，依据引用关系描述关键字可以获得传输子节点MO 221和物理设备子节点MO 212存在引用关系，并获得传输子节点MO 221引用的物理设备子节点MO 212，物理设备子节点MO 212引用的物理设备子节点MO 211。
步骤102，基于网管系统的物理设备模型文件解析站点的物理设备模型，获得站点的物理设备信息。
站点的物理设备信息包括站点中所有的物理设备、物理设备的层次和每层物理设备的MO实例。
网管系统的物理设备模型文件采用但不限于XML、Excel、Yang格式的文件。网管系统的物理设备模型文件描述站点的站型，该站点支持的多层物理设备的层次关系，以及每层物理设备对应的MO实例。
在一些实施例中，站点中多个物理设备的组织层次从高到低依次为基站、机柜、机架、机框、槽位、单板、单板的业务能力，每个层次的物理设备节点都有对应的MO，如基站MO、机柜MO、机架MO、机框MO、槽位MO、单板MO、单板的业务能力MO。当基于网管系统的物理设备模型文件解析站点的物理设备模型，获得站点的物理设备信息后，可以将站点的物理设备信息按照树状结构存储并向用户展示。
虽然物理设备层次和MO是相对固定的，但每种站型下多个层次的物理设备MO实例并不一定相同。
在一些实施例中，基于网管系统的物理设备模型文件解析站点的物理设备模型，可以获得站点的物理设备信息，该物理设备信息包括站点中物理设备的层次和每层物理设备的MO实例，即站点下所有的物理设备，物理设备的层次关系，以及每层物理设备对应的MO实例。
在一些实施例中，网管系统的MO模型文件和物理设备模型文件可以内置在网管系统中，站点数据和站点的物理设备模型可以作为输入信号。
步骤103，基于用户选定的目标物理设备、站点数据信息和站点的物理设备信息确定目标物理设备的MO实例、目标物理设备下可替换的物理设备的MO实例以及与物理设备的业务相关的MO实例。
在本实施例中，站点中多个MO之间的父子关系、引用关系以及站点的物理设备信息是以树状结构展示，用户可以根据站点的改造情况在网管系统的界面选择目标物理设备。
在一些实施例中，基于用户选定的目标物理设备和所述站点的物理设备信息逐层确定所述目标物理设备下多层物理设备支持的业务类型；基于每层物理设备支持的业务类型确定对应层次物理设备的类型；基于每层所述物理设备的类型确定所述目标物理设备下可替换的物理设备的MO实例。
例如，网管系统计算每个节点可替换的物理设备类型。根据当前(当前层)物理设备的类型，计算该当前物理设备所能支持的同业务类型的物理设备类型。其中，当前物理设备的类型和业务类型可在MO模型文件，也可在物理设备模型文件。用户选定站点的站型后，可选择的替换机柜类型为该站点下支持的相同业务功能的机柜类型，换言之，站点的站型确定后，该站点下的机柜的类型即可确定；在机柜类型选定后，用户可选择的替换机架为该机柜下支持的相同业务功能的机架类型；以此类推，直至最底层的单板业务。因此，在确定一个层次的物理设备后，可根据该层物理设备的类型确定该层物理设备下的多层物理设备的类型，从而确定对应的MO实例。
在本实施例中，目标物理设备可以根据站点的改造情况任意选定，即，可以选定站点中一个物理设备作为目标物理设备，仅对该目标物理设备、该目标物理设备下的多层物理设备以及相关的业务数据进行更新，不需要对目标物理设备以外的其它物理设备的配置数据进行更新，提高了站点的配置数据的灵活性，从而提高更新的效率。
步骤104，基于目标物理设备的MO实例、目标物理设备下可替换的物理设备的MO实例，以及与物理设备的业务相关的MO实例生成站点的配置数据。
在一些实施例中，基于站点的配置数据创建或替换目标物理设备的MO实 例、替换目标物理设备下引用物理设备的MO实例，以及更新与物理设备的业务相关的MO实例。
在一些实施例中，更新物理设备下的业务MO实例；获取引用物理设备的MO，更新引用物理设备的MO的属性值。
在本实施例中，目标物理设备的MO实例、目标物理设备下可替换的物理设备的MO实例，以及与物理设备的业务相关的MO实例生成站点的配置数据。
步骤105，利用站点的配置数据更新站点。
在步骤105中，利用站点的配置数据，对相应层次物理设备MO实例进行替换；查找引用这些物理设备的MO，更新其“相关属性”值为新的物理设备MO实例的识别名；将变更的物理设备MO实例传入扩展接口，调用接口完成对应业务MO实例的更新。
图3为本公开实施例提供的另一种更新站点配置数据的方法的流程图。参照图3，更新站点配置数据的方法包括：
步骤301，基于网管系统的MO模型文件解析站点数据，获得站点数据信息。
站点数据信息包括所有MO及所述所有MO之间的父子关系和引用关系。
步骤302，基于网管系统的物理设备模型文件解析站点的物理设备模型，获得站点的物理设备信息。
站点的物理设备信息包括站点中所有的物理设备、物理设备的层次和每层物理设备的MO实例。
步骤303，基于用户选定的目标物理设备、站点数据信息和站点的物理设备信息确定目标物理设备的MO实例、目标物理设备下可替换的物理设备的MO实例以及与物理设备的业务相关的MO实例。
在本实施例中，步骤301至步骤303与上述实施例中步骤101至步骤103相同，在此不再赘述。
步骤304，对目标物理设备下可替换的物理设备进行合法性验证。
在一些实施例中，依次验证目标物理设备下多层物理设备的类型、业务类型和实例数目，以确定目标物理设备的合法性。
网管系统按照用户的选择，获取每个层次的目标物理设备MO实例。合法性的校验可以从站点的站型开始，校验过程包括：校验站点中每个机柜的类型是否为可创建的机柜类型，校验机柜的业务类型(如主柜、副柜或辅柜)是否同替换前的机柜的业务类型相同；以及校验站点支持的机柜实例数目是否大于或等于站点配置的机柜实例的数目。例如：假设站点存在两台副柜，若更新后 的站型支持能力大于或等于两台副柜，则校验通过。当机柜校验通过后，则继续校验下一层物理设备，即进行机架的校验。机架的校验内容与机柜相同，同样按照机架类型、机架的业务类型、机柜支持的机架数目进行；直至遍历至站点的最后一个层级，即单板业务MO实例。在校验单板业务MO实例时，判断单板的类型，判断单板MO实例是否为单板支持的业务MO，单板业务MO实例数目是否能够大于或等于站点对应单板的业务MO实例数目。
当目标物理设备下一个层次的物理设备未替换，则继续使用原有的物理设备。
当目标物理设备下可替换的物理设备通过验证时，执行步骤305。当目标物理设备下可替换的物理设备未通过验证时，网管系统可以指导用户更换目标物理设备。例如，网管系统可向用户推荐合适的目标物理设备。网管系统还可以指导用户改造站点的数据。
步骤305，基于目标物理设备的MO实例、目标物理设备下可替换的物理设备的MO实例，以及与物理设备的业务相关的MO实例生成站点的配置数据。
在本实施例中，步骤305与上述实施例中步骤104相同，在此不再赘述。
步骤306，利用站点的配置数据更新站点。
在步骤306中，可以逐层更新物理设备的MO实例。例如，首先更新机柜MO实例和业务MO实例，然后向下逐层更新不同层级的物理设备MO实例和业务MO实例。对于单板的业务MO，其为单板的能力描述，即：对于确定的单板，其支持的业务和MO实例的数目是确定的。因此，在替换单板后，该单板下的业务MO实例会替换站点的单板的业务MO实例。其次，查找引用这些物理设备的MO，并更新其“相关物理设备MO”属性值为新的物理设备MO实例的标识名值。最后，将变更的物理设备业务MO实例导入扩展接口，当调用该扩展接口时完成对应的物理设备业务MO实例的更新。
当替换后的物理设备业务MO实例比站点的对应的物理设备业务MO实例多时，可以创建一个业务MO实例。例如，当替换后的单板业务MO实例比站点的单板业务MO实例多时，可以创建一个单板业务MO实例。
为了理解本公开实施例提供的更新站点配置数据的方法，下面以介绍更新站点配置数据的方法。
图4为本公开实施例提供的另一种更新站点配置数据的方法的流程图。如图4所示，更新站点配置数据的方法包括：
步骤401，基于网管系统的MO模型文件解析站点数据，获得站点数据信息。
站点数据信息包括所有MO及所述所有MO之间的父子关系和引用关系。
在本实施例中，网管系统的MO模型文件是Excel格式的文件。在网管系统的MO模型文件中，行为MO及其属性名称，列为MO及其属性的描述，包括父MO名称、取值类型、取值范围、默认值、是否有关键字等信息。
当网管系统启动后，首先加载MO模型文件，然后解析用户输入的站点数据，将站点数据按照设备、传输和无线分块，并将每块的MO实例按照树状结构存储；同时，根据引用关系描述关键字查找引用物理设备MO实例，以获取引用的物理设备MO实例。其中，引用物理设备MO实例可以存储在物理、传输、无线MO实例中。
步骤402，基于网管系统的物理设备模型文件解析站点的物理设备模型，获得站点的物理设备信息。
物理设备模型文件使用Excel格式文件描述。物理设备模型文件用于描述站型、多层物理设备的层次关系以及每层物理设备对应的MO实例。
在本实施例中，基站、机柜、机架、机框、槽位、单板可以使用独立页面进行描述。在每个页面中，行为物理设备MO实例，列为物理设备的MO属性及其子设备类型，且最后一列填写该物理设备支持的子设备类型。例如，在单板页面，列包含有单板的MO属性及其业务能力属性，行为单板的MO实例及其支持的业务能力MO实例。
在网管系统启动后，加载站点的物理设备模型文件并对其进行解析，获得站点下实际配置的所有物理设备MO实例，以及物理设备的层次和每层物理设备的MO实例。
在完成步骤401和402后，网管系统可以将解析获得的站点中所有MO及所有MO之间的父子关系和引用关系，所有物理设备MO实例，以及物理设备的层次和每层物理设备的MO实例呈现给用户，供用户选择可替换的物理设备MO实例。
步骤403，基于用户选定的目标物理设备、站点数据信息和站点的物理设备信息确定目标物理设备的MO实例、目标物理设备下可替换的物理设备的MO实例以及与物理设备的业务相关的MO实例。
网管系统按照树状结构将站点中每层物理设备及对应的MO实例呈现给用户。例如，在用户界面，以树状结构中不同层次的树节点表示不同层次的物理设备，用户点击树节点时，会以表格形式呈现每个树节点对应的物理设备的MO实例。根据每层物理设备所支持的物理设备MO实例，用户可以获知可替换的物理设备类型。
在步骤403中，用户选定目标物理设备后，在目标物理设备对应的树节点可以获知可替换的物理设备类型，以及该目标物理设备下可替换的物理设备MO实例。
在步骤403中，网管系统还可以根据物理设备的相关属性，获得引用该物理设备的MO实例。
步骤404，对目标物理设备下可替换的物理设备进行合法性验证。
网管系统基于用户选择的目标物理设备，整合替换后的站点的物理设备层次，获得每一层的物理设备类型和MO实例，进行合法性校验：校验从设备根节点(站型)开始，校验其第一级子节点的类型是否为其下可创建的子设备类型；其次，校验子设备业务类型是否与替换前的原设备相同；第三，校验子设备的实例数目是否大于或等于源站点对应层次设备的实例数目；如果校验通过，则进行下一级的校验，遍历至最后一级单板业务能力MO。
例如，校验站点中多个机柜的类型是否为可创建的机柜类型，校验机柜的业务类型(如主柜、副柜或辅柜)是否同替换前的机柜的业务类型相同；以及校验站点支持的机柜实例数目是否大于或等于站点配置的机柜实例的数目。例如：假设站点存在两台副柜，若更新后的站型支持能力大于或等于两台副柜，则校验通过。当机柜校验通过后，则继续校验下一层物理设备，即进行机架的校验。机架的校验内容与机柜相同，同样按照机架类型、机架的业务类型、机柜支持的机架数目进行；直至遍历至站点的最后一个层级，即单板业务MO实例。
对于未通过校验的物理设备，网管系统可以给明确的提示，知道用户进行目标物理设备的更换，或者改造原站点的数据。
步骤405，基于目标物理设备的MO实例、目标物理设备下可替换的物理设备的MO实例，以及与物理设备的业务相关的MO实例生成站点的配置数据。
步骤406，利用站点的配置数据更新站点。
利用配置数据更新站点的原配置数据，更新物理设备MO实例，查找物理设备的MO，更新相关属性值为新的物理设备MO实例的DN，将更新的物理设备MO实例传入扩展接口，当调用该扩展接口时，完成对应业务MO实例的更新，从而完成站点配置数据的更新。
虽然本实施例是以Ecxel格式的MO模型文件为例，介绍了站点的配置数据的生成和更新，但本公开并不局限于此。其它格式的MO模型文件同样可以按照本实施例提供的方法对站点配置数据进行更新，而且能获得相同的技术效果。
本公开实施例提供的更新站点配置数据的方法，网管系统的MO模型文件 解析站点数据，获得站点中多个MO之间的父子关系和引用关系；基于网管系统的物理设备模型文件解析站点的物理设备模型，获得所述站点的物理设备信息；基于用户选定的目标物理设备和所述站点的物理设备信息确定所述目标物理设备下可替换的物理设备的MO实例；基于所述目标物理设备的MO实例、所述目标物理设备下可替换的物理设备的MO实例，以及与所述物理设备的业务相关的MO实例生成所述站点的配置数据；利用所述站点的配置数据更新所述站点，使得用户在网管侧结合用户期望的目标物理设备对站点的配置数据进行更新，而且更新的配置数据既包括物理设备数据，还包括业务数据，提高了更新站点配置数据的通用性，从而提升了用户体验。另外，本实施例提供的更新站点配置数据的方法可对多种类型、多个层次的物理设备进行替换，使用户可以灵活地选择可替换的目标物理设备，达到了使用一个系统涵盖多种类型物理设备替换的效果，而且配置效率高，不易出错。
本公开实施例提供一种更新站点配置数据的装置。图5为本公开实施例提供的一种更新站点配置数据的装置的原理图。参照图5，本公开实施例提供的更新站点配置数据的装置，包括：
第一解析模块501，配置为基于网管系统的MO模型文件解析站点数据，获得站点数据信息。其中，所述站点数据信息包括所有MO及所述所有MO之间的父子关系和引用关系。
第一解析模块501的具体实施方式与上述实施例中步骤101相同，在此不再赘述。
第二解析模块502，配置为基于网管系统的物理设备模型文件解析站点的物理设备模型，获得站点的物理设备信息。其中，站点的物理设备信息包括站点中所有的物理设备、物理设备的层次和每层物理设备的MO实例。
第二解析模块502的具体实施方式与上述实施例中步骤102相同，在此不再赘述。
物理设备确定模块503，配置为基于用户选定的目标物理设备、所述站点数据信息和所述站点的物理设备信息确定所述目标物理设备的MO实例、所述目标物理设备下可替换的物理设备的MO实例以及与所述物理设备的业务相关的MO实例。
物理设备确定模块503的具体实施方式与上述实施例中步骤103相同，在此不再赘述。
配置数据生成模块504，配置为基于目标物理设备的MO实例、目标物理设 备下可替换的物理设备的MO实例，以及与物理设备的业务相关的MO实例生成站点的配置数据。
配置数据生成模块504的具体实施方式与上述实施例中步骤104相同，在此不再赘述。
配置数据更新模块505，配置为利用站点的配置数据更新站点。
图6为本公开实施例提供的另一种更新站点配置数据的装置的原理图。参照图6，本公开实施例提供的更新站点配置数据的装置，包括：
第一解析模块601，配置为基于网管系统的MO模型文件解析站点数据，获得站点数据信息。其中，所述站点数据信息包括所有MO及所述所有MO之间的父子关系和引用关系。
第二解析模块602，配置为基于网管系统的物理设备模型文件解析站点的物理设备模型，获得站点的物理设备信息。
物理设备确定模块603，配置为基于用户选定的目标物理设备、所述站点数据信息和所述站点的物理设备信息确定所述目标物理设备的MO实例、所述目标物理设备下可替换的物理设备的MO实例以及与所述物理设备的业务相关的MO实例。
校验模块604，配置为对目标物理设备下可替换的物理设备进行合法性验证。
在一些实施例中，依次验证目标物理设备下多层物理设备的类型、业务类型和实例数目，以确定目标物理设备的合法性。
配置数据生成模块605，配置为基于目标物理设备的MO实例、目标物理设备下可替换的物理设备的MO实例，以及与物理设备的业务相关的MO实例生成站点的配置数据。
配置数据更新模块606，配置为利用站点的配置数据更新站点。
本公开实施例提供的更新站点配置数据的装置，用户可以在网管侧结合用户期望的目标物理设备对站点的配置数据进行更新，而且更新的配置数据既包括物理设备数据，还包括业务数据，提高了更新站点配置数据的通用性，从而提升了用户体验。另外，本实施例提供的更新站点配置数据的装置可对多种类型、多个层次的物理设备进行替换，使用户可以灵活地选择可替换的目标物理设备，达到了使用一个系统涵盖多种类型物理设备替换的效果，而且配置效率高，不易出错。
参照图7，本公开实施例提供一种电子设备，其包括：
一个或多个处理器701；存储器702，其上存储有一个或多个程序，当一个或多个程序被一个或多个处理器执行，使得一个或多个处理器实现上述任意一项的更新站点配置数据的方法；一个或多个I/O接口703，连接在处理器与存储器之间，配置为实现处理器与存储器的信息交互。
处理器701为具有数据处理能力的器件，其包括但不限于中央处理器(Central Processing Unit，CPU)等；存储器702为具有数据存储能力的器件，其包括但不限于随机存取存储器(Random Access Memory，RAM)，如同步动态随机存取内存(Synchronous Dynamic RAM，SDRAM)、双倍速率同步动态随机存储器(Double Data Rate SDRAM，DDR SDRAM)等、只读存储器(Read-Only Memory，ROM)、带电可擦可编程只读存储器(Electrically Erasable Programmable ROM，EEPROM)、闪存(FLASH)；I/O接口(读写接口)703连接在处理器701与存储器702间，能实现处理器701与存储器702的信息交互，其包括但不限于数据总线(Bus)等。
在一些实施例中，处理器701、存储器702和I/O接口703通过总线相互连接，进而与计算设备的其它组件连接。
本公开实施例提供一种计算机可读介质，其上存储有计算机程序，程序被处理器执行时实现上述任意一种更新站点配置数据的方法。
上文中所公开方法中的全部或一些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由多个物理组件合作执行。一些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在配置为存储信息(诸如计算机可读指令、数据结构、程序模块或其它数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其它存储器技术、光盘只读存储器(Compact Disc ROM，CD-ROM)、数字多功能盘(Digital Versatile Disc，DVD)或其它光盘存储、磁盒、磁带、磁盘存储或其它磁存储装置、或者可以配置为存储期望的信息并且可以被计算机访问的任何其它的介质。通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其它传输机制之 类的调制数据信号中的其它数据，并且可包括任何信息递送介质。

Claims (11)

  1. 一种更新站点配置数据的方法，包括：
    基于网管系统的管理对象MO模型文件解析站点数据，获得站点数据信息；其中，所述站点数据信息包括所有MO及所述所有MO之间的父子关系和引用关系；
    基于所述网管系统的物理设备模型文件解析站点的物理设备模型，获得所述站点的物理设备信息；其中，所述站点的物理设备信息包括所述站点中所有的物理设备、所述所有的物理设备的层次和每层物理设备的MO实例；
    基于用户选定的目标物理设备、所述站点数据信息和所述站点的物理设备信息确定所述目标物理设备的MO实例、所述目标物理设备所在层次下的可替换的物理设备的MO实例以及与所述可替换的物理设备的业务相关的MO实例；
    基于所述目标物理设备的MO实例、所述目标物理设备所在层次下的所述可替换的物理设备的MO实例，以及与所述可替换的物理设备的业务相关的MO实例生成所述站点的配置数据；
    利用所述站点的配置数据更新所述站点。
  2. 根据权利要求1所述的方法，其中，所述基于网管系统的MO模型文件解析站点数据，获得站点数据信息，包括：
    基于所述网管系统的MO模型文件解析所述站点数据，对所述站点进行分块，获得每个分块中的MO及获得的MO之间的父子关系；
    基于所述网管系统的MO模型文件解析所述站点数据，获得引用关系描述关键字，依据所述引用关系描述关键字获得所述所有MO引用的物理设备的MO实例。
  3. 根据权利要求1所述的方法，其中，所述基于用户选定的目标物理设备和所述站点的物理设备信息确定所述目标物理设备所在层次下的可替换的物理设备的MO实例，包括：
    基于所述用户选定的目标物理设备和所述站点的物理设备信息逐层确定所述目标物理设备所在层次下多层物理设备支持的业务类型；
    基于所述多层物理设备中每层物理设备支持的业务类型确定所述每层物理设备的类型；
    基于所述多层物理设备中每层物理设备的类型确定所述目标物理设备所在层次下的所述可替换的物理设备的MO实例。
  4. 根据权利要求1所述的方法，在所述基于所述目标物理设备的MO实例、所述目标物理设备所在层次下的可替换的物理设备的MO实例，以及与所述可 替换的物理设备的业务相关的MO实例生成所述站点的配置数据之前，还包括：
    对所述目标物理设备所在层次下的所述可替换的物理设备进行合法性验证；
    在所述可替换的物理设备不合法的情况下，提醒所述用户；
    所述基于所述目标物理设备的MO实例、所述目标物理设备所在层次下的可替换的物理设备的MO实例，以及与所述可替换的物理设备的业务相关的MO实例生成所述站点的配置数据，包括：
    在所述可替换的物理设备合法的情况下，基于所述目标物理设备的MO实例、所述目标物理设备所在层次下的所述可替换的物理设备的MO实例及与所述可替换的物理设备的业务相关的MO实例生成所述站点的配置数据。
  5. 根据权利要求4所述的方法，其中，所述对所述目标物理设备所在层次下的所述可替换的物理设备进行合法性验证，包括：
    依次验证所述目标物理设备所在层次下每层可替换的物理设备的类型、业务类型和实例数目，以确定所述目标物理设备的合法性。
  6. 根据权利要求4所述的方法，在所述在所述可替换的物理设备不合法的情况下，提醒所述用户之后，还包括：
    更换所述目标物理设备，或者，改造所述站点数据。
  7. 根据权利要求1所述的方法，其中，所述利用所述站点的配置数据更新所述站点，包括：
    基于所述站点的配置数据创建或替换所述目标物理设备的MO实例，替换所述目标物理设备所在层次下的引用物理设备的MO实例，以及更新与替换后的引用物理设备的业务相关的MO实例。
  8. 根据权利要求7所述的方法，其中，所述更新与替换后的引用物理设备的业务相关的MO实例，包括：
    更新所述替换后的引用物理设备的业务MO实例；
    获取引用所述替换后的引用物理设备的MO，将引用所述替换后的引用物理设备的MO的属性值更新为所述替换后的引用物理设备的属性值。
  9. 一种更新站点配置数据的装置，包括：
    第一解析模块，配置为基于网管系统的管理对象MO模型文件解析站点数据，获得站点数据信息；其中，所述站点数据信息包括所有MO及所述所有MO之间的父子关系和引用关系；
    第二解析模块，配置为基于所述网管系统的物理设备模型文件解析站点的 物理设备模型，获得所述站点的物理设备信息；其中，所述站点的物理设备信息包括所述站点中所有的物理设备、所述所有的物理设备的层次和每层物理设备的MO实例；
    物理设备确定模块，配置为基于用户选定的目标物理设备、所述站点数据信息和所述站点的物理设备信息确定所述目标物理设备的MO实例、所述目标物理设备所在层次下的可替换的物理设备的MO实例以及与所述可替换的物理设备的业务相关的MO实例；
    配置数据生成模块，配置为基于所述目标物理设备的MO实例、所述目标物理设备所在层次下的所述可替换的物理设备的MO实例，以及与所述可替换的物理设备的业务相关的MO实例生成所述站点的配置数据；
    配置数据更新模块，配置为利用所述站点的配置数据更新所述站点。
  10. 一种电子设备，包括：
    至少一个处理器；
    存储器，存储有至少一个程序，当所述至少一个程序被所述至少一个处理器执行，使得所述至少一个处理器实现根据权利要求1-8任一项所述的更新站点配置数据的方法；
    至少一个输入/输出I/O接口，连接在所述至少一个处理器与所述存储器之间，配置为实现所述至少一个处理器与所述存储器的信息交互。
  11. 一种计算机可读介质，存储有计算机程序，所述程序被处理器执行时实现根据权利要求1-8任一项所述的更新站点配置数据的方法。
PCT/CN2021/082728 2020-04-28 2021-03-24 更新站点配置数据的方法及装置、电子设备 WO2021218503A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/014,646 US20230276262A1 (en) 2020-04-28 2021-03-24 Method and apparatus for updating site configuration data, and electronic device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010351673.7 2020-04-28
CN202010351673.7A CN113573328A (zh) 2020-04-28 2020-04-28 更新站点配置数据的方法及装置、电子设备

Publications (1)

Publication Number Publication Date
WO2021218503A1 true WO2021218503A1 (zh) 2021-11-04

Family

ID=78158160

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/082728 WO2021218503A1 (zh) 2020-04-28 2021-03-24 更新站点配置数据的方法及装置、电子设备

Country Status (3)

Country Link
US (1) US20230276262A1 (zh)
CN (1) CN113573328A (zh)
WO (1) WO2021218503A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115243297A (zh) * 2022-09-20 2022-10-25 深圳市艾伯通信有限公司 基于tr069协议的基站开站方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102611576A (zh) * 2012-02-29 2012-07-25 大唐移动通信设备有限公司 一种生成网管配置模型文件的方法及装置
CN103139806A (zh) * 2011-11-23 2013-06-05 中兴通讯股份有限公司 网管与基站配置数据解耦的方法及基站
WO2014042567A1 (en) * 2012-09-14 2014-03-20 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement for configuring managed object model for combined cell
CN105227337A (zh) * 2014-06-23 2016-01-06 中兴通讯股份有限公司 一种多模网管配置模型升级方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103139806A (zh) * 2011-11-23 2013-06-05 中兴通讯股份有限公司 网管与基站配置数据解耦的方法及基站
CN102611576A (zh) * 2012-02-29 2012-07-25 大唐移动通信设备有限公司 一种生成网管配置模型文件的方法及装置
WO2014042567A1 (en) * 2012-09-14 2014-03-20 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement for configuring managed object model for combined cell
CN105227337A (zh) * 2014-06-23 2016-01-06 中兴通讯股份有限公司 一种多模网管配置模型升级方法及装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115243297A (zh) * 2022-09-20 2022-10-25 深圳市艾伯通信有限公司 基于tr069协议的基站开站方法及系统

Also Published As

Publication number Publication date
US20230276262A1 (en) 2023-08-31
CN113573328A (zh) 2021-10-29

Similar Documents

Publication Publication Date Title
CN110147411B (zh) 数据同步方法、装置、计算机设备及存储介质
CN110110174B (zh) 数据可视化页面的生成、监听及展示方法、浏览器及服务器
US9483260B1 (en) Documentation generation for web APIs based on byte code analysis
CN109582471A (zh) 信息处理方法、装置和系统
CN110489409B (zh) 一种动态扩展数据字段的方法及装置
CN108572819A (zh) 页面更新方法、装置、终端及计算机可读存储介质
TW201439792A (zh) 資料庫訪問系統及方法
CN104572668A (zh) 基于多个样式文件生成合并样式文件的方法和设备
CN108279882B (zh) 框架生成方法、装置、设备及计算机可读介质
WO2021218503A1 (zh) 更新站点配置数据的方法及装置、电子设备
CN107357588B (zh) 目标代码生成方法及装置
WO2023029881A1 (zh) 设备控制方法及装置
CN115878092A (zh) 一种基于微服务架构的代码生成方法、设备及介质
CN109284488A (zh) 基于本地存储修改前端表格列数据的方法、装置及介质
US9189486B2 (en) Autonomic generation of document structure in a content management system
EP2889789B1 (en) Replication description model for data distribution
CN114153910A (zh) 数据采集方法、装置及电子装置、计算机程序产品
CN111198678A (zh) 一种生成GraphQL前端操作接口的方法及装置
CN113742372A (zh) 一种边缘节点中的数据的访问方法、装置及系统
CN112491943B (zh) 数据请求方法、装置、存储介质和电子设备
CN115442201B (zh) 一种基于snmp代理动态采集ems数据的方法及设备
CN106775645A (zh) 一种页面信息配置方法和装置
CN114722784A (zh) 一种业务流转中同一表单实时同步编辑的方法
CN114138240A (zh) java对象生成方法、系统、计算机设备及可读存储介质
CN104166737B (zh) 用于数据库名称的修改方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21796009

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 17/03/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 21796009

Country of ref document: EP

Kind code of ref document: A1