WO2016188223A1 - 故障信息采集的方法及装置 - Google Patents
故障信息采集的方法及装置 Download PDFInfo
- Publication number
- WO2016188223A1 WO2016188223A1 PCT/CN2016/077901 CN2016077901W WO2016188223A1 WO 2016188223 A1 WO2016188223 A1 WO 2016188223A1 CN 2016077901 W CN2016077901 W CN 2016077901W WO 2016188223 A1 WO2016188223 A1 WO 2016188223A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- fault information
- fault
- terminal
- collecting
- collection
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
-
- 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
Definitions
- the present invention relates to the field of device fault processing technologies, and in particular, to a method and device for collecting fault information.
- the main purpose of the embodiments of the present invention is to provide a method and device for collecting fault information, which aims to solve the technical problem that the effective fault information cannot be collected.
- the embodiment of the present invention provides a method for collecting fault information, and the method for collecting fault information includes the following steps:
- the collected fault information is checked for integrity
- the step of attempting to collect the fault information according to the pre-configured collection mode includes:
- the fault event reported by the faulty component is obtained according to the pre-configured acquisition mode, and the parameter in the fault component register is obtained.
- the step of receiving the collection command sent by the terminal, collecting the fault information according to the collection command, and storing the method includes:
- the step of establishing a connection with the designated terminal includes:
- the pre-generated check code is obtained, and the check code is sent to the designated terminal;
- the method includes:
- the collection permission information is obtained, and the collection authority information is sent to the terminal to cooperate with the authorized terminal to collect the fault information.
- the method further includes:
- the successfully verified fault information or the collected fault information is sent to the terminal for display or fault processing by the terminal.
- the present invention further provides an apparatus for collecting fault information, and the apparatus for collecting fault information includes:
- the first collection module is configured to attempt to collect fault information according to a pre-configured collection mode when the device is faulty or the service is faulty;
- the verification module is configured to perform integrity verification on the collected fault information after the fault information is collected;
- the first sending module is configured to establish a connection with the designated terminal when the fault information is not collected or the verification fails;
- the second collection module is configured to receive an acquisition command sent by the terminal, collect fault information according to the collection command, and store the fault information.
- the first collection module includes:
- the first acquiring unit is configured to: when the device is faulty or the service is faulty, acquire the fault event reported by the fault component according to the pre-configured acquisition mode, and obtain the parameter in the fault component register;
- the second obtaining unit is configured to try to collect fault information according to the fault event and the parameter.
- the second collection module includes:
- the collecting unit is configured to receive an acquisition command sent by the terminal, and collect bottom information of the fault component according to the collection instruction;
- the third obtaining unit is configured to acquire and store the fault information according to the underlying information.
- the first sending module includes:
- the first sending unit is configured to: when the fault information is not collected or the verification fails, obtain a pre-generated check code, and send the check code to the designated terminal;
- a second sending unit configured to establish a connection with the terminal after the terminal passes the verification according to the check code
- the device for collecting the fault information further includes: a sending module, configured to acquire the collecting right information and send the collecting right information to the terminal, so as to cooperate with the authorized terminal to collect the fault information.
- the device for collecting fault information further includes:
- the second sending module is configured to send the fault information that is successfully verified or send the collected fault information to the terminal for the terminal to display or perform fault processing.
- a computer storage medium is further provided, and the computer storage medium may store an execution instruction, where the execution instruction is used to execute the method for collecting the fault information.
- the embodiment of the present invention provides a method and a device for collecting fault information.
- the fault information can be collected according to a pre-configured collection mode, and the collected fault information is performed. If the fault information is not collected or the verification fails, the terminal can establish a connection with the terminal, collect the fault information through the terminal, and obtain the fault information of the fault point at the first time when the equipment fault occurs.
- the fault information can be collected in time. It is convenient for maintenance personnel to recover the faulty equipment or perform other processing to ensure the normal operation of the business.
- FIG. 1 is a schematic flowchart of an embodiment of a method for collecting fault information according to the present invention
- FIG. 2 is a schematic diagram of a refinement process of step S101 in FIG. 1;
- step S104 in FIG. 1 is a schematic diagram of a refinement process of step S104 in FIG. 1;
- FIG. 4 is a schematic diagram of a refinement process of step S103 in FIG. 1;
- FIG. 5 is a schematic diagram of functional modules of an apparatus for collecting fault information according to the present invention.
- FIG. 6 is a schematic diagram of a refinement function module of the first acquisition module in FIG. 5;
- FIG. 7 is a schematic diagram of a refinement function module of the second acquisition module in FIG. 5;
- FIG. 8 is a schematic diagram of a refinement function module of the first transmitting module in FIG. 5.
- the present invention provides a method for collecting fault information.
- the method for collecting fault information includes:
- step S101 when the device is faulty or the service is faulty, the fault information is attempted to be collected according to the pre-configured collection mode.
- the device fault may be a fault in the device and/or the cabinet.
- the service may be interrupted when the service is faulty.
- the optical fiber is faulty, the board is faulty, or the service type is faulty. Wait.
- the fault collection core processing chip is added to the device, and the fault collection core processing chip cooperates with the network management system and the main control board in the device to complete the collection of the fault information in this embodiment.
- the fault information when a device fault or a service fault occurs, the fault information may be collected according to a default fault collection method, that is, a pre-configured collection mode (also referred to as a fault collection data dictionary), and the fault information may or may not be collected. Collected.
- a pre-configured collection mode also referred to as a fault collection data dictionary
- the fault information may not be collected. Collected.
- the board may not report a reset event or the reported process reset event is lost, the reset event has been reported but the fault parameter cannot be obtained from the board register, etc. , both result in the failure to collect the fault information.
- Step S102 after collecting the fault information, performing integrity verification on the collected fault information
- the collection operation needs to be performed by manual intervention.
- the integrity of the fault information needs to be verified.
- the integrity check is performed by the network management system described above.
- the next step can be performed. If it is incomplete, it needs to be re-acquired.
- the complete fault information has not been collected for a predetermined number of acquisitions, the manual intervention is also required. operating.
- Step S103 establishing a connection with the designated terminal when the fault information is not collected or the verification fails;
- Step S104 Receive an acquisition command sent by the terminal, collect fault information according to the collection command, and store the fault information.
- the maintenance personnel can hold the designated terminal to collect the fault information in the field, and the first faulty device can establish a wireless connection with the designated terminal, for example, establishing infrared, Bluetooth or A wireless connection such as NFC can automatically collect fault information after establishing a connection with the terminal, or can be collected by a maintenance personnel by inputting an acquisition command.
- a wireless connection such as NFC can automatically collect fault information after establishing a connection with the terminal, or can be collected by a maintenance personnel by inputting an acquisition command.
- the fault information after the fault information is collected, it can be stored in an encrypted manner to improve security.
- the fault information when a device is faulty or a service is faulty, for example, when a board fails, the fault information can be collected according to the pre-configured collection mode, and the collected fault information is verified. The fault information is not collected or the verification fails.
- the fault information can be collected in time, and the maintenance personnel can recover the faulty device or perform other processing to ensure that the fault is restored. The normal operation of the business.
- the foregoing step S101 includes:
- step S1011 when the device is faulty or the service is faulty, the fault event reported by the faulty component is acquired according to the pre-configured acquisition mode, and the parameter in the fault component register is obtained.
- Step S1012 Try to collect fault information according to the fault event and the parameter.
- the faulty component is a board.
- the reset fault of the board may be a fault reset or an artificial manual reset:
- the change of the hardware interface and the software interface of the board is monitored by the main control board (for example, the change of the H port and the S port of the device), and the reset event (that is, the fault event) reported on the board received by the main control board. , to determine whether the reset event is an automatic reset or an artificial manual reset.
- the reset event is a manual reset
- query the parameters in the board register according to the acquisition mode in the fault collection data dictionary for example, the 7th bit in the parameter is the value representing the reset state. If the parameter is consistent with the reset event, then Reported to the above network management system, and save the parameters in the register to confirm that it is a manual reset;
- the parameters in the board register are queried according to the collection mode in the fault collection data dictionary. If the parameter is consistent with the reset event, it is reported to the network management system and the parameters in the register are saved. Confirmation is automatic reset;
- the parameters in the board register are queried and the parameters are reported to the network management system.
- the network management system verifies the parameters in the board register according to the translation file stored in the database. For example, the parameter in the register is 00000000010102, and the network management system reads this parameter. For example, the last bit 02 represents manual reset. Then match with the fault event, both of which are manual resets, then pass the verification and save the corresponding parameters in the register to confirm that it is a manual reset. If they are inconsistent, record this information in the network management system for maintenance personnel. View and troubleshoot again.
- the foregoing step S104 includes:
- Step S1041 Receive an acquisition command sent by the terminal, and collect low-level information of the fault component according to the collection instruction.
- Step S1042 Acquire fault information according to the underlying information and store it.
- the device After the device establishes a connection with the terminal, the receiving command sent by the terminal is received, and the device initiates an application request for the underlying permission according to the underlying fault information collection mode of the data dictionary, and collects the underlying chip of the faulty component.
- the underlying information is mirrored on the faulty component, and the current state information of the faulty component and the collected underlying information are packaged and stored.
- the foregoing step S103 includes:
- step S1031 when the fault information is not collected or the verification fails, the pre-generated check code is obtained, and the check code is sent to the designated terminal.
- Step S1032 After the terminal passes the verification according to the check code, establish a connection with the terminal.
- the device when the connection is established with the terminal when the fault information is not collected or the verification fails, the device itself generates a check code in advance and sends the check code to the terminal.
- the check code is generated by the network management system and sent to the terminal.
- the terminal establishes a connection with the terminal after the terminal passes the verification according to the check code, and improves the security of the fault information collection and the fault information through the real-time and uniqueness of the check code.
- the device may send the collection authority information to the terminal, so that the terminal having the collection authority may collect the fault information on the device. It can further improve the safety of fault information collection and fault information.
- the device will verify the successful fault information or send the collected fault information to the terminal, and the terminal displays it, and the maintenance personnel can perform operations on the terminal or perform fault processing. .
- the present invention also provides a device for collecting fault information.
- the device for collecting fault information includes:
- the first collection module 101 is configured to attempt to collect fault information according to a pre-configured collection mode when the device is faulty or the service is faulty.
- the device fault may be a fault in the device and/or the cabinet.
- the service may be interrupted when the service is faulty.
- the optical fiber is faulty, the board is faulty, or the service type is faulty. Wait.
- the fault collection core processing chip is added to the device, and the fault collection core processing chip cooperates with the network management system and the main control board in the device to complete the collection of the fault information in this embodiment.
- the fault information when a device fault or a service fault occurs, the fault information may be collected according to a default fault collection method, that is, a pre-configured collection mode (also referred to as a fault collection data dictionary), and the fault information may or may not be collected. Collected. In the case that the fault information cannot be collected, for example, for a board reset fault, the board may not be available. If the reset event is reported or the process reset event is lost, the reset event has been reported but the fault parameter cannot be obtained from the board register, and the result of the fault information cannot be collected.
- a default fault collection method that is, a pre-configured collection mode (also referred to as a fault collection data dictionary)
- the fault information may or may not be collected. Collected.
- the fault information cannot be collected, for example, for a board reset fault, the board may not be available. If the reset event is reported or the process reset event is lost, the reset event has been reported but the fault parameter cannot be obtained from the board register, and the result of the fault information cannot be collected
- the verification module 102 is configured to perform integrity verification on the collected fault information after collecting the fault information.
- the collection operation needs to be performed by manual intervention.
- the integrity of the fault information needs to be verified.
- the integrity check is performed by the network management system described above.
- the next step can be performed. If it is incomplete, it needs to be re-acquired.
- the complete fault information has not been collected for a predetermined number of acquisitions, the manual intervention is also required. operating.
- the first sending module 103 is configured to establish a connection with the designated terminal when the fault information is not collected or the verification fails;
- the second collection module 104 is configured to receive an acquisition command sent by the terminal, collect fault information according to the collection command, and store the fault information.
- the maintenance personnel can hold the designated terminal to collect the fault information in the field, and the first faulty device can establish a wireless connection with the designated terminal, for example, establishing infrared, Bluetooth or A wireless connection such as NFC can automatically collect fault information after establishing a connection with the terminal, or can be collected by a maintenance personnel by inputting an acquisition command.
- a wireless connection such as NFC can automatically collect fault information after establishing a connection with the terminal, or can be collected by a maintenance personnel by inputting an acquisition command.
- the fault information after the fault information is collected, it can be stored in an encrypted manner to improve security.
- the fault information can be collected according to the pre-configured collection mode, and the collected fault information is verified.
- the fault information is not collected or the verification fails.
- the terminal can establish a connection with the terminal, collect the fault information through the terminal, and obtain the fault information of the fault point at the first time when the equipment fault occurs, and can collect valid fault information in time, so that the maintenance personnel can recover the faulty device or perform other operations. Process to ensure the normal operation of the business.
- the first collection module 101 includes:
- the first obtaining unit 1011 is configured to: when the device is faulty or the service is faulty, acquire the fault event reported by the fault component according to the pre-configured acquisition mode, and obtain the parameter in the fault component register;
- the second obtaining unit 1012 is configured to try to collect fault information according to the fault event and the parameter.
- the faulty component is a board.
- the reset fault of the board may be a fault reset or an artificial manual reset:
- the change of the hardware interface and the software interface of the board is monitored by the main control board (for example, the change of the H port and the S port of the device), and the reset event (that is, the fault event) reported on the board received by the main control board. , to determine whether the reset event is an automatic reset or an artificial manual reset.
- the reset event is a manual reset
- query the parameters in the board register according to the acquisition mode in the fault collection data dictionary for example, the 7th bit in the parameter is the value representing the reset state. If the parameter is consistent with the reset event, then Reported to the above network management system, and save the parameters in the register to confirm that it is a manual reset;
- the parameters in the board register are queried according to the collection mode in the fault collection data dictionary. If the parameter is consistent with the reset event, it is reported to the network management system and the parameters in the register are saved. Confirmation is automatic reset;
- the parameters in the board register are queried and the parameters are reported to the network management system.
- the network management system verifies the parameters in the board register according to the translation file stored in the database. For example, the parameter in the register is 00000000010102, and the network management system reads this parameter. For example, the last bit 02 represents manual reset. Then match with the fault event, both of which are manual resets, then pass the verification and save the corresponding parameters in the register to confirm that it is a manual reset. If they are inconsistent, record this information in the network management system for maintenance personnel. View and troubleshoot again.
- the second collection module 104 includes:
- the collecting unit 1041 is configured to receive an acquisition command sent by the terminal, and collect low-level information of the fault component according to the collection instruction;
- the third obtaining unit 1042 is configured to acquire and store the fault information according to the underlying information.
- the device After the device establishes a connection with the terminal, the receiving command sent by the terminal is received, and the device initiates an application request for the underlying permission according to the underlying fault information collection mode of the data dictionary, and collects the underlying chip of the faulty component.
- the underlying information is mirrored on the faulty component, and the current state information of the faulty component and the collected underlying information are packaged and stored.
- the first sending module 103 includes:
- the first sending unit 1031 is configured to: when the fault information is not collected or the verification fails, obtain a pre-generated check code, and send the check code to the designated terminal;
- the second sending unit 1032 is configured to establish a connection with the terminal after the terminal passes the verification according to the check code.
- the device when the connection is established with the terminal when the fault information is not collected or the verification fails, the device itself generates a check code in advance and sends the check code to the terminal.
- the check code is generated by the network management system and sent to the terminal.
- the terminal establishes a connection with the terminal after the terminal passes the verification according to the check code, and improves the security of the fault information collection and the fault information through the real-time and uniqueness of the check code.
- the device may send the collection authority information to the terminal, so that the terminal having the collection authority may collect the fault information on the device. It can further improve the safety of fault information collection and fault information.
- the device will verify the successful fault information or send the collected fault information to the terminal, and the terminal displays it, and the maintenance personnel can perform operations on the terminal or perform fault processing. .
- each of the above modules may be implemented by software or hardware.
- the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.
- Embodiments of the present invention also provide a storage medium.
- the foregoing storage medium may be configured to store program code for performing the following steps:
- S4 Receive an acquisition command sent by the terminal, collect fault information according to the collection command, and store the fault information.
- the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM).
- ROM Read-Only Memory
- RAM Random Access Memory
- the fault can be collected according to the pre-configured collection mode and the collected fault information is verified.
- the fault information or the verification fails, a connection can be established with the terminal, and the fault information is collected through the terminal, when the equipment fault occurs.
- the fault information of the fault point is obtained, the fault information can be collected in time to facilitate the maintenance personnel to recover the faulty device or perform other processing to ensure the normal operation of the service.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Debugging And Monitoring (AREA)
Abstract
本发明公开了一种故障信息采集的方法及装置，所述故障信息采集的方法包括以下步骤：当设备故障或业务故障时，根据预先配置的采集方式尝试采集故障信息；在采集到故障信息后，将所采集的故障信息进行完整性校验；在未采集到故障信息或校验失败时，与指定的终端建立连接；接收所述终端发送的采集命令，根据所述采集命令采集故障信息并存储。本发明能够及时采集到有效的故障信息。
Description
本发明涉及设备故障处理技术领域，尤其涉及一种故障信息采集的方法及装置。
目前，各种或大或小的设备(例如通信设备或网络设备等)在不同的场景下运行并发挥自身的作用。随着工程现场的管理越来越严格，对现场的设备的运维要求也越来越高，一套易于维护的设备在出现故障时，能通过简易的方法定位故障、快速的解决故障。
在现有的设备维护处理条件下，通常在发生故障时要求维护人员及时进行分析并定位故障等处理，保证业务的正常运营。而故障的采集一般交由办事处处理，需要维护人员到现场执行处理，如果维护人员对设备不了解，对故障进行处理的过程中，故障信息(例如单板寄存器信息或性能信息等)因为故障的恢复而丢失，对准确定位并分析故障原因造成很大的影响，无法采集得到有效的故障信息。
上述内容仅用于辅助理解本发明的技术方案，并不代表承认上述内容是现有技术。
发明内容
本发明实施例的主要目的在于提供一种故障信息采集的方法及装置，旨在解决无法采集得到有效的故障信息的技术问题。
为实现上述目的，本发明实施例提供一种故障信息采集的方法，所述故障信息采集的方法包括以下步骤：
当设备故障或业务故障时，根据预先配置的采集方式尝试采集故障信息；
在采集到故障信息后，将所采集的故障信息进行完整性校验；
在未采集到故障信息或校验失败时，与指定的终端建立连接；
接收所述终端发送的采集命令，根据所述采集命令采集故障信息并存储。
在本发明实施例中，所述当设备故障或业务故障时，根据预先配置的采集方式尝试采集故障信息的步骤包括：
当设备故障或业务故障时，根据预先配置的采集方式获取故障部件上报的故障事件以及获取故障部件寄存器中的参数；
根据所述故障事件及所述参数尝试采集故障信息。
在本发明实施例中，所述接收所述终端发送的采集命令，根据所述采集命令采集故障信息并存储的步骤包括：
接收所述终端发送的采集命令，根据所述采集指令采集故障部件的底层信息；
根据所述底层信息获取故障信息并存储。
在本发明实施例中，所述在未采集到故障信息或校验失败时，与指定的终端建立连接的步骤包括：
在未采集到故障信息或校验失败时，获取预先生成的校验码，将所述校验码发送给指定的终端；
在所述终端根据所述校验码通过校验后，与终端建立连接；
所述在未采集到故障信息或校验失败时，与指定的终端建立连接的步骤之后包括：
获取采集权限信息并将所述采集权限信息下发给所述终端，以与有权限的终端配合采集故障信息。
在本发明实施例中，所述接收所述终端根据所述采集权限信息发送的采集命令，根据所述采集命令采集故障信息并存储的步骤之后还包括：
将校验成功的故障信息或者将所采集的故障信息发送给所述终端，以供所述终端进行显示或进行故障处理。
此外，为实现上述目的，本发明还提供一种故障信息采集的装置，所述故障信息采集的装置包括：
第一采集模块，设置为当设备故障或业务故障时，根据预先配置的采集方式尝试采集故障信息；
校验模块，设置为在采集到故障信息后，将所采集的故障信息进行完整性校验；
第一发送模块，设置为在未采集到故障信息或校验失败时，与指定的终端建立连接；
第二采集模块，设置为接收所述终端发送的采集命令，根据所述采集命令采集故障信息并存储。
在本发明实施例中，所述第一采集模块包括：
第一获取单元，设置为当设备故障或业务故障时，根据预先配置的采集方式获取故障部件上报的故障事件以及获取故障部件寄存器中的参数；
第二获取单元，设置为根据所述故障事件及所述参数尝试采集故障信息。
在本发明实施例中，所述第二采集模块包括：
采集单元，设置为接收所述终端发送的采集命令，根据所述采集指令采集故障部件的底层信息；
第三获取单元，设置为根据所述底层信息获取故障信息并存储。
在本发明实施例中，所述第一发送模块包括：
第一发送单元，设置为在未采集到故障信息或校验失败时，获取预先生成的校验码，将所述校验码发送给指定的终端；
第二发送单元，设置为在所述终端根据所述校验码通过校验后，与终端建立连接；
所述故障信息采集的装置还包括：下发模块，设置为获取采集权限信息并将所述采集权限信息下发给所述终端，以与有权限的终端配合采集故障信息。
在本发明实施例中，所述故障信息采集的装置还包括：
第二发送模块，设置为将校验成功的故障信息或者将所采集的故障信息发送给所述终端，以供所述终端进行显示或进行故障处理。
在本发明实施例中，还提供了一种计算机存储介质，该计算机存储介质中可以存储有执行指令，该执行指令用于执行上述故障信息的采集方法。
本发明实施例提供了一种故障信息采集的方法及装置，在设备故障或业务故障时，例如单板发生故障时，能根据预先配置的采集方式尝试采集故障信息并将采集到的故障信息进行校验，在未采集到故障信息或校验失败时，可与终端建立连接，通过终端采集故障信息，在设备故障发生时第一时间获取故障点的故障信息，能够及时采集到有效的故障信息，方便维护人员对故障设备进行恢复或者进行其他的处理，确保业务的正常运行。
图1为本发明故障信息采集的方法一实施例的流程示意图；
图2为图1中步骤S101的细化流程示意图；
图3为图1中步骤S104的细化流程示意图；
图4为图1中步骤S103的细化流程示意图；
图5为本发明故障信息采集的装置一实施例的功能模块示意图；
图6为图5中第一采集模块的细化功能模块示意图；
图7为图5中第二采集模块的细化功能模块示意图；
图8为图5中第一发送模块的细化功能模块示意图。
本发明目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。
本发明提供一种故障信息采集的方法，参照图1，在一实施例中，该故障信息采集的方法包括：
步骤S101，当设备故障或业务故障时，根据预先配置的采集方式尝试采集故障信息；
本实施例中，设备故障可以是设备和/或机柜等出现故障，业务故障时可能是业务中断，例如光纤出现故障、单板出现故障等，也可能是业务类型问题或者是客户侧业务的问题等。
本实施例中，在设备中增加故障采集核心处理芯片，由该故障采集核心处理芯片与设备中网络管理系统及主控单板进行配合，完成本实施例的故障信息的采集。
本实施例中，当设备故障或业务故障时，根据默认的故障采集方法，也就是预先配置的采集方式(也可以称为故障采集数据字典)来采集故障信息，故障信息可能能够采集也可能无法采集到。对于无法采集到故障信息的情况中，例如对于单板复位故障而言，单板可能未上报复位事件或者上报的过程复位事件丢失、复位事件已经上报但是无法从单板寄存器中获取故障参数等等，均会导致无法采集到故障信息的结果。
步骤S102，在采集到故障信息后，将所采集的故障信息进行完整性校验；
本实施例中，如果未能采集到故障信息，需要通过人工干预进行采集操作。
如果能够采集到故障信息，需要对故障信息的完整性进行校验，优选地，由上述的网络管理系统进行完整性的校验。在校验的过程中，如果故障信息完整，则可以进行下一步操作，如果不完整，则需要重新采集，在采集预定次数仍未能够采集到完整的故障信息时，同样需要通过人工干预进行采集操作。
步骤S103，在未采集到故障信息或校验失败时，与指定的终端建立连接；
步骤S104，接收所述终端发送的采集命令，根据所述采集命令采集故障信息并存储。
本实施例中，在未采集到故障信息或校验失败时，可由维护人员手持指定的终端至现场采集故障信息，首先发生故障的设备可与指定的终端建立无线连接，例如建立红外、蓝牙或NFC等无线连接，与终端建立连接后，可以自动采集故障信息也可以由维护人员使用通过输入采集命令的方式进行采集。
本实施例中，在采集故障信息后，可将其进行加密存储，以提高安全性。
本实施例在设备故障或业务故障时，例如单板发生故障时，能根据预先配置的采集方式尝试采集故障信息并将采集到的故障信息进行校验，在未采集到故障信息或校验失败时，可
与终端建立连接，通过终端采集故障信息，在设备故障发生时第一时间获取故障点的故障信息，能够及时采集到有效的故障信息，方便维护人员对故障设备进行恢复或者进行其他的处理，确保业务的正常运行。
在一优选的实施例中，如图2所示，在上述图1的实施例的基础上，上述步骤S101包括：
步骤S1011，当设备故障或业务故障时，根据预先配置的采集方式获取故障部件上报的故障事件以及获取故障部件寄存器中的参数；
步骤S1012，根据所述故障事件及所述参数尝试采集故障信息。
本实施例中，当设备故障或业务故障时，例如故障部件为单板，以单板复位为例，单板出现复位故障可能是故障复位也可能是人为手动复位：
当通过主控单板监控到单板硬件接口和软件接口的变化(例如设备的H口和S口的变化)，以及通过主控单板收到的单板上报的复位事件(即故障事件)，判断该复位事件是自动复位还是人为手动复位。
当复位事件是手动复位时，根据故障采集数据字典里的采集方式，查询单板寄存器中的参数(例如参数中的第7位是代表复位状态的值)，若该参数与复位事件一致，则上报给上述的网络管理系统，并保存寄存器中的参数，确认是手动复位；
当复位事件是自动复位时，根据故障采集数据字典里的采集方式，查询单板寄存器中的参数，若该参数与复位事件一致，则上报给上述的网络管理系统，并保存寄存器中的参数，确认是自动复位；
当仅仅监测到单板硬件接口和软件接口的变化，未获取到复位事件(复位事件可能未上报或上报时丢失)，则查询单板寄存器中的参数，并将参数上报给上述的网络管理系统；
当仅监测到单板硬件接口和软件接口的变化，未获取到复位事件，且无法进行单板寄存器的查询，则通知网络管理系统故障采集失败。
网络管理系统将单板寄存器中的参数按照自身数据库中存储的翻译文件进行校验，例如寄存器中的参数为00000000010102，则网络管理系统将此参数进行读取，例如最后一位02代表手动复位，则与故障事件进行匹配，两者都是手动复位，则通过校验，并保存寄存机中对应的参数，确认是手动复位，若不一致，则将此信息记录在网络管理系统中，供维护人员查看并再次进行故障定位。
在一优选的实施例中，如图3所示，在上述图1的实施例的基础上，上述步骤S104包括：
步骤S1041，接收所述终端发送的采集命令，根据所述采集指令采集故障部件的底层信息；
步骤S1042，根据所述底层信息获取故障信息并存储。
本实施例中，在设备与终端建立连接后，接收终端发送的采集命令，设备根据数据字典带有的底层故障信息采集方式，对故障部件发起底层权限的申请请求，对故障部件的底层芯片采集底层信息，并对故障部件进行镜像操作，将故障部件当前状态信息及所采集的底层信息打包存储。
在一优选的实施例中，如图4所示，在上述图1的实施例的基础上，上述步骤S103包括：
步骤S1031，在未采集到故障信息或校验失败时，获取预先生成的校验码，将所述校验码发送给指定的终端；
步骤S1032，在所述终端根据所述校验码通过校验后，与终端建立连接。
本实施例中，在未采集到故障信息或校验失败时，与终端建立连接时，设备自身预先生成校验码并发送给终端，优选地，可以由网络管理系统生成校验码并发送给终端，在终端根据校验码通过校验后，与终端建立连接，通过校验码的实时性及唯一性来提高故障信息采集及故障信息的安全性。
进一步地，在另一优选的实施例中，在设备与指定的终端建立连接后，可以由设备将采集权限信息下发给终端，这样，有采集权限的终端方可采集到设备上的故障信息，能够进一步提高故障信息采集及故障信息的安全性。
在一优选的实施例中，在采集到故障信息后，设备将校验成功的故障信息或者将所采集的故障信息发送给终端，终端进行显示，维护人员可以在终端上进行操作或进行故障处理。
本发明还提供一种故障信息采集的装置，如图5所示，在一实施例中，所述故障信息采集的装置包括：
第一采集模块101，设置为当设备故障或业务故障时，根据预先配置的采集方式尝试采集故障信息；
本实施例中，设备故障可以是设备和/或机柜等出现故障，业务故障时可能是业务中断，例如光纤出现故障、单板出现故障等，也可能是业务类型问题或者是客户侧业务的问题等。
本实施例中，在设备中增加故障采集核心处理芯片，由该故障采集核心处理芯片与设备中网络管理系统及主控单板进行配合，完成本实施例的故障信息的采集。
本实施例中，当设备故障或业务故障时，根据默认的故障采集方法，也就是预先配置的采集方式(也可以称为故障采集数据字典)来采集故障信息，故障信息可能能够采集也可能无法采集到。对于无法采集到故障信息的情况中，例如对于单板复位故障而言，单板可能未
上报复位事件或者上报的过程复位事件丢失、复位事件已经上报但是无法从单板寄存器中获取故障参数等等，均会导致无法采集到故障信息的结果。
校验模块102，设置为在采集到故障信息后，将所采集的故障信息进行完整性校验；
本实施例中，如果未能采集到故障信息，需要通过人工干预进行采集操作。
如果能够采集到故障信息，需要对故障信息的完整性进行校验，优选地，由上述的网络管理系统进行完整性的校验。在校验的过程中，如果故障信息完整，则可以进行下一步操作，如果不完整，则需要重新采集，在采集预定次数仍未能够采集到完整的故障信息时，同样需要通过人工干预进行采集操作。
第一发送模块103，设置为在未采集到故障信息或校验失败时，与指定的终端建立连接；
第二采集模块104，设置为接收所述终端发送的采集命令，根据所述采集命令采集故障信息并存储。
本实施例中，在未采集到故障信息或校验失败时，可由维护人员手持指定的终端至现场采集故障信息，首先发生故障的设备可与指定的终端建立无线连接，例如建立红外、蓝牙或NFC等无线连接，与终端建立连接后，可以自动采集故障信息也可以由维护人员使用通过输入采集命令的方式进行采集。
本实施例中，在采集故障信息后，可将其进行加密存储，以提高安全性。
本实施例在设备故障或业务故障时，例如单板发生故障时，能根据预先配置的采集方式尝试采集故障信息并将采集到的故障信息进行校验，在未采集到故障信息或校验失败时，可与终端建立连接，通过终端采集故障信息，在设备故障发生时第一时间获取故障点的故障信息，能够及时采集到有效的故障信息，方便维护人员对故障设备进行恢复或者进行其他的处理，确保业务的正常运行。
在一优选的实施例中，如图6所示，在上述图5的实施例的基础上，第一采集模块101包括：
第一获取单元1011，设置为当设备故障或业务故障时，根据预先配置的采集方式获取故障部件上报的故障事件以及获取故障部件寄存器中的参数；
第二获取单元1012，设置为根据所述故障事件及所述参数尝试采集故障信息。
本实施例中，当设备故障或业务故障时，例如故障部件为单板，以单板复位为例，单板出现复位故障可能是故障复位也可能是人为手动复位：
当通过主控单板监控到单板硬件接口和软件接口的变化(例如设备的H口和S口的变化)，以及通过主控单板收到的单板上报的复位事件(即故障事件)，判断该复位事件是自动复位还是人为手动复位。
当复位事件是手动复位时，根据故障采集数据字典里的采集方式，查询单板寄存器中的参数(例如参数中的第7位是代表复位状态的值)，若该参数与复位事件一致，则上报给上述的网络管理系统，并保存寄存器中的参数，确认是手动复位；
当复位事件是自动复位时，根据故障采集数据字典里的采集方式，查询单板寄存器中的参数，若该参数与复位事件一致，则上报给上述的网络管理系统，并保存寄存器中的参数，确认是自动复位；
当仅仅监测到单板硬件接口和软件接口的变化，未获取到复位事件(复位事件可能未上报或上报时丢失)，则查询单板寄存器中的参数，并将参数上报给上述的网络管理系统；
当仅监测到单板硬件接口和软件接口的变化，未获取到复位事件，且无法进行单板寄存器的查询，则通知网络管理系统故障采集失败。
网络管理系统将单板寄存器中的参数按照自身数据库中存储的翻译文件进行校验，例如寄存器中的参数为00000000010102，则网络管理系统将此参数进行读取，例如最后一位02代表手动复位，则与故障事件进行匹配，两者都是手动复位，则通过校验，并保存寄存机中对应的参数，确认是手动复位，若不一致，则将此信息记录在网络管理系统中，供维护人员查看并再次进行故障定位。
在一优选的实施例中，如图7所示，在上述图5的实施例的基础上，第二采集模块104包括：
采集单元1041，设置为接收所述终端发送的采集命令，根据所述采集指令采集故障部件的底层信息；
第三获取单元1042，设置为根据所述底层信息获取故障信息并存储。
本实施例中，在设备与终端建立连接后，接收终端发送的采集命令，设备根据数据字典带有的底层故障信息采集方式，对故障部件发起底层权限的申请请求，对故障部件的底层芯片采集底层信息，并对故障部件进行镜像操作，将故障部件当前状态信息及所采集的底层信息打包存储。
在一优选的实施例中，如图8所示，在上述图5的实施例的基础上，第一发送模块103包括：
第一发送单元1031，设置为在未采集到故障信息或校验失败时，获取预先生成的校验码，将所述校验码发送给指定的终端；
第二发送单元1032，设置为在所述终端根据所述校验码通过校验后，与终端建立连接。
本实施例中，在未采集到故障信息或校验失败时，与终端建立连接时，设备自身预先生成校验码并发送给终端，优选地，可以由网络管理系统生成校验码并发送给终端，在终端根据校验码通过校验后，与终端建立连接，通过校验码的实时性及唯一性来提高故障信息采集及故障信息的安全性。
进一步地，在另一优选的实施例中，在设备与指定的终端建立连接后，可以由设备将采集权限信息下发给终端，这样，有采集权限的终端方可采集到设备上的故障信息，能够进一步提高故障信息采集及故障信息的安全性。
在一优选的实施例中，在采集到故障信息后，设备将校验成功的故障信息或者将所采集的故障信息发送给终端，终端进行显示，维护人员可以在终端上进行操作或进行故障处理。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述模块分别位于多个处理器中。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，当设备故障或业务故障时，根据预先配置的采集方式尝试采集故障信息；
S2，在采集到故障信息后，将所采集的故障信息进行完整性校验；
S3，在未采集到故障信息或校验失败时，与指定的终端建立连接；
S4，接收所述终端发送的采集命令，根据所述采集命令采集故障信息并存储。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
以上仅为本发明的优选实施例，并非因此限制本发明的专利范围，凡是利用本发明说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本发明的专利保护范围内。
本发明实施例提供的上述技术方案，在设备故障或业务故障时，例如单板发生故障时，能根据预先配置的采集方式尝试采集故障信息并将采集到的故障信息进行校验，在未采集到故障信息或校验失败时，可与终端建立连接，通过终端采集故障信息，在设备故障发生时第
一时间获取故障点的故障信息，能够及时采集到有效的故障信息，方便维护人员对故障设备进行恢复或者进行其他的处理，确保业务的正常运行。
Claims (10)
- 一种故障信息采集的方法，所述故障信息采集的方法包括：当设备故障或业务故障时，根据预先配置的采集方式尝试采集故障信息；在采集到故障信息后，将所采集的故障信息进行完整性校验；在未采集到故障信息或校验失败时，与指定的终端建立连接；接收所述终端发送的采集命令，根据所述采集命令采集故障信息并存储。
- 如权利要求1所述的故障信息采集的方法，其中，所述当设备故障或业务故障时，根据预先配置的采集方式尝试采集故障信息的步骤包括：当设备故障或业务故障时，根据预先配置的采集方式获取故障部件上报的故障事件以及获取故障部件寄存器中的参数；根据所述故障事件及所述参数尝试采集故障信息。
- 如权利要求2所述的故障信息采集的方法，其中，所述接收所述终端发送的采集命令，根据所述采集命令采集故障信息并存储的步骤包括：接收所述终端发送的采集命令，根据所述采集指令采集故障部件的底层信息；根据所述底层信息获取故障信息并存储。
- 如权利要求1所述的故障信息采集的方法，其中，所述在未采集到故障信息或校验失败时，与指定的终端建立连接的步骤包括：在未采集到故障信息或校验失败时，获取预先生成的校验码，将所述校验码发送给指定的终端；在所述终端根据所述校验码通过校验后，与终端建立连接；所述在未采集到故障信息或校验失败时，与指定的终端建立连接的步骤之后包括：获取采集权限信息并将所述采集权限信息下发给所述终端，以与有权限的终端配合采集故障信息。
- 如权利要求1至4任一项所述的故障信息采集的方法，其中，所述接收所述终端根据所述采集权限信息发送的采集命令，根据所述采集命令采集故障信息并存储的步骤之后还包括：将校验成功的故障信息或者将所采集的故障信息发送给所述终端，以供所述终端进行显示或进行故障处理。
- 一种故障信息采集的装置，所述故障信息采集的装置包括：第一采集模块，设置为当设备故障或业务故障时，根据预先配置的采集方式尝试采 集故障信息；校验模块，设置为在采集到故障信息后，将所采集的故障信息进行完整性校验；第一发送模块，设置为在未采集到故障信息或校验失败时，与指定的终端建立连接；第二采集模块，设置为接收所述终端发送的采集命令，根据所述采集命令采集故障信息并存储。
- 如权利要求6所述的故障信息采集的装置，其中，所述第一采集模块包括：第一获取单元，设置为当设备故障或业务故障时，根据预先配置的采集方式获取故障部件上报的故障事件以及获取故障部件寄存器中的参数；第二获取单元，设置为根据所述故障事件及所述参数尝试采集故障信息。
- 如权利要求7所述的故障信息采集的装置，其中，所述第二采集模块包括：采集单元，设置为接收所述终端发送的采集命令，根据所述采集指令采集故障部件的底层信息；第三获取单元，设置为根据所述底层信息获取故障信息并存储。
- 如权利要求6所述的故障信息采集的装置，其中，所述第一发送模块包括：第一发送单元，设置为在未采集到故障信息或校验失败时，获取预先生成的校验码，将所述校验码发送给指定的终端；第二发送单元，设置为在所述终端根据所述校验码通过校验后，与终端建立连接；所述故障信息采集的装置还包括：下发模块，设置为获取采集权限信息并将所述采集权限信息下发给所述终端，以与有权限的终端配合采集故障信息。
- 如权利要求6至9任一项所述的故障信息采集的装置，其中，所述故障信息采集的装置还包括：第二发送模块，设置为将校验成功的故障信息或者将所采集的故障信息发送给所述终端，以供所述终端进行显示或进行故障处理。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510282114.4 | 2015-05-28 | ||
| CN201510282114.4A CN106301841A (zh) | 2015-05-28 | 2015-05-28 | 故障信息采集的方法及装置 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2016188223A1 true WO2016188223A1 (zh) | 2016-12-01 |
Family
ID=57392475
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2016/077901 WO2016188223A1 (zh) | 2015-05-28 | 2016-03-30 | 故障信息采集的方法及装置 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106301841A (zh) |
| WO (1) | WO2016188223A1 (zh) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111950743A (zh) * | 2020-07-08 | 2020-11-17 | 北京思特奇信息技术股份有限公司 | 一种用于移动终端故障工单解决的方法及系统 |
| CN112214491A (zh) * | 2020-10-19 | 2021-01-12 | 珠海格力电器股份有限公司 | 故障数据的采集方法、故障数据采集终端 |
| CN112579335A (zh) * | 2020-12-18 | 2021-03-30 | 歌尔光学科技有限公司 | 智能设备故障处理方法、装置、设备及存储介质 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1832417A (zh) * | 2005-03-10 | 2006-09-13 | 华为技术有限公司 | 一种数据采集方法及系统 |
| CN102608970A (zh) * | 2012-03-05 | 2012-07-25 | 浪潮通信信息系统有限公司 | 一种基于集中管理、自动调度的分布式数据采集的方法 |
| CN103095492A (zh) * | 2012-12-28 | 2013-05-08 | 中兴通讯股份有限公司 | 一种数据采集方法及装置 |
| US9021310B1 (en) * | 2012-02-14 | 2015-04-28 | Amazon Technologies, Inc. | Policy-driven automatic network fault remediation |
-
2015
- 2015-05-28 CN CN201510282114.4A patent/CN106301841A/zh active Pending
-
2016
- 2016-03-30 WO PCT/CN2016/077901 patent/WO2016188223A1/zh active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1832417A (zh) * | 2005-03-10 | 2006-09-13 | 华为技术有限公司 | 一种数据采集方法及系统 |
| US9021310B1 (en) * | 2012-02-14 | 2015-04-28 | Amazon Technologies, Inc. | Policy-driven automatic network fault remediation |
| CN102608970A (zh) * | 2012-03-05 | 2012-07-25 | 浪潮通信信息系统有限公司 | 一种基于集中管理、自动调度的分布式数据采集的方法 |
| CN103095492A (zh) * | 2012-12-28 | 2013-05-08 | 中兴通讯股份有限公司 | 一种数据采集方法及装置 |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111950743A (zh) * | 2020-07-08 | 2020-11-17 | 北京思特奇信息技术股份有限公司 | 一种用于移动终端故障工单解决的方法及系统 |
| CN112214491A (zh) * | 2020-10-19 | 2021-01-12 | 珠海格力电器股份有限公司 | 故障数据的采集方法、故障数据采集终端 |
| CN112579335A (zh) * | 2020-12-18 | 2021-03-30 | 歌尔光学科技有限公司 | 智能设备故障处理方法、装置、设备及存储介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106301841A (zh) | 2017-01-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6496427B2 (ja) | 空気調和ユニットのロック解除方法、装置及びサーバ | |
| CN107623698B (zh) | 远程调试网络设备方法和装置 | |
| US6993683B2 (en) | Analysis of pipelined networks | |
| US10430593B2 (en) | Boot images for units under test | |
| CN105518629A (zh) | 云部署基础结构确认引擎 | |
| RU2011140357A (ru) | Способ и устройство для проверки и подтверждения целостности h(e)nb | |
| CN103138988B (zh) | 网络故障的定位处理方法及装置 | |
| CN107800783B (zh) | 远程监控服务器的方法及装置 | |
| WO2019047070A1 (zh) | 一种数据库维护方法及其系统 | |
| WO2016188223A1 (zh) | 故障信息采集的方法及装置 | |
| CN110063042B (zh) | 一种数据库故障的响应方法及其终端 | |
| CN108965294A (zh) | 一种用户名及密码保护系统 | |
| US20150186677A1 (en) | Server chassis physical security enforcement | |
| CN112905437A (zh) | 一种测试用例的方法、装置及存储介质 | |
| CN111130848B (zh) | 身份验证授权统计aaa的故障检测方法及装置 | |
| CN111782372A (zh) | java进程的启动方法、装置、计算机设备和存储介质 | |
| KR20150025106A (ko) | 애플리케이션 검증결과 모니터링 서비스를 위한 검증장치, 단말장치, 시스템, 방법 및 컴퓨터로 판독 가능한 기록 매체 | |
| US11438380B2 (en) | Method and computing device for commissioning an industrial automation control system | |
| US7962789B2 (en) | Method and apparatus for automated testing of a utility computing system | |
| CN107135089B (zh) | 一种对操作维护中心系统进行升级的方法和装置 | |
| CN111815332A (zh) | 一种设备激活方法、装置及系统 | |
| CN115396231A (zh) | 一种网络安全设备测试系统 | |
| CN110737595A (zh) | 一种自动化测试方法及装置 | |
| CN110932898B (zh) | 一种智能网络管理系统及方法 | |
| CN112650557A (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: 16799112 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: 16799112 Country of ref document: EP Kind code of ref document: A1 |