WO2014180450A1 - 通信运营商网管设备的检测方法及装置、计算机存储介质 - Google Patents

通信运营商网管设备的检测方法及装置、计算机存储介质 Download PDF

Info

Publication number
WO2014180450A1
WO2014180450A1 PCT/CN2014/080019 CN2014080019W WO2014180450A1 WO 2014180450 A1 WO2014180450 A1 WO 2014180450A1 CN 2014080019 W CN2014080019 W CN 2014080019W WO 2014180450 A1 WO2014180450 A1 WO 2014180450A1
Authority
WO
WIPO (PCT)
Prior art keywords
detected
network management
management equipment
solution
management device
Prior art date
Application number
PCT/CN2014/080019
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 WO2014180450A1 publication Critical patent/WO2014180450A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and apparatus for detecting a network management device of a communication carrier, and a computer storage medium. Background technique
  • the main purpose of the embodiments of the present invention is to provide a method and device for detecting a network management device of a communication carrier, and a computer storage medium, which are intended to obtain the detection result of the network management device more quickly, and improve the working efficiency and detection efficiency of the network management device.
  • the embodiment of the present invention provides a method for detecting a network management device of a communication carrier.
  • the method includes: when receiving a detection instruction including the identity information of the network management device to be detected, the server according to the identity information of the network management device to be detected in the received detection instruction, Obtain the type of network management device to be detected.
  • the server determines, according to the mapping relationship between the pre-stored network management device type and the detection item, the to-be-detected item corresponding to the type of the network management device to be detected.
  • the server detects the to-be-detected network management device according to the determined item to be detected, and generates a detection result of each of the items to be detected.
  • the method further includes:
  • the server compares the generated test results with the corresponding pre-stored standard results to determine whether the network device to be detected is abnormal.
  • the server determines that the network device to be detected is abnormal when the difference between the generated detection result and the corresponding pre-stored standard result is greater than a preset threshold.
  • the method further comprises: after the step of determining that the network device to be detected has an abnormality, the method further comprises: after the step of determining that the network device to be detected is abnormal, when the difference between the generated detection result and the corresponding pre-stored standard result is greater than a preset threshold, the method further includes:
  • the server determines that the abnormality type of the network management device to be detected is abnormal, and obtains a solution corresponding to the determined abnormal type according to the mapping relationship between the pre-existing abnormal type and the solution; the server performs the network device to be detected according to the obtained solution. Make a repair.
  • the step of determining, by the server, the abnormal type of the abnormality of the to-be-detected network management device, and obtaining the solution corresponding to the determined abnormal type according to the mapping relationship between the pre-existing abnormal type and the solution includes:
  • the server determines that the abnormality type of the network management device to be detected is abnormal, and obtains all the solutions corresponding to the determined abnormality type according to the mapping relationship between the pre-stored abnormal type and the solution;
  • the server determines the solution with the highest priority among all the obtained solutions according to the priority order of each solution as the solution of the network device to be detected.
  • the server performs the to-be-detected network management device according to the obtained solution.
  • the method further includes:
  • the server determines whether the repair is successful
  • the server determines whether there is a candidate solution in all the obtained solutions
  • the server determines the solution with the highest priority order among the candidate solutions as the solution of the network device to be detected;
  • the server repairs the to-be-detected network management device according to the determined solution.
  • the embodiment of the invention further provides a detecting device for a network operator of a communication carrier, the device comprising:
  • the acquiring module is configured to obtain, according to the identity information of the network management device to be detected in the received detection instruction, the type of the network management device to be detected, when receiving the detection instruction that includes the identity information of the network device to be detected;
  • a processing module configured to determine, according to a mapping relationship between the pre-stored network management device type and the detection item, the to-be-detected item corresponding to the type of the network management device to be detected;
  • a detecting module configured to detect the to-be-detected network management device according to the determined item to be detected; and generate a module, configured to generate a detection result of each of the items to be detected.
  • the apparatus further comprises an analysis module,
  • the analyzing module is further configured to compare the generated each detection result with a corresponding pre-stored standard result to determine whether the network device to be detected is abnormal;
  • the device further comprises a repair module
  • the processing module is further configured to determine an abnormal type of the abnormality of the to-be-detected network management device, and obtain a solution corresponding to the determined abnormal type according to the mapping relationship between the pre-stored abnormal type and the solution;
  • the repairing module is configured to repair the to-be-detected network management device according to the obtained solution.
  • the processing module is further configured to determine an abnormal type of the abnormality of the to-be-detected network management device, and obtain all solutions corresponding to the determined abnormal type according to the mapping relationship between the pre-stored abnormal type and the solution;
  • the solution with the highest priority among all the obtained solutions is determined as the solution of the network device to be detected.
  • the analysis module is further configured to determine whether the repair is successful.
  • the processing module is further configured to: when there is a candidate solution to be selected, select a solution with the highest priority order from the candidate solutions;
  • the repair module is further configured to repair the to-be-detected network management device according to the determined solution.
  • Embodiments of the present invention also provide a computer storage medium in which computer executable instructions are stored, the computer executable instructions being used to perform the above method.
  • the method and device for detecting the network management device of the communication carrier according to the embodiment of the present invention, and the computer storage medium the server obtains the type of the network management device to be detected according to the identity information of the network management device to be detected included in the detection instruction, and determines the acquired network management device to be detected.
  • the server determines the corresponding network device to be detected according to the determined network management device to be detected, and generates a detection result of each of the detection items.
  • FIG. 1 is a schematic flowchart diagram of a first embodiment of a method for detecting a network management device of a communication carrier according to the present invention
  • FIG. 2 is a schematic flow chart of a second embodiment of a method for detecting a network management device of a communication carrier according to the present invention
  • FIG. 3 is a schematic flowchart of a third embodiment of a method for detecting a network management device of a communication carrier according to the present invention.
  • FIG. 4 is a schematic flow chart of a fourth embodiment of a method for detecting a network management device of a communication carrier according to the present invention.
  • FIG. 5 is a functional block diagram of a first embodiment of a device for detecting a network management device of a communication carrier according to the present invention
  • Figure 6 is a functional block diagram of a second embodiment of a device for detecting a network management device of a communication carrier according to the present invention
  • Figure 7 is a functional block diagram of a third embodiment of a device for detecting a network management device of a communication carrier according to the present invention.
  • the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
  • FIG. 1 is a schematic flowchart diagram of a first embodiment of a method for detecting a network management device of a communication carrier according to the present invention.
  • the server When receiving the detection instruction including the identity information of the network management device to be detected, the server obtains the type of the network management device to be detected according to the identity information of the network management device to be detected in the received detection instruction; The server determines, according to the mapping relationship between the pre-stored network management device type and the detection item, the to-be-detected item corresponding to the type of the network management device to be detected; the server detects the to-be-detected network management device according to the determined item to be detected, and generates each to be detected. The test results of the project.
  • Step S11 The server obtains the type of the network management device to be detected according to the identity information of the network management device to be detected in the received detection command, when receiving the detection instruction including the identity information of the network management device to be detected.
  • the communication operation system includes a server, a network management device, and the like, and the server communicates with each network management device.
  • the network management device needs to obtain a server user name and password through registration, and the server centrally manages each network management device connected with the network management device.
  • the server provides a human-computer interaction interface for the user to browse or control the operation.
  • the user inputs a detection instruction through the human-computer interaction interface provided by the server.
  • the detection instruction includes the identity information of the network management device to be detected, and the user can input the identity information of each network management device to be detected one by one. Or, the identity information of the network management device to be detected may be imported in batches.
  • the identity information may be the IP address of the network management device, or the information such as the login user name or the network management device identifier of the network management device that can identify the network management device.
  • the server receives the network management device detection command, it determines, according to the identity information of the network management device to be detected in the received detection command, and obtains the type of the network management device to be detected according to the mapping relationship between the network management device identity information and the network management device type.
  • the server may acquire the network management device to be detected and determine the type of the network management device to be detected when the communication network is faulty, and the preset time may be 10s. The time period set by the user, such as the 30s, based on factors such as the running status of the network management device or the time interval when the network management device fails.
  • Step S12 The server determines, according to the mapping relationship between the pre-stored network management device type and the detection item, the to-be-detected item corresponding to the type of the network management device to be detected.
  • Step S13 The server detects the to-be-detected network management device according to the determined item to be detected, and A detection result of each of the items to be detected is generated.
  • the server pre-stores the types of the network management device and the corresponding detection items. After obtaining the type of the network management device to be detected, determining the type of the network management device to be detected according to the mapping relationship between the pre-stored network management device type and the detection item. Test items.
  • the item to be detected may be an operating parameter of the operating system of the network management device, an operating parameter of the database, or an operating parameter of the software, and the like, which may affect the operation of the network management device.
  • the server After determining the to-be-detected item corresponding to the type of the network device to be detected, the server detects the to-be-detected network management device according to the determined item to be detected, and if the type of the network management device to be detected is determined to be multiple network management device types, the server follows the The to-be-detected item detects the corresponding type of network management device to be detected, that is, the detection value corresponding to the item to be detected is obtained from the network management device to be detected, and the detection result of each item to be detected is generated.
  • the server obtains the to-be-detected network management device type according to the identity of the network management device to be detected included in the detection instruction, and determines the to-be-detected item corresponding to the to-be-detected network management device, and the server detects the corresponding to-be-detected according to the determined network management device to be detected.
  • the network management device generates a detection result of each of the detection items.
  • the server automatically detects the same type of network management device to be detected, and does not need to find the corresponding network management device to process the detection result of the network management device. This improves the working efficiency and detection efficiency of the network management device.
  • FIG. 2 it is a schematic flowchart of a second embodiment of a method for detecting a network management device of a communication carrier according to the present invention.
  • the method further includes:
  • Step S14 The server compares the generated detection results with the corresponding pre-stored standard results to determine whether the network device to be detected is abnormal.
  • step S15 the server determines that the network device to be detected is abnormal when the difference between the generated detection result and the corresponding pre-stored standard result is greater than a preset threshold.
  • the server receives the sent by each network device to be detected, and the corresponding check is to be detected.
  • the detection result of the item is measured, the detection result of each item to be detected of each network device to be detected is generated.
  • the server pre-stores the standard result of each item to be detected.
  • the standard result is a reasonable running parameter value of the network management device during the actual running process, and may also be a parameter value that is set in advance by the user when the network management device is expected to operate normally.
  • the server determines and correspondingly pre-stores If the difference between the standard results is greater than the preset threshold, the corresponding detection network management device is abnormal.
  • the preset threshold is set to 0 when the network management device is abnormal, that is, the detection result of the item to be detected and the pre-stored standard
  • the result is completely consistent.
  • the party determines that the item to be detected of the network management device to be detected is normal.
  • the detection item of the network management device to be detected is available storage space, and the standard result of the available storage space is 500 MB of available storage space.
  • the available storage space of the device to be detected is detected, and the result of the available storage space of the device to be detected is generated, that is, how much storage space is currently remaining in the device to be detected, and the detection result is to be detected. If the available storage space of the device is greater than 500 MB, it is determined that the network management device to be detected is abnormal. If the detection result is that the available storage space of the device to be detected is less than 500 MB, it is determined that the network management device to be detected is abnormal.
  • the preset threshold may be set according to the tolerance difference value, that is, when the difference between the detection result of the item to be detected and the pre-stored standard result is within the tolerance range, Determining that the network management device to be detected has no abnormality.
  • the detection item of the network management device to be detected is an available storage space
  • the standard result of the available storage space is 500 MB of available storage space
  • the preset threshold value is 100 MB larger than the standard storage result.
  • Detecting, generating, and generating available storage space of the device to be detected The result of the available storage space of the device to be tested, that is, the amount of storage space of the device to be detected. If the detection result is that the available storage space of the device to be detected is greater than 600 MB, it is determined that the network device to be detected has no abnormality, and the detection result is to be detected. If the available storage space of the device is less than 600 MB, it is determined that the device to be detected is abnormal.
  • the preset threshold is set according to a required value of a normal operation parameter of the network management device.
  • the server automatically detects the same type of network management device to be detected, and compares the generated detection result of each to-be-detected item with the corresponding pre-stored standard result to determine whether the network management device to be detected has an abnormality. Then find the corresponding network management equipment provider for processing, so as to quickly determine whether each network management equipment has failed, and improve the efficiency of the network management equipment.
  • FIG. 3 it is a schematic flowchart of a third embodiment of a method for detecting a network management device of a communication carrier according to the present invention.
  • the method further includes:
  • Step S16 The server determines that the abnormality type of the network management device to be detected is abnormal, and obtains a solution corresponding to the determined abnormal type according to the mapping relationship between the pre-stored abnormal type and the solution;
  • Step S17 The server repairs the to-be-detected network management device according to the determined solution.
  • the server determines that the abnormality of the identity information of the network device to be detected is abnormal after the difference between the generated detection result and the corresponding pre-stored standard result is greater than a preset threshold.
  • the server pre-stores a solution corresponding to each exception type, and some exception types have at least one corresponding solution.
  • the server obtains the solution corresponding to the determined abnormal type according to the mapping relationship between the pre-existing abnormal type and the solution. When the solution corresponding to the determined abnormal type is obtained, the server performs the network device to be detected according to the obtained solution.
  • the server obtains the solution corresponding to each abnormal type according to the mapping relationship between the pre-stored abnormal type and the solution, and correspondingly according to the obtained solution.
  • the network management device to be tested is repaired.
  • the detection item of the network management device to be tested is to be used to detect the available storage space of the network management device.
  • the standard result is 500 MB
  • the preset threshold value is 0 MB of the available storage space than the standard result.
  • the detection result is available for the network management device to be detected. When the storage space is 400 MB, it is determined that the network device to be detected is abnormal.
  • the corresponding solution is to delete some data stored by the device to be detected, and some data that is far away from the current time point may be deleted, or a segment may be deleted.
  • the data that is not browsed is deleted in the time, and the data stored in the network management device to be detected is deleted according to other rules.
  • the preset rule may be the foregoing two types, or may be set by other users in advance. Data deletion conditions.
  • the server determines that the abnormality type of the network device to be detected is abnormal, and obtains the determined abnormal type according to the mapping relationship between the pre-stored abnormal type and the solution. All solutions; the server determines the solution with the highest priority among all the acquired solutions according to the priority order of each solution as the solution of the network device to be detected.
  • the server determines that the abnormality type of the network management device to be detected is abnormal, and obtains a solution corresponding to the determined abnormal type according to the mapping relationship between the pre-stored abnormal type and the solution, and the solution according to the obtained solution.
  • the network management device to be tested is repaired. Therefore, the solution can be quickly found according to the abnormal type of the abnormality of the network management device to be detected, and the corresponding network management device is repaired, and the faulty network management device is quickly located and automatically repaired, thereby effectively preventing the equipment supply from being found for a long time.
  • the service solves the communication abnormality caused by the fault and improves the efficiency of the network management equipment fault resolution.
  • Step S18 The server determines whether the repair is successful
  • Step S19 When the repair fails, the server determines whether there is a solution to be selected in all the obtained solutions;
  • step S20 the server determines the solution with the highest priority in the candidate solution as the solution of the to-be-detected network management device when there is a solution to be selected;
  • Step S21 The server repairs the to-be-detected network management device according to the determined solution.
  • the server determines whether the repair is successful, and the preset time may be 0.5s or Is, according to the performance of the network management device.
  • the server determines whether there is a solution to be selected in all the solutions obtained.
  • the server determines the solution with the highest priority order among the solutions to be detected as the network device to be detected.
  • the solution server repairs the to-be-detected network management device according to the determined solution.
  • the user interface is prompted to add a new solution, because the existing solution can not solve the current exception type.
  • a repair failure 4 notification is also generated, so that the user can find a reasonable solution that can solve the abnormal type of the unsuccessful repair, so as to timely repair and recover the communication.
  • FIG. 5 it is a functional block diagram of a first embodiment of a detecting device of a communication carrier network management device according to the present invention.
  • the device includes: an obtaining module 10, a processing module 20, a detecting module 30, and a generating module 40,
  • the obtaining module 10 is configured to obtain, according to the identity information of the network management device to be detected in the received detection instruction, the type of the network management device to be detected, when receiving the detection instruction that includes the identity information of the network device to be detected.
  • the communication operation system includes a server, a network management device, and the like, and the server communicates with each network management device.
  • the network management device needs to obtain a server user name and password through registration, and the server centrally manages each network management device connected with the network management device.
  • the server provides a human-computer interaction interface for the user to browse or control the operation.
  • the user inputs a detection instruction through the human-computer interaction interface provided by the server.
  • the detection instruction includes the identity information of the network management device to be detected, and the user can input the identity information of each network management device to be detected one by one. Or, the identity information of the network management device to be detected may be imported in batches.
  • the identity information may be the IP address of the network management device, or the information such as the login user name or the network management device identifier of the network management device that can identify the network management device.
  • the detecting device of the communication carrier network management device is preferably a server, and may also be other devices that centrally control all network management devices.
  • the obtaining module 10 determines the identity of the network management device to be detected according to the received network device identity information in the received detection command, and obtains the network device type to be detected according to the mapping relationship between the network management device identity information and the network management device type.
  • the acquiring module 10 obtains the network management device to be detected, and determines the type of the network management device to be detected, when the preset time arrives, or the communication operation network fails. It is the time period set by users such as 10s or 30s according to factors such as the running status of the network management device or the time interval when the network management device fails.
  • the processing module 20 is configured to determine, according to a mapping relationship between the pre-stored network management device type and the detection item, the to-be-detected item corresponding to the acquired network management device type to be detected;
  • the detecting module 30 is configured to detect the to-be-detected network management device according to the determined item to be detected;
  • the generating module 40 is configured to generate a detection result of each of the items to be detected.
  • the server pre-stores each network management device type and its corresponding detection item
  • the processing module 20 determines, according to the mapping relationship between the pre-stored network management device type and the detection item, the to-be-detected item corresponding to the type of the network management device to be detected.
  • the item to be detected may be an operating parameter of an operating system of the network management device, an operating parameter of the database, or an operating parameter of the software, and any other items that may affect the operation of the network management device.
  • the detecting module 30 detects the network device to be detected according to the determined item to be detected, and determines that the type of the network device to be detected is a plurality of network management devices. When the type is detected, the detecting module 30 detects the corresponding type of the network management device to be detected according to the item to be detected, that is, obtains the detection value corresponding to the item to be detected from the network device to be detected, and generates a detection result of each item to be detected.
  • the acquiring module 10 obtains the to-be-detected network management device type according to the identity information of the network management device to be detected included in the detection instruction, and the processing module 20 determines the to-be-detected item corresponding to the to-be-detected network management device, and the detection module 30 is determined to be detected according to the determination.
  • the network management device detects the corresponding network management device to be detected and generates a detection result of each of the detection items through the generation module 40.
  • the server automatically detects the same type of network management device to be detected, and does not need to find the corresponding network management device to process the detection result of the network management device. This improves the working efficiency and detection efficiency of the network management device.
  • FIG. 6 is a functional block diagram of a second embodiment of a detecting apparatus for a network operator of a communication carrier according to the present invention.
  • the apparatus also includes an analysis module 50,
  • the analyzing module 50 is further configured to compare the generated each detection result with a corresponding pre-stored standard result to determine whether the network device to be detected is abnormal;
  • the generating module 40 when receiving the detection result of the corresponding item to be detected sent by each to-be-detected network management device, generates a detection result of each item to be detected of each network device to be detected.
  • the standard result is network management equipment
  • the value of the reasonable running parameter in the actual running process may also be the parameter value that the user expects in advance to expect the network management device to operate normally.
  • the analysis module 50 compares the generated detection result of each item to be detected with the corresponding pre-stored standard result to determine whether the network device to be detected has an abnormality, that is, analyzes the detection result of the item to be detected of the network device to be detected.
  • the corresponding detection network management device is abnormal.
  • the preset threshold is set to 0 when the network management device is abnormal, that is, the detection result of the item to be detected and the pre-stored standard The result is completely consistent.
  • the analysis module 50 determines that the item to be detected of the to-be-detected network management device has no abnormality.
  • the detection item of the network management device to be detected is available storage space
  • the standard result of the available storage space is 500 MB of available storage space.
  • the threshold value is 0 MB larger than the standard result
  • the detecting module 30 detects the available storage space of the device to be detected
  • the generating module 40 generates a result of the available storage space of the device to be detected, that is, how much storage is currently stored in the device to be detected.
  • the analysis module 50 determines that the network device to be detected has no abnormality when the detection result is that the available storage space of the device to be detected is greater than 500 MB.
  • the analysis module 50 determines that the storage is Detecting that the network management device is abnormal; when the network management device to be detected If the detection result of a certain item to be detected is different from the pre-stored standard detection result, the preset threshold value may be set according to the tolerance difference value, that is, the detection of the item to be detected. When the difference between the result and the pre-stored standard result is within the tolerance range, the analysis module 50 determines that the network device to be detected has no abnormality, for example, the detection item of the network management device to be detected is an available storage space, and the standard result of the available storage space is the available storage.
  • the space is 500 MB, and the preset threshold is 100 MB larger than the standard result.
  • the detecting module 30 detects the available storage space of the device to be detected, and the generating module 40 generates the available storage space of the device to be detected, that is, the to-be-detected. Assume How much storage space is currently available, and the detection result is that the available storage space of the device to be tested is greater than
  • the analysis module 50 determines that the network management device to be detected has no abnormality. When the detection result indicates that the available storage space of the device to be tested is less than 600 MB, the analysis module 50 determines that the network management device to be detected is abnormal.
  • the preset threshold may be 0 or 1.5, and any applicable user may set according to the required value of the operating parameters of the network management device.
  • the detection module 30 automatically detects the same type of network management device to be detected, and compares the detection result of each to-be-detected item with the corresponding pre-stored standard result by the analysis module 50 to determine the network management to be detected. If the device is abnormal, you do not need to find the corresponding network management device provider to process it, so as to determine whether each network management device is faulty and improve the working efficiency of the network management device.
  • FIG. 7 it is a functional block diagram of a third embodiment of a detecting apparatus for a network operator of a communication carrier according to the present invention.
  • the device also includes a repair module 60,
  • the processing module 20 is further configured to determine an abnormal type of the abnormality of the to-be-detected network management device, and obtain a solution corresponding to the determined abnormal type according to the mapping relationship between the pre-stored abnormal type and the solution;
  • the repairing module 60 is configured to repair the to-be-detected network management device according to the obtained solution.
  • the analysis module 50 determines that the network device to be detected has an abnormality
  • the processing module 20 determines that the network device to be detected has an abnormality.
  • the processing module 20 obtains the solution corresponding to the determined abnormal type according to the mapping relationship between the pre-existing abnormal type and the solution.
  • the repairing module 60 follows the acquired solution.
  • the processing module 20 obtains the solution corresponding to each abnormal type according to the mapping relationship between the pre-existing abnormal type and the solution, and repairs the corresponding network device to be detected according to the obtained solution by the repairing module 60.
  • the detection item of the network management device to be detected is to be used to detect the available storage space of the network management device.
  • the standard result is 500 MB
  • the preset threshold is 0 MB as the available storage space is larger than the standard result. The detection result is available for the network management device to be detected.
  • the analysis module 50 determines that the network device to be detected has an abnormality, and the corresponding determining solution is that the repair module 60 deletes some data stored by the device to be detected, and may be far away from the current time point.
  • the preset rule may be the above two types, It can be a data deletion condition set by other users in advance.
  • the processing module 20 determines that the abnormality type of the to-be-detected network management device is abnormal, and obtains the determined abnormal type according to the mapping relationship between the pre-stored abnormal type and the solution. Corresponding all solutions; The processing module 20 determines, according to the priority order of the respective solutions, the solution with the highest priority order among all the obtained solutions as the solution of the network device to be detected.
  • the processing module 20 obtains an abnormal type of the abnormality of the network device to be detected, and obtains a solution corresponding to the determined abnormal type according to the mapping relationship between the pre-stored abnormal type and the solution, and obtains the solution according to the repair module 60.
  • the solution repairs the network management device to be detected. Therefore, the solution can be quickly found according to the abnormal type of the abnormality of the network management device to be detected, and the corresponding network management device is repaired, and the faulty network management device is quickly located and automatically repaired, thereby effectively preventing the equipment supply from being found for a long time.
  • the service solves the communication abnormality caused by the fault and improves the efficiency of the network management equipment fault resolution.
  • the analyzing module 50 is further configured to determine whether the repair is successful; and
  • the processing module 20 is further configured to: when there is a candidate solution to be selected, select a solution with the highest priority order from the candidate solutions;
  • the repair module 60 is further configured to repair the to-be-detected network management device according to the determined solution.
  • the analysis module 50 determines whether the repair is successful, and the preset time may be 0.5s or Is, etc.
  • the time period set in advance according to factors such as the performance of the network management device; when the repair is successful, a repair success report of each item to be detected is generated, and the report includes data of any repair process such as the repaired item, the repaired solution, and the time required for the repair. , in order to allow users to select a better repair solution through various repairs, or to find out the cause of the failure, etc., to avoid the same failure again.
  • the analysis module 50 determines whether there is a candidate solution to be selected among all the obtained solutions.
  • the processing module 20 determines the solution with the highest priority order among the candidate solutions as the The solution server of the network management device to be tested repairs the network management device to be detected according to the determined solution.
  • the user interface is prompted to add a new solution, because the existing solution can not solve the current exception type.
  • a repair failure 4 error is generated, so that the user can find a reasonable solution that can solve the abnormal type of the unsuccessful repair, so as to timely repair and recover the communication.
  • Each of the above units may be implemented by a central processing unit (CPU), a digital signal processor (DSP) or a Field-Programmable Gate Array (FPGA) in the electronic device.
  • CPU central processing unit
  • DSP digital signal processor
  • FPGA Field-Programmable Gate Array
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware aspects. Moreover, the invention may be employed in one or more of its A computer program product embodied on a computer usable storage medium (including but not limited to disk storage and optical storage, etc.) containing computer usable program code.
  • a computer usable storage medium including but not limited to disk storage and optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • the embodiment of the present invention further provides a computer storage medium, wherein computer executable instructions are stored, and the computer executable instructions are used to execute the method described in any of the above embodiments.

Abstract

本发明公开了一种通信运营商网管设备的检测方法及装置、计算机存储介质，该方法包括：服务器根据检测指令中包括的待检测网管设备身份信息，获取待检测网管设备类型，确定获取的待检测网管设备对应的待检测项目，服务器按照确定的待检测网管设备检测对应的待检测网管设备并生成各个所述检测项目的检测结果。该装置相应的包括：获取模块，用于根据接收的检测指令中的待检测网管设备身份信息，获取待检测网管设备类型；处理模块，用于确定获取的待检测网管设备类型对应的待检测项目；检测模块，用于按照确定的待检测项目检测所述待检测网管设备；生成模块，用于生成各个所述待检测项目的检测结果。

Description

通信运营商网管设备的检测方法及装置、 计算 储介质 技术领域
本发明涉及到通信领域， 特别涉及到通信运营商网管设备的检测方法 及装置、 计算机存储介质。 背景技术
基于现有移动通信领域多代（2G、 3G和 4G )技术共存的现状： 通信 运营商在线运行的系统和设备无论是种类还是数量越来越多， 分布也越来 越广； 尤其是对于那些大的跨国通信运营商而言， 往往会同时采购和部署 多个设备供应商的系统和设备； 就算是同一个设备供应商的系统和设备， 有时也会因为分属于不同的产品体系等因素， 造成与各种设备对应的网管 系统千差万别， 不仅数量多而杂， 而且不便于统一监管。
虽然有些通信运营商部分实现了集中监管， 且不同供应商的同类型网 管设备具有较多的共性， 然而在出故障时， 通信运营商还是得找对应的设 备供应商分析和处理， 不仅耗时费力， 很多时候还面临设备商 /部门之间互 相推诿的问题， 网管设备工作效率及检测效率较低。 发明内容
本发明实施例的主要目的为提供一种通信运营商网管设备的检测方法 及装置、 计算机存储介质， 旨在更快的获取到网管设备的检测结果， 提高 网管设备的工作效率及检测效率。
本发明实施例提出一种通信运营商网管设备的检测方法， 该方法包括： 服务器在接收到包括待检测网管设备身份信息的检测指令时， 根据接 收的检测指令中的待检测网管设备身份信息， 获取待检测网管设备类型； 服务器根据预存的网管设备类型与检测项目的映射关系， 确定获取的 待检测网管设备类型对应的待检测项目；
服务器按照确定的待检测项目检测所述待检测网管设备， 并生成各个 所述待检测项目的检测结果。
优选地， 所述服务器按照确定的待检测项目检测所述待检测网管设备， 并生成各个所述待检测项目的检测结果的步骤之后， 该方法还包括：
服务器将生成的各个检测结果与对应的预存标准结果进行比对， 以确 定所述待检测网管设备是否存在异常；
在有生成的检测结果与对应的预存标准结果的差值大于预设阀值时， 服务器确定所述待检测网管设备存在异常。
优选地， 所述在有生成的检测结果与对应的预存标准结果的差值大于 预设阀值时， 服务器确定所述待检测网管设备存在异常的步骤之后， 该方 法还包括：
服务器确定所述待检测网管设备存在异常的异常类型， 并根据预存的 异常类型与解决方案的映射关系， 获取确定的异常类型对应的解决方案； 服务器按照获取的解决方案对所述待检测网管设备进行修复。
优选地， 所述服务器确定所述待检测网管设备存在异常的异常类型， 并根据预存的异常类型与解决方案的映射关系， 获取确定的异常类型对应 的解决方案的步骤包括：
服务器确定所述待检测网管设备存在异常的异常类型， 并根据预存的 异常类型与解决方案的映射关系， 获取确定的异常类型对应的所有解决方 案；
服务器根据各个解决方案的优先级次序， 将获取的所有解决方案中优 先级次序最高的解决方案确定为所述待检测网管设备的解决方案。
优选地， 所述服务器按照获取的解决方案对所述待检测网管设备进行 修复的步骤之后， 该方法还包括：
服务器判断修复是否成功；
在修复失败时， 服务器判断获取的所有解决方案中是否存在待选解决 方案；
在存在待选解决方案时， 服务器将待选解决方案中优先级次序最高的 解决方案确定为所述待检测网管设备的解决方案；
服务器按照确定的解决方案对所述待检测网管设备进行修复。 本发明实施例还提出一种通信运营商网管设备的检测装置， 该装置包 括：
获取模块， 用于在接收到包括待检测网管设备身份信息的检测指令时， 根据接收的检测指令中的待检测网管设备身份信息， 获取待检测网管设备 类型；
处理模块， 用于根据预存的网管设备类型与检测项目的映射关系， 确 定获取的待检测网管设备类型对应的待检测项目；
检测模块， 用于按照确定的待检测项目检测所述待检测网管设备； 生成模块， 用于生成各个所述待检测项目的检测结果。
优选地， 该装置还包括分析模块，
所述分析模块， 还用于将生成的各个检测结果与对应的预存标准结果 进行比对， 以确定所述待检测网管设备是否存在异常； 及
在有生成的检测结果与对应的预存标准结果的差值大于预设阀值时， 确定所述待检测网管设备存在异常。
优选地， 该装置还包括修复模块，
所述处理模块， 还用于确定所述待检测网管设备存在异常的异常类型， 并根据预存的异常类型与解决方案的映射关系， 获取确定的异常类型对应 的解决方案； 所述修复模块， 用于按照获取的解决方案对所述待检测网管设备进行 修复。
优选地， 所述处理模块， 还用于确定所述待检测网管设备存在异常的 异常类型， 并根据预存的异常类型与解决方案的映射关系， 获取确定的异 常类型对应的所有解决方案； 及
根据各个解决方案的优先级次序， 将获取的所有解决方案中优先级次 序最高的解决方案确定为所述待检测网管设备的解决方案。
优选地， 所述分析模块， 还用于判断修复是否成功； 及
在修复失败时， 判断与该网管设备异常项目对应的解决方案中是否存 在待选解决方案；
所述处理模块， 还用于在存在待选解决方案时， 从待选解决方案中选 择优先级次序最高的解决方案；
所述修复模块， 还用于按照确定的解决方案对所述待检测网管设备进 行修复。 本发明实施例还提出一种计算机存储介质， 其中存储有计算机可执行 指令， 所述计算机可执行指令用于执行上述的方法。 本发明实施例所述的通信运营商网管设备的检测方法及装置、 计算机 存储介质， 服务器根据检测指令中包括的待检测网管设备身份信息， 获取 待检测网管设备类型， 确定获取的待检测网管设备对应的待检测项目， 月良 务器按照确定的待检测网管设备检测对应的待检测网管设备并生成各个所 述检测项目的检测结果。 通过服务器自动对相同类型的待检测网管设备进 行检测， 不必再找相应的网管设备提供商进行处理， 从而能够更快的获取 到网管设备的检测结果， 提高网管设备的工作效率及检测效率。 附图说明 图 1 为本发明通信运营商网管设备的检测方法的第一实施例的流程示 意图；
图 2为本发明通信运营商网管设备的检测方法的第二实施例的流程示 意图；
图 3 为本发明通信运营商网管设备的检测方法的第三实施例的流程示 意图；
图 4为本发明通信运营商网管设备的检测方法的第四实施例的流程示 意图；
图 5 为本发明通信运营商网管设备的检测装置的第一实施例的功能模 块图；
图 6为本发明通信运营商网管设备的检测装置的第二实施例的功能模 块图； 图 7为本发明通信运营商网管设备的检测装置的第三实施例的功能模 块图。 具体实施方式 应当理解， 此处所描述的具体实施例仅仅用以解释本发明， 并不用于 限定本发明。
如图 1 所示， 为本发明通信运营商网管设备的检测方法的第一实施例 的流程示意图。
需要强调的是： 图 1 所示流程图仅为一个较佳实施例， 本领域的技术 人员当知， 任何围绕本发明思想构建的实施例都不应脱离于如下技术方案 涵盖的范围：
服务器在接收到包括待检测网管设备身份信息的检测指令时， 根据接 收的检测指令中的待检测网管设备身份信息， 获取待检测网管设备类型； 服务器根据预存的网管设备类型与检测项目的映射关系， 确定获取的待检 测网管设备类型对应的待检测项目； 服务器按照确定的待检测项目检测所 述待检测网管设备， 并生成各个所述待检测项目的检测结果。
以下是本实施例逐步实现对通信运营商网管设备进行检测的具体步 骤：
步骤 Sll， 服务器在接收到包括待检测网管设备身份信息的检测指令 时， 根据接收的检测指令中的待检测网管设备身份信息， 获取待检测网管 设备类型。
具体的， 通信运营系统包括服务器， 网管设备等其他设备， 服务器与 各个网管设备进行通信连接， 网管设备需通过注册获取一个服务器的用户 名和密码， 服务器对各个与其通信连接的网管设备进行集中管理， 服务器 提供人机交互界面供用户进行浏览或控制操作， 用户通过服务器提供的人 机交互界面输入检测指令， 该检测指令中包括待检测网管设备身份信息， 用户可以逐个输入各个待检测网管设备身份信息或批量导入待检测网管设 备身份信息， 所述身份信息可以是网管设备的 IP地址， 也还可是网管设备 的登录用户名或网管设备识别码等唯一能识别出网管设备的信息。 当服务 器接收到网管设备检测指令时， 确定根据接收的检测指令中的待检测网管 设备身份信息， 根据网管设备身份信息与网管设备类型的映射关系， 获取 各个待检测网管设备类型。 在本发明其他实施例中， 也还可以是， 在预设 时间到达， 或通信运营网络出现故障时， 服务器获取待检测网管设备， 并 确定待检测网管设备类型；所述预设时间可以是 10s或 30s等用户根据网管 设备运行状态或网管设备发生故障的时间间隔等因素提前设置的时间段。
步骤 S12，服务器根据预存的网管设备类型与检测项目的映射关系，确 定获取的待检测网管设备类型对应的待检测项目。
步骤 S13，服务器按照确定的待检测项目检测所述待检测网管设备， 并 生成各个所述待检测项目的检测结果。
具体的， 服务器预存有各个网管设备类型及其对应的检测项目， 在获 取待检测网管设备类型后， 根据预存的网管设备类型与检测项目的映射关 系， 确定获取的待检测网管设备类型对应的待检测项目。 所述待检测项目 可以是网管设备操作系统的运行参数、 数据库的运行参数或软件的运行参 数等其他任意会影响网管设备运行的项目。
服务器在确定获取的待检测网管设备类型对应的待检测项目后， 按照 确定的待检测项目检测所述待检测网管设备， 若确定获取的待检测网管设 备类型为多个网管设备类型时， 服务器按照待检测项目检测对应类型的待 检测网管设备， 即从待检测网管设备获取对应待检测项目的检测值， 并生 成各个所述待检测项目的检测结果。
本实施例服务器根据检测指令中包括的待检测网管设备身份信息， 获 取待检测网管设备类型， 确定获取的待检测网管设备对应的待检测项目， 服务器按照确定的待检测网管设备检测对应的待检测网管设备并生成各个 所述检测项目的检测结果。 通过服务器自动对相同类型的待检测网管设备 进行检测， 不必再找相应的网管设备提供商进行处理， 以便更快的获取到 网管设备的检测结果， 提高网管设备的工作效率及检测效率。 如图 2所示， 为本发明通信运营商网管设备的检测方法的第二实施例 的流程示意图。
基于上述第一实施例， 在步骤 S13之后， 该方法还包括：
步骤 S14，服务器将生成的各个检测结果与对应的预存标准结果进行比 对， 以确定所述待检测网管设备是否存在异常；
步骤 S15，在有生成的检测结果与对应的预存标准结果的差值大于预设 阀值时， 服务器确定所述待检测网管设备存在异常。
具体的， 服务器在接收到各个待检测网管设备发送来的， 对应的待检 测项目的检测结果时， 生成各个待检测网管设备的各个待检测项目的检测 结果。 服务器预存有各个待检测项目的标准结果， 所述标准结果为网管设 备在实际运行过程中合理的运行参数值， 也可以是用户提前设置的期望所 述网管设备正常运行时的参数值。 将生成的各个待检测项目的检测结果， 与对应的预存标准结果进行比对， 以确定所述待检测网管设备是否存在异 常， 即分析所述待检测网管设备的待检测项目的检测结果， 是否与对应的 预存标准结果的差异是否在预设阀值之内， 在有生成的待检测项目的检测 结果， 与对应的预存标准结果的差值大于预设阀值时， 服务器确定与对应 的预存标准结果的差值大于预设阀值的待检测项目， 对应的检测网管设备 存在异常。 当所述网管设备的某个待检测项目的检测结果， 与预存标准结 果存在差异将会导致该网管设备异常时， 所述预设阀值设置为 0， 即待检测 项目的检测结果与预存标准结果完全一致， 方确定该待检测网管设备的该 项待检测项目无异常， 例如， 待检测网管设备的检测项目为可用存储空间， 可用存储空间的标准结果为可用存储空间 500MB， 预设阀值为可用存储空 间比标准结果大 0MB， 对所述待检测设备的可用存储空间进行检测， 生成 待检测设备的可用存储空间的结果， 即待检测设备目前剩余多少存储空间， 在检测结果为待检测设备的可用存储空间大于 500MB时， 确定该待检测网 管设备无异常， 在检测结果为待检测设备的可用存储空间小于 500MB时， 确定该待检测网管设备存在异常； 当所述待检测网管设备的某个待检测项 目的检测结果， 与预存标准检测结果存在一定差异不会导致所述待检测网 管设备异常时， 所述预设阀值可以根据容忍的差异值进行设置， 即待检测 项目的检测结果与预存标准结果的差值在容忍范围内时， 确定所述待检测 网管设备无异常， 例如， 待检测网管设备的检测项目为可用存储空间， 可 用存储空间的标准结果为可用存储空间 500MB， 预设阀值为可用存储空间 比标准结果大 100MB， 对所述待检测设备的可用存储空间进行检测， 生成 待检测设备的可用存储空间的结果， 即待检测设备目前剩余多少存储空间， 在检测结果为待检测设备的可用存储空间大于 600MB时， 确定该待检测网 管设备无异常， 在检测结果为待检测设备的可用存储空间小于 600MB时， 确定该待检测网管设备存在异常。 所述预设阀值根据网管设备正常运行参 数的需要值进行设定。
本实施例通过服务器自动对相同类型的待检测网管设备进行检测， 并 将生成的各个待检测项目的检测结果与对应的与预存标准结果进行比对， 以确定待检测网管设备是否存在异常， 不必再找相应的网管设备提供商进 行处理， 以便更快的确定各个网管设备是否发生故障， 提高网管设备的工 作效率。 如图 3 所示， 为本发明通信运营商网管设备的检测方法的第三实施例 的流程示意图。
基于上述第二实施例， 在步骤 S15之后， 该方法还包括：
步骤 S16，服务器确定所述待检测网管设备存在异常的异常类型， 并根 据预存的异常类型与解决方案的映射关系， 获取确定的异常类型对应的解 决方案；
步骤 S17， 服务器按照确定的解决方案对所述待检测网管设备进行修 复。
具体的， 在有生成的检测结果与对应的预存标准结果的差值大于预设 阀值时， 服务器确定所述待检测网管设备存在异常之后， 服务器确定存在 异常的待检测网管设备的身份信息及发生异常的类型。 服务器预存有各个 异常类型对应的解决方案， 且有的异常类型存在至少一个对应的解决方案。 服务器根据预存的异常类型与解决方案的映射关系， 获取确定的异常类型 对应的解决方案， 在获取到确定的异常类型对应的解决方案时， 服务器按 照获取的解决方案对所述待检测网管设备进行修复； 若多个待检测网管设 备存在异常时， 且各个待检测网管设备的异常类型不同时， 服务器根据预 存的异常类型与解决方案的映射关系， 获取确定的各个异常类型对应的解 决方案， 并按照获取的解决方案对对应的待检测网管设备进行修复。 例如， 待检测网管设备的检测项目以待检测网管设备的可用存储空间， 标准结果 以 500MB,预设阀值以可用存储空间比标准结果大 0MB为例，在检测结果 为待检测网管设备的可用存储空间为 400MB时， 确定所述待检测网管设备 存在异常， 相应的解决方案为将所述待检测设备存储的一些数据进行删除， 可以将一些离目前时间点较远的数据删除， 或将一段时间内未被浏览的数 据进行删除， 也还可以是按照其他规则将所述待检测网管设备存储的数据 进行删除， 所述预设规则可以是上述的两种， 也可以是其他用户提前设置 的数据删除条件。
进一步地， 若每个异常类型， 对应多个解决方案时， 服务器确定所述 待检测网管设备存在异常的异常类型， 并根据预存的异常类型与解决方案 的映射关系， 获取确定的异常类型对应的所有解决方案； 服务器根据各个 解决方案的优先级次序， 将获取的所有解决方案中优先级次序最高的解决 方案确定为所述待检测网管设备的解决方案。
本实施例中服务器通过确定的待检测网管设备存在异常的异常类型， 并根据预存的异常类型与解决方案的映射关系， 获取确定的异常类型对应 的解决方案， 并按照获取的解决方案对所述待检测网管设备进行修复。 以 便根据确定的待检测网管设备存在异常的异常类型快速找到解决方案， 对 对应的网管设备进行修复， 快速的对发生故障的网管设备进行定位并自动 进行修复， 有效避免长时间找不到设备供应商解决故障造成的通信异常， 提高网管设备故障解决的效率。 如图 4所示， 为本发明通信运营商网管设备的检测方法的第四实施例 的流程示意图。 基于上述第三实施例， 在步骤 S17之后， 该方法还包括： 步骤 S18， 服务器判断修复是否成功；
步骤 S19，在修复失败时，服务器判断获取的所有解决方案中是否存在 待选解决方案；
步骤 S20，在存在待选解决方案时，服务器将待选解决方案中优先级次 序最高的解决方案确定为所述待检测网管设备的解决方案；
步骤 S21， 服务器按照确定的解决方案对所述待检测网管设备进行修 复。
具体的， 在服务器按照确定的解决方案对所述待检测网管设备进行修 复后， 预设时间到达时， 服务器判断修复是否成功， 所述预设时间可以是 0.5s或 Is等用户根据网管设备性能等因素提前设置的时间段； 在修复成功 时， 生成各个待检测项目的修复成功报告， 该报告包括修复的项目， 修复 的解决方案及修复需要的时间等任意修复过程中的数据， 以供用户通过各 个修复 4艮告选择较佳的修复方案或找出发生故障的原因等， 避免再次发生 同样的故障。 在修复失败时， 服务器判断获取的所有解决方案中是否存在 待选解决方案， 在存在待选解决方案时， 服务器将待选解决方案中优先级 次序最高的解决方案确定为所述待检测网管设备的解决方案服务器按照确 定的解决方案对所述待检测网管设备进行修复。 在不存在待选解决方案时， 通过人机交互界面提示用户需添加新的解决方案， 因现有的解决方案解决 不了目前的异常类型。 同样在修复失败时， 也生成修复失败 4艮告， 以供用 户找出合理的能解决该修复不成功的异常类型的解决方案， 以便及时的对 发生的故障进行合理修复恢复通信。 如图 5 所示， 为本发明通信运营商网管设备的检测装置的第一实施例 的功能模块图。 该装置包括： 获取模块 10， 处理模块 20， 检测模块 30及 生成模块 40， 所述获取模块 10， 用于在接收到包括待检测网管设备身份信息的检测 指令时， 根据接收的检测指令中的待检测网管设备身份信息， 获取待检测 网管设备类型。
具体的， 通信运营系统包括服务器， 网管设备等其他设备， 服务器与 各个网管设备进行通信连接， 网管设备需通过注册获取一个服务器的用户 名和密码， 服务器对各个与其通信连接的网管设备进行集中管理， 服务器 提供人机交互界面供用户进行浏览或控制操作， 用户通过服务器提供的人 机交互界面输入检测指令， 该检测指令中包括待检测网管设备身份信息， 用户可以逐个输入各个待检测网管设备身份信息或批量导入待检测网管设 备身份信息， 所述身份信息可以是网管设备的 IP地址， 也还可是网管设备 的登录用户名或网管设备识别码等唯一能识别出网管设备的信息。 所述通 信运营商网管设备的检测装置优选为服务器， 也还可以是其他将所有网管 设备进行集中控制的设备。 当接收到网管设备检测指令时， 获取模块 10确 定根据接收的检测指令中的待检测网管设备身份信息， 并根据网管设备身 份信息与网管设备类型的映射关系， 获取各个待检测网管设备类型。 在本 发明其他实施例中， 也还可以是， 在预设时间到达， 或通信运营网络出现 故障时， 获取模块 10获取待检测网管设备， 并确定待检测网管设备类型； 所述预设时间可以是 10s或 30s等用户根据网管设备运行状态或网管设备发 生故障的时间间隔等因素提前设置的时间段。
所述处理模块 20， 用于根据预存的网管设备类型与检测项目的映射关 系， 确定获取的待检测网管设备类型对应的待检测项目；
所述检测模块 30， 用于按照确定的待检测项目检测所述待检测网管设 备；
所述生成模块 40， 用于生成各个所述待检测项目的检测结果。
具体的， 服务器预存有各个网管设备类型及其对应的检测项目， 在获 耳 4莫块 10获取待检测网管设备类型后， 处理模块 20根据预存的网管设备 类型与检测项目的映射关系， 确定获取的待检测网管设备类型对应的待检 测项目。 所述待检测项目可以是网管设备操作系统的运行参数、 数据库的 运行参数或软件的运行参数等其他任意会影响网管设备运行的项目。
在处理模块 20确定获取的待检测网管设备类型对应的待检测项目后， 检测模块 30按照确定的待检测项目检测所述待检测网管设备， 若确定获取 的待检测网管设备类型为多个网管设备类型时， 检测模块 30按照待检测项 目检测对应类型的待检测网管设备， 即从待检测网管设备获取对应待检测 项目的检测值， 并生成各个所述待检测项目的检测结果。
本实施例获取模块 10根据检测指令中包括的待检测网管设备身份信 息， 获取待检测网管设备类型， 处理模块 20确定获取的待检测网管设备对 应的待检测项目， 检测模块 30按照确定的待检测网管设备检测对应的待检 测网管设备并通过生成模块 40生成各个所述检测项目的检测结果。 通过服 务器自动对相同类型的待检测网管设备进行检测， 不必再找相应的网管设 备提供商进行处理， 以便更快的获取到网管设备的检测结果， 提高网管设 备的工作效率及检测效率。 如图 6所示， 为本发明通信运营商网管设备的检测装置的第二实施例 的功能模块图。 该装置还包括分析模块 50，
所述分析模块 50， 还用于将生成的各个检测结果与对应的预存标准结 果进行比对， 以确定所述待检测网管设备是否存在异常； 及
在有生成的检测结果与对应的预存标准结果的差值大于预设阀值时， 确定所述待检测网管设备存在异常。
具体的， 生成模块 40在接收到各个待检测网管设备发送来的， 对应的 待检测项目的检测结果时， 生成各个待检测网管设备的各个待检测项目的 检测结果。 预存有各个待检测项目的标准结果， 所述标准结果为网管设备 在实际运行过程中合理的运行参数值， 也可以是用户提前设置的期望所述 网管设备正常运行时的参数值。 分析模块 50将生成的各个待检测项目的检 测结果与对应的预存标准结果进行比对， 以确定所述待检测网管设备是否 存在异常， 即分析所述待检测网管设备的待检测项目的检测结果是否与对 应的预存标准结果的差异是否在预设阀值之内， 在有生成的待检测项目的 检测结果， 与对应的预存标准结果的差值大于预设阀值时， 并确定与对应 的预存标准结果的差值大于预设阀值的待检测项目， 对应的检测网管设备 存在异常。 当所述网管设备的某个待检测项目的检测结果， 与预存标准结 果存在差异将会导致该网管设备异常时， 所述预设阀值设置为 0， 即待检测 项目的检测结果与预存标准结果完全一致， 分析模块 50确定该待检测网管 设备的该项待检测项目无异常， 例如， 待检测网管设备的检测项目为可用 存储空间， 可用存储空间的标准结果为可用存储空间 500MB， 预设阀值为 可用存储空间比标准结果大 0MB，检测模块 30对所述待检测设备的可用存 储空间进行检测， 生成模块 40生成待检测设备的可用存储空间的结果， 即 待检测设备目前剩余多少存储空间， 在检测结果为待检测设备的可用存储 空间大于 500MB时， 分析模块 50确定该待检测网管设备无异常， 在检测 结果为待检测设备的可用存储空间小于 500MB时， 分析模块 50确定该待 检测网管设备存在异常； 当所述待检测网管设备的某个待检测项目的检测 结果， 与预存标准检测结果存在一定差异不会导致所述待检测网管设备异 常时， 所述预设阀值可以根据容忍的差异值进行设置， 即待检测项目的检 测结果与预存标准结果的差值在容忍范围内时， 分析模块 50确定所述待检 测网管设备无异常， 例如， 待检测网管设备的检测项目为可用存储空间， 可用存储空间的标准结果为可用存储空间 500MB， 预设阀值为可用存储空 间比标准结果大 100MB，检测模块 30对所述待检测设备的可用存储空间进 行检测， 生成模块 40生成待检测设备的可用存储空间的结果， 即待检测设 备目前剩余多少存储空间， 在检测结果为待检测设备的可用存储空间大于
600MB时，分析模块 50确定该待检测网管设备无异常，在检测结果为待检 测设备的可用存储空间小于 600MB时， 分析模块 50确定该待检测网管设 备存在异常。所述预设阀值可以是 0或 1.5等任意适用的用户根据网管设备 运行参数需要值进行设定。
本实施例通过检测模块 30 自动对相同类型的待检测网管设备进行检 测， 并通过分析模块 50将生成的各个待检测项目的检测结果与对应的与预 存标准结果进行比对， 以确定待检测网管设备是否存在异常， 不必再找相 应的网管设备提供商进行处理， 以便更快的确定各个网管设备是否发生故 障， 提高网管设备的工作效率。 如图 7 所示， 为本发明通信运营商网管设备的检测装置的第三实施例 的功能模块图。 该装置还包括修复模块 60，
所述处理模块 20， 还用于确定所述待检测网管设备存在异常的异常类 型， 并根据预存的异常类型与解决方案的映射关系， 获取确定的异常类型 对应的解决方案；
所述修复模块 60， 用于按照获取的解决方案对所述待检测网管设备进 行修复。
具体的， 在有生成的检测结果与对应的预存标准结果的差值大于预设 阀值时， 分析模块 50确定所述待检测网管设备存在异常之后， 处理模块 20 确定存在异常的待检测网管设备的身份信息及发生异常的类型。 预存有各 个异常类型对应的解决方案， 且有的异常类型存在至少一个对应的解决方 案。 处理模块 20才艮据预存的异常类型与解决方案的映射关系， 获取确定的 异常类型对应的解决方案， 在获取到确定的异常类型对应的解决方案时， 修复模块 60按照获取的解决方案对所述待检测网管设备进行修复； 若多个 待检测网管设备存在异常时， 且个个待检测网管设备的异常类型不同时， 处理模块 20根据预存的异常类型与解决方案的映射关系， 获取确定的各个 异常类型对应的解决方案， 并通过修复模块 60按照获取的解决方案对对应 的待检测网管设备进行修复。 例如， 待检测网管设备的检测项目以待检测 网管设备的可用存储空间， 标准结果以 500MB， 预设阀值以可用存储空间 比标准结果大 0MB为例， 在检测结果为待检测网管设备的可用存储空间为 400MB时，分析模块 50确定所述待检测网管设备存在异常，相应的确定解 决方案为修复模块 60将所述待检测设备存储的一些数据进行删除， 可以将 一些离目前时间点较远的数据删除， 或将一段时间内未被浏览的数据进行 删除， 也还可以是按照其他规则将所述待检测网管设备存储的数据进行删 除， 所述预设规则可以是上述的两种， 也可以是其他用户提前设置的数据 删除条件。
进一步地， 若每个异常类型， 对应多个解决方案时， 处理模块 20确定 所述待检测网管设备存在异常的异常类型， 并根据预存的异常类型与解决 方案的映射关系， 获取确定的异常类型对应的所有解决方案； 处理模块 20 根据各个解决方案的优先级次序， 将获取的所有解决方案中优先级次序最 高的解决方案确定为所述待检测网管设备的解决方案。
本实施例中处理模块 20通过确定的待检测网管设备存在异常的异常类 型， 并根据预存的异常类型与解决方案的映射关系， 获取确定的异常类型 对应的解决方案， 并通过修复模块 60按照获取的解决方案对所述待检测网 管设备进行修复。 以便根据确定的待检测网管设备存在异常的异常类型快 速找到解决方案， 对对应的网管设备进行修复， 快速的对发生故障的网管 设备进行定位并自动进行修复， 有效避免长时间找不到设备供应商解决故 障造成的通信异常， 提高网管设备故障解决的效率。 进一步地， 所述分析模块 50， 还用于判断修复是否成功； 及
在修复失败时， 判断与该网管设备异常项目对应的解决方案中是否存 在待选解决方案；
所述处理模块 20， 还用于在存在待选解决方案时， 从待选解决方案中 选择优先级次序最高的解决方案；
所述修复模块 60， 还用于按照确定的解决方案对所述待检测网管设备 进行修复。
具体的， 在修复模块 60按照确定的解决方案对所述待检测网管设备进 行修复后， 预设时间到达时， 分析模块 50判断修复是否成功， 所述预设时 间可以是 0.5s或 Is等用户根据网管设备性能等因素提前设置的时间段； 在 修复成功时， 生成各个待检测项目的修复成功报告， 该报告包括修复的项 目， 修复的解决方案及修复需要的时间等任意修复过程中的数据， 以供用 户通过各个修复 4艮告选择较佳的修复方案或找出发生故障的原因等， 避免 再次发生同样的故障。 在修复失败时， 分析模块 50判断获取的所有解决方 案中是否存在待选解决方案， 在存在待选解决方案时， 处理模块 20将待选 解决方案中优先级次序最高的解决方案确定为所述待检测网管设备的解决 方案服务器按照确定的解决方案对所述待检测网管设备进行修复。 在不存 在待选解决方案时， 通过人机交互界面提示用户需添加新的解决方案， 因 现有的解决方案解决不了目前的异常类型。 同样在修复失败时， 也生成修 复失败 4艮告， 以供用户找出合理的能解决该修复不成功的异常类型的解决 方案， 以便及时的对发生的故障进行合理修复恢复通信。
上述各单元可以由电子设备中的中央处理器（ Central Processing Unit, CPU ). 数字信号处理器 （Digital Signal Processor, DSP )或可编程逻辑阵 列 （Field - Programmable Gate Array, FPGA ) 实现。
本领域内的技术人员应明白， 本发明的实施例可提供为方法、 系统、 或计算机程序产品。 因此， 本发明可采用硬件实施例、 软件实施例、 或结 合软件和硬件方面的实施例的形式。 而且， 本发明可采用在一个或多个其 中包含有计算机可用程序代码的计算机可用存储介质 (包括但不限于磁盘 存储器和光学存储器等）上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、 设备（系统）、 和计算机程序 产品的流程图和 /或方框图来描述的。 应理解可由计算机程序指令实现流程 图和 /或方框图中的每一流程和 /或方框、以及流程图和 /或方框图中的流程和 /或方框的结合。 可提供这些计算机程序指令到通用计算机、 专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器， 使得 通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现 在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功 能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理 设备以特定方式工作的计算机可读存储器中， 使得存储在该计算机可读存 储器中的指令产生包括指令装置的制造品， 该指令装置实现在流程图一个 流程或多个流程和 /或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备 上， 使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机 实现的处理， 从而在计算机或其他可编程设备上执行的指令提供用于实现 在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功 能的步骤。
本发明实施例还提出一种计算机存储介质， 其中存储有计算机可执行 指令， 所述计算机可执行指令用于执行上述任一实施例所述的方法。
以上所述仅为本发明的优选实施例， 并非因此限制本发明的专利范围， 凡是利用本发明说明书及附图内容所作的等效结构或等效流程变换， 或直 接或间接运用在其他相关的技术领域， 均同理包括在本发明的专利保护范 围内。

Claims

权利要求书
1、 一种通信运营商网管设备的检测方法， 其中， 该方法包括： 服务器在接收到包括待检测网管设备身份信息的检测指令时， 根据接 收的检测指令中的待检测网管设备身份信息， 获取待检测网管设备类型； 服务器根据预存的网管设备类型与检测项目的映射关系， 确定获取的 待检测网管设备类型对应的待检测项目；
服务器按照确定的待检测项目检测所述待检测网管设备， 并生成各个 所述待检测项目的检测结果。
2、 根据权利要求 1所述的通信运营商网管设备的检测方法， 其中， 所 述服务器按照确定的待检测项目检测所述待检测网管设备， 并生成各个所 述待检测项目的检测结果的步骤之后， 该方法还包括：
服务器将生成的各个检测结果与对应的预存标准结果进行比对， 以确 定所述待检测网管设备是否存在异常；
在有生成的检测结果与对应的预存标准结果的差值大于预设阀值时， 服务器确定所述待检测网管设备存在异常。
3、 根据权利要求 2所述的通信运营商网管设备的检测方法， 其中， 所 述在有生成的检测结果与对应的预存标准结果的差值大于预设阀值时， 服 务器确定所述待检测网管设备存在异常的步骤之后， 该方法还包括：
服务器确定所述待检测网管设备存在异常的异常类型， 并根据预存的 异常类型与解决方案的映射关系， 获取确定的异常类型对应的解决方案； 服务器按照获取的解决方案对所述待检测网管设备进行修复。
4、 根据权利要求 3所述的通信运营商网管设备的检测方法， 其中， 所 述服务器确定所述待检测网管设备存在异常的异常类型， 并根据预存的异 常类型与解决方案的映射关系， 获取确定的异常类型对应的解决方案的步 骤包括： 服务器确定所述待检测网管设备存在异常的异常类型， 并根据预存的 异常类型与解决方案的映射关系， 获取确定的异常类型对应的所有解决方 案；
服务器根据各个解决方案的优先级次序， 将获取的所有解决方案中优 先级次序最高的解决方案确定为所述待检测网管设备的解决方案。
5、 根据权利要求 3所述的通信运营商网管设备的检测方法， 其中， 所 述服务器按照获取的解决方案对所述待检测网管设备进行修复的步骤之 后， 该方法还包括：
服务器判断修复是否成功；
在修复失败时， 服务器判断获取的所有解决方案中是否存在待选解决 方案；
在存在待选解决方案时， 服务器将待选解决方案中优先级次序最高的 解决方案确定为所述待检测网管设备的解决方案；
服务器按照确定的解决方案对所述待检测网管设备进行修复。
6、 一种通信运营商网管设备的检测装置， 其中， 该装置包括： 获取模块， 用于在接收到包括待检测网管设备身份信息的检测指令时， 根据接收的检测指令中的待检测网管设备身份信息， 获取待检测网管设备 类型；
处理模块， 用于根据预存的网管设备类型与检测项目的映射关系， 确 定获取的待检测网管设备类型对应的待检测项目；
检测模块， 用于按照确定的待检测项目检测所述待检测网管设备； 生成模块， 用于生成各个所述待检测项目的检测结果。
7、 根据权利要求 6所述的通信运营商网管设备的检测装置， 其中， 该 装置还包括分析模块，
所述分析模块， 还用于将生成的各个检测结果与对应的预存标准结果 进行比对， 以确定所述待检测网管设备是否存在异常； 及在有生成的检测 结果与对应的预存标准结果的差值大于预设阀值时， 确定所述待检测网管 设备存在异常。
8、 根据权利要求 7所述的通信运营商网管设备的检测装置， 其中， 该 装置还包括修复模块，
所述处理模块， 还用于确定所述待检测网管设备存在异常的异常类型， 并根据预存的异常类型与解决方案的映射关系， 获取确定的异常类型对应 的解决方案；
所述修复模块， 用于按照获取的解决方案对所述待检测网管设备进行 修复。
9、 根据权利要求 8所述的通信运营商网管设备的检测装置， 其中， 所述处理模块， 还用于确定所述待检测网管设备存在异常的异常类型， 并根据预存的异常类型与解决方案的映射关系， 获取确定的异常类型对应 的所有解决方案； 及根据各个解决方案的优先级次序， 将获取的所有解决 方案中优先级次序最高的解决方案确定为所述待检测网管设备的解决方 案。
10、 根据权利要求 8所述的通信运营商网管设备的检测装置， 其中， 所述分析模块， 还用于判断修复是否成功； 及在修复失败时， 判断与 该网管设备异常项目对应的解决方案中是否存在待选解决方案；
所述处理模块， 还用于在存在待选解决方案时， 从待选解决方案中选 择优先级次序最高的解决方案；
所述修复模块， 还用于按照确定的解决方案对所述待检测网管设备进 行修复。
11、 一种计算机存储介质， 其中存储有计算机可执行指令， 所述计算 机可执行指令用于执行所述权利要求 1至 5任一项所述的方法。
PCT/CN2014/080019 2013-11-06 2014-06-16 通信运营商网管设备的检测方法及装置、计算机存储介质 WO2014180450A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310547722.4A CN104639346A (zh) 2013-11-06 2013-11-06 通信运营商网管设备的检测方法及装置
CN201310547722.4 2013-11-06

Publications (1)

Publication Number Publication Date
WO2014180450A1 true WO2014180450A1 (zh) 2014-11-13

Family

ID=51866830

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/080019 WO2014180450A1 (zh) 2013-11-06 2014-06-16 通信运营商网管设备的检测方法及装置、计算机存储介质

Country Status (2)

Country Link
CN (1) CN104639346A (zh)
WO (1) WO2014180450A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109460312A (zh) * 2018-10-31 2019-03-12 阿里巴巴集团控股有限公司 请求失败的处理方法及装置
CN112184185A (zh) * 2020-10-27 2021-01-05 陈双红 商用混凝土搅拌站erp系统
CN112953737A (zh) * 2019-11-26 2021-06-11 中兴通讯股份有限公司 配置异常检测方法、服务器以及存储介质
CN115834436A (zh) * 2022-11-24 2023-03-21 中国联合网络通信集团有限公司 网络连通性检测方法、装置及存储介质
CN115834436B (zh) * 2022-11-24 2024-05-03 中国联合网络通信集团有限公司 网络连通性检测方法、装置及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106918360B (zh) * 2015-12-24 2021-01-12 研祥智能科技股份有限公司 自动检测方法、服务器、待检测设备及终端
CN108804909B (zh) * 2018-06-13 2021-02-26 苏州朗润创新知识产权运营有限公司 一种用于对检测数据进行区块链存证处理的方法
CN113256905A (zh) * 2020-06-08 2021-08-13 深圳市怡化时代科技有限公司 自助柜员机现金业务预处理方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1486083A (zh) * 2002-09-24 2004-03-31 深圳市劲成光纤网络设备有限公司 一种实现有线电视网络网管系统的方法
US20080291018A1 (en) * 2001-11-29 2008-11-27 International Business Machines Corporation Method, computer program element and a system for processing alarms triggered by a monitoring system
CN102064963A (zh) * 2010-12-03 2011-05-18 百度在线网络技术（北京）有限公司 一种用于对多个计算设备进行管理的方法与设备
CN103095489A (zh) * 2012-12-14 2013-05-08 上海斐讯数据通信技术有限公司 一种对网络设备的管理方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103377094B (zh) * 2012-04-12 2016-08-03 金蝶软件（中国）有限公司 异常监测方法和装置
CN102857365A (zh) * 2012-06-07 2013-01-02 中兴通讯股份有限公司 网管系统中故障预防及智能修复方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080291018A1 (en) * 2001-11-29 2008-11-27 International Business Machines Corporation Method, computer program element and a system for processing alarms triggered by a monitoring system
CN1486083A (zh) * 2002-09-24 2004-03-31 深圳市劲成光纤网络设备有限公司 一种实现有线电视网络网管系统的方法
CN102064963A (zh) * 2010-12-03 2011-05-18 百度在线网络技术（北京）有限公司 一种用于对多个计算设备进行管理的方法与设备
CN103095489A (zh) * 2012-12-14 2013-05-08 上海斐讯数据通信技术有限公司 一种对网络设备的管理方法

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109460312A (zh) * 2018-10-31 2019-03-12 阿里巴巴集团控股有限公司 请求失败的处理方法及装置
CN112953737A (zh) * 2019-11-26 2021-06-11 中兴通讯股份有限公司 配置异常检测方法、服务器以及存储介质
CN112184185A (zh) * 2020-10-27 2021-01-05 陈双红 商用混凝土搅拌站erp系统
CN112184185B (zh) * 2020-10-27 2024-02-02 陈双红 商用混凝土搅拌站erp系统
CN115834436A (zh) * 2022-11-24 2023-03-21 中国联合网络通信集团有限公司 网络连通性检测方法、装置及存储介质
CN115834436B (zh) * 2022-11-24 2024-05-03 中国联合网络通信集团有限公司 网络连通性检测方法、装置及存储介质

Also Published As

Publication number Publication date
CN104639346A (zh) 2015-05-20

Similar Documents

Publication Publication Date Title
WO2014180450A1 (zh) 通信运营商网管设备的检测方法及装置、计算机存储介质
CN110928774B (zh) 一种基于节点式的自动化测试系统
CN108600029B (zh) 一种配置文件更新方法、装置、终端设备及存储介质
WO2021196521A1 (zh) 远程运维管理系统及方法
WO2020029407A1 (zh) 告警数据的管理方法、装置、计算机设备及存储介质
CN107807877B (zh) 一种代码性能测试的方法和装置
US20150193296A1 (en) Run-time error repairing method, device and system
US10097427B2 (en) Service assurance platform as a user-defined service
WO2015090098A1 (zh) 一种实现故障定位的方法及装置
WO2016062011A1 (zh) 告警处理方法及装置
CN101369933A (zh) 一种自动化测试方法及系统
CN113645085B (zh) 智能网卡的异常检测方法、装置、电子设备及存储介质
WO2019034095A1 (zh) 软件处理方法、装置、电子设备及计算机可读存储介质
WO2019047071A1 (zh) 一种数据库故障的响应方法及其终端
CN112529223A (zh) 一种设备故障报修方法、装置、服务器及储存介质
CN114793132A (zh) 一种光模块的检测方法、装置、电子设备及存储介质
CN108307414B (zh) 应用程序的Wi-Fi连接异常处理方法、装置、终端及存储介质
CN108650134B (zh) 网络故障定位的方法、装置及电子设备
CN114070752A (zh) 测试方法、装置、电子设备及计算机可读存储介质
CN109271270A (zh) 存储系统中底层硬件的故障排除方法、系统及相关装置
CN111147542A (zh) 一种免密访问的设置方法、装置、设备及介质
CN111209606A (zh) 一种预警raid卡后硬盘变动的方法、装置和设备
CN110930110A (zh) 分布式流程监控方法、装置、存储介质及电子设备
CN115686921A (zh) 一种多路径异常检测修复方法、装置、设备及介质
CN105511952A (zh) 基于云计算平台的资源自迁移方法及系统

Legal Events

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

Ref document number: 14794557

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

Country of ref document: EP

Kind code of ref document: A1