WO2020181699A1 - 一种管控融合型电信网络管理方法及系统 - Google Patents
一种管控融合型电信网络管理方法及系统 Download PDFInfo
- Publication number
- WO2020181699A1 WO2020181699A1 PCT/CN2019/096103 CN2019096103W WO2020181699A1 WO 2020181699 A1 WO2020181699 A1 WO 2020181699A1 CN 2019096103 W CN2019096103 W CN 2019096103W WO 2020181699 A1 WO2020181699 A1 WO 2020181699A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- component
- management
- control
- service
- status
- Prior art date
Links
Images
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/04—Network management architectures or arrangements
-
- 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/04—Network management architectures or arrangements
- H04L41/052—Network management architectures or arrangements using standardised network management architectures, e.g. telecommunication management network [TMN] or unified network management architecture [UNMA]
-
- 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
Definitions
- the invention relates to the technical field of telecommunication network management, in particular to a management and control integrated telecommunication network management method and system.
- the telecommunication network management system is one of the supporting systems for the operation of modern telecommunication networks. It is a general term for the software and hardware systems and organizational systems established to maintain the normal operation and service of the telecommunication network and effectively manage it.
- telecommunications networks mainly provide voice and mobile broadband data services with a rate of not higher than 1Gbps.
- the telecommunications network management system can meet the management needs of telecommunications networks by means of static configuration and management. Therefore, standards organizations such as ISO and ITU-T have defined the five basic functions of telecommunication network management and have been widely accepted. The five functions are: fault management, configuration management, accounting management, performance management and security management. These five functions are the most basic functions of network management.
- the existing EMS/NMS function mainly realizes the above-mentioned five basic functions, which is called a managed telecommunication network management system.
- the EMS (Element Management System)/OSS (Operation Support System) system is the representative of the managed telecommunication network management system.
- SDN Software Defined Networking
- the existing EMS/OSS and SDN controllers only solve the management or control requirements, but the operation and maintenance of the telecommunications network cannot separate the management behavior from the control behavior. Therefore, the EMS/OSS and SDN controller systems built separately are very It is difficult to apply to the actual user needs of today's network operation and maintenance. At the same time, there are many existing network management components. Although some technical measures have been adopted to improve the service capability of the system, the system has become more and more complex, with numerous components, complicated manual deployment, difficult to control the running status of components, and deterioration of component service capabilities that cannot be identified and repaired until Component failures rely on manual processing.
- the purpose of the present invention is to overcome the deficiencies of the above-mentioned background technology and provide a management and control converged telecommunication network management method and system, so as to realize the automatic deployment and operation status evaluation of management components and control components.
- the present invention provides a management and control integrated telecommunication network management method, which includes the following steps:
- the state collection component starts the management component and control component managed by it according to the component metadata
- the status collection component collects the component status data of the management component and the control component, generates the component running score, and sends it to the service management component;
- the service management component evaluates the service capabilities of the management component and the control component according to the component operation score, and when receiving a service request from the user, selects the management component and control component corresponding to the service request and the component operation score meets the set value;
- the selected management components and control components respond to service requests.
- the component metadata includes the management components that the status collection component needs to perform status collection, the component name of the control component, and the startup entry function;
- the component status data includes component running status data, network status data, and sink Host status data.
- the status collection component collects component status data of the management component and the control component, generates the component running score, and sends it to the service management component, which specifically includes the following steps:
- component running status data includes the average response time of the component interface and the number of component interface abnormalities
- the network status data includes network reachability, Network jitter and network response time
- host status data includes CPU utilization, memory utilization and average disk response time
- Component operating status average response time of component interface/10 + number of abnormal component interfaces
- Network status network reachability value + network jitter variance value + network response time; the network reachability value is 10000 when the network is unreachable, and 0 when the network is reachable;
- Host status CPU utilization * 100 + memory utilization * 100 + average disk response time.
- the service management component evaluates the service capabilities of the management component and the control component according to the component operation score, which specifically includes the following steps:
- the service management component starts monitoring and waits to receive the component running scores collected by the status collection component;
- the status collection component connects to the service management component and sends the component running score collected by it;
- the service management component evaluates the service capabilities of the management component and the control component according to the component running score.
- the component that is higher than the unavailable threshold is evaluated as the unavailable component, and the component below the unavailable threshold is evaluated as the serviceable component.
- selecting the management component and control component corresponding to the service request and whose component running score meets the set value specifically includes the following steps:
- the service management component When the service management component receives the user's service request, it obtains the name of the management component and the name of the control component from the URL of the service request;
- the service management component selects the top N management services and top N control services with the lowest component running score from the component list that can provide services, and N is the set value.
- the method further includes the following steps: upon receiving a user's service request, the service management component controls the state collection component to restore the abnormal management component and control component according to the service request.
- the service management component control state collection component restores the abnormal management component and control component according to the service request, which specifically includes the following steps:
- the service management component filters out the name of the management component and the name of the control component whose component running score is higher than the abnormal threshold from the list of unavailable service components as the name of the management component and the name of the control component that need to be restored;
- the service management component notifies the status collection component of the name of the management component and the name of the control component to be restored;
- the state collection component first stops the management component and control component that need to be restored, and then restarts the corresponding management component and control component.
- the present invention also provides a management and control integrated telecommunication network management system, including:
- Status collection component used to start the management component and control component managed by it; collect component status data of the management component and control component managed by it, generate component running score, and send it to the service management component;
- Service management component It is used to evaluate the service capabilities of management components and control components based on component operation scores. When a user's service request is received, the management component and control component with the highest component operation score corresponding to the service request are selected;
- Management component used to respond to service requests and perform various management operations on the managed network
- Control component used to respond to service requests and perform various control operations on the managed network.
- the system further includes a user interaction module, which is used to provide a GUI mode human-computer interaction interface to obtain service requests from users.
- the present invention realizes automatic deployment of management components and control components, evaluation of running status, identification and recovery of service degradation, and on-demand recovery of abnormal services through status collection components and service management components, thereby improving the overall availability of the system.
- the whole process is automatically processed without manual intervention, which reduces the difficulty of system operation and maintenance.
- the present invention collects component running status, network status and host status through the status collection component, and evaluates and selects the service capabilities of the management component and the control component according to the component running score through the service management component, without intrusion or change Existing management components and control components avoid the cost caused by the transformation of existing components.
- the present invention realizes the integration of management components and control components in network management systems such as EMS/OSS and SDN controllers into a converged telecommunication network management system using the technical solution of the present invention. Make full use of existing components to avoid the redundant construction problems caused by the addition of control functions to the management EMS/OSS and the addition of management functions to the control SDN, and to reduce the cost of network management system construction.
- FIG. 1 is a schematic flowchart of a management method for a management and control converged telecommunication network according to an embodiment of the present invention
- Fig. 2 is a schematic structural diagram of a management and control converged telecommunication network management system according to an embodiment of the present invention.
- an embodiment of the present invention provides a management method for a management and control converged telecommunication network, which includes the following steps:
- S1 The state collection component starts the management component and control component managed by it according to the component metadata
- the status collection component collects component status data of the management component and the control component, generates the component running score, and sends it to the service management component;
- the service management component evaluates the service capabilities of the management component and the control component according to the component operation score, and when receiving a service request from the user, selects the management component and control component corresponding to the service request and the component operation score conforms to the set value;
- the embodiment of the present invention realizes automatic deployment of management components and control components, evaluation of operation status, identification and recovery of service degradation, and on-demand recovery of abnormal services through status collection components and service management components, thereby improving the overall availability of the system.
- the whole process is automatically processed without manual intervention, which reduces the difficulty of system operation and maintenance.
- the component metadata includes the management component that the status collection component needs to perform status collection, the component name of the control component, and the startup entry function.
- An example of this file is as follows:
- the status collection component collects component status data of the management component and the control component, generates the component running score, and sends it to the service management component, which specifically includes the following steps:
- the component status data includes component operating status data, network status data, and host status data. Collect component running status data, network status data, and host status data sent by management components and control components; the component running status data includes the average response time of the component interface and the number of component interface abnormalities; the network status data includes network reachability, Network jitter and network response time; host status data includes CPU utilization, memory utilization and average disk response time;
- the component running score is expressed as a decimal percentage system score.
- the generation rule of the component running score is as follows:
- Component running score component running status * 50% + network status * 20% + host machine status * 30%;
- Component operating status average response time of component interface/10 (in milliseconds) + number of abnormal component interfaces;
- Network status network reachability value + network jitter variance value + network response time; the network reachability value is 10000 when the network is unreachable, and 0 when the network is reachable;
- Host state CPU utilization*100+memory utilization*100+average disk response time (in milliseconds).
- the service management component evaluates the service capabilities of the management component and the control component according to the component operation score, which specifically includes the following steps:
- the service management component starts monitoring and waits to receive the running score of the collected component sent by the status collection component;
- the status collection component connects to the service management component and sends the component running score collected by it;
- the service management component evaluates the service capabilities of the management component and the control component according to the component running score.
- the component that is higher than the unavailable threshold is evaluated as the unavailable component, and the component below the unavailable threshold is evaluated as the serviceable component.
- the unavailable threshold can be configured, and the default value is 350.
- the selection of the management component and the control component corresponding to the service request and whose component running score meets the set value specifically includes the following steps:
- the service management component When the service management component receives the user's service request, it obtains the name of the management component and the name of the control component from the URL of the service request;
- the service management component selects the top N management services and the top N control services with the lowest component running score from the component list that can provide services.
- N is the set value.
- the method further includes the following steps: upon receiving a user's service request, the service management component controls the state collection component to restore the abnormal management component and control component according to the service request.
- the service management component control state collection component restores the abnormal management component and control component according to the service request, which specifically includes the following steps:
- the service management component filters out the name of the management component and the name of the control component whose component running score is higher than the abnormal threshold from the list of unavailable service components as the name of the management component and the name of the control component that need to be restored; the abnormal threshold can be configured,
- the default value is 600;
- the service management component notifies the status collection component of the name of the management component and the name of the control component to be restored;
- the state collection component first stops the management component and control component that need to be restored, and then restarts the corresponding management component and control component.
- an embodiment of the present invention also provides a management and control converged telecommunications network management system, including:
- Status collection component used to start the management component and control component managed by it; collect component status data of the management component and control component managed by it, generate component running score, and send it to the service management component; in general, each sink
- the host or virtual host
- One status collection component can collect data on the component running status, network status, and host status of multiple management components and control components.
- Service management component used to evaluate the service capabilities of management components and control components based on component operation scores. When receiving a user's service request, select the management component and control component corresponding to the service request and with the highest component operation score;
- Management component used to respond to service requests and perform various management operations on the managed network; according to actual management needs, management components can be specifically divided into performance management components, fault management components, configuration management components, accounting management components, and security management Components. At the same time, each management component can run multiple instances at the same time to improve service capabilities.
- Control component used to respond to service requests and perform various control operations on the managed network. According to actual control needs, control components can be divided into call control components, connection control components, routing control components (route calculation, topology management), topology discovery components, and message bus components. At the same time, each control component can run multiple instances at the same time to improve service capabilities.
- the forwarding plane network element refers to a network unit that forms a telecommunication network, and is used to complete data forwarding.
- the system further includes a user interaction module, which is used to provide a GUI mode human-computer interaction interface to obtain service requests from users.
- the user interaction module is APP.
- the APP can be an APP on a PC or an APP on a mobile device.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
本发明公开了一种管控融合型电信网络管理方法及系统，涉及电信网络管理技术领域。本发明通过状态采集组件根据组件元数据启动被其管理的管理组件、控制组件；状态采集组件采集管理组件、控制组件的组件状态数据，生成组件运行分数，并发送给服务管理组件；服务管理组件根据组件状态数据对管理组件、控制组件的服务能力进行评估，收到用户的服务请求时，选出与服务请求对应的且组件运行分数最高的管理组件、控制组件；被选出的管理组件、控制组件响应服务请求，实现对管理组件、控制组件的自动部署、运行状态评估、服务劣化的识别与恢复及异常服务的按需恢复，提升了系统整体的可用性。
Description
本发明涉及电信网络管理技术领域，具体是涉及一种管控融合型电信网络管理方法及系统。
电信网络管理系统是现代电信网运行的支撑系统之一，是为保持电信网络正常运行和服务，对它进行有效的管理所建立的软、硬件系统和组织体系的总称。现阶段电信网络主要提供语音及不高于1Gbps速率的移动宽带数据业务，电信网络管理系统以静态的配置与管理为手段即可满足电信网络的管理需求。因此，ISO、ITU-T等标准组织定义了电信网络管理的五大基本功能，并被广泛接受。这五大功能是：故障管理、配置管理、账务管理、性能管理和安全管理，这五大功能是网络管理最基本的功能。现有的EMS/NMS功能主要实现了上述五大基本功能，从而被称为管理型的电信网络管理系统。EMS(Element Management System，网元管理系统)/OSS(Operation Support System，运营支撑系统)系统是管理型的电信网络管理系统的代表。
随着电信网络的服务对象从人与人通信，增加了人与物、物与物的通信。5G技术关键能力比以前几代移动通信更加丰富，用户体验速率、连接数密度、端到端时延、峰值速率和移动性等都将成为5G技术的关键性能指标。面对多样化场景的极端差异化性能需求，5G很难像以往一样以某种单一技术为基础形成针对所有场景的解决方案。为了满足5G网络复杂的运维需求，业界核心的实现思路就是在 新的网络设备上分离设备的控制功能只保留其转发功能，从而需要在电信网络管理系统中实现大量的控制功能。SDN(Software Defined Networking)概念与5G技术下网络设备转发、控制分离的需求不谋而合。其拓扑发现、路由计算等控制功能能良好地支撑5G网络的控制需求。SDN控制器是控制型网络管理系统的典型代表。
现有的EMS/OSS与SDN控制器分别只解决了管理或控制需求，但是电信网络的运维无法将管理行为与控制行为割裂开来，因此分别建设的EMS/OSS与SDN控制器系统，很难适用于现今的网络运维实际用户需求。同时，现有网管组件众多，虽采取一些技术手段提高了系统的服务能力，但系统变得越发复杂，组件众多，人工部署复杂，组件运行状态难以控制，组件服务能力劣化无法识别与修复，直至组件出现故障依赖人工处理。
发明内容
本发明的目的是为了克服上述背景技术的不足，提供一种管控融合型电信网络管理方法及系统，实现对管理组件、控制组件的自动部署、运行状态评估。
本发明提供一种管控融合型电信网络管理方法，包括以下步骤：
状态采集组件根据组件元数据启动被其管理的管理组件、控制组件；
状态采集组件采集管理组件、控制组件的组件状态数据，生成组件运行分数，并发送给服务管理组件；
服务管理组件根据组件运行分数对管理组件、控制组件的服务能力进行评估，收到用户的服务请求时，选出与服务请求对应的且组件运行分数符合设定值的管理组件、控制组件；
被选出的管理组件、控制组件响应服务请求。
在上述方案的基础上，所述组件元数据包括状态采集组件需要进行状态采集的管理组件、控制组件的组件名称及启动入口函数；所述组件状态数据包括组件运行状态数据、网络状态数据和宿主机状态数据。
在上述方案的基础上，所述状态采集组件采集管理组件、控制组件的组件状态数据，生成组件运行分数，并发送给服务管理组件，具体包括以下步骤：
采集管理组件、控制组件发来的组件运行状态数据、网络状态数据及宿主机状态数据；所述组件运行状态数据包括组件接口平均响应时间和组件接口异常次数；网络状态数据包括网络可达性、网络抖动情况和网络响应时间；宿主机状态数据包括CPU利用率、内存利用率和磁盘平均响应时间；
对管理组件、控制组件运行状态、网络状态及宿主机状态进行加权求和生成组件运行分数。
在上述方案的基础上，所述组件运行分数的生成规则如下：
组件运行分数＝组件运行状态*A％+网络状态*B％+宿主机状态*C％，A+B+C＝100；
组件运行状态＝组件接口平均响应时间/10+组件接口异常次数；
网络状态＝网络可达值+网络抖动方差值+网络响应时间；其中网络可达值在网络不可达时取10000，网络可达时取0；
宿主机状态＝CPU利用率*100+内存利用率*100+磁盘平均响应时间。
在上述方案的基础上，所述服务管理组件根据组件运行分数对管理组件、控制组件的服务能力进行评估，具体包括以下步骤：
服务管理组件启动监听，等待接收状态采集组件发送的其采集的 组件运行分数；
状态采集组件连接服务管理组件，并发送其采集的组件运行分数；
服务管理组件根据组件运行分数对管理组件、控制组件的服务能力进行评估，高于不可用阀值的评估为不可提供服务的组件，低于不可用阀值的评估为可提供服务的组件。
在上述方案的基础上，所述收到用户的服务请求时，选出与服务请求对应的且组件运行分数符合设定值的管理组件、控制组件，具体包括以下步骤：
服务管理组件收到用户的服务请求时，从服务请求的URL中得到管理组件的名称、控制组件的名称；
服务管理组件根据管理组件的名称、控制组件的名称，从可提供服务的组件列表中选出的组件运行分数最低的前N位管理服务、前N位控制服务，N为设定值。
在上述方案的基础上，所述方法还包括以下步骤：收到用户的服务请求时，服务管理组件控制状态采集组件根据服务请求恢复异常的管理组件、控制组件。
在上述方案的基础上，收到用户的服务请求时，服务管理组件控制状态采集组件根据服务请求恢复异常的管理组件、控制组件，具体包括以下步骤：
服务管理组件从用户的服务请求的URL中得到的管理组件的名称、控制组件的名称；
服务管理组件从不可提供服务组件列表中筛选出组件运行分数高于异常阀值的管理组件的名称、控制组件的名称作为需要恢复的管理组件的名称、控制组件的名称；
服务管理组件向状态采集组件通知需要恢复的管理组件的名称、控制组件的名称；
状态采集组件先停止需要恢复的管理组件、控制组件，然后重新启动对应的管理组件、控制组件。
本发明还提供一种管控融合型电信网络管理系统，包括：
状态采集组件：用于启动被其管理的管理组件、控制组件；采集被其管理的管理组件、控制组件的组件状态数据，生成组件运行分数，并发送给服务管理组件；
服务管理组件：用于根据组件运行分数对管理组件、控制组件的服务能力进行评估，收到用户的服务请求时，选出与服务请求对应的且组件运行分数最高的管理组件、控制组件；
管理组件：用于响应服务请求，对被管理网络进行各项管理操作活动；
控制组件：用于响应服务请求，对被管理网络进行各项控制操作活动。
在上述方案的基础上，所述系统还包括用户交互模块，用于提供GUI方式的人机交互接口，获取用户的服务请求。
与现有技术相比，本发明的优点如下：
(1)本发明通过状态采集组件、服务管理组件，实现对管理组件、控制组件的自动部署、运行状态评估、服务劣化的识别与恢复及异常服务的按需恢复，提升了系统整体的可用性。整个过程自动处理，无需人工干预，降低系统运维难度。
(2)本发明通过状态采集组件对组件运行状态、网络状态及宿主机状态等进行采集，通过服务管理组件根据组件运行分数对管理组件、控制组件的服务能力进行评估挑选，不侵入、不改变现有管理组 件、控制组件，避免了现有组件的改造带来的成本。
(3)本发明实现将已存在EMS/OSS、SDN控制器等网络管理系统中的管理组件、控制组件，使用本发明的技术方案整合成为一个融合型的电信网络管理系统。充分利用现有的组件，避免了管理类的EMS/OSS增加控制功能，控制类的SDN增加管理功能而造成的重复建设问题，减少网络管理系统建设成本。
图1是本发明实施例的管控融合型电信网络管理方法的流程示意图；
图2是本发明实施例的管控融合型电信网络管理系统的结构示意图。
下面结合附图及具体实施例对本发明作进一步的详细描述。
参见图1所示，本发明实施例提供一种管控融合型电信网络管理方法，包括以下步骤：
S1，状态采集组件根据组件元数据启动被其管理的管理组件、控制组件；
S2，状态采集组件采集管理组件、控制组件的组件状态数据，生成组件运行分数，并发送给服务管理组件；
S3，服务管理组件根据组件运行分数对管理组件、控制组件的服务能力进行评估，收到用户的服务请求时，选出与服务请求对应且组件运行分数符合设定值的管理组件、控制组件；
S4，被选出的管理组件、控制组件响应服务请求。
本发明实施例通过状态采集组件、服务管理组件，实现对管理组 件、控制组件的自动部署、运行状态评估、服务劣化的识别与恢复及异常服务的按需恢复，提升了系统整体的可用性。整个过程自动处理，无需人工干预，降低系统运维难度。
作为优选的实施方式，所述组件元数据包括状态采集组件需要进行状态采集的管理组件、控制组件的组件名称及启动入口函数。该文件示例如下：
作为优选的实施方式，状态采集组件采集管理组件、控制组件的组件状态数据，生成组件运行分数，并发送给服务管理组件，具体包括以下步骤：
所述组件状态数据包括组件运行状态数据、网络状态数据和宿主机状态数据。采集管理组件、控制组件发来的组件运行状态数据、网络状态数据及宿主机状态数据；所述组件运行状态数据包括组件接口平均响应时间和组件接口异常次数；网络状态数据包括网络可达性、网络抖动情况和网络响应时间；宿主机状态数据包括CPU利用率、内存利用率和磁盘平均响应时间；
对管理组件、控制组件运行状态、网络状态及宿主机状态进行加权求和生成组件运行分数。组件运行分数用十进制百分制分数表示。
作为优选的实施方式，所述组件运行分数的生成规则如下：
组件运行分数＝组件运行状态*A％+网络状态*B％+宿主机状态*C％，A+B+C＝100；用户可以根据自己需要自定义A、B、C的值。 如A＝50，B＝20，C＝30，则：
组件运行分数＝组件运行状态*50％+网络状态*20％+宿主机状态*30％；
组件运行状态＝组件接口平均响应时间/10(以毫秒为单位)+组件接口异常次数；
网络状态＝网络可达值+网络抖动方差值+网络响应时间；其中网络可达值在网络不可达时取10000，网络可达时取0；
宿主机状态＝CPU利用率*100+内存利用率*100+磁盘平均响应时间(以毫秒为单位)。
作为优选的实施方式，所述服务管理组件根据组件运行分数对管理组件、控制组件的服务能力进行评估，具体包括以下步骤：
服务管理组件启动监听，等待接收状态采集组件发送的其采集的组件运行分数；
状态采集组件连接服务管理组件，并发送其采集的组件运行分数；
服务管理组件根据组件运行分数对管理组件、控制组件的服务能力进行评估，高于不可用阀值的评估为不可提供服务的组件，低于不可用阀值的评估为可提供服务的组件。不可用阀值可配置，默认值为350。
作为优选的实施方式，所述收到用户的服务请求时，选出与服务请求对应的且组件运行分数符合设定值的管理组件、控制组件，具体包括以下步骤：
服务管理组件收到用户的服务请求时，从服务请求的URL中得到管理组件的名称、控制组件的名称；
服务管理组件根据管理组件的名称、控制组件的名称，从可提供 服务的组件列表中选出的组件运行分数最低的前N位管理服务、前N位控制服务，N为设定值。
作为优选的实施方式，所述方法还包括以下步骤：收到用户的服务请求时，服务管理组件控制状态采集组件根据服务请求恢复异常的管理组件、控制组件。
作为优选的实施方式，收到用户的服务请求时，服务管理组件控制状态采集组件根据服务请求恢复异常的管理组件、控制组件，具体包括以下步骤：
服务管理组件从用户的服务请求的URL中得到的管理组件的名称、控制组件的名称；
服务管理组件从不可提供服务组件列表中筛选出组件运行分数高于异常阀值的管理组件的名称、控制组件的名称作为需要恢复的管理组件的名称、控制组件的名称；异常阀值可配置，默认值为600；
服务管理组件向状态采集组件通知需要恢复的管理组件的名称、控制组件的名称；
状态采集组件先停止需要恢复的管理组件、控制组件，然后重新启动对应的管理组件、控制组件。
参见图2所示，本发明实施例还提供一种管控融合型电信网络管理系统，包括：
状态采集组件：用于启动被其管理的管理组件、控制组件；采集被其管理的管理组件、控制组件的组件状态数据，生成组件运行分数，并发送给服务管理组件；一般情况下每个宿主机(或虚拟主机)运行一个状态采集组件。一个状态采集组件可以采集多个管理组件、控制组件的组件运行状态、网络状态及宿主机状态数据。
服务管理组件：用于根据组件运行分数对管理组件、控制组件的 服务能力进行评估，收到用户的服务请求时，选出与服务请求对应的且组件运行分数最高的管理组件、控制组件；
管理组件：用于响应服务请求，对被管理网络进行各项管理操作活动；根据实际管理需要，管理组件可以具体划分为性能管理组件、故障管理组件、配置管理组件、账务管理组件、安全管理组件。同时，每个管理组件均可以同时运行多个实例以提升服务能力。
控制组件：用于响应服务请求，对被管理网络进行各项控制操作活动。根据实际控制需要，控制组件可以划分为呼叫控制组件、连接控制组件、路由控制组件(路由计算、拓扑管理)、拓扑发现组件、消息总线组件。同时，每个控制组件均可以同时运行多个实例以提升服务能力。所述转发平面(网元)指组成电信网络的网络单元，用于完成数据的转发。
优选的，所述系统还包括用户交互模块，用于提供GUI方式的人机交互接口，获取用户的服务请求。用户交互模块为APP。其中，APP可以是PC端的APP，也可以是移动设备端APP。
本领域的技术人员可以对本发明实施例进行各种修改和变型，倘若这些修改和变型在本发明权利要求及其等同技术的范围之内，则这些修改和变型也在本发明的保护范围之内。说明书中未详细描述的内容为本领域技术人员公知的现有技术。
Claims (10)
- 一种管控融合型电信网络管理方法，其特征在于，包括以下步骤：状态采集组件根据组件元数据启动被其管理的管理组件、控制组件；状态采集组件采集管理组件、控制组件的组件状态数据，生成组件运行分数，并发送给服务管理组件；服务管理组件根据组件运行分数对管理组件、控制组件的服务能力进行评估，收到用户的服务请求时，选出与服务请求对应的且组件运行分数符合设定值的管理组件、控制组件；被选出的管理组件、控制组件响应服务请求。
- 如权利要求1所述的方法，其特征在于：所述组件元数据包括状态采集组件需要进行状态采集的管理组件、控制组件的组件名称及启动入口函数；所述组件状态数据包括组件运行状态数据、网络状态数据和宿主机状态数据。
- 如权利要求2所述的方法，其特征在于：所述状态采集组件采集管理组件、控制组件的组件状态数据，生成组件运行分数，并发送给服务管理组件，具体包括以下步骤：采集管理组件、控制组件发来的组件运行状态数据、网络状态数据及宿主机状态数据；所述组件运行状态数据包括组件接口平均响应时间和组件接口异常次数；网络状态数据包括网络可达性、网络抖动情况和网络响应时间；宿主机状态数据包括CPU利用率、内存利用率和磁盘平均响应时间；对管理组件、控制组件运行状态、网络状态及宿主机状态进行加权求和生成组件运行分数。
- 如权利要求1所述的方法，其特征在于：所述组件运行分数的生成规则如下：组件运行分数＝组件运行状态*A％+网络状态*B％+宿主机状态*C％，A+B+C＝100；组件运行状态＝组件接口平均响应时间/10+组件接口异常次数；网络状态＝网络可达值+网络抖动方差值+网络响应时间；其中网络可达值在网络不可达时取10000，网络可达时取0；宿主机状态＝CPU利用率*100+内存利用率*100+磁盘平均响应时间。
- 如权利要求1所述的方法，其特征在于：所述服务管理组件根据组件运行分数对管理组件、控制组件的服务能力进行评估，具体包括以下步骤：服务管理组件启动监听，等待接收状态采集组件发送的其采集的组件运行分数；状态采集组件连接服务管理组件，并发送其采集的组件运行分数；服务管理组件根据组件运行分数对管理组件、控制组件的服务能力进行评估，高于不可用阀值的评估为不可提供服务的组件，低于不可用阀值的评估为可提供服务的组件。
- 如权利要求1所述的方法，其特征在于：所述收到用户的服务请求时，选出与服务请求对应的且组件运行分数符合设定值的管理组件、控制组件，具体包括以下步骤：服务管理组件收到用户的服务请求时，从服务请求的URL中得到管理组件的名称、控制组件的名称；服务管理组件根据管理组件的名称、控制组件的名称，从可提供 服务的组件列表中选出的组件运行分数最低的前N位管理服务、前N位控制服务，N为设定值。
- 如权利要求1所述的方法，其特征在于：所述方法还包括以下步骤：收到用户的服务请求时，服务管理组件控制状态采集组件根据服务请求恢复异常的管理组件、控制组件。
- 如权利要求7所述的方法，其特征在于：收到用户的服务请求时，服务管理组件控制状态采集组件根据服务请求恢复异常的管理组件、控制组件，具体包括以下步骤：服务管理组件从用户的服务请求的URL中得到的管理组件的名称、控制组件的名称；服务管理组件从不可提供服务组件列表中筛选出组件运行分数高于异常阀值的管理组件的名称、控制组件的名称作为需要恢复的管理组件的名称、控制组件的名称；服务管理组件向状态采集组件通知需要恢复的管理组件的名称、控制组件的名称；状态采集组件先停止需要恢复的管理组件、控制组件，然后重新启动对应的管理组件、控制组件。
- 一种管控融合型电信网络管理系统，其特征在于，包括：状态采集组件：用于启动被其管理的管理组件、控制组件；采集被其管理的管理组件、控制组件的组件状态数据，生成组件运行分数，并发送给服务管理组件；服务管理组件：用于根据组件运行分数对管理组件、控制组件的服务能力进行评估，收到用户的服务请求时，选出与服务请求对应的且组件运行分数最高的管理组件、控制组件；管理组件：用于响应服务请求，对被管理网络进行各项管理操作 活动；控制组件：用于响应服务请求，对被管理网络进行各项控制操作活动。
- 如权利要求7所述的系统，其特征在于：所述系统还包括用户交互模块，用于提供GUI方式的人机交互接口，获取用户的服务请求。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910181504.0 | 2019-03-11 | ||
| CN201910181504.0A CN110011834B (zh) | 2019-03-11 | 2019-03-11 | 一种管控融合型电信网络管理方法及系统 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2020181699A1 true WO2020181699A1 (zh) | 2020-09-17 |
Family
ID=67166819
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2019/096103 WO2020181699A1 (zh) | 2019-03-11 | 2019-07-16 | 一种管控融合型电信网络管理方法及系统 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN110011834B (zh) |
| WO (1) | WO2020181699A1 (zh) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110011834B (zh) * | 2019-03-11 | 2020-09-22 | 烽火通信科技股份有限公司 | 一种管控融合型电信网络管理方法及系统 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103825909A (zh) * | 2014-03-18 | 2014-05-28 | 青岛大学 | 一种支持QoS的服务注册方法 |
| CN105282195A (zh) * | 2014-06-27 | 2016-01-27 | 中兴通讯股份有限公司 | 网络服务提供、策略规则评估、服务组件选择方法及装置 |
| US20160371712A1 (en) * | 2015-06-16 | 2016-12-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and Score Management Node For Supporting Service Evaluation |
| CN106802852A (zh) * | 2017-01-19 | 2017-06-06 | 郑州云海信息技术有限公司 | 一种Linux平台组件统一监控的方法 |
| CN110011834A (zh) * | 2019-03-11 | 2019-07-12 | 烽火通信科技股份有限公司 | 一种管控融合型电信网络管理方法及系统 |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20050122343A (ko) * | 2004-06-24 | 2005-12-29 | 엑서스테크놀러지 주식회사 | 네트워크 통합 관리 시스템 |
| US8560695B2 (en) * | 2008-11-25 | 2013-10-15 | Citrix Systems, Inc. | Systems and methods for health based spillover |
| CN107113190B (zh) * | 2015-04-03 | 2019-12-17 | 华为技术有限公司 | 一种网络管理系统、设备及方法 |
-
2019
- 2019-03-11 CN CN201910181504.0A patent/CN110011834B/zh active Active
- 2019-07-16 WO PCT/CN2019/096103 patent/WO2020181699A1/zh active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103825909A (zh) * | 2014-03-18 | 2014-05-28 | 青岛大学 | 一种支持QoS的服务注册方法 |
| CN105282195A (zh) * | 2014-06-27 | 2016-01-27 | 中兴通讯股份有限公司 | 网络服务提供、策略规则评估、服务组件选择方法及装置 |
| US20160371712A1 (en) * | 2015-06-16 | 2016-12-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and Score Management Node For Supporting Service Evaluation |
| CN106802852A (zh) * | 2017-01-19 | 2017-06-06 | 郑州云海信息技术有限公司 | 一种Linux平台组件统一监控的方法 |
| CN110011834A (zh) * | 2019-03-11 | 2019-07-12 | 烽火通信科技股份有限公司 | 一种管控融合型电信网络管理方法及系统 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110011834B (zh) | 2020-09-22 |
| CN110011834A (zh) | 2019-07-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3627767B1 (en) | Fault processing method and device for nodes in cluster | |
| JP6559670B2 (ja) | ネットワーク機能仮想化情報コンセントレータのための方法、システム、およびコンピュータ読取可能媒体 | |
| CN112491700B (zh) | 网络路径调整方法、系统、装置、电子设备及存储介质 | |
| US20150215228A1 (en) | Methods, systems, and computer readable media for a cloud-based virtualization orchestrator | |
| JP5743809B2 (ja) | 網管理システムおよび網管理方法 | |
| CN102457390B (zh) | 一种基于qoe的故障定位方法和系统 | |
| CN106936613B (zh) | 一种Openflow交换机快速主备切换的方法和系统 | |
| US20150295752A1 (en) | Openflow switch and failure recovery method in openflow network | |
| EP3203684B1 (en) | Method, apparatus and system for network operations, administration and maintenance | |
| WO2017124708A1 (zh) | 一种隧道流量控制方法、装置和网络管理系统 | |
| WO2020181699A1 (zh) | 一种管控融合型电信网络管理方法及系统 | |
| CN112653597B (zh) | 基于服务网格的服务熔断机制调整方法及系统 | |
| JP6746515B2 (ja) | 通信装置管理システム、及び通信装置設定方法 | |
| JP4309321B2 (ja) | ネットワークシステムの運用管理方法及びストレージ装置 | |
| US20230047971A1 (en) | Packet transmission method and communication device | |
| CN110932975B (zh) | 流表下发方法、数据转发方法、装置及电子设备 | |
| CN113055427B (zh) | 一种基于业务的服务器集群接入方法及装置 | |
| WO2016176910A1 (zh) | 处理tr-069消息的方法及装置 | |
| CN112040513A (zh) | 一种数据传输方法、数据传输装置及数据传输系统 | |
| JP4907189B2 (ja) | 監視制御方法 | |
| JP7238515B2 (ja) | ネットワーク制御装置、システム、方法、及びプログラム | |
| CN113055214B (zh) | 端口属性确定方法以及相关设备 | |
| CN109039680A (zh) | 一种切换主宽带网络网关bng和备bng的方法、系统和bng | |
| WO2022247675A1 (zh) | 设备运维方法、网络设备及存储介质 | |
| KR102157538B1 (ko) | 가상화 네트워크 장치 또는 시스템의 소프트웨어 갱신을 위한 시스템 및 그 방법 |
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: 19918762 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: 19918762 Country of ref document: EP Kind code of ref document: A1 |