WO2010078748A1 - Procédé et dispositif de synchronisation des configurations de la gestion de réseau et d’un élément de réseau - Google Patents
Procédé et dispositif de synchronisation des configurations de la gestion de réseau et d’un élément de réseau Download PDFInfo
- Publication number
- WO2010078748A1 WO2010078748A1 PCT/CN2009/072959 CN2009072959W WO2010078748A1 WO 2010078748 A1 WO2010078748 A1 WO 2010078748A1 CN 2009072959 W CN2009072959 W CN 2009072959W WO 2010078748 A1 WO2010078748 A1 WO 2010078748A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- configuration
- network element
- configuration change
- network management
- network
- Prior art date
- Legal status (The legal status 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 status listed.)
- Ceased
Links
Classifications
-
- 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/0866—Checking the configuration
- H04L41/0869—Validating the configuration within one network element
Definitions
- the present invention relates to the field of network management technologies, and in particular, to a method and apparatus for synchronizing network management and network element configuration. Background technique
- the network element deployment in the current communication network is very complicated.
- the administrators of each network element manage the network equipment through the network management system.
- the commonly used network management system uses the SNMP protocol (Simple Network Management Protocol) or the ETCO F protocol (Network Configuration Protocol). , Network Configuration Protocol) Remotely manage network devices.
- SNMP protocol Simple Network Management Protocol
- ETCO F Network Configuration Protocol
- Network Configuration Protocol Remotely manage network devices.
- the configuration of the current NMS is not exactly the same as that of the NE.
- the NMS can send the configuration to the NE.
- the U2000 can also save the configuration of the device. However, when the U2000 manages the NE, when the configuration of the NE changes in real time, the NMS that causes the configuration change will be saved. The configurations are inconsistent with the configuration of NEs.
- the NMS When the NMS wants to query the configuration of the NE, the NMS needs to send the query request to the NE immediately. After the NE processes the query request and responds to the query data, the NMS can view the NE configuration and the query time is long.
- the NMS needs to query the NE first. After the query, the device can be configured to increase network traffic.
- Some network management systems can save the configuration of the NEs or the NEs in real time. However, when the network connection is unstable, the configuration of the NMS and NEs cannot be synchronized in real time. The real-time performance is not good. Summary of the invention
- the embodiment of the present invention provides a method and an apparatus for synchronizing the configuration of the network management system and the network element.
- the technical solution is as follows:
- a method for synchronizing network management and network element configuration includes: Setting a serial number of the configuration change that can be identified by the network element and the network management unit, where the serial number is a mark indicating that the configuration of the network element is changed, and is identified by a sequence number;
- the network element When the configuration of the network element changes, the network element reports a configuration change event to the network management, where the configuration change event includes the sequence number and configuration change information;
- the network management device After receiving the configuration change event, the network management device synchronizes the configuration of the network element according to the sequence number.
- a device for synchronizing a network management system and a network element including:
- sequence number setting module configured to set, by the network element, a configuration change sequence number that can be identified by the network element and the network management, where the sequence number is a mark of a network element configuration change, and is identified by a sequence number;
- a change event reporting module configured to: when the configuration of the network element changes, the network element reports a configuration change event to the network management, where the configuration change event includes the serial number and configuration change information;
- the synchronization module is configured to synchronize the configuration of the network element according to the sequence number after the network management system receives the configuration change event.
- the network management system and the network element in the embodiment of the present invention synchronize the configuration sequence number to improve the reliability of the synchronization, and reduce the system resource overhead when the network management system and the network element synchronize.
- FIG. 1 is a flowchart of a method for configuring a synchronous network management system and a network element according to an embodiment of the present invention
- FIG. 2 is a flowchart of a method for configuring a synchronization network management system and a network element according to an embodiment of the present invention
- FIG. 3 is a schematic diagram of correspondence between a configuration change sequence number and a change configuration according to an embodiment of the present invention
- FIG. 4 is a schematic flowchart of synchronous full configuration between a network management system and a network element according to an embodiment of the present invention
- FIG. 5 is a schematic diagram of a configuration change of a first type of network element according to an embodiment of the present invention.
- FIG. 6 is a schematic diagram of a situation in which a configuration of a second type of network element changes according to an embodiment of the present invention
- FIG. 7 is a schematic diagram 1 of a configuration change sequence number queue according to an embodiment of the present invention.
- FIG. 8 is a second schematic diagram of a configuration change sequence number queue according to an embodiment of the present invention.
- FIG. 9 is a schematic diagram of a synchronization process of a network management system and a network element according to an embodiment of the present invention.
- FIG. 10 is a schematic diagram of an apparatus for configuring a synchronous network management system and a network element according to Embodiment 3 of the present invention. detailed description
- An embodiment of the present invention provides a method as shown in FIG. 1 , including the following steps:
- the configuration change sequence number that can be identified by the network element and the network management is set to the network element, where the configuration change sequence number is a mark of the network element configuration change, and is identified by a sequence number;
- the network element When the configuration of the network element changes, the network element reports a configuration change event to the network management, where the configuration change event includes a configuration change sequence number and configuration change information.
- the network management device After receiving the configuration change event, the network management device synchronizes the configuration of the network element according to the configuration change sequence number.
- the network management system and the network element in the embodiment of the present invention synchronize the configuration sequence number to improve the reliability of the synchronization, and reduce the system resource overhead when the network management system and the network element synchronize.
- Embodiment 2
- the method for synchronizing the configuration of the network management system and the network element is described in detail below with reference to the specific embodiments.
- the network environment to which the embodiment of the present invention is applied includes one or more network elements, and includes one or more network management devices.
- the network management equipment is referred to as the network management system.
- the method includes the following steps:
- the configuration change sequence number is a tag that changes the NE configuration, and is identified by the sequence number that the NMS and the NE can recognize, such as 1, 2, 3, and so on.
- each configuration change sequence number corresponds to the configuration in which the NE changes this time, as shown in Figure 3.
- Fig. 3 shows a change configuration corresponding to some configuration change serial numbers (such as configuration change numbers 101, 102, and 118), and the change configuration is directly displayed by the configuration detail text displayed on the network element device.
- Each time the network element changes its configuration it will generate a configuration change sequence number, and save the current change to generate the configuration change number and the corresponding change configuration to the configuration change event.
- the NMS obtains all configuration information of the NE and saves it to the local storage device when it is connected to the NE or disconnected for a long time.
- All configuration information of the network element acquired by the network management unit includes the latest configuration change sequence number of the network element.
- the NMS client When the NMS starts to manage the specified NEs, the NMS client obtains the initial configuration of the NEs (synchronous full configuration) through the ETCO F protocol and saves them on the local storage device, such as a disk. The NMS client can display the current status through the interface. All configurations of the lower NE.
- the configuration of the network element may change during the connection interruption. Therefore, the network management system also needs to synchronize all the configurations of the network element.
- the NMS indicates that all the configuration data of the synchronization NE is required by specifying a special synchronization sequence number, and tells the network element the address of the file server that receives the configuration data.
- the network element After receiving the full configuration request of the network management system, the network element generates a configuration file by using its own configuration data.
- the network element uploads the configuration file generated by the configuration data of the self to the file server specified by the network management.
- the network element sends a configuration synchronization response to the network management, and notifies the network management system to obtain a configuration file from the file server specified by the network management system.
- the network management device obtains the configuration of the network element from the specified file server.
- the configuration change sequence contains the configuration change sequence number of this configuration change.
- a configuration client or other network administrator modifies the configuration of the NE that is monitored by the network management system A.
- the NE sends a configuration change event to the network management system A that subscribes to the NE configuration change, as shown in Figure 5.
- the NE When the network management system A is configured to modify the configuration of the monitored NE, the NE returns the configuration change number of the current NE in the configuration response message, as shown in Figure 6.
- the configuration changes of the NEs are notified to the monitoring network management system in time, whether it is monitoring the configuration delivered by the network management system of the NE or the configuration of other network management or clients.
- the NMS After receiving the configuration change event, the NMS adds the configuration change sequence number in the configuration change event to the configuration change sequence number queue, and sets the unsynchronized state.
- the NMS saves the latest configuration change sequence number that has been synchronized. As shown in Figure 7, after the network management receives a new configuration change event, the latest configuration change sequence number 118 is added to the configuration change sequence number queue, and the latest configuration change sequence number 118 is set to the unsynchronized state.
- the NMS updates the configuration of the saved NE according to the predetermined policy and the received configuration change event, and updates the configuration change sequence number in the post-configuration change sequence queue to the synchronization state.
- the configuration change event of the NE carries the basic information of the configuration change, such as the configuration change sequence number, the configuration change time, the scope of the configuration change, the user information that causes the NE configuration change, the reason for the NE configuration change, and the configuration change list. Wait.
- the network management system receives the configuration change event of the network element, it can select how to synchronize the network element according to the predetermined policy. Configuration. For example, the NMS can update the configuration of the saved NE once the network configuration change event (including a corresponding configuration change sequence number). The NMS can also cache the configuration change event of the NE.
- the configuration change event corresponding to the configuration change sequence number of any one of the time segments is selected according to the time of the configuration change to update the saved configuration of the network element.
- the network management system After the above update (ie, synchronization), the network management system must set the synchronized configuration change sequence number in the configuration change sequence number queue to the synchronization state.
- the NMS updates the configuration of the saved NE once it receives the configuration change event of the NE.
- the NMS can choose to automatically initiate configuration synchronization every time the configuration change sequence number is received.
- the network management system can automatically synchronize the NE configuration.
- the network management client can also manually initiate configuration synchronization. This scenario is used when the network management task is busy and the real-time requirements are not high.
- the network management caches the configuration change event of the network element, after multiple configuration change sequence numbers arrive, the configuration change event corresponding to the configuration change sequence number of any one time period is selected according to the time of the configuration change to update the saved network.
- the configuration of the meta-network can update the saved network by selecting the configuration change sequence number and configuration change event (including the boundary) corresponding to the time of any two configuration changes according to the configuration change time carried in the configuration change event.
- Meta configuration For example, in Figure 8, the configuration change event with the configuration change sequence number between 119 and 127 is selected to update the saved configuration of the network element.
- the network management system may also cache the serial number configuration change event, and after the plurality of configuration change sequence numbers arrive, update the saved network element by selecting a configuration change event corresponding to one or more configuration change sequence numbers according to the configuration change information corresponding to the configuration change sequence number.
- Configuration For example, the NMS can update the saved configuration of the NE by selecting the corresponding configuration change sequence number and configuration change event based on the user information that causes the NE configuration change.
- the user information that causes the configuration change of the network element can be carried in the configuration change event and displayed directly on the network management, such as the IP address and terminal type of the terminal user.
- the network management system may update the saved configuration of the network element by selecting a corresponding configuration change sequence number and a configuration change event according to the configuration change list included in the configuration change event.
- the configuration list of configuration changes may include OSPF (Open Shortest Path First), BGP (Border Gateway Protocol), IS-IS (Intermediate System-Intermediate System), S MP, USM (User-based Security Model) features, etc.
- the NMS can determine whether to synchronize the corresponding configuration change event according to the configuration list of the configuration change. If the configuration change feature is not the feature of the network management, the NMS can not synchronize. If one or some of the NMSs are only concerned with the configuration of the NEs, the BGP, and the ISIS feature, the NMS does not synchronize their corresponding configuration change events when the USM and SMP features of the NE are changed.
- the network management system initiates a synchronization configuration request to the network element.
- the configuration change sequence number information that needs to be synchronized is carried.
- the network element After receiving the synchronization configuration request sent by the network management system, the network element sends a synchronization configuration response to the network management device, and according to the synchronization configuration Set the configuration change sequence number carried in the request, find the corresponding configuration information, and send it to the NMS.
- the NMS sets the configuration change sequence number in the configuration change sequence queue, and the configuration change sequence number carried in the synchronization configuration request is the synchronization status.
- the network management saves the configuration information of the network element updated by the network management system and the corresponding configuration change sequence number to the local storage device. In this way, when the NMS or the user queries the NE configuration, the configuration of the NE can be queried locally on the NMS, saving the query time.
- the synchronization check based on the configuration change sequence number is used to avoid the consumption of massive useless data occupying the network bandwidth.
- the latest configuration sequence number of the network element is re-read, and then the latest configuration change sequence number of the network element and the locally saved synchronized serial number are compared, if not, the same is true. Need to resynchronize the configuration.
- the NMS queries the configuration change sequence number after the NE is reset, compares the latest configuration change sequence number saved locally and the configuration change sequence number after the NE reset. If the two serial numbers are the same, then The network management also does not need to re-configure synchronization.
- the network management system and the network element in the embodiment of the present invention synchronize the configuration sequence number and the predetermined policy, thereby improving the reliability of the synchronization and reducing the system resource overhead when the network management system and the network element are synchronized.
- Embodiment 3
- An embodiment of the present invention provides a device for configuring a synchronous network management system and a network element.
- the method includes: a change sequence number setting module 101, configured to set a sequence number of a configuration change that can be identified by the network element and the network management unit.
- the configuration change sequence number is a mark indicating that the network element configuration is changed, and is identified by a sequence number;
- the change event reporting module 102 is configured to: when the configuration of the network element changes, the network element reports a configuration change event to the network management, where the configuration change event includes a configuration change sequence number and configuration change information;
- the configuration synchronization module 103 is configured to synchronize the configuration of the network element according to the configuration change sequence number after the network management system receives the configuration change event.
- the configuration synchronization module 103 specifically includes:
- the queue adding unit 1031 is configured to: after the network management receives the configuration change event, add the configuration change sequence number in the configuration change event to the configuration change sequence number queue, and set the unsynchronized state;
- the configuration synchronization unit 1032 is configured to update, by the network management, the configuration of the network element saved according to the predetermined policy and the received configuration change event, and update the configuration change sequence number in the post configuration change sequence number queue to the synchronization state.
- the configuration change event of the NE carries basic information about the configuration change, such as the configuration change sequence number, the time of the configuration change, the scope of the configuration change, the user information that causes the NE configuration change, the cause of the NE configuration change, and the configuration change characteristics. List, etc.
- the NMS receives the configuration change event of the NE, you can choose how to synchronize the NE configuration according to the predetermined policy. For example, the NMS can update the configuration of the saved NE once it receives the configuration change event of the NE.
- the NMS can also cache the configuration change event of the NE. After multiple configuration change sequence numbers arrive, the configuration changes. The information is selected by one or more configuration change events corresponding to the configuration change sequence number to update the saved configuration of the network element.
- the configuration synchronization unit 1032 can include:
- the synchronization sub-unit 1032a is configured to update the configuration of the network element stored and updated according to the configuration change event corresponding to the configuration change sequence number, and to update the configuration change sequence number in the post-configuration change queue to the synchronization state.
- the first cache synchronization sub-unit 1032b is configured to use the network management cache configuration change sequence number, and when the plurality of configuration change sequence numbers arrive, select and update the saved network according to the configuration change configuration change event corresponding to the configuration change sequence number of any one time period.
- the configuration change sequence number of any one of the above time periods in the update post configuration change queue is the synchronization state.
- the configuration synchronization unit 1032 may further include:
- the second cache synchronization subunit 1032c is configured to use the network management cache configuration change sequence number, and after the plurality of configuration change sequence numbers arrive, select the configuration change event corresponding to any one or more configuration change sequence numbers according to the configuration change information, and update the saved configuration number.
- any one or more of the above configuration change numbers in the update post configuration change queue is in a synchronized state.
- the network management system After the above update (that is, synchronization), the network management system must set the synchronized configuration change sequence number in the configuration change sequence number queue to be in the synchronization state.
- all configuration changes of the network element are sent to all the monitoring network management tubes, which occupies a large amount of system resources of the network element and the bandwidth of the network.
- the synchronization check based on the configuration change sequence number is used to avoid the use of massive garbage data to occupy the network bandwidth.
- the network management system can automatically initiate configuration synchronization every time a configuration change sequence number is received. This scenario is used when the network management requirements are high in real time, and the network management real-time automatic synchronization network element configuration is implemented; You can also manually initiate configuration synchronization. This scenario is used when the network management task is busy and the real-time requirements are not high.
- the network management system can select the configuration change sequence number and the configuration change event (including the boundary) corresponding to the time of any two configuration changes according to the configuration change time carried in the configuration change event. To update the saved configuration of the network element. For example, in FIG.
- the configuration change event with the configuration change sequence number between 119 and 127 is selected to update the saved configuration of the network element.
- the network management system may select the corresponding configuration change sequence number and the configuration change event to update the saved configuration of the network element according to the user information that causes the network element configuration change.
- the user information that causes the configuration change of the network element can be carried in the configuration change event and displayed directly on the network management, such as the IP address and terminal type of the terminal user.
- the network management can also be changed according to the configuration.
- the configuration list of the configuration changes included in the event selects the corresponding configuration change sequence number and the configuration change event to update the saved configuration of the network element.
- the list of configuration changes includes OSPF (Open Shortest Path First), BGP (Border Gateway Protocol), and IS-IS (Intermediate System-Intermediate System). , S MP USM (User-based Security Model) features, etc.
- the NMS can determine whether to synchronize the corresponding configuration change event according to the configuration list of the configuration change. If the configuration change feature is not the feature of the network management, the NMS can not synchronize. For example, the NMS only cares about the configuration of the OSPF, BGP, and ISIS features. When the USM (user management) and SNMP features of the NE are changed, the NMS does not synchronize their configuration change events.
- the NMS initiates a synchronization configuration request to the NE.
- the synchronization configuration request carry the configuration change sequence number information that needs to be synchronized.
- the network element After receiving the synchronization configuration request sent by the network management system, the network element sends a synchronization configuration response to the network management system, and finds the corresponding configuration information according to the configuration change sequence number carried in the synchronization configuration request, and sends the configuration information to the network management system.
- the NMS sets the configuration change sequence number carried in the configuration change request queue to the synchronization status.
- apparatus for configuring the synchronization network management system and the network element in the embodiment of the present invention may further include:
- the full-scale synchronization module 104 is configured to acquire all configuration information of the network element (including the latest configuration change sequence number of the network element) and save the information to the local storage device, for example, when the network management device is initially connected to the network element or disconnected for a long time. Disk.
- the apparatus for configuring the synchronization network management system and the network element in the embodiment of the present invention further includes:
- the local storage module 105 is configured to save the configuration information of the network element updated by the network management system and the corresponding configuration change sequence number to a local storage device, such as a disk.
- the device of the embodiment of the present invention if the network management is abnormally reset during the operation, after the network management reset is completed, the latest configuration sequence number of the network element is re-read, and then the latest configuration change sequence number of the network element and the locally saved synchronized sequence number are compared. If the same, you do not need to resynchronize the configuration. If the NE is reset during the running, after the NE is reset, the NMS queries the configuration change sequence number after the NE is reset, compares the latest configuration change sequence number saved locally and the configuration change sequence number after the NE reset. If the two serial numbers are the same, then The network management also does not need to re-configure synchronization. The network management system and the network element in the embodiment of the present invention synchronize the configuration sequence number and the predetermined policy, thereby improving the reliability of the synchronization and reducing the system resource overhead when the network management system and the network element are synchronized.
- Embodiments of the present invention may be implemented in software, and the corresponding software program may be stored in a readable storage medium, such as a hard disk, a cache, or an optical disk of a router.
- a readable storage medium such as a hard disk, a cache, or an optical disk of a router.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Procédé et dispositif de synchronisation des configurations de la gestion de réseau et d’un élément de réseau, le procédé comportant les étapes suivantes : on attribue à l’élément de réseau des numéros de changements de configuration reconnaissables aussi bien par l’élément de réseau que par la gestion de réseau, lesdits numéros représentant une étiquette à l’instant où la configuration de l’élément de réseau a changé, que l’on identifie par des numéros de série; l’élément de réseau rend compte d’un évènement de changement de configuration à la gestion de réseau lorsque la configuration de l’élément de réseau a changé, l’évènement de changement de configuration comprenant le numéro de changement de configuration et les informations de changement de configuration; après que la gestion de réseau a reçu l’évènement de changement de configuration, elle synchronise la configuration de l’élément de réseau en fonction du numéro de changement de configuration. Le dispositif comprend : un module de spécification des numéros de changements, un module de compte rendu d’évènements de changement et un module de synchronisation de configuration.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009100006399 | 2009-01-12 | ||
| CNA2009100006399A CN101447895A (zh) | 2009-01-12 | 2009-01-12 | 同步网管与网元的配置的方法和装置 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2010078748A1 true WO2010078748A1 (fr) | 2010-07-15 |
Family
ID=40743316
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2009/072959 Ceased WO2010078748A1 (fr) | 2009-01-12 | 2009-07-28 | Procédé et dispositif de synchronisation des configurations de la gestion de réseau et d’un élément de réseau |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101447895A (fr) |
| WO (1) | WO2010078748A1 (fr) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102447582A (zh) * | 2011-12-31 | 2012-05-09 | 中兴通讯股份有限公司 | 资源同步方法和装置 |
Families Citing this family (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101447895A (zh) * | 2009-01-12 | 2009-06-03 | 华为技术有限公司 | 同步网管与网元的配置的方法和装置 |
| CN101600176A (zh) * | 2009-06-15 | 2009-12-09 | 中兴通讯股份有限公司 | 一种用于彩信业务的综合数据网管系统、设备及方法 |
| CN101908979A (zh) * | 2010-08-19 | 2010-12-08 | 中兴通讯股份有限公司 | 一种网管管理资源的方法及装置 |
| CN102231679B (zh) * | 2011-06-29 | 2014-06-04 | 烽火通信科技股份有限公司 | 网元和网管实现配置同步的方法 |
| CN102299819B (zh) * | 2011-06-30 | 2017-12-05 | 中兴通讯股份有限公司 | 实现多网管共管网元配置数据一致性的方法、系统及装置 |
| CN102364895B (zh) * | 2011-11-01 | 2013-04-17 | 杭州依赛通信有限公司 | 一种快速同步对象的上载方法 |
| CN103874104B (zh) * | 2012-12-10 | 2017-06-30 | 北京信威通信技术股份有限公司 | 一种网管自适应兼容设备功能和版本的方法 |
| CN105144630B (zh) * | 2014-03-31 | 2019-01-11 | 华为技术有限公司 | 一种网元设备的呈现装置、方法及网元 |
| CN105516063B (zh) * | 2014-09-26 | 2019-02-12 | 成都鼎桥通信技术有限公司 | 一种异构网络中保持数据一致性的方法和用户数据中心 |
| CN104539460B (zh) * | 2015-01-07 | 2018-01-26 | 烽火通信科技股份有限公司 | 一种eml‑nml低效参数全量同步的方法 |
| CN106161063A (zh) * | 2015-04-09 | 2016-11-23 | 中兴通讯股份有限公司 | 一种业务模型变化上报方法和装置 |
| CN105357048A (zh) * | 2015-11-24 | 2016-02-24 | 上海斐讯数据通信技术有限公司 | 网络设备数据同步方法和系统 |
| CN105681105B (zh) * | 2016-03-09 | 2019-07-16 | 上海斐讯数据通信技术有限公司 | 网元配置信息同步方法和装置 |
| CN105959137B (zh) * | 2016-04-29 | 2019-05-24 | 烽火通信科技股份有限公司 | 一种pon系统中实现配置数据同步的方法及装置 |
| CN106375116B (zh) * | 2016-08-30 | 2020-05-19 | 成都广达新网科技股份有限公司 | 一种网元设备配置信息查看系统及其工作方法 |
| CN106961426B (zh) * | 2017-03-09 | 2020-04-24 | 深圳创维-Rgb电子有限公司 | 智能设备的通讯方法及装置 |
| CN108880849B (zh) * | 2017-10-12 | 2021-10-19 | 视联动力信息技术股份有限公司 | 属性信息的统计方法、装置及系统 |
| CN110661653B (zh) * | 2019-09-12 | 2022-04-15 | 烽火通信科技股份有限公司 | 一种网管与网元设备配置数据实时同步的方法和系统 |
| CN113438100B (zh) * | 2021-06-07 | 2023-07-18 | 江西山水光电科技股份有限公司 | 一种基于netconf协议的网络设备配置同步和上载方法 |
| CN119520279B (zh) * | 2023-08-23 | 2025-10-31 | 中国电信股份有限公司技术创新中心 | 信息同步方法、系统、交换设备和控制器 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6944657B1 (en) * | 1997-09-22 | 2005-09-13 | Mci Communications Corporation | Automatic network synchronization of the network configuration with the management information database |
| CN1248453C (zh) * | 2002-09-13 | 2006-03-29 | 华为技术有限公司 | 网元与电信网管系统的实时数据同步方法 |
| CN101247619A (zh) * | 2008-02-29 | 2008-08-20 | 中兴通讯股份有限公司 | 无线通信系统及其告警同步方法 |
| CN101447895A (zh) * | 2009-01-12 | 2009-06-03 | 华为技术有限公司 | 同步网管与网元的配置的方法和装置 |
-
2009
- 2009-01-12 CN CNA2009100006399A patent/CN101447895A/zh active Pending
- 2009-07-28 WO PCT/CN2009/072959 patent/WO2010078748A1/fr not_active Ceased
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6944657B1 (en) * | 1997-09-22 | 2005-09-13 | Mci Communications Corporation | Automatic network synchronization of the network configuration with the management information database |
| CN1248453C (zh) * | 2002-09-13 | 2006-03-29 | 华为技术有限公司 | 网元与电信网管系统的实时数据同步方法 |
| CN101247619A (zh) * | 2008-02-29 | 2008-08-20 | 中兴通讯股份有限公司 | 无线通信系统及其告警同步方法 |
| CN101447895A (zh) * | 2009-01-12 | 2009-06-03 | 华为技术有限公司 | 同步网管与网元的配置的方法和装置 |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102447582A (zh) * | 2011-12-31 | 2012-05-09 | 中兴通讯股份有限公司 | 资源同步方法和装置 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101447895A (zh) | 2009-06-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2010078748A1 (fr) | Procédé et dispositif de synchronisation des configurations de la gestion de réseau et d’un élément de réseau | |
| CN101627379B (zh) | 分布式网络管理系统和方法 | |
| WO2013097719A1 (fr) | Procédé et appareil pour la synchronisation de ressources | |
| CN103974140B (zh) | 一种基于tr069协议的大规模交互电视终端管理方法及系统 | |
| CN102082702A (zh) | 一种终端告警的处理方法、装置及系统 | |
| TWI740210B (zh) | 終端設備管理方法及伺服器 | |
| WO2017198003A1 (fr) | Procédé et système de traitement de service | |
| WO2012155615A1 (fr) | Procédé, système et appareil connexe de mise en œuvre d'une gestion de réseau rfid | |
| US10805195B2 (en) | Network operational flaw detection using metrics | |
| CN117827402B (zh) | 一种异地双活系统中执行定时任务的方法和装置 | |
| US20180176872A1 (en) | Metered interface | |
| CN102118274A (zh) | 一种状态监控方法、装置和系统 | |
| WO2017000589A1 (fr) | Procédé, appareil et système d'extension de capacité flexible | |
| CN105681105B (zh) | 网元配置信息同步方法和装置 | |
| CN104125079A (zh) | 一种确定双机热备份配置信息的方法及装置 | |
| CN107005434B (zh) | 一种同步虚拟网络功能vnf状态的方法、装置和设备 | |
| CN103957127B (zh) | 异构厂家传输网络接口适配方法 | |
| CN113821334A (zh) | 一种配置边缘侧设备的方法、装置及系统 | |
| CN110750369A (zh) | 一种分布式节点管理方法及系统 | |
| CN116346834A (zh) | 一种会话同步方法、装置、计算设备及计算机存储介质 | |
| JP2012164134A (ja) | 管理装置、管理方法、及びプログラム | |
| CN115883549B (zh) | 负载分担系统 | |
| WO2011079561A1 (fr) | Procédé, système et client de synchronisation de données basés sur un service de gestion de périphérique | |
| CN114048187B (zh) | 高并发轻量数据缓存组件的设计方法 | |
| EP1936865B1 (fr) | Procede, systeme et appareil de synchronisation du flux entre la couche de commande support et les appareils de la couche support |
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: 09837306 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 09837306 Country of ref document: EP Kind code of ref document: A1 |