WO2015070588A1 - 用于电信网管系统的性能数据采集方法及服务器 - Google Patents
用于电信网管系统的性能数据采集方法及服务器 Download PDFInfo
- Publication number
- WO2015070588A1 WO2015070588A1 PCT/CN2014/078839 CN2014078839W WO2015070588A1 WO 2015070588 A1 WO2015070588 A1 WO 2015070588A1 CN 2014078839 W CN2014078839 W CN 2014078839W WO 2015070588 A1 WO2015070588 A1 WO 2015070588A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- performance data
- performance
- data
- configuration
- configuration object
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
-
- 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
- H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
Definitions
- the present invention relates to a network management technology, and in particular, to a performance data collection method and a server for a telecommunication network management system.
- BACKGROUND Performance management is one of the five management functions provided by a telecommunication network management system for a telecommunication management network and a telecommunication service (the telecommunication network management system provides five basic functions, including configuration management, fault management, performance management, security management, and billing management). It monitors and corrects the behavior and efficiency of the network and the device under test by collecting and analyzing the operational data collected from the device under test, helping users to plan, implement and maintain, and measure the quality of service.
- the telecom network management system needs to periodically collect performance data from the managed device under test, and then store it in the background network management system database for statistical analysis.
- the network administrator will notify the front-end device to be tested in advance. Either way, the correct and complete access to the performance data of the device under test at the front desk is the basis for correctly providing the operator with the operating status of the network device.
- the data loss is often occurred in the process of sending the required performance data to the background network management system, such as: When the network management system link is disconnected, the network transmission is congested, the background network management system is faulty, or the background network management system is restarted, some performance data will be lost. If some important performance data is lost, the front desk will be greatly affected. Analysis results of equipment operation indicators.
- performance data is lost (not collected)
- the device to be tested is resent to the foreground device for additional acquisition to obtain a new one.
- Performance data repeated transmission of the acquisition request by this method is likely to cause congestion in the transmission network.
- the embodiments of the present invention provide a performance data collection method for a telecommunication network management system. In the performance data collection process, when a loss occurs in the performance data reporting process, the device does not need to be sent back to the device under test. Requests can also be regenerated for lost performance data.
- the embodiment of the invention provides a performance data collection method for a telecommunication network management system, which includes the following steps: The server receives and stores the performance data corresponding to each configuration object reported by the device under test according to the preset collection period, and stores the performance data in the performance database; and receives the performance corresponding to each configuration object reported by the device under test.
- the server analyzes whether the number of the configuration objects corresponding to the performance data is smaller than the number of the preset configuration objects; if the number of the configuration objects corresponding to the received performance data is smaller than the preset configuration object If the number is determined, the server determines the configuration object that the performance data is not collected in the current collection period, and obtains the performance data of the preset quantity collection period before the current collection period corresponding to each determined configuration object from the performance database, and determines each of the obtained acquisition periods. The performance data corresponding to the configuration object is analyzed and processed to generate new performance data of the current collection period corresponding to each determined configuration object.
- the method when receiving the performance data corresponding to each configuration object reported by the device under test, includes: analyzing, by the server, whether the number of configuration objects corresponding to the preset type of performance data in the received performance data is less than a preset The number of the configuration objects is set; if the number of the configuration objects corresponding to the performance data of the preset type in the performance data is less than the number of the preset configuration objects, the server determines that the preset is not collected in the current collection period.
- the performance data of the type of performance data is obtained from the performance database, and the performance data of the preset number of collection periods before the current collection period corresponding to each determined configuration object is obtained, and the performance data corresponding to each determined configuration object is analyzed and processed.
- the new performance data of the current collection period corresponding to each determined configuration object is generated.
- the step of performing the analysis processing on the acquired performance data corresponding to each of the determined configuration objects to generate the new performance data of the current collection period corresponding to each of the determined configuration objects comprises: corresponding to each of the obtained determined configuration objects The performance data is subjected to a weight setting; the performance data corresponding to each of the determined configuration objects is weighted according to the set weights to generate new performance data of the current collection period corresponding to each determined configuration object.
- the method further includes: storing the new performance data in the performance database.
- the method when receiving the performance data corresponding to each configuration object reported by the device under test, the method further includes: performing legality judgment on the received performance data; The result of the judgment is that the legal performance data is stored.
- the embodiment of the present invention further provides a server, where the server includes: a performance database, a performance data collection module connected to the performance database, a data verification module connected to the performance data collection module, and the data verification module.
- a data generating module the data generating module is further connected to the performance database, wherein: the performance data collecting module is configured to receive performance data corresponding to each configuration object reported by the device under test according to a preset collection period, and And storing the performance data in the performance database; the data verification module is configured to analyze the received configuration object corresponding to the performance data when receiving the performance data corresponding to each configuration object reported by the device under test Whether the number is smaller than the preset number of configuration objects; the data generation module is configured to set the number of configuration objects corresponding to the performance data received by the data verification module to be smaller than the preset configuration object Number, the configuration object that determines that the performance data is not collected in the current acquisition cycle, from The performance data of the preset number of collection periods before the current collection period corresponding to each of the determined configuration objects is obtained
- the data verification module is further configured to analyze whether the number of configuration objects corresponding to the preset type of performance data in the received performance data is smaller than a preset number of configuration objects;
- the server further determines that the number of configuration objects corresponding to the preset type of performance data in the performance data received by the data verification module is less than the number of preset configuration objects, and the server determines the current collection period.
- the configuration object of the preset type of performance data is not collected, and the performance data of the preset number of collection periods before the current collection period corresponding to each determined configuration object is obtained from the performance database, and corresponding to the obtained determined configuration objects
- the performance data is analyzed to generate new performance data for the current acquisition period corresponding to each of the determined configuration objects.
- the analyzing, by the analyzing, the performance data corresponding to the obtained specific configuration objects to generate the new performance data of the current collection period corresponding to each of the determined configuration objects includes: performing performance on each of the obtained determined configuration objects The data is subjected to weight setting; and the performance data corresponding to each determined configuration object is weighted according to the set weight to generate new performance data of the current collection period corresponding to each determined configuration object.
- the data generating module is further configured to store the new performance data in the performance database.
- the performance data collection module is further configured to perform legality judgment on the received performance data, and store the performance result as legal performance data.
- FIG. 1 is a schematic flowchart of a first embodiment of a performance data collection method for a telecommunication network management system according to an embodiment of the present invention
- FIG. 2 is a schematic diagram of a performance data collection method for a telecommunication network management system according to an embodiment of the present invention
- FIG. 3 is a schematic structural diagram of a preferred embodiment of a server according to an embodiment of the present invention.
- FIG. 1 is a schematic flowchart of a first embodiment of a method for collecting performance data of a telecommunication network management system according to an embodiment of the present invention. The method includes the following steps:
- the server receives the performance data corresponding to each configuration object reported by the device under test according to a preset collection period, and stores the performance data in the performance database.
- the preset collection period may be Hours, daily, weekly or other collection cycle.
- the performance data reported by the plurality of devices under test such as the device under test A, the device under test 8, and the The measurement device C and the like collect the performance data parameters corresponding to each configuration object of the device under test.
- the configuration object of the device A includes the port A1, the port A2, the port A3, etc., and the performance data of the port A1 may be the uplink rate or the downlink. rate.
- the device under test A reports performance data (uplink rate) of the configuration object port A1, port A2, and port A3. S11.
- the server analyzes whether the number of the configuration objects corresponding to the performance data is less than the preset number of configuration objects.
- S12 In the step S11, the configuration object corresponding to the received performance data is verified, for example, there are three configuration objects preset by the device A to be tested (that is, three configuration objects corresponding to the device A to be tested are required to be collected).
- the performance data determines whether the number of configuration objects corresponding to the performance data received from the device under test A is less than three. If the value is less than, the device under test A does not completely complete the three configuration objects that the server wishes to collect. The performance data is reported or the performance data is lost during the reporting process.
- the server determines a configuration object that does not collect the performance data in the current collection period, and obtains performance data of a preset number of collection periods before the current collection period corresponding to each determined configuration object from the performance database, and obtains each determined configuration of the obtained collection period.
- the performance data corresponding to the object is analyzed and processed to generate new performance data of the current collection period corresponding to each determined configuration object.
- the server determines that the configuration object of the performance data is not collected in the current collection period. For example, there are three configuration objects preset by the device A to be tested (for example, port A1, port A2, and port A3, respectively), but only collected in step S10.
- the server determines that the configuration object corresponding to the collected performance data is the port A1, and determines that the configuration object corresponding to the uncaptured performance data is the port A2 and the port A3, and then reacquires the configuration object port A2 in the step S12.
- performance data of the port A3, in the performance database obtain performance data of the preset number of collection periods of the configuration object port A2 and port A3 before the current collection period, and the preset number of collection periods may be set according to actual conditions, such as Set the first two acquisition cycles, the first three acquisition cycles, the first four acquisition cycles, etc., and obtain the two historical data collected by the configuration object port A2 and port A3 in the first two acquisition periods of the current acquisition cycle.
- Three historical data collected during the first three acquisition cycles of the current acquisition cycle, in the first four of the current acquisition cycle Four historical data collected acquisition cycle; these historical data analysis process to obtain the configuration object ports A2 and A3 of the new performance data ports.
- the new performance data obtained is in line with the actual collected performance data.
- the performance data collection of the telecommunication network management system when a loss occurs in the performance data reporting process, the collection request is not required to be sent back to the device under test, and the lost performance may also be performed.
- the data is regenerated and easy to implement, which greatly improves the integrity and correctness of the performance data of the network management system, and better solves the problem of loss of performance data.
- step S12 the step of analyzing the acquired performance data corresponding to each determined configuration object to generate new performance data of the current collection period corresponding to each determined configuration object includes: S13: determining each of the acquired The performance data corresponding to the configuration object is weighted; in the step S13, the obtained performance data is weighted, for example, the weight of each historical data may be sequentially incremented or decremented or randomly allocated according to the collection time.
- the historical data of the configuration object port A2 collected in step S12 is the historical data collected in the first four acquisition periods, which are: performance data S1 collected in the first acquisition period and performance data collected in the second acquisition period.
- the weights of S1, S2, S3, and S4 may be set to Q1, Q2, Q3, and P Q4, respectively, Q1 is greater than Q2, Q2 is greater than Q3, Q3 is greater than Q4, or Q1 is less than Q2, Q2 is less than Q3, Q3 is less than Q4, or Ql, Q2, Q3, and Q4 are randomly assigned.
- step S14 Perform weight calculation on the acquired performance data corresponding to each determined configuration object according to the set weights, to generate new performance data of the current collection period corresponding to each determined configuration object.
- the method further includes the following steps:
- step S11 Deposit the new performance data into the performance database. Further, when the performance data corresponding to each configuration object reported by the device under test is received in step S11, the method further includes:
- FIG. 2 is a schematic flowchart diagram of a second embodiment of a method for collecting performance data of a telecommunication network management system according to an embodiment of the present invention, where the method includes the following steps:
- the server receives the performance data corresponding to each configuration object reported by the device under test according to a preset collection period, and stores the performance data in the performance database.
- the preset collection period may be hourly, daily, weekly or other collection period.
- the performance data reported by the plurality of devices under test such as the device under test A, the device under test 8, and the device under test C, may be collected, and the performance data parameters corresponding to the configuration objects of the devices under test are collected, for example,
- the configuration object of the test device A includes the port A1, the port A2, the port A3, and the like.
- the performance data of the port A1 may be an uplink rate or a downlink rate.
- the device under test A reports performance data (uplink rate) of the configuration object port A1, port A2, and port A3.
- the server analyzes whether the number of configuration objects corresponding to the preset type of performance data in the received performance data is less than the preset number of configuration objects. If the value is less than, the step S22 is performed; in the step S21, the configuration object corresponding to the performance data of the preset type in the received performance data is verified, for example, the performance data is received from the device under test A, Then, the performance data that matches the preset type is selected from the five performance data, for example, two performance data that meet the preset type are selected, and then the number of configuration objects corresponding to the performance data that meets the preset type is analyzed is smaller than The number of preset configuration objects.
- the device A When the number of configuration objects corresponding to the performance data of the preset type is less than the number of preset configuration objects, the device A is not fully configured by the server. The performance data of the object is reported or the performance data is lost during the reporting process, such as the default configuration pair corresponding to the preset type of performance data. The number is 3, and the selected performance data type matches the predetermined configuration corresponding to only two objects.
- the server determines that the configuration object of the preset type of performance data is not collected in the current collection period, and obtains the performance data of the preset quantity collection period before the current collection period corresponding to each determined configuration object from the performance database, and obtains the acquired performance data.
- the performance data corresponding to each of the determined configuration objects is subjected to analysis processing to generate new performance data of the current collection period corresponding to each of the determined configuration objects.
- the server determines that the configuration data of the preset type of performance data is not collected in the current collection period, for example, the number of preset configuration objects corresponding to the performance data of the preset type of the device A is three (for example, port Al, port respectively) A2 and port A3), and only two selected configuration objects corresponding to the preset type of performance data, and the server determines that the configuration object corresponding to the performance data of the preset type is port A1 and port A2, and then determines that the configuration object is not collected.
- the configuration object that meets the performance data of the preset type is A3, and then in step S22, the performance data of the configuration object port A3 is re-acquired, and the preset number of the configuration object port A3 before the current collection period is obtained in the performance database.
- the performance data of the collection period, the preset number of acquisition periods can be set according to actual conditions, for example, the first two acquisition periods, the first three acquisition periods, the first four collection periods, etc., Two historical data collected by port A3 in the first two acquisition periods of the current acquisition period, in the first three collection weeks of the current collection period. Three historical data collected in the first four periods of the current acquisition acquisition acquisition cycle Four historical data, etc.; the historical data is analyzed and processed to obtain new performance data of the configuration object port A3.
- step S22 the step of analyzing the acquired performance data corresponding to each determined configuration object to generate new performance data of the current collection period corresponding to each determined configuration object includes: S23: determining each of the acquired The performance data corresponding to the configuration object is weighted; in the step S23, the obtained performance data is weighted, for example, the weight of each historical data may be sequentially incremented or decremented or randomly allocated according to the collection time.
- the historical data of the configuration object port A3 collected in step S22 is the historical data collected in the first four acquisition periods, which are: performance data S1 collected in the first acquisition period and performance data collected in the second acquisition period.
- the weights of S1, S2, S3, and S4 may be set to Q1, Q2, Q3, and P Q4, respectively, Q1 is greater than Q2, Q2 is greater than Q3, Q3 is greater than Q4, or Q1 is less than Q2, Q2 is less than Q3, Q3 is less than Q4, or Ql, Q2, Q3, and Q4 are randomly assigned.
- step S21 Store the new performance data into the performance database. Further, when the performance data corresponding to each configuration object reported by the device under test is received in step S21, the method further includes:
- the server includes: a performance database 10, a performance data collection module 20 connected to the performance database 10, and a data verification connection with the performance data collection module 20.
- the module 30 is connected to the data generation module 40, and the data generation module 40 is further connected to the performance database 10, wherein:
- the performance data collection module 20 is configured to receive performance data corresponding to each configuration object reported by the device under test according to a preset collection period, and store the performance data in the performance database;
- the data verification module 30 is set to When the performance data corresponding to each configuration object reported by the device under test is received, it is analyzed whether the number of the configuration objects corresponding to the received performance data is smaller than the preset number of configuration objects; and the data generating module 40 is configured to be in the data.
- the analysis result of the verification module is that the number of the configuration objects corresponding to the received performance data is smaller than the preset number of configuration objects, and the configuration object that the performance data is not collected in the current collection period is determined, and each determined data is obtained from the performance database.
- the performance data of the preset number of collection periods before the current collection period corresponding to the object is configured, and the obtained performance data corresponding to each determined configuration object is analyzed and processed to generate new performance data of the current collection period corresponding to each determined configuration object.
- the preset acquisition period can be hourly, daily, weekly, or other acquisition cycle.
- the performance data collection module 20 can receive the performance data reported by the plurality of devices under test, such as the device under test A, the device under test 8, and the device under test C, and collect performance parameter parameters corresponding to each configuration object of each device under test.
- the configuration object of the device A includes port A1, port A2, port A3, etc.
- the performance data of the port A1 may be an uplink rate or a downlink rate.
- the device under test A reports performance data (uplink rate) of the configuration object port A1 and port A2.
- the data verification module 30 verifies the configuration object corresponding to the received performance data by the performance data collection module 20, for example, there are three configuration objects preset by the device A to be tested (that is, three pieces of the device A to be tested are desired to be collected).
- the performance data corresponding to the configuration object is configured, it is determined whether the number of configuration objects corresponding to the performance data received from the device under test A is less than three. If the value is less than, the device under test A does not completely collect the information that the server wants to collect. The performance data of the three configuration objects is reported or the performance data is lost during the reporting process.
- the data generating module 40 determines a configuration object that does not collect performance data in the current collection period, such as the device under test.
- a preset configuration object has three (for example, port A1, port A2, and port A3 respectively), and the performance data collection module 20 only collects one performance data, and the data generation module 40 determines the configuration corresponding to the collected performance data.
- the object is the port A1, and the configuration object corresponding to the uncaptured performance data is the port A2 and the port A3, and then the performance data of the configuration object port A2 and port A3 is re-acquired by the data generating module 40, and the configuration object is obtained in the performance database.
- the preset number of acquisition periods can be set according to the actual situation. For example, the first two collection periods and the first three collection periods can be set.
- the first four acquisition cycles, etc. can obtain two historical data collected by the configuration object port A2 and port A3 in the first two acquisition periods of the current acquisition period, and three collected in the first three acquisition periods of the current collection period.
- Historical data four historical data collected during the first four acquisition cycles of the current acquisition cycle, etc.; for these histories
- the new performance data obtained is in line with the actual collected performance data.
- the data verification module 30 is further configured to analyze whether the number of configuration objects corresponding to the preset type of performance data in the received performance data is less than a preset number of configuration objects; the data generation module 40 further sets If the number of configuration objects corresponding to the preset type of performance data in the performance data received by the data verification module is less than the preset number of configuration objects, the server determines that the current collection period is not collected.
- the performance data of the type of performance data is obtained, and the performance data of the preset number of collection periods before the current collection period corresponding to each determined configuration object is obtained from the performance database, and the performance data corresponding to each determined configuration object is analyzed. Processing to generate new performance data for the current acquisition cycle corresponding to each of the determined configuration objects.
- the data verification module 30 verifies the configuration object corresponding to the preset type of performance data in the received performance data. If the performance data is received from the device under test A, the selection of the five performance data is performed. Perform performance data that meets the preset type, such as selecting two performance data that meet the preset type, and then analyzing whether the number of configuration objects corresponding to the performance data corresponding to the preset type is less than the preset number of configuration objects. When the number of configuration objects corresponding to the performance data of the preset type is less than the number of the preset configuration objects, it indicates that the device A under test does not completely report or report the performance data of the configuration object that the server wants to collect. The performance data is lost in the process.
- the number of preset configuration objects corresponding to the preset type of performance data is three, and only two selected configuration objects corresponding to the preset type of performance data are selected.
- the data generating module 40 determines that the configuration object of the preset type of performance data is not collected in the current collection period, for example, the number of preset configuration objects corresponding to the performance data of the preset type of the device A is three (for example, respectively Port A1, port A2, and port A3), and only two selected configuration objects corresponding to the preset type of performance data, and the data generating module 40 determines that the configuration object corresponding to the performance data of the preset type is port A1 and On the port A2, the configuration object that meets the preset type of performance data is A3, and then obtains the performance data of the configuration object port A3, and obtains the preset of the configuration object port A3 before the current collection period in the performance database.
- the performance data of the quantity collection period, the preset number of acquisition periods can be set according to actual conditions, for example, the first two acquisition periods, the first three acquisition periods, the first four collection periods, etc. can be obtained, respectively, and the configuration can be obtained separately.
- the data generating module 40 analyzes the acquired performance data corresponding to each of the determined configuration objects to generate new performance data of the current collection period corresponding to each of the determined configuration objects, including: corresponding to each of the acquired determined configuration objects Performance data is weighted; and Performing weight calculation on the acquired performance data corresponding to each determined configuration object according to the set weights to generate new performance data of the current collection period corresponding to each determined configuration object.
- the data generating module 40 performs weight setting on the acquired performance data, for example, the weights of the historical data may be sequentially incremented or decremented or randomly allocated according to the collection time.
- the historical data of the configuration object port A3 collected in step S22 is the historical data collected in the first four acquisition periods, which are: performance data S1 collected in the first acquisition period and performance data collected in the second acquisition period.
- S2 the performance data S3 collected in the first three acquisition periods, and the performance data S4 collected in the previous four collection periods, the weights of S1, S2, S3, and S4 may be set to Q1, Q2, Q3, and P Q4, respectively, Ql is greater than Q2, Q2 is greater than Q3, Q3 is greater than Q4, or Ql is less than Q2, Q2 is less than Q3, Q3 is less than Q4, or Ql, Q2, Q3, and Q4 are randomly assigned.
- the data generating module 40 calculates new performance data according to the searched corresponding historical data and the weight of each historical data, for example, the new performance data S0 of the configuration object port A3 is S1*Q1+S2*Q2+S3*Q3+S4*Q4. Further, the data generation module 40 is further configured to store the new performance data in a performance database. Further, the performance data collection module 20 is further configured to perform legality judgment on the received performance data, and store the performance result as legal performance data.
- the above is only a preferred embodiment of the present invention, and is not intended to limit the scope of the invention, and the equivalent structure or equivalent process transformations made by the description of the invention and the drawings may be directly or indirectly applied to other related technologies.
- the fields are all included in the scope of patent protection of the present invention.
- Industrial Applicability The embodiment of the present invention can be applied to the field of communication.
- the lost performance data can be regenerated, which is easy to implement, greatly improves the integrity and correctness of the performance data of the network management system, and better solves the problem of loss of performance data.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
一种用于电信网管系统的性能数据采集方法及服务器，其中，该方法包括：服务器按照预设的采集周期定时接收被测设备上报的各配置对象对应的性能数据，并将性能数据存入性能数据库中；分析接收的性能数据对应的配置对象的个数是否小于预设的配置对象的个数；若小于，则服务器确定当前采集周期未采集到性能数据的配置对象，从性能数据库中获取各个确定的配置对象对应的当前采集周期之前的预设数量采集周期的性能数据，并对获取的各个确定的配置对象对应的性能数据进行分析处理以生成新性能数据。该方法不需重新向被测设备发送采集请求，也可对丢失的性能数据进行重新生成，易于实施，大大提高了网管系统性能数据的完整性和正确性。
Description
用于电信网管系统的性能数据采集方法及服务器 技术领域 本发明实施例涉及一种网络管理技术， 特别涉及到一种用于电信网管系统的性能 数据采集方法及服务器。 背景技术 性能管理是电信网管系统为电信管理网及电信业务提供的五大管理功能之一 （电 信网管系统提供了五大基本功能， 包括配置管理、 故障管理、 性能管理、 安全管理、 及计费管理），主要通过收集和分析从被测设备上采集的运行数据来监视和修正网络和 被测设备的行为和效率， 帮助用户进行计划编制、 实施和维护以及业务质量测量。 电 信网管系统为了了解网络和被测设备的运行状态， 需要定时从所管理的被测设备上采 集性能数据， 然后存入后台网管系统数据库中， 供统计分析时使用。 具体的采集方式 有两种： 一种是后台网管系统定时向前台被测设备请求需要的性能数据， 一种是前台 被测设备定时向后台网管系统发送需要的性能数据 （在发送数据之前， 后台网管会将 需要的内容提前通知给前台被测设备）。不管采用哪种方式， 正确而完整的获取前台被 测设备的性能数据是正确向运营商提供网络设备运行状态的基础。 但是在现有的后台网管系统采集前台被测设备的性能数据的过程中， 或者， 前台 被测设备向后台网管系统发送需要的性能数据的过程中，经常会出现数据丢失的情况， 如： 当后台网管系统链路发生断路、 网络传输出现拥堵、 后台网管系统发生故障或者 后台网管系统重新启动时， 都会造成一些性能数据丢失， 如果一些重要的性能数据丢 失， 将会极大的影响前台被测设备运行指标的分析结果。 针对上述缺陷， 在现有技术 中， 对后台网管系统采集性能数据的过程中， 若发现有性能数据丢失（未采集到）， 则 向前台被测设备重新发送采集请求进行补充采集， 以获得新的性能数据； 采用该方法 重复发送采集请求容易造成传输网络拥堵。 发明内容 本发明实施例提供一种用于电信网管系统的性能数据采集方法， 可在性能数据采 集过程中， 当性能数据上报过程中出现丢失的情况时， 不需要重新向前台被测设备发 送采集请求， 也可对丢失的性能数据进行重新生成。 本发明实施例提供一种用于电信网管系统的性能数据采集方法， 包括以下步骤：
服务器按照预设的采集周期定时接收并存储被测设备上报的各配置对象对应的性 能数据， 并将所述性能数据存入性能数据库中； 在接收到被测设备上报的各配置对象对应的性能数据时， 服务器分析接收的所述 性能数据对应的配置对象的个数是否小于预设的配置对象的个数； 若接收的所述性能数据对应的配置对象的个数小于预设的配置对象的个数， 则服 务器确定当前采集周期未采集到性能数据的配置对象， 从性能数据库中获取各个确定 的配置对象对应的当前采集周期之前的预设数量采集周期的性能数据， 并对获取的各 个确定的配置对象对应的性能数据进行分析处理以生成各个确定的配置对象对应的当 前采集周期的新性能数据。 可选地， 在接收到被测设备上报的各配置对象对应的性能数据时， 该方法包括： 服务器分析接收的所述性能数据中预设类型的性能数据对应的配置对象的个数是 否小于预设的配置对象的个数； 若接收的所述性能数据中预设类型的性能数据对应的配置对象的个数小于预设的 配置对象的个数， 则服务器确定当前采集周期未采集到预设类型的性能数据的配置对 象， 从性能数据库中获取各个确定的配置对象对应的当前采集周期之前的预设数量采 集周期的性能数据， 并对获取的各个确定的配置对象对应的性能数据进行分析处理以 生成各个确定的配置对象对应的当前采集周期的新性能数据。 可选地， 所述对获取的各个确定的配置对象对应的性能数据进行分析处理以生成 各个确定的配置对象对应的当前采集周期的新性能数据的步骤包括： 对获取的各个确定的配置对象对应的性能数据进行权重设置； 根据设置的权重对获取的各个确定的配置对象对应的性能数据进行权重计算， 以 生成各个确定的配置对象对应的当前采集周期的新性能数据。 可选地， 所述方法还包括： 将所述新性能数据存入所述性能数据库中。 可选地，在接收到被测设备上报的各配置对象对应的性能数据时，该方法还包括: 对接收的所述性能数据进行合法性判断；
得判断结果为合法的性能数据进行存储。
本发明实施例还提供一种服务器， 所述服务器包括： 性能数据库、 与所述性能数 据库连接的性能数据采集模块、 与所述性能数据采集模块连接的数据校验模块、 与所 述数据检验模块连接的数据生成模块， 所述数据生成模块还与所述性能数据库连接， 其中： 性能数据采集模块， 设置为按照预设的采集周期定时接收被测设备上报的各配置 对象对应的性能数据， 并将所述性能数据存入所述性能数据库中； 数据校验模块， 设置为在接收到被测设备上报的各配置对象对应的性能数据时， 分析接收的所述性能数据对应的配置对象的个数是否小于预设的配置对象的个数； 数据生成模块， 设置为在所述数据校验模块的分析结果为接收的所述性能数据对 应的配置对象的个数小于预设的配置对象的个数， 确定当前采集周期未采集到性能数 据的配置对象， 从性能数据库中获取各个确定的配置对象对应的当前采集周期之前的 预设数量采集周期的性能数据， 并对获取的各个确定的配置对象对应的性能数据进行 分析处理以生成各个确定的配置对象对应的当前采集周期的新性能数据。 可选地， 所述数据校验模块还设置为分析接收的所述性能数据中预设类型的性能 数据对应的配置对象的个数是否小于预设的配置对象的个数； 所述数据生成模块还设置为在所述数据校验模块的分析结果为接收的所述性能数 据中预设类型的性能数据对应的配置对象的个数小于预设的配置对象的个数， 则服务 器确定当前采集周期未采集到预设类型的性能数据的配置对象， 从性能数据库中获取 各个确定的配置对象对应的当前采集周期之前的预设数量采集周期的性能数据， 并对 获取的各个确定的配置对象对应的性能数据进行分析处理以生成各个确定的配置对象 对应的当前采集周期的新性能数据。 可选地， 所述对获取的各个确定的配置对象对应的性能数据进行分析处理以生成 各个确定的配置对象对应的当前采集周期的新性能数据包括： 对获取的各个确定的配置对象对应的性能数据进行权重设置； 及 根据设置的权重对获取的各个确定的配置对象对应的性能数据进行权重计算， 以 生成各个确定的配置对象对应的当前采集周期的新性能数据。
可选地， 所述数据生成模块还设置为将所述新性能数据存入所述性能数据库中。 可选地，所述性能数据采集模块还设置为对接收的所述性能数据进行合法性判断， 并将判断结果为合法的性能数据进行存储。
实施本发明实施例的方案， 在对电信网管系统的性能数据采集中， 当性能数据上 报过程中出现丢失的情况时， 不需要重新向前台被测设备发送采集请求， 也可对丢失 的性能数据进行重新生成， 易于实施， 大大提高了网管系统性能数据的完整性和正确 性， 更好地解决了性能数据丢失漏报的问题。 附图说明 图 1为本发明实施例的用于电信网管系统的性能数据采集方法的第一实施例的流 程示意图； 图 2为本发明实施例的用于电信网管系统的性能数据采集方法的第二实施例的流 程示意图； 图 3为本发明实施例的服务器的优选实施例的结构示意图。
本发明实施例目的的实现、 功能特点及优点将结合实施例， 参照附图做进一步说 明。 具体实施方式 应当理解， 此处所描述的具体实施例仅仅用以解释本发明实施例， 并不用于限定 本发明实施例。 参照图 1， 图 1为本发明实施例的用于电信网管系统的性能数据采集方法的第一 实施例的流程示意图， 该方法包括以下步骤：
S10、服务器按照预设的采集周期定时接收被测设备上报的各配置对象对应的性能 数据， 并将该性能数据存入性能数据库中； 在该步骤 S10中， 该预设的采集周期可以为每小时、每天、每周或其他采集周期。 在该步骤 S10可接收多个被测设备上报的性能数据， 如被测设备 A、 被测设备8、 被
测设备 C等， 采集各被测设备的各配置对象对应的性能数据参数， 如被测设备 A的配 置对象包括端口 Al、 端口 A2、 端口 A3等， 端口 A1的性能数据可以是上行速率或下 行速率。 如， 被测设备 A上报配置对象端口 Al、 端口 A2和端口 A3的性能数据 （上 行速率）。 Sll、在接收到被测设备上报的各配置对象对应的性能数据时，服务器分析接收的 该性能数据对应的配置对象的个数是否小于预设的配置对象的个数， 若小于， 则执行 步骤 S12; 在该步骤 S11中， 对接收到的性能数据对应的配置对象进行校验， 如被测设备 A 预设的配置对象有 3个 （即希望采集被测设备 A的三个配置对象对应的性能数据）， 则判断从该被测设备 A上接收的性能数据对应的配置对象的个数是否小于 3个， 若小 于， 则说明被测设备 A并没有完全将服务器希望采集的 3个配置对象的性能数据上报 或者说在上报过程中性能数据丢失了。
S12、服务器确定当前采集周期未采集到性能数据的配置对象，从性能数据库中获 取各个确定的配置对象对应的当前采集周期之前的预设数量采集周期的性能数据， 并 对获取的各个确定的配置对象对应的性能数据进行分析处理以生成各个确定的配置对 象对应的当前采集周期的新性能数据。 服务器确定当前采集周期未采集到性能数据的配置对象， 如被测设备 A预设的配 置对象有 3个 （例如： 分别为端口 Al、 端口 A2和端口 A3 )， 而在步骤 S10中只是采 集到了一个性能数据，服务器确定该采集的性能数据对应的配置对象是端口 Al， 则确 定未采集的性能数据对应的配置对象是端口 A2和端口 A3， 然后在该步骤 S12中， 重 新获取配置对象端口 A2和端口 A3的性能数据，在性能数据库中获取该配置对象端口 A2和端口 A3在当前采集周期之前的预设数量采集周期的性能数据， 该预设数量采集 周期可根据实际情况设定， 如可设定为前两个采集周期、 前三个采集周期、 前四个采 集周期等，即可分别获得该配置对象端口 A2和端口 A3在当前采集周期的前两个采集 周期采集的两个历史数据、 在当前采集周期的前三个采集周期采集的三个历史数据、 在当前采集周期的前四个采集周期采集的四个历史数据等； 对这些历史数据进行分析 处理得到该配置对象端口 A2和端口 A3的新性能数据。该获得的新性能数据比较符合 真实采集的性能数据。 采用上述的实施例， 在对电信网管系统的性能数据采集中， 当性能数据上报过程 中出现丢失的情况时， 不需要重新向前台被测设备发送采集请求， 也可对丢失的性能
数据进行重新生成， 易于实施， 大大提高了网管系统性能数据的完整性和正确性， 更 好地解决了性能数据丢失漏报的问题。 进一步的， 在步骤 S12中， 对获取的各个确定的配置对象对应的性能数据进行分 析处理以生成各个确定的配置对象对应的当前采集周期的新性能数据的步骤包括： S13、 对获取的各个确定的配置对象对应的性能数据进行权重设置； 在该步骤 S13中， 对获取的性能数据进行权重设置， 如可按照采集时间的先后对 各历史数据的权重依次递增或递减或随机分配。 如在步骤 S12中采集的配置对象端口 A2的历史数据为前 4个采集周期采集的历史数据， 依次为： 前第一个采集周期采集的 性能数据 Sl、 前第二个采集周期采集的性能数据 S2、 前第三个采集周期采集的性能 数据 S3、 前第四个采集周期采集的性能数据 S4， 可设置 Sl、 S2、 S3和 S4的权重分 别为 Ql、 Q2、 Q3禾 P Q4， 其中， Q1大于 Q2、 Q2大于 Q3、 Q3大于 Q4， 或 Q1小于 Q2、 Q2小于 Q3、 Q3小于 Q4， 或者随机分配 Ql、 Q2、 Q3和 Q4的大小。
514、 根据设置的权重对获取的各个确定的配置对象对应的性能数据进行权重计 算， 以生成各个确定的配置对象对应的当前采集周期的新性能数据。 在该步骤 S14中， 根据查找出的对应的历史数据及各历史数据的权重计算得出新 性能数据， 如配置对象端口 A3的新性能数据 S0 = S1*Q1+ S2*Q2+ S3*Q3+ S4*Q4。 进一步的， 该方法还包括以下步骤：
515、 将该新性能数据存入到性能数据库中。 进一步的， 在步骤 S11中接收到被测设备上报的各配置对象对应的性能数据时， 该方法还包括：
516、 对接收的该性能数据进行合法性判断；
517、 将判断结果为合法的性能数据进行存储。
参照图 2， 图 2为本发明实施例的用于电信网管系统的性能数据采集方法的第二 实施例的流程示意图， 该方法包括以下步骤：
S20、服务器按照预设的采集周期定时接收被测设备上报的各配置对象对应的性能 数据， 并将该性能数据存入性能数据库中；
在该步骤 S20中， 该预设的采集周期可以为每小时、每天、每周或其他采集周期。 在该步骤 S20可接收多个被测设备上报的性能数据， 如被测设备 A、 被测设备8、 被 测设备 C等， 采集各被测设备的各配置对象对应的性能数据参数， 如被测设备 A的配 置对象包括端口 Al、 端口 A2、 端口 A3等， 端口 A1的性能数据可以是上行速率或下 行速率。 如， 被测设备 A上报配置对象端口 Al、 端口 A2和端口 A3的性能数据 （上 行速率）。
521、在接收到被测设备上报的各配置对象对应的性能数据时，服务器分析接收的 该性能数据中预设类型的性能数据对应的配置对象的个数是否小于预设的配置对象的 个数， 若小于， 则执行步骤 S22; 在该步骤 S21中， 对接收到的性能数据中预设类型的性能数据对应的配置对象进 行校验， 如从被测设备 A接收到性能数据为 5个， 则从该 5个性能数据的选出符合预 设类型的性能数据， 如选出 2个符合预设类型的性能数据， 然后分析该符合预设类型 的性能数据对应的配置对象的个数是否小于预设的配置对象的个数， 当符合预设类型 的性能数据对应的配置对象的个数小于预设的配置对象的个数时， 则说明被测设备 A 并没有完全将服务器希望采集的配置对象的性能数据上报或者说在上报过程中性能数 据丢失了， 如预设类型的性能数据对应的预设配置对象的个数为 3个， 而选出的符合 预设类型的性能数据对应的配置对象只有 2个。
522、服务器确定当前采集周期未采集到预设类型的性能数据的配置对象，从性能 数据库中获取各个确定的配置对象对应的当前采集周期之前的预设数量采集周期的性 能数据， 并对获取的各个确定的配置对象对应的性能数据进行分析处理以生成各个确 定的配置对象对应的当前采集周期的新性能数据。 服务器确定当前采集周期未采集到预设类型的性能数据的配置对象， 如被测设备 A的预设类型的性能数据对应的预设配置对象的个数为 3个（例如分别为端口 Al、端 口 A2和端口 A3 )， 而选出的符合预设类型的性能数据对应的配置对象只有 2个， 服 务器确定该符合预设类型的性能数据对应的配置对象为端口 A1和端口 A2， 则确定未 采集的符合预设类型的性能数据的配置对象为 A3，然后在该步骤 S22中，重新获取配 置对象端口 A3的性能数据，在性能数据库中获取该配置对象端口 A3在当前采集周期 之前的预设数量采集周期的性能数据， 该预设数量采集周期可根据实际情况设定， 如 可设定为前两个采集周期、 前三个采集周期、 前四个采集周期等， 即可分别获得该配 置对象端口 A3在当前采集周期的前两个采集周期采集的两个历史数据、 在当前采集 周期的前三个采集周期采集的三个历史数据、 在当前采集周期的前四个采集周期采集
的四个历史数据等； 对这些历史数据进行分析处理得到该配置对象端口 A3 的新性能 数据。 进一步的， 在步骤 S22中， 对获取的各个确定的配置对象对应的性能数据进行分 析处理以生成各个确定的配置对象对应的当前采集周期的新性能数据的步骤包括： S23、 对获取的各个确定的配置对象对应的性能数据进行权重设置； 在该步骤 S23中， 对获取的性能数据进行权重设置， 如可按照采集时间的先后对 各历史数据的权重依次递增或递减或随机分配。 如在步骤 S22中采集的配置对象端口 A3的历史数据为前 4个采集周期采集的历史数据， 依次为： 前第一个采集周期采集的 性能数据 Sl、 前第二个采集周期采集的性能数据 S2、 前第三个采集周期采集的性能 数据 S3、 前第四个采集周期采集的性能数据 S4， 可设置 Sl、 S2、 S3和 S4的权重分 别为 Ql、 Q2、 Q3禾 P Q4， 其中， Q1大于 Q2、 Q2大于 Q3、 Q3大于 Q4， 或 Q1小于 Q2、 Q2小于 Q3、 Q3小于 Q4， 或者随机分配 Ql、 Q2、 Q3和 Q4的大小。
524、 根据设置的权重对获取的各个确定的配置对象对应的性能数据进行权重计 算， 以生成各个确定的配置对象对应的当前采集周期的新性能数据。 在该步骤 S24中， 根据查找出的对应的历史数据及各历史数据的权重计算得出新 性能数据， 如配置对象端口 A3的新性能数据 S0 = S1 *Q1+ S2*Q2+ S3*Q3+ S4*Q4。 进一步的， 该方法还包括以下步骤：
525、 将该新性能数据存入到性能数据库中。 进一步的， 在步骤 S21中接收到被测设备上报的各配置对象对应的性能数据时， 该方法还包括：
526、 对接收的该性能数据进行合法性判断；
527、 将判断结果为合法的性能数据进行存储。
图 3为本发明实施例的服务器的优选实施例的结构示意图， 该服务器包括： 性能 数据库 10、 与该性能数据库 10连接的性能数据采集模块 20、 与该性能数据采集模块 20连接的数据校验模块 30、 与该数据检验模块 30连接的数据生成模块 40， 该数据生 成模块 40还与该性能数据库 10连接， 其中：
性能数据采集模块 20， 设置为按照预设的采集周期定时接收被测设备上报的各配 置对象对应的性能数据， 并将该性能数据存入该性能数据库中； 数据校验模块 30， 设置为在接收到被测设备上报的各配置对象对应的性能数据 时， 分析接收的该性能数据对应的配置对象的个数是否小于预设的配置对象的个数； 数据生成模块 40， 设置为在该数据校验模块的分析结果为接收的该性能数据对应 的配置对象的个数小于预设的配置对象的个数， 确定当前采集周期未采集到性能数据 的配置对象， 从性能数据库中获取各个确定的配置对象对应的当前采集周期之前的预 设数量采集周期的性能数据， 并对获取的各个确定的配置对象对应的性能数据进行分 析处理以生成各个确定的配置对象对应的当前采集周期的新性能数据。 该预设的采集周期可以为每小时、 每天、 每周或其他采集周期。 该性能数据采集 模块 20可接收多个被测设备上报的性能数据， 如被测设备 A、 被测设备8、 被测设备 C等， 采集各被测设备的各配置对象对应的性能数据参数， 如被测设备 A的配置对象 包括端口 Al、端口 A2、端口 A3等，端口 A1的性能数据可以是上行速率或下行速率。 如， 被测设备 A上报配置对象端口 Al、 端口 A2的性能数据 （上行速率）。 该数据校验模块 30对性能数据采集模块 20对接收到的性能数据对应的配置对象 进行校验， 如被测设备 A预设的配置对象有 3个（即希望采集被测设备 A的三个配置 对象对应的性能数据）， 则判断从该被测设备 A上接收的性能数据对应的配置对象的 个数是否小于 3个， 若小于， 则说明被测设备 A并没有完全将服务器希望采集的 3个 配置对象的性能数据上报或者说在上报过程中性能数据丢失了。 该数据生成模块 40确定当前采集周期未采集到性能数据的配置对象，如被测设备
A预设的配置对象有 3个 （例如： 分别为端口 Al、 端口 A2和端口 A3 )， 而性能数据 采集模块 20只是采集到了一个性能数据， 数据生成模块 40确定该采集的性能数据对 应的配置对象是端口 Al， 则确定未采集的性能数据对应的配置对象是端口 A2和端口 A3 , 然后通过数据生成模块 40重新获取配置对象端口 A2和端口 A3的性能数据， 在 性能数据库中获取该配置对象端口 A2和端口 A3在当前采集周期之前的预设数量采集 周期的性能数据， 该预设数量采集周期可根据实际情况设定， 如可设定为前两个采集 周期、 前三个采集周期、 前四个采集周期等， 即可分别获得该配置对象端口 A2和端 口 A3在当前采集周期的前两个采集周期采集的两个历史数据、 在当前采集周期的前 三个采集周期采集的三个历史数据、 在当前采集周期的前四个采集周期采集的四个历 史数据等；对这些历史数据进行分析处理得到该配置对象端口 A2和端口 A3的新性能 数据。 该获得的新性能数据比较符合真实采集的性能数据。
进一步的，该数据校验模块 30还设置为分析接收的该性能数据中预设类型的性能 数据对应的配置对象的个数是否小于预设的配置对象的个数； 该数据生成模块 40 还设置为在该数据校验模块的分析结果为接收的该性能数据 中预设类型的性能数据对应的配置对象的个数小于预设的配置对象的个数， 则服务器 确定当前采集周期未采集到预设类型的性能数据的配置对象， 从性能数据库中获取各 个确定的配置对象对应的当前采集周期之前的预设数量采集周期的性能数据， 并对获 取的各个确定的配置对象对应的性能数据进行分析处理以生成各个确定的配置对象对 应的当前采集周期的新性能数据。 该数据校验模块 30 对接收到的性能数据中预设类型的性能数据对应的配置对象 进行校验， 如从被测设备 A接收到性能数据为 5个， 则从该 5个性能数据的选出符合 预设类型的性能数据， 如选出 2个符合预设类型的性能数据， 然后分析该符合预设类 型的性能数据对应的配置对象的个数是否小于预设的配置对象的个数， 当符合预设类 型的性能数据对应的配置对象的个数小于预设的配置对象的个数时， 则说明被测设备 A并没有完全将服务器希望采集的配置对象的性能数据上报或者说在上报过程中性能 数据丢失了， 如预设类型的性能数据对应的预设配置对象的个数为 3个， 而选出的符 合预设类型的性能数据对应的配置对象只有 2个。 该数据生成模块 40确定当前采集周期未采集到预设类型的性能数据的配置对象， 如被测设备 A的预设类型的性能数据对应的预设配置对象的个数为 3个（例如分别为 端口 Al、 端口 A2和端口 A3 )， 而选出的符合预设类型的性能数据对应的配置对象只 有 2个， 数据生成模块 40确定该符合预设类型的性能数据对应的配置对象为端口 A1 和端口 A2， 则确定未采集的符合预设类型的性能数据的配置对象为 A3， 然后重新获 取配置对象端口 A3的性能数据，在性能数据库中获取该配置对象端口 A3在当前采集 周期之前的预设数量采集周期的性能数据，该预设数量采集周期可根据实际情况设定， 如可设定为前两个采集周期、 前三个采集周期、 前四个采集周期等， 即可分别获得该 配置对象端口 A3在当前采集周期的前两个采集周期采集的两个历史数据、 在当前采 集周期的前三个采集周期采集的三个历史数据、 在当前采集周期的前四个采集周期采 集的四个历史数据等； 对这些历史数据进行分析处理得到该配置对象端口 A3 的新性 能数据。 进一步的，数据生成模块 40对获取的各个确定的配置对象对应的性能数据进行分 析处理以生成各个确定的配置对象对应的当前采集周期的新性能数据包括： 对获取的各个确定的配置对象对应的性能数据进行权重设置； 及
根据设置的权重对获取的各个确定的配置对象对应的性能数据进行权重计算， 以 生成各个确定的配置对象对应的当前采集周期的新性能数据。 该数据生成模块 40对获取的性能数据进行权重设置，如可按照采集时间的先后对 各历史数据的权重依次递增或递减或随机分配。 如在步骤 S22中采集的配置对象端口 A3的历史数据为前 4个采集周期采集的历史数据， 依次为： 前第一个采集周期采集的 性能数据 Sl、 前第二个采集周期采集的性能数据 S2、 前第三个采集周期采集的性能 数据 S3、 前第四个采集周期采集的性能数据 S4， 可设置 Sl、 S2、 S3和 S4的权重分 别为 Ql、 Q2、 Q3禾 P Q4， 其中， Ql大于 Q2、 Q2大于 Q3、 Q3大于 Q4， 或 Ql小于 Q2、 Q2小于 Q3、 Q3小于 Q4， 或者随机分配 Ql、 Q2、 Q3和 Q4的大小。 该数据生成模块 40 根据查找出的对应的历史数据及各历史数据的权重计算得出 新性能数据， 如配置对象端口 A3的新性能数据 S0 = S1*Q1+ S2*Q2+ S3*Q3+ S4*Q4。 进一步的， 数据生成模块 40还设置为将该新性能数据存入性能数据库中。 进一步的， 性能数据采集模块 20还设置为对接收的该性能数据进行合法性判断， 并将判断结果为合法的性能数据进行存储。
以上该仅为本发明的优选实施例， 并非因此限制本发明的专利范围， 凡是利用本 发明说明书及附图内容所作的等效结构或等效流程变换， 或直接或间接运用在其他相 关的技术领域， 均同理包括在本发明的专利保护范围。 工业实用性 本发明实施例例可以应用于通信领域， 在对电信网管系统的性能数据采集中， 当 性能数据上报过程中出现丢失的情况时， 不需要重新向前台被测设备发送采集请求， 也可对丢失的性能数据进行重新生成， 易于实施， 大大提高网管系统性能数据的完整 性和正确性， 更好地解决性能数据丢失漏报的问题。
Claims
权 利 要 求 书 、 一种用于电信网管系统的性能数据采集方法， 包括： 服务器按照预设的采集周期定时接收被测设备上报的各配置对象对应的性 能数据， 并将所述性能数据存入性能数据库中；
在接收到被测设备上报的各配置对象对应的性能数据时， 服务器分析接收 的所述性能数据对应的配置对象的个数是否小于预设的配置对象的个数； 若接收的所述性能数据对应的配置对象的个数小于预设的配置对象的个 数， 则服务器确定当前采集周期未采集到性能数据的配置对象， 从性能数据库 中获取各个确定的配置对象对应的当前采集周期之前的预设数量采集周期的性 能数据， 并对获取的各个确定的配置对象对应的性能数据进行分析处理以生成 各个确定的配置对象对应的当前采集周期的新性能数据。 、 根据权利要求 1所述的方法， 设置为， 在接收到被测设备上报的各配置对象对 应的性能数据时， 包括： 服务器分析接收的所述性能数据中预设类型的性能数据对应的配置对象的 个数是否小于预设的配置对象的个数； 若接收的所述性能数据中预设类型的性能数据对应的配置对象的个数小于 预设的配置对象的个数， 则服务器确定当前采集周期未采集到预设类型的性能 数据的配置对象， 从性能数据库中获取各个确定的配置对象对应的当前采集周 期之前的预设数量采集周期的性能数据， 并对获取的各个确定的配置对象对应 的性能数据进行分析处理以生成各个确定的配置对象对应的当前采集周期的新 性能数据。 、 根据权利要求 1或 2所述的方法， 设置为， 所述对获取的各个确定的配置对象 对应的性能数据进行分析处理以生成各个确定的配置对象对应的当前采集周期 的新性能数据包括：
对获取的各个确定的配置对象对应的性能数据进行权重设置； 根据设置的权重对获取的各个确定的配置对象对应的性能数据进行权重计 算， 以生成各个确定的配置对象对应的当前采集周期的新性能数据。 、 根据权利要求 1或 2所述的方法， 设置为， 还包括：
将所述新性能数据存入所述性能数据库中。 、 根据权利要求 1或 2所述的方法， 设置为， 在接收到被测设备上报的各配置对 象对应的性能数据时， 还包括： 对接收的所述性能数据进行合法性判断； 将判断结果为合法的性能数据进行存储。 、 一种服务器， 所述服务器包括： 性能数据库、 与所述性能数据库连接的性能数 据采集模块、 与所述性能数据采集模块连接的数据校验模块、 与所述数据检验 模块连接的数据生成模块，所述数据生成模块还与所述性能数据库连接，其中： 性能数据采集模块， 设置为按照预设的采集周期定时接收被测设备上报的 各配置对象对应的性能数据， 并将所述性能数据存入所述性能数据库中；
数据校验模块， 设置为在接收到被测设备上报的各配置对象对应的性能数 据时， 分析接收的所述性能数据对应的配置对象的个数是否小于预设的配置对 象的个数；
数据生成模块， 设置为在所述数据校验模块的分析结果为接收的所述性能 数据对应的配置对象的个数小于预设的配置对象的个数， 确定当前采集周期未 采集到性能数据的配置对象， 从性能数据库中获取各个确定的配置对象对应的 当前采集周期之前的预设数量采集周期的性能数据， 并对获取的各个确定的配 置对象对应的性能数据进行分析处理以生成各个确定的配置对象对应的当前采 集周期的新性能数据。 、 根据权利要求 6所述的服务器， 设置为， 所述数据校验模块还设置为分析接收 的所述性能数据中预设类型的性能数据对应的配置对象的个数是否小于预设的 配置对象的个数； 所述数据生成模块还设置为在所述数据校验模块的分析结果为接收的所述 性能数据中预设类型的性能数据对应的配置对象的个数小于预设的配置对象的 个数， 则服务器确定当前采集周期未采集到预设类型的性能数据的配置对象， 从性能数据库中获取各个确定的配置对象对应的当前采集周期之前的预设数量 采集周期的性能数据， 并对获取的各个确定的配置对象对应的性能数据进行分 析处理以生成各个确定的配置对象对应的当前采集周期的新性能数据。
、根据权利要求 6或 7所述的服务器， 设置为， 所述对获取的各个确定的配置对象对 应的性能数据进行分析处理以生成各个确定的配置对象对应的当前采集周期的 新性能数据包括： 对获取的各个确定的配置对象对应的性能数据进行权重设置； 及 根据设置的权重对获取的各个确定的配置对象对应的性能数据进行权重计 算， 以生成各个确定的配置对象对应的当前采集周期的新性能数据。 、根据权利要求 6或 7所述的服务器， 设置为， 所述数据生成模块还设置为将所述新 性能数据存入所述性能数据库中。 0、 根据权利要求 6或 7所述的服务器， 设置为， 所述性能数据采集模块还设置为对 接收的所述性能数据进行合法性判断， 并将判断结果为合法的性能数据进行存 储。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310562128.2A CN104639353A (zh) | 2013-11-12 | 2013-11-12 | 用于电信网管系统的性能数据采集方法及服务器 |
| CN201310562128.2 | 2013-11-12 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2015070588A1 true WO2015070588A1 (zh) | 2015-05-21 |
Family
ID=53056709
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2014/078839 WO2015070588A1 (zh) | 2013-11-12 | 2014-05-29 | 用于电信网管系统的性能数据采集方法及服务器 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN104639353A (zh) |
| WO (1) | WO2015070588A1 (zh) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104965815A (zh) * | 2015-07-08 | 2015-10-07 | 北京恒华伟业科技股份有限公司 | 一种数据处理方法和装置 |
| CN108989089A (zh) * | 2018-06-22 | 2018-12-11 | 迈普通信技术股份有限公司 | 一种设备数据获取方法、设备及系统 |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1747397A (zh) * | 2004-09-08 | 2006-03-15 | 中兴通讯股份有限公司 | 一种电信网管中性能数据补采系统及其方法 |
| CN1859187A (zh) * | 2005-12-14 | 2006-11-08 | 华为技术有限公司 | 一种集中配置终端设备的方法和系统 |
| EP1806002B1 (en) * | 2004-10-28 | 2010-08-25 | Telecom Italia S.p.A. | Method for managing resources in a platform for telecommunication service and/or network management, corresponding platform and computer program product therefor |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101183993B (zh) * | 2007-12-21 | 2010-12-08 | 亿阳信通股份有限公司 | 一种网络管理系统和性能数据处理方法 |
| CN101808007B (zh) * | 2010-02-22 | 2012-02-29 | 烽火通信科技股份有限公司 | 网管实时性能数据采集的方法 |
-
2013
- 2013-11-12 CN CN201310562128.2A patent/CN104639353A/zh not_active Withdrawn
-
2014
- 2014-05-29 WO PCT/CN2014/078839 patent/WO2015070588A1/zh active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1747397A (zh) * | 2004-09-08 | 2006-03-15 | 中兴通讯股份有限公司 | 一种电信网管中性能数据补采系统及其方法 |
| EP1806002B1 (en) * | 2004-10-28 | 2010-08-25 | Telecom Italia S.p.A. | Method for managing resources in a platform for telecommunication service and/or network management, corresponding platform and computer program product therefor |
| CN1859187A (zh) * | 2005-12-14 | 2006-11-08 | 华为技术有限公司 | 一种集中配置终端设备的方法和系统 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104639353A (zh) | 2015-05-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108989136B (zh) | 业务端到端性能监控方法及装置 | |
| US8001601B2 (en) | Method and apparatus for large-scale automated distributed denial of service attack detection | |
| EP2681870B1 (en) | Technique for determining correlated events in a communication system | |
| EP2870725B1 (en) | Method and apparatus for automatically determining causes of service quality degradation | |
| US20130176858A1 (en) | Method for Determining a Severity of a Network Incident | |
| US20150181022A1 (en) | Technique for Performance Management in a Mobile Communications Network | |
| US20070168505A1 (en) | Performance monitoring in a network | |
| CN111064600B (zh) | Onu区域断电脱网监控方法及装置 | |
| US10708155B2 (en) | Systems and methods for managing network operations | |
| CN111600781A (zh) | 一种基于测试仪的防火墙系统稳定性测试方法 | |
| EP3897026A1 (en) | Network analytics | |
| CN107872503B (zh) | 一种防火墙会话数监控方法及装置 | |
| CN103957118A (zh) | 电力数据通信网网络流量实时智能分析方法及其系统 | |
| US8826296B2 (en) | Method of supervising a plurality of units in a communications network | |
| WO2011026371A1 (zh) | 历史性能数据的有效性检测方法及装置 | |
| WO2015070588A1 (zh) | 用于电信网管系统的性能数据采集方法及服务器 | |
| CN113434474B (zh) | 基于联邦学习的流量审计方法、设备、存储介质 | |
| CN109963292B (zh) | 投诉预测的方法、装置、电子设备和存储介质 | |
| CN108632104B (zh) | 一种网络质量评估工具的指标权重验证方法及装置 | |
| CN101917699B (zh) | 基于用户的随机上报信令跟踪方法和装置 | |
| CN108989137B (zh) | 端到端通信的时延测量方法及装置、计算机可读存储介质 | |
| CN114567469A (zh) | 基于b/s模式下的应用密码类型检测方法及平台 | |
| WO2012116551A1 (zh) | 一种组播性能分析方法及系统 | |
| WO2014173127A1 (zh) | 用于电力系统通讯网络的监测方法、装置及系统 | |
| RU2381550C2 (ru) | Способ мониторинга безопасности web-сервера |
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: 14861273 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: 14861273 Country of ref document: EP Kind code of ref document: A1 |