WO2017016386A1 - 一种实现射频拉远单元故障分析的方法和装置 - Google Patents

一种实现射频拉远单元故障分析的方法和装置 Download PDF

Info

Publication number
WO2017016386A1
WO2017016386A1 PCT/CN2016/089690 CN2016089690W WO2017016386A1 WO 2017016386 A1 WO2017016386 A1 WO 2017016386A1 CN 2016089690 W CN2016089690 W CN 2016089690W WO 2017016386 A1 WO2017016386 A1 WO 2017016386A1
Authority
WO
WIPO (PCT)
Prior art keywords
rru
script
fault
alarm
fault analysis
Prior art date
Application number
PCT/CN2016/089690
Other languages
English (en)
French (fr)
Inventor
李静
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017016386A1 publication Critical patent/WO2017016386A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • This document relates to, but is not limited to, the field of communication technologies, and in particular, to a method and apparatus for implementing radio remote unit (RRU) fault analysis.
  • RRU radio remote unit
  • the RRU fault analysis function is set on the alarm module of the network management system.
  • the network management system can perform RRU fault analysis based on the RRU fault information and return the fault analysis result.
  • the user can accordingly perform corresponding processing, such as returning to the factory for repair or field troubleshooting.
  • the RRU may find that the RRU is not faulty. The reason why it cannot work normally may be caused by external factors such as poor power contact at the site.
  • the RRU fault analysis function in the related art is integrated in the network management system, but is a small function in the network management system, which is very inconvenient for developers and users.
  • the network management system is mostly developed in Java language.
  • the development process is cumbersome, the development is difficult, and the source code after development is poorly readable.
  • the RRU failure analysis algorithm can only be understood by the developer in combination with the entire source code, and the user is more difficult. understanding. If the RRU model or the fault analysis algorithm is changed, the developer needs to modify, test, and patch the network management system. The whole process takes a long time.
  • the fault analysis function is only a small function in the network management system, the RRU fault analysis algorithm is often single, resulting in an inaccurate RRU fault analysis result, which affects the user to make a correct judgment on the maintenance of the RRU board.
  • Embodiments of the present invention provide a method and apparatus for implementing RRU fault analysis, which can reduce the development difficulty of RRU fault analysis.
  • the embodiment of the invention provides a method for implementing fault analysis of a radio remote unit RRU, including:
  • the fault analysis result is performed on the RRU alarm according to the obtained RRU alarm information, and the fault analysis result of the RRU alarm is obtained.
  • the RRU alarm information includes: a fault log
  • the obtaining the RRU alarm and the corresponding RRU alarm information includes:
  • the performing fault analysis includes:
  • the fault analysis is performed on the fault log according to the fault analysis algorithm, and the fault analysis result of the RRU alarm is obtained.
  • the RRU alarm information includes: a fault log and a reverse file
  • the obtaining, by using a preset script, the RRU alarm and the corresponding RRU alarm information including:
  • the RRU alarm and the corresponding RRU alarm information are respectively obtained from the network element by using the script according to the SNMP interface that establishes the connection.
  • performing the fault analysis on the RRU alarm according to the RRU alarm information by using the script including:
  • the preset script is a script built on a preset platform, and the method further includes:
  • the tool library functions include:
  • a network element connection function that establishes a connection with the network management system or the network element
  • a fault analysis algorithm corresponding to the version of the fault log and the type of the RRU is configured in advance, and the fault analysis algorithm is configured to perform fault analysis on the RRU alarm.
  • the embodiment of the present invention further provides an apparatus for implementing an RRU fault analysis, including: an obtaining module, configured to acquire an RRU alarm and a corresponding RRU alarm information by using a preset script;
  • the analysis module is configured to perform fault analysis on the RRU alarm according to the acquired RRU alarm information, and obtain a fault analysis result of the RRU alarm.
  • the RRU alarm information includes: a fault log
  • the obtaining module is configured to: connect the network management system by using the script; and send the human language MML command by using the script to obtain an RRU alarm and the corresponding RRU alarm information from the connected network management system.
  • the analysis module is configured to:
  • the RRU alarm information includes: a fault log and a reverse file
  • the obtaining module is configured to: initialize a simple network management protocol stack SNMP by using the script; and establish a reliable user data packet protocol RUDP connection with the network element by using the script according to the SNMP after initialization;
  • the SNMP interface obtains the RRU alarm and the RRU fault information from the network element by using the script.
  • the analysis module is configured to:
  • the preset script is a script built on a preset platform, and the device further includes a function library module.
  • the tool library functions include:
  • a network element connection function that establishes a connection with the network management system or the network element
  • a fault analysis algorithm corresponding to the version of the fault log and the type of the RRU is configured in advance, and the fault analysis algorithm is configured to perform fault analysis on the RRU alarm.
  • the embodiment of the invention is independent of the network management system, and implements RRU fault analysis based on a preset script. Yes, it is targeted for RRU failure analysis.
  • the scripting language has the characteristics of simplicity, easy to understand, easy to learn, etc., which makes the development process of the invention simple, readable, time-sensitive, and convenient to modify and update the execution script, and is convenient for developers and users.
  • the technical solution provided by the present invention includes: obtaining a RRU alarm and a corresponding RRU alarm information by using a preset script; performing a fault analysis on the RRU alarm according to the RRU alarm information by using a script, and obtaining a fault analysis of the RRU alarm. result.
  • the embodiment of the invention is independent of the network management system, and implements the RRU fault analysis function based on the preset script, which simplifies the development difficulty of the RRU fault analysis; in addition, the fault analysis algorithm is selected by the version of the fault log and the type of the RRU to improve the fault. The correct rate of analysis.
  • FIG. 1 is a flow chart of a method of implementing RRU failure analysis in accordance with a first embodiment of the present invention
  • FIG. 2 is a flow chart of a method of implementing RRU failure analysis in accordance with a second embodiment of the present invention
  • FIG. 3 is a flow chart of a method of implementing RRU failure analysis in accordance with a third embodiment of the present invention.
  • FIG. 4 is a flow chart showing the steps of performing fault analysis on an alarm RRU according to a fourth embodiment of the present invention.
  • FIG. 5 is a structural diagram of an apparatus for implementing RRU failure analysis according to a fifth embodiment of the present invention.
  • This embodiment provides a method for implementing RRU failure analysis. As shown in FIG. 1, it is a flowchart of a method for implementing RRU failure analysis according to a first embodiment of the present invention.
  • Step 110 Obtain an RRU alarm and a corresponding RRU alarm information by using a preset script.
  • the RRU alarm information includes: a fault log of the RRU alarm, or the RRU alarm information includes: a fault log and an anti-construction file of the RRU alarm.
  • the RRU alarm file and the fault log are obtained from the network element management system (EMS) based on the preset script; or, based on the script, the RRU alarm and the corresponding RRU are obtained from the network element.
  • the alarm information, the RRU alarm information may include: a fault log and a reverse configuration file.
  • the network element management system is simply referred to as a network management system.
  • the script can include python scripts.
  • the development and operation of this script can be done on the script tool platform.
  • the script tool platform includes: a script development platform and a script execution management platform.
  • the script development platform is a script compilation, debugging, and running environment.
  • the function library is embedded in the platform to support the operation and maintenance business of the network management system.
  • the built-in tool library functions of the platform can be used to establish a remote login (telnet) connection. And sending a Man-Machine Language (MML) command, parsing the MML message, obtaining the message data, extracting the information, performing fault analysis according to the failure analysis algorithm, and outputting the failure analysis result.
  • MML Man-Machine Language
  • the script running management platform can include a platform that runs out of script development and only manages the script project. It is for people who do not need to write scripts and rely on scripts for daily operation and maintenance.
  • the platform supports timed tasks as well as instant tasks and task sorting. And other functions.
  • the preset script is a script that is established on the preset platform, and the embodiment of the present invention further includes:
  • Tool library functions include:
  • a network element connection function that establishes a connection with the network management system or the network element
  • a fault analysis algorithm corresponding to the version of the fault log and the type of the RRU is configured in advance, and the fault analysis algorithm is configured to perform fault analysis on the RRU alarm.
  • the network element connection function, the man-machine command statement, and the message parsing function can be edited and compiled by the conventional technical means in the related art; wherein the network element connection function can include a remote login instruction; the message parsing function can be The utility model is used for parsing the fault log, the reverse file, and the like; the human machine command statement may include, for example, a function of sending a human machine command function, a human machine command result obtaining function, and the like, and the embodiment of the present invention may further include other related functions, such as a control function. For calling the phase A function or statement.
  • Step 120 Perform a fault analysis on the RRU alarm according to the obtained RRU alarm information, and obtain a fault analysis result of the RRU alarm.
  • the fault analysis results include but are not limited to one or more of the following: version fault, power fault, clock fault, equipment fault, pilot power fault, over temperature fault, downlink output underpower fault, cable fault, channel fault
  • the optical fiber is faulty, the IR interface signal strength is abnormal, the optical module is not in place, and the optical port rate is not matched.
  • the fault analysis results of this embodiment are of various types, which can meet the user troubleshooting requirements.
  • the IR interface includes an interface between the RRU and the baseband processing unit (BBU), and may be connected by using an optical fiber;
  • the maintenance methods corresponding to the failure analysis results include: manual maintenance and automatic maintenance.
  • manual maintenance requires manual intervention, operation and maintenance personnel to intervene, and corresponding maintenance work according to the failure analysis results.
  • Automatic maintenance can be automatically maintained without manual intervention, such as modifying some configuration parameters.
  • This embodiment is independent of the network management system and implements the RRU fault analysis function through a preset script, which provides convenience for the operation and maintenance personnel to perform RRU fault analysis according to the site conditions.
  • the script of this embodiment can be released and run in real time, and has high timeliness.
  • the script project of this embodiment runs on the intelligent script analysis tool, and can be implemented according to the situation on the site, and selects the near-end and far-end operation modes.
  • This embodiment utilizes the concise, easy-to-understand and easy-to-learn features of the scripting language to facilitate communication between the developer and the business personnel, and realizes "code as a document", thereby efficiently developing a script for implementing RRU failure analysis.
  • the operation and maintenance personnel can modify and run the released scripts, which is more convenient.
  • This script is very convenient to use. Users can use this script to diagnose the RRU fault at any time, clarify the current status of the RRU, and obtain the fault analysis result.
  • This embodiment describes the RRU failure analysis from the remote end.
  • FIG. 2 is a flow chart of a method for implementing RRU failure analysis in accordance with a second embodiment of the present invention.
  • This embodiment can be deployed on the client side of the network management system.
  • the RRU alarm information of this embodiment includes: a fault log.
  • step 210 the network management system (EMS) is connected through a preset script.
  • EMS network management system
  • the script runs on a script development platform.
  • the script development platform integrates tool library functions for connecting network elements, sending MML commands, and parsing MML commands; the Python language can be used to develop, debug, and run on the script development platform; the script can be posted to the EMS side and run. View the run log.
  • Step 220 Send an MML command by using a script to obtain an RRU alarm from the network management system.
  • the selected RRU alarms may be one or more. If there are multiple RRU alarms, an RRU alarm set may be formed.
  • the RRU alarm is filtered out from the alarm file.
  • the RRU alarm in the alarm file may be filtered according to the frame slot in the alarm information.
  • Step 230 Send an MML command by using a script to obtain a fault log of the RRU alarm from the network management system.
  • the RRU board works in the NE.
  • the fault log of the RRU alarm is stored in the NE.
  • the network management system After the fault log is connected to the network management system, the network management system obtains the fault log of the RRU alarm from the network management system.
  • the fault log of each RRU alarm is obtained through the script sequence, and the RRU fault analysis process is performed for each RRU alarm.
  • the script sends the MML command, so that the network management system obtains the fault log of the RRU alarm from the network element that generates the RRU alarm; the script starts the File Transfer Protocol (FTP) service, and downloads the RRU from the network management system.
  • FTP File Transfer Protocol
  • the fault log of the alarm is sent to the local.
  • the first-level network management system is an EMS
  • the second-level network management system is an OMMB (Operation & Maintenance Module Broker).
  • One EMS manages multiple OMMBs
  • one OMMB manages multiple network elements.
  • the MML command is sent to switch the connection relationship from the EMS to the OMMB where the network element in which the RRU alarm occurs, and then send an MML command to control the OMMB to obtain the fault log of the RRU alarm from the network element that generates the RRU alarm, and Uploaded to the EMS, after the connection relationship is switched back from the OMMB to the EMS, the fault log of the RRU alarm can be obtained from the EMS.
  • Step 240 Perform a fault analysis on the RRU alarm according to the fault log of the RRU alarm, and obtain a fault analysis result of the RRU alarm.
  • the RRU alarm includes the type of RRU in which the RRU alarm occurs.
  • the type of the RRU includes the type of the RRU board, for example, the types of RRUs such as R8968, R8972, R8928, and R8964.
  • the fault log of the RRU alarm contains the version of the fault log and related information about the RRU alarm.
  • the fault log is parsed by a script to obtain a version of the fault log; the type of the RRU is obtained by using a script in the RRU alarm; and the fault log is obtained by using a script in a preset multiple fault analysis algorithm.
  • the fault analysis algorithm corresponding to the version and the type of the RRU is configured to perform fault analysis on the fault log according to the acquired fault analysis algorithm to obtain a fault analysis result of the RRU alarm.
  • the fault log includes a binary file, parses the binary file, and obtains the data information therein; the data information includes: version information of the fault log, an alarm code, an alarm type, a service parameter, and the like.
  • This embodiment describes the RRU failure analysis from the near end.
  • the Simple Network Management Protocol (SNMP) is used to directly connect NEs from the near end to implement RRU fault handling. Therefore, the embodiment can be deployed on a client on the network element side.
  • SNMP Simple Network Management Protocol
  • the RRU alarm information includes: a fault log and an anti-construction file.
  • Step 310 Initialize a Simple Network Management Protocol Stack (SNMP) by using a preset script.
  • SNMP Simple Network Management Protocol Stack
  • Step 320 Based on the initialized SNMP, establish a Reliable User Datagram Protocol (RUDP) connection with the network element by using a script.
  • RUDP Reliable User Datagram Protocol
  • Step 330 Obtain an alarm file, an anti-construction file, and a fault log respectively from the connected network element by using a script based on the established SNMP interface.
  • the interface may include a set interface such as SNMP (the set interface includes an Element Management System Simple Network Management Protocol (SNMP) set interface: the set operation is used to control management information (eg, modify, set)
  • the internal interface optionally, based on the FTP service, obtains the alarm file, the anti-construction file, and the fault log containing the RRU alarm information from the connected network elements through the SNMP set interface.
  • SNMP Element Management System Simple Network Management Protocol
  • the corresponding object identifier (Object identifier, oid for short) exists in the alarm file, the anti-construction file, and the fault log. Obtain an alarm file, an anti-construction file, and a fault log according to the oid corresponding to the alarm file, the anti-construction file, and the fault log.
  • step 340 the RRU alarm is filtered out from the alarm file by using a script.
  • the number of RRU alarms that are filtered out from the alarm file may be one or more.
  • the fault log includes the version of the fault log and the fault information of each RRU alarm.
  • the anti-construction file includes the type of RRU in which each RRU alarm occurs.
  • Step 350 Perform a fault analysis on each RRU alarm in the alarm file according to the fault log and the anti-construction file, and obtain a fault analysis result of each RRU alarm.
  • Step 1 Parse the fault log through a script to obtain the version of the fault log.
  • Step 2 Parse the anti-construction file through a script to obtain the type of the RRU. If the number of RRU alarms is multiple, the type of the RRU currently performing fault analysis is obtained.
  • Step 3 The fault analysis algorithm corresponding to the version of the fault log and the type of the RRU is obtained by using a script in a preset multiple fault analysis algorithm. If the number of RRU alarms is multiple, a fault analysis algorithm corresponding to the version of the fault log and the type of the current RRU is obtained.
  • Step 4 Perform a fault analysis on the fault log according to the obtained fault analysis algorithm to obtain a fault analysis result of the RRU alarm. If the RRU alarm is multiple, the fault analysis of the current RRU alarm in the fault log is performed according to the obtained fault analysis algorithm to obtain a fault analysis result of the RRU alarm.
  • This embodiment describes the fault analysis of the alarm RRU.
  • FIG. 4 is a flow chart showing the steps of fault analysis of an alarm RRU according to a fourth embodiment of the present invention.
  • step 410 the fault log is parsed by a preset script.
  • step 420 the script determines whether the version of the fault log is V1. If the version of the fault log is V1, step 430 is performed; if the version of the fault log is not V1, step 460 is performed.
  • Step 430 Determine whether the type of the RRU board is A by using a script. If the type of the RRU is A, go to step 440. If the type of the RRU is not A, go to step 450.
  • This type A can be set according to requirements, for example, the type A is of the type number R8968, R8972, R8928, or R8964.
  • Step 440 Perform a fault analysis on the fault log by using a preset first algorithm, and obtain a fault analysis result of the RRU alarm.
  • Step 450 Perform a fault analysis on the fault log by using a preset second algorithm, and obtain a fault analysis result of the RRU alarm.
  • Step 460 Determine whether the type of the RRU board is B by using a script. If the type of the RRU is B, go to step 470. If the type of the RRU is not B, go to step 480.
  • This type B can be set according to requirements, for example: the type B is R8968, R8972, R8928, or R8964.
  • Step 470 Perform a fault analysis on the fault log by using a preset third algorithm, and obtain a fault analysis result of the RRU alarm.
  • Step 480 Perform a fault analysis on the fault log by using a preset fourth algorithm, and obtain a fault analysis result of the RRU alarm.
  • the first algorithm, the second algorithm, the third algorithm, and the fourth algorithm are all set according to the version of the fault log and the type of the RRU, and are used to analyze the version of the corresponding fault log and the RRU board type. s reason. For example, if the version of the fault log is V1 and the type of the RRU board is R8968, the algorithm used can be 8 antenna (8T) algorithm; the version of the fault log is V2. The type of the RRU board is R8972. The algorithm used can be the 2T algorithm.
  • the analysis algorithms corresponding to different types of RRU boards and different types of fault logs are configured to make the fault analysis result more accurate.
  • the RRU of the A type and the B type are simply enumerated, and the RRU alarm analysis performed by a suitable algorithm is found. It should be understood by those skilled in the art that the present embodiment can be modified as needed.
  • the embodiment of the present invention may be implemented by using a server or a terminal that is independent of the network management system as a hardware execution entity.
  • the embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the RRU fault analysis method.
  • This embodiment provides an apparatus for implementing RRU failure analysis.
  • FIG. 5 it is a structural diagram of an apparatus for implementing RRU failure analysis according to a fifth embodiment of the present invention.
  • the device includes:
  • the obtaining module 510 is configured to obtain an RRU alarm and a corresponding RRU alarm information by using a preset script.
  • the analysis module 520 is configured to perform fault analysis on the RRU alarm according to the acquired RRU alarm information, and obtain a fault analysis result of the RRU alarm.
  • the RRU alarm information may include: a fault log.
  • the obtaining module 510 is configured to: connect the network management system by using a preset script; and send the human language MML command through the script to obtain the RRU alarm and the corresponding RRU alarm information from the connected network management system.
  • the analyzing module 520 is configured to: parse the fault log by using a script to obtain a version of the fault log; obtain a type of the RRU in the RRU alarm by using a script; The fault analysis algorithm corresponding to the version of the fault log and the type of the RRU; the failure analysis is performed on the fault log according to the fault analysis algorithm to obtain the fault analysis result of the RRU alarm.
  • the RRU alarm information may include: a fault log and a reverse file.
  • the obtaining module 510 is configured to: initialize SNMP by using a preset script; establish a reliable user data packet protocol (RUDP) connection with the network element by using the script after the initialization, and establish a connection based SNMP interface by using a script. Obtain RRU alarms and RRU fault information from the NEs.
  • RUDP reliable user data packet protocol
  • the analysis module 520 is configured to: parse the fault log through a script to obtain a version of the fault log; parse the anti-construction file through the script to obtain the type of the RRU; and obtain a fault analysis algorithm corresponding to the version of the fault log and the type of the RRU through the script; The script analyzes the fault log according to the fault analysis algorithm to obtain the fault analysis result of the RRU alarm.
  • the preset script is a script that is established on the preset platform, and the device in the embodiment of the present invention further includes a function library module 500.
  • Tool library functions include:
  • a network element connection function that establishes a connection with the network management system or the network element
  • a fault analysis algorithm corresponding to the version of the fault log and the type of the RRU is configured in advance, and the fault analysis algorithm is configured to perform fault analysis on the RRU alarm.
  • This embodiment is independent of the network management system and can be set in the client on the network management system side to implement the operation of the network element from the remote end. It can also be set in the client on the network element side to directly connect the network element from the near end. RRU fault handling at the near end.
  • each module/unit in the foregoing embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, being executed by a processor and stored in a memory. Programs/instructions to implement their respective functions.
  • the invention is not limited to any specific form of combination of hardware and software.

Abstract

一种实现射频拉远单元(RRU)故障分析的方法和装置。包括：通过预设的脚本获取RRU告警及对应的RRU告警信息；通过脚本根据RRU告警信息，对RRU告警进行故障分析，获得RRU告警的故障分析结果。本发明实施例独立于网管系统，基于预设的脚本实现RRU故障分析功能，简化了RRU故障分析的开发难度；另外，通过故障日志的版本及RRU的类型选择相应的故障分析算法，提高了故障分析的正确率。

Description

一种实现射频拉远单元故障分析的方法和装置 技术领域
本文涉及但不限于通信技术领域，尤其涉及一种实现射频拉远单元(Radio Remote Unit，简称RRU)故障分析的方法和装置。
背景技术
目前，在网管系统的告警模块上多设置RRU故障分析功能。当发现有RRU告警的时候，网管系统可以根据RRU故障信息进行RRU故障分析，并返回故障分析结果，用户依此做出相应的处理，例如：返厂维修或者现场故障排查。但是，RRU返回原厂后可能会发现该RRU并没有故障，之所以不能正常工作可能是现场电源接触不良等外部因素造成的。
目前这种由于现场外在因素而导致的RRU返修的情况很多，因此经常需要对RRU故障分析功能进行改进。而相关技术中的RRU故障分析功能集成在网管系统中，只是网管系统中的一个小功能，对于开发者和使用者都非常不便。
网管系统多使用Java语言开发，开发过程繁琐、开发难度较大、且开发后的源代码可读性差，导致RRU故障分析算法只有开发者结合整个源代码才能够读懂，而使用者更是难以理解。如果RRU型号或者故障分析算法发生更改，则需要开发者对网管系统进行代码修改、测试、和打补丁等，整个过程耗时较长。另外，由于故障分析功能只是网管系统中的一个小功能，因此，RRU故障分析算法往往单一，导致RRU故障分析结果不够准确，影响使用者对RRU单板的维修作出正确的判断。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供一种实现RRU故障分析的方法和装置，能够降低RRU故障分析的开发难度。
本发明实施例提供了一种实现射频拉远单元RRU故障分析的方法，包括：
通过预设的脚本获取RRU告警及对应的RRU告警信息；
通过所述脚本根据获取的RRU告警信息对RRU告警进行故障分析，获得所述RRU告警的故障分析结果。
可选的，所述RRU告警信息包括：故障日志；
所述获取RRU告警及对应的RRU告警信息，包括：
通过所述脚本连接网管系统；
通过所述脚本发送人机语言MML命令从连接到的所述网管系统中，获取RRU告警和对应的所述RRU告警信息。
可选的，所述进行故障分析，包括：
通过所述脚本解析所述故障日志，获得所述故障日志的版本；
通过所述脚本在所述RRU告警中，获得所述RRU的类型；
通过所述脚本获取与所述故障日志的版本及所述RRU的类型对应的故障分析算法；
通过所述脚本根据所述故障分析算法，对所述故障日志进行故障分析，获得所述RRU告警的故障分析结果。
可选的，所述RRU告警信息包括：故障日志和反构文件；
所述通过预设的脚本，获取RRU告警及对应的RRU告警信息，包括：
通过所述脚本初始化简单网络管理协议栈SNMP；
基于初始化后的所述SNMP，通过所述脚本与网元建立可靠用户数据包协议RUDP连接；
基于建立连接的所述SNMP的接口，通过所述脚本从所述网元中，分别获取RRU告警、及对应的RRU告警信息。
可选的，通过所述脚本根据所述RRU告警信息，对所述RRU告警进行故障分析，包括：
通过所述脚本解析所述故障日志，获得所述故障日志的版本；
通过所述脚本解析所述反构文件，获得所述RRU的类型；
通过所述脚本获取与所述故障日志的版本及所述RRU的类型对应的故障分析算法；
通过所述脚本根据所述故障分析算法，对所述故障日志进行故障分析，以获得所述RRU告警的故障分析结果。
可选的，所述预设的脚本为建立在预设平台的脚本，所述方法之前还包括：
在所述预设平台内建工具库函数；
所述工具库函数包含有：
与网管系统或网元建立连接的网元连接函数；
用于获取RRU告警和对应的RRU告警信息的人机命令语句；
用于解析获取的告警信息的报文解析函数；
预先建立的与故障日志的版本及RRU的类型对应的故障分析算法，所述故障分析算法用于对所述RRU告警进行故障分析。
本发明实施例还提供了一种实现RRU故障分析的装置，包括：获取模块，设置为通过预设的脚本，获取RRU告警及对应的RRU告警信息；
分析模块，设置为通过脚本根据获取的所述RRU告警信息，对所述RRU告警进行故障分析，获得所述RRU告警的故障分析结果。
可选的，所述RRU告警信息包括：故障日志；
所述获取模块是设置为：通过所述脚本连接网管系统；通过所述脚本发送人机语言MML命令从连接到的所述网管系统中，获取RRU告警和对应的所述RRU告警信息。
可选的，所述分析模块是设置为：
通过所述脚本解析所述故障日志，获得所述故障日志的版本；
通过所述脚本在所述RRU告警中，获得所述RRU的类型；
通过所述脚本获取与所述故障日志的版本及所述RRU的类型对应的故障分析算法；
通过所述脚本根据所述故障分析算法，对所述故障日志进行故障分析，以获得所述RRU告警的故障分析结果。
可选的，所述RRU告警信息包括：故障日志和反构文件；
所述获取模块是设置为：通过所述脚本初始化简单网络管理协议栈SNMP；基于初始化后的所述SNMP，通过所述脚本与网元建立可靠用户数据包协议RUDP连接；基于建立连接的所述SNMP的接口，通过所述脚本从所述网元中，分别获取RRU告警和RRU故障信息。
可选的，所述分析模块是设置为：
通过所述脚本解析所述故障日志，获得所述故障日志的版本；
通过所述脚本解析所述反构文件，获得所述RRU的类型；
通过所述脚本获取与所述故障日志的版本及所述RRU的类型对应的故障分析算法；
通过所述脚本根据所述故障分析算法，对所述故障日志进行故障分析，以获得所述RRU告警的故障分析结果。
可选的，所述预设的脚本为建立在预设平台的脚本，所述装置还包括函数库模块，
设置为在所述预设平台内建工具库函数；
所述工具库函数包含有：
与网管系统或网元建立连接的网元连接函数；
用于获取RRU告警和对应的RRU告警信息的人机命令语句；
用于解析获取的告警信息的报文解析函数；
预先建立的与故障日志的版本及RRU的类型对应的故障分析算法，所述故障分析算法用于对所述RRU告警进行故障分析。
本发明实施例有益效果如下：
本发明实施例独立于网管系统，基于预设的脚本实现RRU故障分析功 能，对RRU故障分析具有针对性。脚本语言具有简洁、易懂、易学等特点，使得本发明的开发过程简单、可读性强、时效性高、且执行脚本的修改、更新较为方便，对于开发人员和使用人员都较为便利。
与相关技术相比，本发明提供的技术方案，包括：通过预设的脚本获取RRU告警及对应的RRU告警信息；通过脚本根据RRU告警信息，对RRU告警进行故障分析，获得RRU告警的故障分析结果。本发明实施例独立于网管系统，基于预设的脚本实现RRU故障分析功能，简化了RRU故障分析的开发难度；另外，通过故障日志的版本及RRU的类型选择相应的故障分析算法，提高了故障分析的正确率。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1是根据本发明第一实施例的实现RRU故障分析的方法的流程图；
图2是根据本发明第二实施例的实现RRU故障分析的方法的流程图；
图3是根据本发明第三实施例的实现RRU故障分析的方法的流程图；
图4是根据本发明第四实施例的对告警RRU进行故障分析的步骤流程图；
图5是根据本发明第五实施例的实现RRU故障分析的装置的结构图。
本发明的实施方式
下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
实施例一
本实施例提供了一种实现RRU故障分析的方法。如图1所示，为根据本发明第一实施例的实现RRU故障分析的方法的流程图。
步骤110，通过预设的脚本，获取RRU告警及对应的RRU告警信息。
RRU告警信息包括：RRU告警的故障日志，或者RRU告警信息包括：RRU告警的故障日志和反构文件。
可选地，基于预设的脚本，从网元管理系统(network element management system，简称EMS)获取RRU告警的文件和故障日志；或者，基于该脚本，从网元，获取RRU告警及对应的RRU告警信息，RRU告警信息可以包括：故障日志和反构文件。本发明实施例，将网元管理系统简称为网管系统。
该脚本可以包括python脚本。该脚本的开发和运行可以是在脚本工具平台上完成的。脚本工具平台包括：脚本开发平台和脚本运行管理平台。脚本开发平台是一个脚本编译、调试、运行环境，平台内部内嵌了函数库用来支持网管系统的运维业务，平台内建的工具库函数，库函数可以用于建立远程登录(telnet)连接、发送人机语言(Man-Machine Language，简称MML)命令，解析MML报文，获取报文数据、提取信息、根据故障分析算法进行故障分析，输出故障分析结果等。
脚本运行管理平台可以包括一个脱离脚本开发、仅对脚本工程进行运行管理的平台，面向不需要编写脚本、仅依靠脚本进行日常运维工作的人员，该平台支持定时任务以及即时任务、任务分类整理等功能。
本发明实施例，预设的脚本为建立在预设平台的脚本，本发明实施例还包括：
在预设平台内建工具库函数；
工具库函数包含有：
与网管系统或网元建立连接的网元连接函数；
用于获取RRU告警和对应的RRU告警信息的人机命令语句；
用于解析获取的告警信息的报文解析函数；
预先建立的与故障日志的版本及RRU的类型对应的故障分析算法，所述故障分析算法用于对所述RRU告警进行故障分析。
需要说明的是，网元连接函数、人机命令语句、报文解析函数可以通过相关技术中的惯用技术手段进行编辑整理了；其中，网元连接函数可以包括远程登录指令；报文解析函数可以用于解析故障日志、反构文件等处理；人机命令语句可以包括例如、发送人机命令函数、人机命令结果获取函数等函数，本发明实施例还可以包括其他相关的函数，例如控件函数，用于调用相 关函数或语句。
步骤120，通过脚本根据获取的RRU告警信息对RRU告警进行故障分析，获得RRU告警的故障分析结果。
故障分析结果包括但不限于下述的一种或多种：版本故障、电源故障、时钟故障、设备故障、导频功率故障、过温故障、下行输出欠过功率故障、线缆故障、通道故障、光纤接错故障、IR接口信号强度异常故障、光模块不在位、光口速率不匹配。本实施例的故障分析结果种类较多，可以满足用户故障排查需求。本发明实施例，IR接口包括RRU和基带处理单元(BBU)之间的接口，可以通过光纤连接；
故障分析结果对应的维修方式包括：手动维修和自动维修。其中，手动维修需要人工干预，运维人员介入，根据故障分析结果进行相应的维修工作。自动维修无需人工干预，可以自动维护，例如修改一些配置参数等。
本实施例独立于网管系统，通过预设的脚本实现RRU故障分析功能，为运维人员根据现场情况进行RRU故障分析提供了便捷。本实施例的脚本可以实时发布、运行，时效性高。本实施例的脚本工程在智能脚本分析工具上运行，可以根据现场的情况进行实施，选择近端和远端运行方式。
本实施例利用脚本语言的简洁、易懂、易学的特性，方便开发人员与业务人员进行交流，实现“代码即文档”，从而可以高效地开发出用于实现RRU故障分析的脚本。运维人员可以在发布的脚本上进行修改、运行，操作更方便。该脚本在使用上极为方便，用户利用此脚本可以随时对RRU故障进行诊断，明确RRU当前的状态，获得故障分析结果。
实施例二
本实施例对从远端实现RRU故障分析进行说明。
图2是本发明第二实施例的实现RRU故障分析的方法的流程图。本实施例可以部署在网管系统侧的客户端上。本实施例的RRU告警信息包括：故障日志。
步骤210，通过预设的脚本连接网管系统(EMS)。
该脚本运行在脚本开发平台上。
该脚本开发平台内部集成有用于连接网元、发送MML命令、解析MML命令的工具库函数；可以使用Python语言，在脚本开发平台上进行开发、调试、运行；可以将脚本发布到EMS侧运行并查看运行日志。
步骤220，通过脚本发送MML命令，从网管系统中获取RRU告警。
通过脚本发送MML命令查询网管系统当前的告警文件，并在当前的告警文件中筛选出RRU告警。筛选出的RRU告警可以是一个或多个，如果是多个RRU告警，可以组成一个RRU告警集合。
可选的，利用工具库函数，发送人机语言命令。输入显示当前告警的人机语言命令作为函数参数，即可查看包含网管系统当前所有告警信息的告警文件。
从告警文件中筛选出RRU告警。可选地，可以根据告警信息中的架框槽筛选出告警文件中的RRU告警。
步骤230，通过脚本发送MML命令，从网管系统中获取RRU告警的故障日志。
RRU单板在网元工作，RRU告警的故障日志被存储在网元。
故障日志在连接网管系统之后，通过人机语言命令，控制网管系统从发生RRU告警的网元处获取的；然后从网管系统中获取RRU告警的故障日志。
如果存在RRU告警集合，则通过脚本顺序获取每一条RRU告警的故障日志，对每条RRU告警做RRU故障分析处理。
可选的，基于脚本发送MML命令，使网管系统从发生该RRU告警的网元，获取该RRU告警的故障日志；脚本开启文件传输协议(FTP，File Transfer Protocol)服务，从网管系统下载该RRU告警的故障日志到本地。可选地，如果存在两级网管系统，一级网管系统为EMS，二级网管系统为网元操作维护系统(OMMB，Operation&Maintenance Module Broker)一个EMS管理多个OMMB，一个OMMB管理多个网元，则基于脚本先发送MML命令使连接关系从EMS切换到发生RRU告警的网元所在的OMMB，再发送一个MML命令控制OMMB从发生RRU告警的网元获取该RRU告警的故障日志，并 上传到EMS，这样连接关系从OMMB切换回EMS之后，就可以从EMS获取到该RRU告警的故障日志了。
步骤240，通过脚本根据RRU告警的故障日志，对RRU告警进行故障分析，获得RRU告警的故障分析结果。
RRU告警中包括发生该RRU告警的RRU的类型。RRU的类型包括RRU单板的类型，例如：R8968、R8972、R8928、R8964等RRU的类型。
RRU告警的故障日志中包含故障日志的版本、以及RRU告警的相关信息。
可选的，通过脚本解析故障日志，获得该故障日志的版本；通过脚本在该RRU告警中，获得该RRU的类型；通过脚本在预设的多个故障分析算法中，获取与该故障日志的版本及该RRU的类型对应的故障分析算法；通过脚本根据该获取的故障分析算法，对该故障日志进行故障分析，以获得该RRU告警的故障分析结果。
本发明实施例，故障日志包括二进制文件，解析二进制文件，获得其中的数据信息；该数据信息包括：故障日志的版本信息、告警码、告警类型、业务参数等。
实施例三
本实施例对从近端实现RRU故障分析进行说明。采用简单网络管理协议栈(Simple Network Management Protocol，简称SNMP)实现从近端直接连接网元，实现RRU故障处理功能。因此，本实施例可以部署在网元侧的客户端上。
图3是本发明第三实施例的实现RRU故障分析的方法的流程图。在本实施例中，RRU告警信息包括：故障日志和反构文件。
步骤310，通过预设的脚本初始化简单网络管理协议栈(SNMP)；
步骤320，基于初始化后的SNMP，通过脚本与网元建立可靠用户数据包协议(Reliable User Datagram Protocol，简称RUDP)连接。
在建立RUDP连接的同时，还可以通过脚本启动FTP服务。
步骤330，基于建立连接的SNMP的接口，通过脚本从连接的网元中，分别获取告警文件、反构文件和故障日志。
该接口可以包括例如SNMP的set接口(set接口包括网元管理系统(Element Management System)简单网络管理协议(SNMP)的set接口：通过set操作用来对管理信息进行控制(例如、修改、设置))在内的接口，可选的，基于FTP服务，通过SNMP的set接口，从连接的网元中，分别获取包含RRU告警信息的告警文件、反构文件和故障日志。
告警文件、反构文件和故障日志分别存在对应的对象标识符(Object identifier，简称oid)。根据告警文件、反构文件和故障日志分别对应的oid，分别获取告警文件、反构文件和故障日志。
步骤340，通过脚本从告警文件中筛选出RRU告警。
从告警文件中筛选出RRU告警的数量可以是一个或多个。
故障日志中包括故障日志的版本、以及每个RRU告警的故障信息。
反构文件中包括每个发生RRU告警的RRU的类型。
步骤350，通过脚本根据故障日志和反构文件，对告警文件中的每个RRU告警进行故障分析，获得每个RRU告警的故障分析结果。
步骤1，通过脚本解析故障日志，获得该故障日志的版本。
步骤2，通过脚本解析反构文件，获得RRU的类型。如果RRU告警为多个，则获取当前进行故障分析的RRU的类型。
步骤3，通过脚本在预设的多个故障分析算法中，获取与故障日志的版本及该RRU的类型对应的故障分析算法。如果RRU告警为多个，则获取与故障日志的版本及该当前RRU的类型对应的故障分析算法。
步骤4，通过脚本根据获取的故障分析算法，对故障日志进行故障分析，以获得该RRU告警的故障分析结果。如果RRU告警为多个，则根据获取的故障分析算法，对故障日志中当前RRU告警的故障信息进行故障分析，以获得该RRU告警的故障分析结果。
实施例四
本实施例对告警RRU进行故障分析进行说明。
图4是本发明第四实施例的对告警RRU进行故障分析的步骤流程图。
步骤410，通过预设的脚本解析故障日志。
通过解析故障日志，可以获知故障日志的版本包括：版本1(V1)或V2等。
步骤420，通过脚本判断故障日志的版本是否为V1。若故障日志的版本为V1，则执行步骤430；若故障日志的版本不是V1，则执行步骤460。
步骤430，通过脚本判断RRU单板的类型是否为A。若RRU单板的类型为A，则执行步骤440，若RRU单板的类型不为A，则执行步骤450。该类型A可以根据需求来设置，例如：该类型A为类型编号为R8968、R8972、R8928、或者R8964的类型。
步骤440，使用预设的第一算法，通过脚本对故障日志进行故障分析，获得RRU告警的故障分析结果。
步骤450，使用预设的第二算法，通过脚本对故障日志进行故障分析，获得RRU告警的故障分析结果。
步骤460，通过脚本判断RRU单板的类型是否为B。若RRU单板的类型为B，则执行步骤470，若RRU单板的类型不为B，则执行步骤480。该类型B可以根据需求来设置，例如：该类型B为R8968、R8972、R8928、或者R8964。
步骤470，使用预设的第三算法，通过脚本对故障日志进行故障分析，获得RRU告警的故障分析结果。
步骤480，使用预设的第四算法，通过脚本对故障日志进行故障分析，获得RRU告警的故障分析结果。
上述第一算法、第二算法、第三算法和第四算法，都是根据故障日志的版本、RRU单板类型设置的，用于分析对应故障日志的版本、RRU单板类型下，发生RRU告警的原因。例如：故障日志的版本为V1、RRU单板的类型为R8968，那么使用的算法可以为8天线(8T)算法；故障日志的版本为V2、 RRU单板的类型为R8972，那么使用的算法可以为2T算法。
本实施例为不同类型的RRU单板、不同类型故障日志配置分别对应的分析算法，使故障分析结果更加准确。当然本实施例为了使本发明便于理解，仅简单列举了V1和V2两种版本的故障日志、A和B两种类型的RRU的情形，并找到合适的算法进行的RRU告警分析，本领域技术人员应当知道在本发明的思想下，可以根据需求对本实施例作出改进。
需要说明的是，本发明实施例可以由独立于网管系统的服务器或终端等作为硬件执行主体，进行本发明实施例的实施。
本发明实施例还提供一种计算机存储介质，计算机存储介质中存储有计算机可执行指令，计算机可执行指令用于执行上述RRU故障分析的方法。
实施例五
本实施例提供了一种实现RRU故障分析的装置。如图5所示，为根据本发明第五实施例的实现RRU故障分析的装置的结构图。
该装置包括：
获取模块510，设置为通过预设的脚本，获取RRU告警及对应的RRU告警信息；
分析模块520，设置为通过脚本根据获取的所述RRU告警信息，对所述RRU告警进行故障分析，获得所述RRU告警的故障分析结果。
在一个可选实施例中，RRU告警信息可以包括：故障日志。
获取模块510是设置为：通过预设的脚本，连接网管系统；通过所述脚本发送人机语言MML命令从连接到的网管系统中，获取RRU告警和对应的RRU告警信息。
可选的，分析模块520是设置为：通过脚本解析故障日志，获得故障日志的版本；通过脚本在RRU告警中，获得RRU的类型；通过脚本获取与故 障日志的版本及RRU的类型对应的故障分析算法；通过脚本根据故障分析算法，对故障日志进行故障分析，以获得RRU告警的故障分析结果。
在另一可选实施例中，RRU告警信息可以包括：故障日志和反构文件。
获取模块510是设置为：通过预设的脚本，初始化SNMP；基于初始化后的SNMP，通过所述脚本与网元建立可靠用户数据包协议(RUDP)连接；基于建立连接的SNMP的接口，通过脚本从网元中，分别获取RRU告警和RRU故障信息。
分析模块520是设置为：通过脚本解析故障日志，获得故障日志的版本；通过脚本解析反构文件，获得RRU的类型；通过脚本获取与故障日志的版本及RRU的类型对应的故障分析算法；通过脚本根据故障分析算法，对故障日志进行故障分析，以获得RRU告警的故障分析结果。
本发明实施例，预设的脚本为建立在预设平台的脚本，本发明实施例装置还包括函数库模块500，
设置为在预设平台内建工具库函数；
工具库函数包含有：
与网管系统或网元建立连接的网元连接函数；
用于获取RRU告警和对应的RRU告警信息的人机命令语句；
用于解析获取的告警信息的报文解析函数；
预先建立的与故障日志的版本及RRU的类型对应的故障分析算法，所述故障分析算法用于对所述RRU告警进行故障分析。
本实施例的装置的功能已经在图1-4所示的方法实施例中进行了描述，故本实施例的描述中未详尽之处，可以参见前述实施例中的相关说明，在此不做赘述。
本实施例独立于网管系统，可以设置在网管系统侧的客户端中，从远端实现对网元的操作；也可以设置在网元侧的客户端中，从近端直连网元，实现在近端的RRU故障处理。
尽管为示例目的，已经公开了本发明的可选实施例，本领域的技术人员 将意识到改进、增加和取代也是可能的，因此，本发明的范围应当不限于上述实施例。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件(例如处理器)完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的每个模块/单元可以采用硬件的形式实现，例如通过集成电路来实现其相应功能，也可以采用软件功能模块的形式实现，例如通过处理器执行存储于存储器中的程序/指令来实现其相应功能。本发明不限制于任何特定形式的硬件和软件的结合。
虽然本申请所揭露的实施方式如上，但所述的内容仅为便于理解本申请而采用的实施方式，并非用以限定本申请，如本发明实施方式中的具体的实现方法。任何本申请所属领域内的技术人员，在不脱离本申请所揭露的精神和范围的前提下，可以在实施的形式及细节上进行任何的修改与变化，但本申请的专利保护范围，仍须以所附的权利要求书所界定的范围为准。
工业实用性
上述技术方案简化了RRU故障分析的开发难度。

Claims (12)

  1. 一种实现射频拉远单元RRU故障分析的方法，所述方法包括：
    通过预设的脚本获取RRU告警及对应的RRU告警信息；
    通过所述脚本根据获取的RRU告警信息对RRU告警进行故障分析，获得所述RRU告警的故障分析结果。
  2. 如权利要求1所述的方法，其中，
    所述RRU告警信息包括：故障日志；
    所述获取RRU告警及对应的RRU告警信息，包括：
    通过所述脚本连接网管系统；
    通过所述脚本发送人机语言MML命令从连接到的所述网管系统中，获取RRU告警和对应的所述RRU告警信息。
  3. 如权利要求2所述的方法，其中，所述进行故障分析，包括：
    通过所述脚本解析所述故障日志，获得所述故障日志的版本；
    通过所述脚本在所述RRU告警中，获得所述RRU的类型；
    通过所述脚本获取与所述故障日志的版本及所述RRU的类型对应的故障分析算法；
    通过所述脚本根据所述故障分析算法，对所述故障日志进行故障分析，获得所述RRU告警的故障分析结果。
  4. 如权利要求1所述的方法，其中，
    所述RRU告警信息包括：故障日志和反构文件；
    所述通过预设的脚本，获取RRU告警及对应的RRU告警信息，包括：
    通过所述脚本初始化简单网络管理协议栈SNMP；
    基于初始化后的所述SNMP，通过所述脚本与网元建立可靠用户数据包协议RUDP连接；
    基于建立连接的所述SNMP的接口，通过所述脚本从所述网元中，分别获取RRU告警、及对应的RRU告警信息。
  5. 如权利要求4所述的方法，其中，通过所述脚本根据所述RRU告警信息，对所述RRU告警进行故障分析，包括：
    通过所述脚本解析所述故障日志，获得所述故障日志的版本；
    通过所述脚本解析所述反构文件，获得所述RRU的类型；
    通过所述脚本获取与所述故障日志的版本及所述RRU的类型对应的故障分析算法；
    通过所述脚本根据所述故障分析算法，对所述故障日志进行故障分析，以获得所述RRU告警的故障分析结果。
  6. 根据权利要求1～5任一项所述的方法，其中，所述预设的脚本为建立在预设平台的脚本，所述方法之前还包括：
    在所述预设平台内建工具库函数；
    所述工具库函数包含有：
    与网管系统或网元建立连接的网元连接函数；
    用于获取RRU告警和对应的RRU告警信息的人机命令语句；
    用于解析获取的告警信息的报文解析函数；
    预先建立的与故障日志的版本及RRU的类型对应的故障分析算法，所述故障分析算法用于对所述RRU告警进行故障分析。
  7. 一种实现RRU故障分析的装置，所述装置包括：
    获取模块，设置为通过预设的脚本，获取RRU告警及对应的RRU告警信息；
    分析模块，设置为通过脚本根据获取的所述RRU告警信息，对所述RRU告警进行故障分析，获得所述RRU告警的故障分析结果。
  8. 如权利要求7所述的装置，其中，
    所述RRU告警信息包括：故障日志；
    所述获取模块是设置为：通过所述脚本连接网管系统；通过所述脚本发送人机语言MML命令从连接到的所述网管系统中，获取RRU告警和对应的所述RRU告警信息。
  9. 如权利要求8所述的装置，其中，所述分析模块是设置为：
    通过所述脚本解析所述故障日志，获得所述故障日志的版本；
    通过所述脚本在所述RRU告警中，获得所述RRU的类型；
    通过所述脚本获取与所述故障日志的版本及所述RRU的类型对应的故障分析算法；
    通过所述脚本根据所述故障分析算法，对所述故障日志进行故障分析，以获得所述RRU告警的故障分析结果。
  10. 如权利要求7所述的装置，其中，
    所述RRU告警信息包括：故障日志和反构文件；
    所述获取模块是设置为：通过所述脚本初始化简单网络管理协议栈SNMP；基于初始化后的所述SNMP，通过所述脚本与网元建立可靠用户数据包协议RUDP连接；基于建立连接的所述SNMP的接口，通过所述脚本从所述网元中，分别获取RRU告警和RRU故障信息。
  11. 如权利要求10所述的装置，其中，所述分析模块是设置为：
    通过所述脚本解析所述故障日志，获得所述故障日志的版本；
    通过所述脚本解析所述反构文件，获得所述RRU的类型；
    通过所述脚本获取与所述故障日志的版本及所述RRU的类型对应的故障分析算法；
    通过所述脚本根据所述故障分析算法，对所述故障日志进行故障分析，以获得所述RRU告警的故障分析结果。
  12. 根据权利要求7～11任一项所述的装置，其中，所述预设的脚本为建立在预设平台的脚本，所述装置还包括函数库模块，
    设置为在所述预设平台内建工具库函数；
    所述工具库函数包含有：
    与网管系统或网元建立连接的网元连接函数；
    用于获取RRU告警和对应的RRU告警信息的人机命令语句；
    用于解析获取的告警信息的报文解析函数；
    预先建立的与故障日志的版本及RRU的类型对应的故障分析算法，所述故障分析算法用于对所述RRU告警进行故障分析。
PCT/CN2016/089690 2015-07-28 2016-07-11 一种实现射频拉远单元故障分析的方法和装置 WO2017016386A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510451416.XA CN106714216A (zh) 2015-07-28 2015-07-28 一种基于脚本实现rru故障分析的方法和装置
CN201510451416.X 2015-07-28

Publications (1)

Publication Number Publication Date
WO2017016386A1 true WO2017016386A1 (zh) 2017-02-02

Family

ID=57884076

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/089690 WO2017016386A1 (zh) 2015-07-28 2016-07-11 一种实现射频拉远单元故障分析的方法和装置

Country Status (2)

Country Link
CN (1) CN106714216A (zh)
WO (1) WO2017016386A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112383338A (zh) * 2020-10-21 2021-02-19 武汉虹信科技发展有限责任公司 室分设备监控方法及装置
CN113660115A (zh) * 2021-07-28 2021-11-16 上海纽盾科技股份有限公司 基于告警的网络安全数据处理方法、装置及系统
CN113726555A (zh) * 2021-08-02 2021-11-30 华迪计算机集团有限公司 一种适用于数据通信网络辅助解析告警的系统及方法

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112217899A (zh) * 2020-10-19 2021-01-12 政采云有限公司 容器故障排查系统及方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1479461A (zh) * 2002-08-29 2004-03-03 华为技术有限公司 通讯系统故障诊断方法和系统
CN101360001A (zh) * 2007-07-31 2009-02-04 中兴通讯股份有限公司 一种上级网管对告警进行处理装置及方法
CN101527660A (zh) * 2009-04-03 2009-09-09 华为技术有限公司 告警方法、相关设备及系统
CN102111797A (zh) * 2011-02-15 2011-06-29 大唐移动通信设备有限公司 一种故障的诊断方法和设备
CN102231676A (zh) * 2011-06-23 2011-11-02 中兴通讯股份有限公司 一种网管数据采集方法和装置
EP2866388A1 (en) * 2012-07-23 2015-04-29 ZTE Corporation Method for detecting correctness of optic fiber connection based on radio remote unit (rru) looped network, and base band unit (bbu)

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101197621B (zh) * 2007-12-07 2012-03-07 中兴通讯股份有限公司 一种对网管系统故障进行远程诊断定位的方法及其系统
CN101582807B (zh) * 2009-07-02 2011-10-05 北京讯风光通信技术开发有限责任公司 一种基于北向接口实现网络管理的方法及系统
CN101945410A (zh) * 2010-10-12 2011-01-12 武汉虹旭信息技术有限责任公司 一种移动分组网故障的智能分析方法
CN103596208B (zh) * 2013-11-15 2017-02-15 大唐移动通信设备有限公司 一种网元故障判断方法及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1479461A (zh) * 2002-08-29 2004-03-03 华为技术有限公司 通讯系统故障诊断方法和系统
CN101360001A (zh) * 2007-07-31 2009-02-04 中兴通讯股份有限公司 一种上级网管对告警进行处理装置及方法
CN101527660A (zh) * 2009-04-03 2009-09-09 华为技术有限公司 告警方法、相关设备及系统
CN102111797A (zh) * 2011-02-15 2011-06-29 大唐移动通信设备有限公司 一种故障的诊断方法和设备
CN102231676A (zh) * 2011-06-23 2011-11-02 中兴通讯股份有限公司 一种网管数据采集方法和装置
EP2866388A1 (en) * 2012-07-23 2015-04-29 ZTE Corporation Method for detecting correctness of optic fiber connection based on radio remote unit (rru) looped network, and base band unit (bbu)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112383338A (zh) * 2020-10-21 2021-02-19 武汉虹信科技发展有限责任公司 室分设备监控方法及装置
CN112383338B (zh) * 2020-10-21 2022-04-19 武汉虹信科技发展有限责任公司 室分设备监控方法及装置
CN113660115A (zh) * 2021-07-28 2021-11-16 上海纽盾科技股份有限公司 基于告警的网络安全数据处理方法、装置及系统
CN113660115B (zh) * 2021-07-28 2023-10-03 上海纽盾科技股份有限公司 基于告警的网络安全数据处理方法、装置及系统
CN113726555A (zh) * 2021-08-02 2021-11-30 华迪计算机集团有限公司 一种适用于数据通信网络辅助解析告警的系统及方法

Also Published As

Publication number Publication date
CN106714216A (zh) 2017-05-24

Similar Documents

Publication Publication Date Title
WO2018006789A1 (zh) 一种参数校验方法和装置、以及网管服务器和计算机存储介质
CN103812726A (zh) 一种数据通信设备的自动化测试方法及装置
WO2022104396A9 (en) Active assurance for virtualized services
WO2017016386A1 (zh) 一种实现射频拉远单元故障分析的方法和装置
CN105450463B (zh) 硬件设备的调试方法、装置和系统
EP3420681A1 (en) Cloud verification and test automation
US20020162059A1 (en) Methods and systems for testing communications network components
WO2021114812A1 (zh) 数据采集方法、装置、计算机设备及计算机可读介质
US11405302B1 (en) Methods, systems, and computer readable media for network testing using configurable test infrastructure
CN105052076B (zh) 一种基于云计算的网元管理系统及网元管理方法
WO2021120544A1 (zh) 用于调试设备的方法及装置
CN107566513B (zh) 测试设备dos环境数据采集方法和系统
WO2020207105A1 (zh) 目的报文的确定方法及装置、存储介质、电子装置
CN111435227B (zh) 一种智能家居设备测试方法、装置、设备及介质
CN106708717B (zh) 一种开发调试方法及装置
CN110677322A (zh) 一种基于Python语言的工控安全设备自动化测试系统及方法
CN107231275B (zh) 用于用户设备与家居设备连接配置的方法
CN107172013B (zh) 一种数据传输方法及系统
CN105827462B (zh) 一种检测网络设备的方法和工具
CN113127009A (zh) 大数据管理平台的自动化部署方法和装置
US20220224616A1 (en) End-to-End Network Performance Measurement, Diagnosis, and Tuning
CN112433938A (zh) 移动端应用测试的方法和装置
CN111314805B (zh) 一种gpon系统互通omci消息的调试方法和装置
CN114172832A (zh) 物联网测试方法、装置、中控设备及计算机设备
US20190230538A1 (en) Apparatus, system and method for testing of communication networks

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: 16829752

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: 16829752

Country of ref document: EP

Kind code of ref document: A1