CN107562562B - Method and system for setting extra information describing fault event - Google Patents
Method and system for setting extra information describing fault event Download PDFInfo
- Publication number
- CN107562562B CN107562562B CN201710806508.4A CN201710806508A CN107562562B CN 107562562 B CN107562562 B CN 107562562B CN 201710806508 A CN201710806508 A CN 201710806508A CN 107562562 B CN107562562 B CN 107562562B
- Authority
- CN
- China
- Prior art keywords
- extra information
- version number
- setting
- extra
- information
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000004458 analytical method Methods 0.000 claims abstract description 69
- 238000006243 chemical reaction Methods 0.000 claims abstract description 60
- 238000007405 data analysis Methods 0.000 claims abstract description 18
- 239000013589 supplement Substances 0.000 claims description 3
- 238000010606 normalization Methods 0.000 abstract description 6
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 229910002056 binary alloy Inorganic materials 0.000 description 8
- 238000013461 design Methods 0.000 description 6
- 238000013500 data storage Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 239000000047 product Substances 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000001502 supplementing effect Effects 0.000 description 1
Images
Landscapes
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a setting method of extra information for describing fault events, which comprises the following steps: carrying out storage form conversion on the extra information according to a preset system to obtain extra information of the preset system; generating a version number according to a preset system, and setting the version number before the extra information of the preset system, so that the version number and the extra information of the preset system form an extra information reading field together; setting the extra information reading field at a preset position of an original data structure to form a new data structure; and carrying out data analysis on the new data structure according to an analysis algorithm corresponding to the extra information reading field to obtain extra information. The setting method enables the storage form of the extra information to be more uniform and convenient to analyze through the binary conversion, and can match the corresponding analysis algorithm according to the version number, so that the matching analysis algorithm is more flexible to call, and the normalization of extra information setting is enhanced. The application also discloses a system for setting the extra information for describing the fault event, and the beneficial effects are achieved.
Description
Technical Field
The present application relates to the field of data structure technologies, and in particular, to a method and a system for setting extra information describing a failure event.
Background
When the storage system fails, the fault information is acquired and the fault event is reported, and the GUI (Graphical User Interface) terminal analyzes and visually presents the reported fault information. The event data reported by the bottom layer is a data structure which is confirmed by the bottom layer core software team and the management software team to collaborate, and mainly comprises event identification, the type of a Field Replaceable Unit (FRU) generated by a fault event, the FRU identification generated by the fault event, fault description information and other main fields.
And when the GUI receives the fault reported by the bottom layer, analyzing according to the data structure format of the contract, acquiring the reported data, and performing the next operation. The reported fields of the faults are general data structure fields of development team contracts, but in some fault events, the data structure fields of the contracts cannot completely describe fault information, for example, when a fault event that the temperature of an equipment disk is too high, extra temperature threshold data is needed, and the like, and data of the general structure of the contracts adopt that temperature threshold fields are independently added to store in the general structure, when data are needed to be obtained in a management software layer, firstly, the reported structure is judged, and if the fault event that the temperature of the disk is too high, the temperature threshold fields are independently obtained. According to the design method, the reported data structure has no universality, if other information needed by some faults is more, a lot of other field information can be added to the data structure of the deal, the analysis of the management software layer to the data can be judged according to different events firstly, and then the added field data can be obtained, obviously, a temperature threshold data field cannot be added to the fault event independently, otherwise, the data structure of the deal is not universal, the analysis method has a plurality of judgment branches, and the maintenance difficulty and the code readability are increased.
Therefore, how to provide a general additional information setting mechanism with higher versatility, more friendly information display condition and more flexible matching analysis algorithm invocation for the fault event with additional information is a problem to be solved urgently by the technical personnel in the field.
Disclosure of Invention
The method and the system are applied to the fault event with the extra information, the extra information storage form is more unified through the system conversion, the analysis is convenient, the corresponding analysis algorithm can be matched according to the version number, the universality is better, the calling of the matching analysis algorithm is more flexible, and the normalization of the extra information setting is enhanced.
In order to solve the above technical problem, the present application provides a setting method of additional information describing a failure event, the setting method including:
carrying out storage form conversion on the extra information according to a preset system to obtain extra information of the preset system;
generating a version number according to the preset system, and setting the version number before the extra information of the preset system so that the version number and the extra information of the preset system jointly form an extra information reading field;
setting the extra information reading field at a preset position of an original data structure to form a new data structure containing the extra information reading field;
and carrying out data analysis on the new data structure according to an analysis algorithm corresponding to the extra information reading field to obtain the extra information.
Optionally, the storing form conversion is performed on the extra information according to a preset scale, so as to obtain the extra information of the preset scale, and the method includes:
and carrying out the binary conversion on the additional information by using a 16-binary conversion rule to obtain 16-binary additional information.
Optionally, after the extra information is converted according to the storage form of the preset scale to obtain the extra information of the preset scale, the method further includes:
setting a maximum data length of the 16-ary additional information to 128 bytes;
and forming the 128-byte 16-system additional information in the form of 16 bytes in each group and 8 groups in total, so as to improve the readability of the 16-system additional information.
Optionally, the setting the extra information reading field at a preset position of an original data structure to form a new data structure including the extra information reading field includes:
setting the extra information reading field at the tail end of the original data structure so as to supplement the original information by using the extra information contained in the extra information reading field; wherein the original information is contained in the original data structure.
Optionally, performing data analysis on the new data structure according to an analysis algorithm corresponding to the extra information reading field to obtain the extra information, where the method includes:
converting the preset system version number in the extra information reading field into an Interger type to obtain an identifiable version number;
obtaining an analysis algorithm corresponding to the identifiable algorithm by utilizing the identifiable version number and the corresponding relationship between the version number and the corresponding analysis algorithm;
and carrying out data type conversion on the preset system extra information by using the analysis algorithm to obtain the restored extra information.
Optionally, before performing data analysis according to an analysis algorithm corresponding to the extra information reading field to obtain the extra information, the method further includes:
determining a setting object of the additional information reading field according to externally input configuration information;
generating an event configuration table by using the identification information of all the setting objects;
and configuring the event configuration table in the analysis algorithm, and judging whether a target object needs to call the analysis algorithm according to the event configuration table.
The present application also provides a setup system for additional information describing a failure event, the setup system comprising:
the system conversion unit is used for carrying out storage form conversion on the extra information according to a preset system to obtain the extra information of the preset system;
an additional information reading field generating unit, configured to generate a version number according to the preset scale and set the version number before the preset scale additional information, so that the version number and the preset scale additional information together form an additional information reading field;
a new data structure forming unit, configured to set the extra information reading field at a preset position of an original data structure, so as to form a new data structure including the extra information reading field;
and the matching algorithm analysis unit is used for carrying out data analysis on the new data structure according to the analysis algorithm corresponding to the extra information reading field to obtain the extra information.
Optionally, the binary conversion unit includes:
and the preferred system conversion unit is used for carrying out system conversion on the extra information by using a 16 system conversion rule to obtain 16 system extra information.
Optionally, the binary conversion unit further includes:
a byte length setting subunit configured to set a maximum data length of the 16-ary additional information to 128 bytes;
and the structure setting subunit is used for forming the 16-system extra information of the 128 bytes by using 16-byte groups and setting 8 groups in total so as to improve the readability of the 16-system extra information.
Optionally, the matching algorithm parsing unit includes:
a version number conversion subunit, configured to convert the preset system version number in the extra information reading field into an Interger type, so as to obtain an identifiable version number;
the matching analysis algorithm searching subunit is used for obtaining an analysis algorithm corresponding to the identifiable algorithm by utilizing the identifiable version number and the corresponding relationship between the version number and the corresponding analysis algorithm;
and the data analysis subunit is used for performing data type conversion on the preset system extra information by using the analysis algorithm to obtain the restored extra information.
According to the method for setting the extra information for describing the fault event, the extra information is converted according to the storage form of the extra information according to the preset scale, and the extra information of the preset scale is obtained; generating a version number according to the preset system, and setting the version number before the extra information of the preset system so that the version number and the extra information of the preset system jointly form an extra information reading field; setting the extra information reading field at a preset position of an original data structure to form a new data structure containing the extra information reading field; performing data analysis on the new data structure according to an analysis algorithm corresponding to the extra information reading field to obtain the extra information
Obviously, the technical scheme provided by the application is applied to the fault event with the extra information, the extra information storage form is more unified and is convenient to analyze through the binary conversion, the corresponding analysis algorithm can be matched according to the version number, the universality is better, the matching analysis algorithm is more flexible to call, and the normalization of the extra information setting is enhanced. The application also provides a system for setting the extra information for describing the fault event, which has the beneficial effects and is not repeated herein.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart illustrating a method for setting additional information describing a failure event according to an embodiment of the present disclosure;
FIG. 2 is a flow chart of another method for setting additional information describing a failure event provided by an embodiment of the present application;
fig. 3 is a block diagram illustrating a configuration of a system for setting additional information describing a failure event according to an embodiment of the present disclosure.
Detailed Description
The core of the application is to provide a method and a system for setting extra information for describing fault events, the method and the system are applied to the fault events with the extra information, the extra information storage form is more uniform through system conversion, analysis is convenient, corresponding analysis algorithms can be matched according to version numbers, the universality is better, the calling of the matching analysis algorithms is more flexible, and the normalization of extra information setting is enhanced.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Fig. 1 is a flowchart illustrating a method for setting additional information describing a failure event according to an embodiment of the present disclosure, in conjunction with fig. 1.
The method specifically comprises the following steps:
s101: carrying out storage form conversion on the extra information according to a preset system to obtain extra information of the preset system;
the step aims to convert the storage form of the extra information describing the fault event according to a preset system so as to obtain the preset extra information. The reason for the conversion according to the preset scale is that the original extra information adding party is not uniform, the adding form is not uniform, the maximum information length is not uniform, and the like, and the series of non-uniformity causes that the extra information added by multiple parties has no universal readability and has strong limitation, so that the step converts the extra information into the same storage form by using a common scale according to the length and content of the extra information under the actual condition and the universal rule of the multi-party reading equipment, and the subsequent reading equipment can restore the original extra information only by using the most common scale conversion.
The specific binary system used is not specifically limited, for example, the binary system, decimal system and 16 binary system are common, wherein the binary system has the highest universality, but the representation length of the binary system determines that the binary system is only suitable for describing very short information, so that the format is uniform, the reading is convenient, and the length after the conversion of the additional information is shorter, which means that more additional information can be stored in the same storage length. Of course, higher or other special systems can be adopted to perform storage form conversion of the additional information according to actual situations.
S102: generating a version number according to a preset system, and setting the version number before the extra information of the preset system so that the version number and the extra information of the preset system form an extra information reading field together;
on the basis of S101, this step is intended to perform version number conversion using the same default that is used to perform default scale conversion on the extra information, and place the converted default scale version number between the default scale extra information, so that the default scale version number and the default scale extra information together form an extra information reading field. The same preset system is used for unifying storage forms in the commonly formed extra information reading fields and enhancing the whole readability, for example, under the condition that 16 systems are selected to be used, 16 systems of extra information and 16 systems of version numbers obtained by 16 systems of conversion can be obtained in sequence.
The purpose of setting the version number is that, according to the different lengths of the extra information, the different preset systems possibly used by the special requirements of existence and the influence of other factors, a plurality of schemes can be generated and exist simultaneously, and the scheme of the system conversion and the use scheme and other changes used in the version are mapped or represented by different version numbers, just like only 1 year, 3 shifts can think about which students are in the version.
The reason why the version number is set before the predetermined system of extra information is that the version number information can be obtained first when the extra information reading field is read, so as to match the corresponding parsing algorithm in time. Of course, in special cases, the version number may be set in other special positions as long as the additional information reading field can be formed together and the version number can be identified for matching the corresponding parsing algorithm.
S103: setting the extra information reading field at a preset position of an original data structure to form a new data structure containing the extra information reading field;
on the basis of S103, this step is intended to set the formed additional information reading field at a preset position of the original data structure to form a new data structure containing the additional information reading field. The preset position is specifically located at what position of the original data structure, and the preset position is not specifically limited, and only the completeness and readability of the original data structure are not affected, and the additional extra information reading field can be read at the same time. The extra information reading field is usually placed at the end of the original data structure as the supplementary information, but the location may be considered according to the specific requirement, reading mode and other factors.
S104: and carrying out data analysis on the new data structure according to an analysis algorithm corresponding to the extra information reading field to obtain extra information.
On the basis of S103, this step aims to perform data parsing on the new data structure according to the parsing algorithm corresponding to the extra-information reading field, and the extra information converted into the storage form according to the presetting has been restored back to the original description mode.
In addition, because the extra information reading field provided by the present application is not attached to all the original data structures, the extra information needs to be supplemented only when the failure event cannot be fully described in the original data structures, and if the matching of the analysis algorithm is performed regardless of the description objects of all the original data structures, the matching efficiency is affected, and unnecessary computation load is consumed.
Therefore, furthermore, the setting object with the extra information reading field can be determined according to the configuration information of the external data, the event configuration table is generated by utilizing the identification information of the setting object, and the event configuration table is configured in the analysis algorithm.
Based on the technical scheme, the method for setting the extra information for describing the fault event is applied to the fault event with the extra information, the extra information storage form is more uniform through the system conversion, the analysis is convenient, the corresponding analysis algorithm can be matched according to the version number, the universality is better, the calling of the matching analysis algorithm is more flexible, and the normalization of extra information setting is enhanced.
Fig. 2 is a flowchart illustrating another method for setting additional information describing a failure event according to an embodiment of the present disclosure, in conjunction with fig. 2.
The method specifically comprises the following steps:
s201: carrying out scale conversion on the additional information by using a 16 scale conversion rule to obtain 16 scale additional information;
in this embodiment, the original extra information is converted by using a proper 16-system to obtain 16-system extra information under the 16-system, so as to ensure the storage length and uniform readability of most extra information.
S202: setting the maximum data length of the 16-ary additional information to 128 bytes;
on the basis of S201, the step sets the maximum data length of the 16-ary extra information to 128 bytes, considering that even if the length of the extra information cannot be too long, and the length of the 16-ary extra information obtained through 16-ary conversion is not allowed to exceed the maximum extent in normal cases, and considering that too much information causes inconvenience in display. Of course, the adjustment can be appropriately made according to the actual situation.
S203: 16-system extra information of 128 bytes is formed by using 16 bytes in each group and setting 8 groups in total;
on the basis of S202, in this step, considering that 128 bytes are displayed in the same level, or if there is information with distinct levels in the extra information, it is inconvenient for the administrator to read the core content after the display, so that this step adopts 16 bytes per group, and 8 groups together constitute the 128 bytes. Further, the 8 groups may also be named as Sense (read) 1 to Sense8, respectively.
S204: generating a 16-system version number in a 16-system mode, and setting the 16-system version number in front of 16-system extra information to jointly form an extra information reading field;
this step is intended to generate a 16-ary version number by using 16 as well, and place the 16-ary version number at the front end of the 16-ary extra information by adopting a common method to jointly form the extra information reading field.
S205: setting the extra information reading field at the tail end of the original data structure to form a new data structure containing the extra information reading field;
after the extra information read field is formed in S204, this step is intended to place the extra information read field at the end of the original data structure to construct a new data structure containing the extra information read field.
S206: determining a setting object of an additional information reading field according to externally input configuration information;
s207: generating an event configuration table by using the identification information of all the set objects, and configuring the event configuration table in an analysis algorithm;
s208: judging whether the target object needs to call an analysis algorithm or not according to the event configuration table;
s206, S207, and S208 are substantially the same as the contents in S104, and the detailed description may refer to the relevant part of S104, which is not described herein again.
S209: converting the preset system version number in the extra information reading field into an Interger type to obtain an identifiable version number;
this step is established on the basis that the decision result of S208 is that the target object needs to call the parsing algorithm, and is intended to convert the 16-system version number located in the extra information reading field into an Interger (number) type to specify the corresponding recognizable version number.
S210: obtaining an analytic algorithm corresponding to the identifiable algorithm by utilizing the identifiable version number and the corresponding relationship between the version number and the corresponding analytic algorithm;
on the basis of S209, this step aims to find the resolution algorithm corresponding to the identifiable algorithm by using the identification version number and the correspondence between the version number and the corresponding resolution algorithm. The corresponding relation should be set in advance, the concrete expression forms are various, and may be a corresponding table, a mapping relation or other similar expression forms, only the corresponding relation needs to be searched, and the method is not limited specifically here.
S211: and carrying out data type conversion on the preset system extra information by using an analysis algorithm to obtain the restored extra information.
Based on the technical scheme, the method for setting the extra information for describing the fault event is applied to the fault event with the extra information, the extra information storage form is more uniform through the system conversion, the analysis is convenient, the corresponding analysis algorithm can be matched according to the version number, the universality is better, the calling of the matching analysis algorithm is more flexible, and the normalization of extra information setting is enhanced.
Because the situation is complicated and cannot be illustrated by a list, those skilled in the art can realize that many examples exist based on the principle of the basic method provided by the present application in combination with the actual situation, and the method is within the scope of the present application without sufficient inventive effort.
Referring to fig. 3, fig. 3 is a block diagram illustrating a configuration of a system for setting additional information describing a failure event according to an embodiment of the present disclosure.
The setting system may include:
the system conversion unit 100 is configured to perform storage form conversion on the extra information according to a preset system to obtain extra information of the preset system;
an extra information reading field generating unit 200, configured to generate a version number in a preset scale, and set the version number before the preset scale extra information, so that the version number and the preset scale extra information together form an extra information reading field;
a new data structure forming unit 300, configured to set the extra information reading field at a preset position of the original data structure to form a new data structure including the extra information reading field;
and a matching algorithm analysis unit 400, configured to perform data analysis on the new data structure according to an analysis algorithm corresponding to the extra information reading field to obtain the extra information.
The binary conversion unit 100 includes:
and the preferred system conversion unit is used for performing system conversion on the extra information by using a 16 system conversion rule to obtain 16 system extra information.
Wherein the new data structure forming unit 300 includes:
the preferred end setting subunit is used for setting the extra information reading field at the end of the original data structure so as to supplement the extra information contained in the extra information reading field to the original information; wherein the original information is contained in an original data structure.
Wherein, the matching algorithm parsing unit 400 includes:
the version number conversion subunit is used for converting the preset system version number in the extra information reading field into an Interger type to obtain an identifiable version number;
the matching analysis algorithm searching subunit is used for obtaining an analysis algorithm corresponding to the identifiable algorithm by utilizing the identifiable version number and the corresponding relationship between the version number and the corresponding analysis algorithm;
and the data analysis subunit is used for performing data type conversion on the preset system extra information by using an analysis algorithm to obtain the restored extra information.
Further, the binary conversion unit 100 may further include:
a byte length setting subunit for setting a maximum data length of the 16-ary additional information to 128 bytes;
and the structure setting subunit is used for forming the 16-system extra information of 128 bytes by using 16 bytes in each group and setting 8 groups in total so as to improve the readability of the 16-system extra information.
Further, the setting system may further include:
a matching unit for determining a setting object of the extra information reading field according to externally input configuration information;
a configuration table generating unit for generating an event configuration table using identification information of all setting objects;
and the calling judgment unit is used for configuring the event configuration table in the analysis algorithm and judging whether the target object needs to call the analysis algorithm according to the event configuration table.
The above units can be applied to the following specific practical example:
since the present application mainly comprises 2 aspects: firstly, on the basis of an existing data structure, a sense data (extra information reading) field is added, extra data information is stored in a hexadecimal form, and a data storage form is designed; secondly, an analysis algorithm corresponding to the sense data is designed, field data information stored in the sense data is analyzed, and the following description is given.
1. sense data field design
The sense data field stores extra data information, firstly considering the data storage form of the extra information, and secondly the length size of the field.
(1) Data storage form
The reporting of the fault event is completed by the underlying core software, the sense data is used as a part of the reporting event, firstly, a system for storing the multi-purpose support of the operating system is considered, wherein the binary system and the hexadecimal system are most widely applied, the hexadecimal system has better readability than the binary system, and the length of extra information of the sense data can be influenced. The embodiment selects hexadecimal as the data storage form of the extra information in the sense data.
(2) sense data field length
The sense data is used as an extra information field for storing the fault event, is a field added on the basis of the existing general field, and is used for storing extra data in a hexadecimal form. The length of sense data needs to satisfy the following condition: (a) more extra information is stored; (b) some extra information is long, such as a serial number of a storage device.
Because the data information is represented in a hexadecimal form and is represented by a power number of 2, the data information has 64 bits, 128 bits and 256-bit length values, if ab is satisfied, the 64 bits may not be represented enough for some special events, and meanwhile, the data length is a bit too long for 256 bits, so that the data information is too complicated in analysis.
Here, the length of 128-bit byte is selected to store extra data information, and 0 is used for supplementing the insufficient bit number. If the CLI is used for query, the display content is poor in readability even though the length of a single field is 128 bytes, and the CLI can be further designed to divide the 128 bytes into 16-8 byte patterns for display, and the sensor 1-sensor 8 are used for sequentially representing, each sensor has 16 bytes, for example, the hex display for storing the HELLO WORLD information sensor data is as follows:
Sense1 01 00 48 45 4C 4C 4F 00 00 00 00 00 00 00 00 00
Sense2 00 00 00 00 00 00 00 00 00 00 00 57 4F 52 4C 44
Sense3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Sense4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Sense5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Sense6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Sense7 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Sense8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
number of bytes 128 of Sense data-number of bytes per row 16 x Sense row 8
The corresponding data structure is designed as follows:
struct SomeDataStruct
unit16 version
char hello[25]
char world[25]
wherein, version represents the version number of the current sense data, identifies different versions of the product, occupies the first 2 bytes of each sense data, and the 2 bytes of data are enough to represent different iteration numbers of the versions. HELLO byte data occupies 25 bytes, and the length is calculated from version, that is, HELLO data starts to occupy 25 bytes in bytes 3-27, similarly, world data occupies 25 bytes, and starts to occupy 25 bytes in bytes 28-52.
The reason why HELLO will occupy 25 bytes instead of 5 or 6 bytes is that the number of bytes used by "h" or other letters can be set by itself, and special requirements can be met in special cases.
2. sense data parsing algorithm
Corresponding data structures are designed on the sense data of the event, and when the sense data are analyzed, the corresponding analysis is carried out by referring to the data structures in the sense data design.
(1) Data byte number acquisition
According to the data structure during design, each data occupies a certain number of bytes, the number of bytes is obtained, the number of bytes occupied from the end position of the previous data to the data itself, such as the sense data of the above HELLO WORLD, it can be obtained that the HELLO data occupies 25 bytes of an array length of char (a basic data type that can accommodate a single character in a computer programming language), and then the start position of the HELLO data is from the 3 rd byte (after 2 bytes occupied by version) to 3+24, that is, the 27 th byte is ended.
And adding a version number in the sense data to identify the version applicable to the current sense data. The version number fixedly occupies 2 bytes in length, when the sense data is acquired, the version number is firstly verified, and the next data analysis is not needed for the sense data with unmatched version number.
(2) Data type conversion
The sense data is stored in hexadecimal, such as version and HELLO data, but the data has different types during analysis, and when the data is acquired according to the byte length, type conversion is required, for example, version is an Integer type, HELLO is a String type, and when the data is acquired, conversion into a corresponding format is required.
(3) Analytical algorithm
When the bottom layer fault is reported, the GUI displays the reported event, and at this time, if the event needs to be further analyzed, and when the event information is acquired, a sense data analysis function may be called. Whether the analysis function is called or not is agreed with the bottom layer, and what type of report information contains sense data needing analysis.
Firstly, judging whether function analysis is needed or not according to an event identifier, and establishing a new corresponding relationship key-value (event configuration table) between the event identifier and sense data analysis, wherein the value corresponds to a java (which is a one-door object oriented programming language) class for analyzing the sense data, so that the advantage of realizing the decoupling is that the sense data analysis of the event is separated from the service logic of the event, and the decoupling is realized;
secondly, acquiring the version number of the sense data, firstly checking the version number, and not needing to perform the next data analysis on the sense data with unmatched version numbers;
and finally, during analysis, calculating the initial position of each datum and the length of the number of bytes occupied according to the data structure designed by the current sense data, and acquiring data information from 128 bytes of the sense data according to the data type and the initial position and the length during design. And analyzing the Java classes, creating an enumeration class, wherein the attribute values in the enumeration correspond to the attribute values stored in the sense data one by one, and setting respective value values for each attribute in the enumeration class according to a data structure.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. A method for providing additional information describing a failure event, comprising:
carrying out storage form conversion on the extra information according to a preset system to obtain extra information of the preset system;
generating a version number according to the preset system, and setting the version number before the extra information of the preset system so that the version number and the extra information of the preset system jointly form an extra information reading field;
setting the extra information reading field at a preset position of an original data structure to form a new data structure containing the extra information reading field;
and carrying out data analysis on the new data structure according to an analysis algorithm corresponding to the extra information reading field to obtain the extra information.
2. The setting method according to claim 1, wherein the step of converting the storage form of the extra information according to a preset scale to obtain the extra information of the preset scale comprises:
and carrying out the binary conversion on the additional information by using a 16-binary conversion rule to obtain 16-binary additional information.
3. The setting method according to claim 2, wherein after the storing form conversion of the extra information according to the preset scale is performed to obtain the preset scale extra information, the method further comprises:
setting a maximum data length of the 16-ary additional information to 128 bytes;
and forming the 128-byte 16-system additional information in the form of 16 bytes in each group and 8 groups in total, so as to improve the readability of the 16-system additional information.
4. The setting method according to any one of claims 1 to 3, wherein setting the extra-information reading field at a predetermined position of an original data structure to form a new data structure containing the extra-information reading field comprises:
setting the extra information reading field at the tail end of the original data structure so as to supplement the original information by using the extra information contained in the extra information reading field; wherein the original information is contained in the original data structure.
5. The setting method according to claim 4, wherein performing data parsing on the new data structure according to a parsing algorithm corresponding to the extra information reading field to obtain the extra information comprises:
converting the version number in the extra information reading field into an Interger type to obtain an identifiable version number;
obtaining an analysis algorithm corresponding to the identifiable version number by utilizing the identifiable version number and the corresponding relationship between the version number and the corresponding analysis algorithm;
and carrying out data type conversion on the preset system extra information by using the analysis algorithm to obtain the restored extra information.
6. The setting method according to claim 5, before performing data parsing according to a parsing algorithm corresponding to the extra information reading field to obtain the extra information, further comprising:
determining a setting object of the additional information reading field according to externally input configuration information;
generating an event configuration table by using the identification information of all the setting objects;
and configuring the event configuration table in the analysis algorithm, and judging whether a target object needs to call the analysis algorithm according to the event configuration table.
7. A system for providing additional information describing a failure event, comprising:
the system conversion unit is used for carrying out storage form conversion on the extra information according to a preset system to obtain the extra information of the preset system;
an additional information reading field generating unit, configured to generate a version number according to the preset scale and set the version number before the preset scale additional information, so that the version number and the preset scale additional information together form an additional information reading field;
a new data structure forming unit, configured to set the extra information reading field at a preset position of an original data structure, so as to form a new data structure including the extra information reading field;
and the matching algorithm analysis unit is used for carrying out data analysis on the new data structure according to the analysis algorithm corresponding to the extra information reading field to obtain the extra information.
8. The setting system according to claim 7, wherein the scale conversion unit includes:
and the preferred system conversion unit is used for carrying out system conversion on the extra information by using a 16 system conversion rule to obtain 16 system extra information.
9. The setting system according to claim 8, wherein the scale conversion unit further includes:
a byte length setting subunit configured to set a maximum data length of the 16-ary additional information to 128 bytes;
and the structure setting subunit is used for forming the 16-system extra information of the 128 bytes by using 16-byte groups and setting 8 groups in total so as to improve the readability of the 16-system extra information.
10. The setup system according to any one of claims 7 to 9, wherein the companion algorithm parsing unit comprises:
a version number conversion subunit, configured to convert the version number in the extra information reading field into an Interger type, so as to obtain an identifiable version number;
the matching analysis algorithm searching subunit is used for obtaining an analysis algorithm corresponding to the identifiable version number by utilizing the identifiable version number and the corresponding relationship between the version number and the corresponding analysis algorithm;
and the data analysis subunit is used for performing data type conversion on the preset system extra information by using the analysis algorithm to obtain the restored extra information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710806508.4A CN107562562B (en) | 2017-09-08 | 2017-09-08 | Method and system for setting extra information describing fault event |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710806508.4A CN107562562B (en) | 2017-09-08 | 2017-09-08 | Method and system for setting extra information describing fault event |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107562562A CN107562562A (en) | 2018-01-09 |
| CN107562562B true CN107562562B (en) | 2021-06-29 |
Family
ID=60979762
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710806508.4A Active CN107562562B (en) | 2017-09-08 | 2017-09-08 | Method and system for setting extra information describing fault event |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107562562B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110517699B (en) * | 2019-08-23 | 2023-05-26 | 平安科技（深圳）有限公司 | Information steganography method, device, equipment and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104993584B (en) * | 2015-06-03 | 2017-03-15 | 广西电网有限责任公司 | Protect the generation method of letter failure and generate system |
| CN105843899B (en) * | 2016-03-23 | 2017-07-18 | 炫彩互动网络科技有限公司 | A kind of big data automation analytic method for simplifying programming and system |
-
2017
- 2017-09-08 CN CN201710806508.4A patent/CN107562562B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN107562562A (en) | 2018-01-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111176976B (en) | Test data generation method and device, storage medium and electronic device | |
| CN109902071A (en) | Business diary storage method, system, device and equipment | |
| CN110188135B (en) | File generation method and equipment | |
| CN108762764A (en) | Code automatic generation method, device, computer equipment and storage medium | |
| CN109871289A (en) | A kind of remote procedure call service creation method and device | |
| JP6653850B1 (en) | Electronic device for converting data set structure using JSON and method of operating the same | |
| CN110008743A (en) | Data attribute identification method, device and equipment in a kind of piece of chain type account book | |
| CN105227405A (en) | Method for supervising and system | |
| US20200019896A1 (en) | Numerical graphical flow diagram conversion and comparison | |
| CN115065459A (en) | Multi-party privacy set intersection method, device, equipment and storage medium | |
| CN115567607A (en) | Processing method, device and system for calling link, electronic equipment and storage medium | |
| CN107562562B (en) | Method and system for setting extra information describing fault event | |
| JP7041603B2 (en) | How to generate patterns for computer systems and business flows | |
| CN110019189A (en) | A kind of generation method and generation system of chart | |
| CN109783287B (en) | Test instruction generation method, system, terminal and medium based on configuration file | |
| CN107766519B (en) | Method for visually configuring data structure | |
| CN111339566B (en) | Block summarization method, device, computer equipment and storage medium | |
| CN117669514A (en) | Method and device for generating analysis report, electronic equipment and storage medium | |
| CN104378362A (en) | Method and device for carrying out conversion of message interfaces | |
| CN111143450A (en) | Method and device for importing data | |
| CN116738954A (en) | Report export method, report template configuration device and computer equipment | |
| CN113641523B (en) | Log processing method and device | |
| KR102429200B1 (en) | DNA code generation method based on Reversible Self-Dual code | |
| CN114970464A (en) | Method, device, terminal equipment and storage medium for generating identification | |
| CN109542904A (en) | Business data processing method, device, server and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |