CN112230892A

CN112230892A - Fault management method based on extensible markup language

Info

Publication number: CN112230892A
Application number: CN202011104055.9A
Authority: CN
Inventors: 王雨龙
Original assignee: Tianjin Jinhang Computing Technology Research Institute
Current assignee: Tianjin Jinhang Computing Technology Research Institute
Priority date: 2020-10-15
Filing date: 2020-10-15
Publication date: 2021-01-15
Anticipated expiration: 2040-10-15
Also published as: CN112230892B

Abstract

The invention discloses a fault management method based on extensible markup language, comprising the following steps: designing a system fault management element; for different ground subsystems, respectively storing partial elements in system fault management elements in a subsystem local storage medium in the form of text documents; establishing connection between a server and client equipment, and analyzing a failure original document of the client equipment; loading a third-party open source XML class, and analyzing and loading the content file into the memory after the system is started; each ground subsystem is connected to the switch through the Ethernet and sends fault data to the fault management system; visually displaying and storing the current fault; and analyzing the XML file with the time as the name and displaying the analysis result. By using the extensible markup language, the fault list can be added, modified and deleted under the condition of not changing the source code, the fault information does not need to be compiled into the code, and the code amount is reduced.

Description

Fault management method based on extensible markup language

Technical Field

The invention belongs to the technical field of aerospace system data communication, and relates to a fault management method based on extensible markup language.

Background

In the management of the aircraft ground system, fault management is an important link, devices with different functions are connected through a switch, message data are sent through a network, and a fault management module receives fault information sent by different nodes through the Ethernet and displays the fault information through a human-computer interaction interface.

The XML, a subset of standard generalized markup languages, abbreviated as XML, is a markup language for marking electronic documents to be structured. Data elements are depicted using a set of tags, XML tags being employed throughout the system as well as across the system, so data for various different data stores will be more easily exchanged and manipulated.

Disclosure of Invention

Objects of the invention

In the fault management of the aircraft ground system, a mode which is usually adopted is to compile a fault list into a program in the form of codes, usually only a fault identifier is stored, and a user corresponds to fault and fault description according to the fault identifier.

(II) technical scheme

In order to solve the above technical problem, the present invention provides a fault management method based on a markable extensible language, including the following steps:

STEP1, designing a system fault management mode, wherein the fault management comprises the following STEPs: fault serial number errno., fault source ErrSrc, fault identification code ErrLabel, fault severity program ErrLevel, fault information description errcopy, fault solution ErrSolution, fault generation time ErrTime, and user remark ErrNote to fault information.

STEP2 for different ground subsystems, including a ground station Ex01, an executable logic unit Ex02, an information processing device Ex03 and a control device Ex04, respectively storing a fault identification code ErrLabel, a fault severity program ErrLevel and a fault information description ErrDescript in a local storage medium of the subsystem in the form of a text document.

STEP 3: the fault management device is used as a server, the devices Ex 01-Ex 04 are used as clients to establish connection, the fault management device acquires fault original documents of all the devices to the local through an ftp mode, and the text documents are analyzed through a python script mode. And generating an extensible markup language file, wherein the name of the XML file is content, the XML file takes ROOT as a ROOT node and List as a child node, the content of the node comprises an identification code ErrLabel, a fault severity program ErrLevel, fault information description ErrDescript and a fault solution Errsolution.

The ErrLabel is divided into four areas according to 16 bits, the area occupied by Ex01 is 0x 0100-0 x01ff, the area occupied by Ex02 is 0x 0200-0 x02ff, the area occupied by Ex03 is 0x 0300-0 x03ff, the area occupied by Ex04 is 0x 0400-0 x04ff, the fault severity program is divided into severity critic, importance, general normal and warning, and fault description and solution are provided by development of each ground system.

STEP4, loading a third-party open source XML class (the design adopts TINYXML), and analyzing and loading the content file into the memory after the system is started. The specific implementation method comprises the following steps: firstly, creating an XML file object with an object name of doc, loading the XML file by using a loading method of LoadFile, obtaining XM ROOT node elmroot by using a ROOT node obtaining method of Rootelement, pointing to first child element () through a ROOT pointer, circularly obtaining a plurality of data, setting an XML format pointer variable elmErrData, setting a cycle starting point as a first variable of the elmRoot, and respectively defining XMLEement type pointer variables, wherein the pointer variable is not null: the method comprises the steps of fault identification XMLErrLabel, fault severity XMLErrLevel, fault information description XMLErrDescript, fault solution XMLErrsolution, map template variable mapError provided by a C + + standard library, matching of two character strings through a template, setting the first character string as the value of the XMLErrLabel character string, setting the second character string variables as XMLErrLevel, XMLErrDescript and XMLErrsolution, and splicing of three character strings. After execution, the two strings are loaded into the memory using the mapError insertion method.

STEP5, each subsystem is connected to the switch through Ethernet, each subsystem sends fault data to the fault management system through UDP protocol, different subsystems are set to different IPs in the same network segment (for example, ground stations are set to IP:192.168.100.01PORT:0x8001, executable logic units are set to 192.168.100.02PORT:0x8002, information processing equipment is 192.168.100.03PORT:0x8003, control equipment is 192.168.100.04PORT:0x8004), the fault management system judges fault sources through IP and PORT numbers, a search method find in map is used, a fault identifier is used as a search variable, a second element of the searched data is extracted and placed in a variable sum. If the matching is not successful, prompting a user through a popup window, decomposing sum elements, proposing the severity of the fault, describing fault information, solving the fault, firstly reading the last fault by a fault sequence number processing method, and adding one to the new fault on the basis of the last fault. The system time record directly records the current time in a character string mode.

STEP 6: the current fault is displayed through a visualization method and is processed in the background, the processing mode is that the current fault is stored in an XML file mode, and the name of the stored file is time.

STEP7, adding XML file with time as name in visual display method to analyze, and displaying the analyzed fault sequence number ErrNo., fault source ErrSrc, fault identification code ErrLabel, fault severity program ErrLevel, fault information description ErrRescript, fault solution Errsolution, fault generation time ErrTime and fault information remark ErrNote of user.

(III) advantageous effects

According to the fault management method based on the extensible markup language, the extensible markup language is used, the fault list can be added, modified and deleted under the condition that the source code is not changed, fault information does not need to be compiled into the code, and the code amount is reduced.

Drawings

FIG. 1 is a flow chart of the method of the present invention.

Detailed Description

In order to make the objects, contents and advantages of the present invention clearer, the following detailed description of the embodiments of the present invention will be made in conjunction with the accompanying drawings and examples.

Referring to fig. 1, the fault management method based on the extensible markup language of the present invention includes the following steps:

The fault information is displayed visually.

STEP 6: the current fault is displayed through a visualization method and is processed in the background, the current fault is stored in an XML file mode, and the name of the stored file is time and XML.

The above description is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, several modifications and variations can be made without departing from the technical principle of the present invention, and these modifications and variations should also be regarded as the protection scope of the present invention.

Claims

1. A fault management method based on extensible markup language is characterized by comprising the following steps:

STEP1 designing system fault management elements;

STEP2, respectively storing partial elements in the system fault management elements in the local storage medium of the subsystem in the form of text documents for different ground subsystems;

STEP 3: the method comprises the steps that a fault management device serves as a server and is connected with client devices Ex 01-Ex 04, the fault management device acquires fault original documents of the client devices locally in an ftp mode, and analyzes text documents in a python script mode to generate extensible markup language files;

STEP4, loading a third-party open source XML class, and analyzing and loading the content file into the memory after the system is started;

STEP5, connecting each ground subsystem to a switch through Ethernet, sending fault data to a fault management system through UDP protocol, setting different ground subsystems as different IPs in the same network segment, judging fault source by the fault management system through IP and port number, using Hash to search for find method find in map, using fault identification as search variable, extracting the second element of the searched data, and putting the second element in variable sum; if the matching is not successful, prompting a user through a popup window, decomposing sum elements, and providing a fault severity, fault information description and fault solution, wherein a fault sequence number processing method firstly reads the last fault and adds one to a new fault on the basis of the last fault; the system time record directly records the current time in a character string mode;

STEP 6: displaying the current fault by a visualization method, and processing the current fault in a background in a way of storing the current fault in an XML file, wherein the name of the stored file is time, XML;

STEP7 parsing XML file named time is added to visualization method and parsed result is displayed.

2. The extensible markup language-based fault management method according to claim 1, wherein in said STEP1, the fault management element comprises: the fault identification code ErrNo. is a fault serial number ErrSrc, a fault identification code ErrLabel, a fault severity program ErrLevel, a fault information description ErrDescript, a fault solution Errsolution, a fault generation time ErrTime and a user note ErrNote of fault information.

3. The XML-based fault management method according to claim 2, wherein in STEP STEP2, the ground subsystem includes a ground station Ex01, an executable logic unit Ex02, an information processing device Ex03, and a control device Ex 04.

4. The extensible markup language-based fault management method according to claim 3, wherein in STEP STEP2, the system fault management elements stored in the subsystem local storage medium include a fault identification code ErrLabel, a fault severity ErrLevel, a fault information description ErrDescript, and a fault solution Errsolution.

5. The XML-based fault management method according to claim 4, wherein in STEP STEP3, the XML file name is content, the XML file has ROOT as the ROOT node, List as the child node, and the node contents include the identification code ErrLabel, the fault severity ErrLevel, the fault information description ErrDescript, and the fault resolution Errsolution.

6. The XML-based fault management method according to claim 5, wherein in STEP STEP3, ErrLabel is divided into four regions by 16 bits, Ex01 occupies 0x 0100-0 x01ff, Ex02 occupies 0x 0200-0 x02ff, Ex03 occupies 0x 0300-0 x03ff, Ex04 occupies 0x 0400-0 x04ff, the fault severity program is divided into severity, importance, normal and warning, and fault description and resolution schemes are developed and provided by each ground system.

7. The fault management method based on extensible markup language according to claim 6, wherein in STEP4, the content file parsing implementation method is: firstly, creating an XML file object with an object name of doc, loading the XML file by using a loading method LoadFile, obtaining XM ROOT node elmroot by using a ROOT node obtaining method Rootelement, pointing to first child element () through a ROOT pointer, circularly obtaining a plurality of data, setting an XML format pointer variable elmErrData, setting a circular starting point as a first variable of the elmRoot, respectively defining XMLELELELELEment type pointer variables and map template variables mapERROr provided by a C + + standard library, matching the templates by two character strings, setting the first character string as the value of the XMLErLabel character string, and setting the second character string variables as XMLErLevel, XMLErDescript and XMLErrSolution and splicing the three character strings; after execution, the character string is loaded into the memory by using a mapError insertion method.

8. The extensible markup language based fault management method according to claim 7, wherein in said STEP4, an xml element type pointer variable: the fault diagnosis method comprises a fault identification XMLErrLabel, a fault severity XMLErrLevel, a fault information description XMLErrDescript and a fault solution XMLErrsolution.

9. The XML-based fault management method according to claim 8, wherein in STEP STEP5, different ground subsystems are set to different IPs in the same network segment, the ground stations are set to IP 192.168.100.01PORT:0x8001, the executable logic unit is set to 192.168.100.02PORT:0x8002, the information processing device is 192.168.100.03PORT:0x8003, and the control device is 192.168.100.04PORT:0x 8004.

10. The fault management method based on extensible markup language according to claim 9, wherein in STEP7, the parsed and displayed content comprises: the fault identification code ErrNo. is a fault serial number ErrSrc, a fault identification code ErrLabel, a fault severity program ErrLevel, a fault information description ErrDescript, a fault solution Errsolution, a fault generation time ErrTime and a user note ErrNote of fault information.