CN107992408B - A kind of software probe method of software probe - Google Patents
A kind of software probe method of software probe Download PDFInfo
- Publication number
- CN107992408B CN107992408B CN201711136725.3A CN201711136725A CN107992408B CN 107992408 B CN107992408 B CN 107992408B CN 201711136725 A CN201711136725 A CN 201711136725A CN 107992408 B CN107992408 B CN 107992408B
- Authority
- CN
- China
- Prior art keywords
- software
- probe
- detected
- information
- identification 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3696—Methods or tools to render software testable
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The present invention relates to a kind of software probe methods of software probe, including software to identify, fault case is collected, software emulation, five steps such as software probe and detection result push.The method of the present invention is simple, operation and implementation are easy, on the one hand when carrying out software probe operation, it will not influence software equipment normal operation, to effectively raise convenience, flexibility and the reliability of software probe operation, on the other hand when carrying out software probe operation, the working efficiency and precision of effective raising detect operation, while being also convenient for the corresponding processing method of the failure for directly obtaining with detecting.
Description
Technical field
The present invention relates to a kind of software probe methods of software probe, belong to computer software technical field.
Background technique
The various kinds of equipment based on computer software operation all kinds of at present are in the fields such as routine office work, automation control
It is widely used, in actual operation, in order to improve equipment reliability of operation and stability, and meets equipment to not
With the needs of working condition operation, it is required to carry out failure detection to the operating status of the software run in each equipment, but current
When carrying out software systems detect operation, mainly by being run by dedicated software probe class software to target software
It is detected in the process, although this mode can satisfy the needs to software probe operation, but detect operation efficiency is relatively
It is low, while easily leading to detected software when one side detect operation and being unable to operate normally, on the other hand also easily lead to detect operation
Result be often only capable of obtaining simple fault message and effective counter-measure lacked to the failure detected, so as to cause working as
The preceding working efficiency when carrying out software probe operation is relatively poor, and reliability is relatively low, therefore is directed to this problem, urgently
Need to develop a kind of completely new software probe method, to meet the needs of actual use.
Summary of the invention
The object of the invention, which is that, overcomes above-mentioned deficiency, provides a kind of software probe method of software probe.
To achieve the above object, the present invention is to be achieved through the following technical solutions:
A kind of software probe method of software probe, comprising the following steps:
The first step, software identification, will be equipped with first the test equipment of software probe by data communication mechanism with to
Inspection software operation terminal room interlinks, and then carries out identification by test equipment and operation terminal room, and complete body
After part identification, the identification information of current runs software is sent from operation terminal to test equipment, and visit in the software of test equipment
It surveys device to complete after identifying software identification information, the software copy backup to be detected in terminal will be run into test equipment, so
Establish the software probe information recognized list based on software identification information and software information list to be detected respectively afterwards, and by software
Detection information recognized list and software information list to be detected interlink with software probe；
Second step, fault case collect, complete first step operation after, according to the first step acquire software identification information, by
Test equipment collects the most common failure and troubleshooting case that match with each software identification information by communication network, then ties
Software fault identification information root to be detected is established in the software information list to be detected for closing the first step, then will collect to
Inspection software most common failure and troubleshooting case are saved under software fault identification information root to be detected, then by software
Detector interlinks with software fault identification information root to be detected；
After completing the first step, it is to be checked in test equipment to directly drive backup by test equipment for third step, software emulation
It surveys software copy backup part and carries out simulation run, then during carrying out simulation run, by software probe to be detected soft
The operating status of part copy backup part is monitored；
4th step, software probe after completing second step operation, identify according to software collected in the first step believe first
Breath, recognizes current runs software essential information, is then started according to software identification information corresponding in software probe
Code is detected, and by the detection code building detection data recognized list of each starting, and is set in detection data recognized list
At least one detection pointer, then by detection pointer respectively with current simulation run software, software probe information recognized list, to
Inspection software information list and software fault identification information root to be detected establish data link, and in simulation software operation
When occurring with the corresponding data segment of pointer data is detected, then by software probe software probe information recognized list, to be detected soft
Part information list and software fault identification information root to be detected establish data link, on the one hand prompt current simulation software event
Hinder information, on the other hand immediately arrive at fault message and corresponding troubleshooting methods, to complete to carry out detection work to software
Industry；
5th step, detection result push, after completing the 4th step operation, the detection failure knot that will be obtained after simulation run
On the one hand fruit and troubleshooting methods information are stored in test equipment, be on the other hand pushed directly to corresponding operation terminal position
Set place.
Further, in the first step software identification information include software version information, it is software check value information, soft
Part updates policy information.
Further, in the second step, the software most common failure to be detected collected and troubleshooting side
In case, when a failure has multiple troubleshooting methods, each troubleshooting methods are mutually juxtaposed, and according to troubleshooting side
Case, which corresponds to program and arrives from childhood, to be arranged greatly, and establishes software fault identification information level-one specific item to be detected after completing arrangement
Record.
Further, in the third step, when software carries out simulation run, continuous operation 2-5 times, respectively to each fortune
Row carries out operating status complete monitoring.
Further, in the 4th step, detecting data in pointer is octal system, appointing in hexadecimal structured data
Anticipate one kind, and detecting pointer content includes interruption subroutine and identification data segment, and interruption subroutine respectively with identification data
Section, current simulation run software, software probe information recognized list, software information list to be detected and software fault to be detected are known
Other information root establishes data link.
Further, the identification data segment includes the identification information of software, probe software fault identification information, detection
Code information.
Further, in the 4th step, when detection pointer is two and is more than two, each interruption for detecting pointer
Program is identical, and identification data segment content is different.
Further, the interruption subroutine includes software addressing retrieval subprogram, counting statistics subprogram, degree of belief
Counting subroutine and data sorting subprogram.
The method of the present invention is simple, and operation and implementation are easy, and on the one hand when carrying out software probe operation, will not influence software
Equipment operates normally, to effectively raise the convenience of software probe operation, flexibility and reliability, on the other hand into
When row software probe operation, the effective working efficiency and precision for improving detect operation, while being also convenient for directly obtaining and detect
The corresponding processing method of the failure arrived.
Detailed description of the invention
Fig. 1 is flow diagram of the present invention；
Fig. 2 is that detection pointer data links schematic diagram.
Specific embodiment
As illustrated in fig. 1 and 2, a kind of software probe method of software probe, comprising the following steps:
The first step, software identification, will be equipped with first the test equipment of software probe by data communication mechanism with to
Inspection software operation terminal room interlinks, and then carries out identification by test equipment and operation terminal room, and complete body
After part identification, the identification information of current runs software is sent from operation terminal to test equipment, and visit in the software of test equipment
It surveys device to complete after identifying software identification information, the software copy backup to be detected in terminal will be run into test equipment, so
Establish the software probe information recognized list based on software identification information and software information list to be detected respectively afterwards, and by software
Detection information recognized list and software information list to be detected interlink with software probe；
Second step, fault case collect, complete first step operation after, according to the first step acquire software identification information, by
Test equipment collects the most common failure and troubleshooting case that match with each software identification information by communication network, then ties
Software fault identification information root to be detected is established in the software information list to be detected for closing the first step, then will collect to
Inspection software most common failure and troubleshooting case are saved under software fault identification information root to be detected, then by software
Detector interlinks with software fault identification information root to be detected；
After completing the first step, it is to be checked in test equipment to directly drive backup by test equipment for third step, software emulation
It surveys software copy backup part and carries out simulation run, then during carrying out simulation run, by software probe to be detected soft
The operating status of part copy backup part is monitored；
4th step, software probe after completing second step operation, identify according to software collected in the first step believe first
Breath, recognizes current runs software essential information, is then started according to software identification information corresponding in software probe
Code is detected, and by the detection code building detection data recognized list of each starting, and is set in detection data recognized list
At least one detection pointer, then by detection pointer respectively with current simulation run software, software probe information recognized list, to
Inspection software information list and software fault identification information root to be detected establish data link, and in simulation software operation
When occurring with the corresponding data segment of pointer data is detected, then by software probe software probe information recognized list, to be detected soft
Part information list and software fault identification information root to be detected establish data link, on the one hand prompt current simulation software event
Hinder information, on the other hand immediately arrive at fault message and corresponding troubleshooting methods, to complete to carry out detection work to software
Industry；
5th step, detection result push, after completing the 4th step operation, the detection failure knot that will be obtained after simulation run
On the one hand fruit and troubleshooting methods information are stored in test equipment, be on the other hand pushed directly to corresponding operation terminal position
Set place.
In the present embodiment, in the first step software identification information include software version information, software check value information,
Software upgrading policy information.
In the present embodiment, in the second step, the software most common failure to be detected collected and troubleshooting
In scheme, when a failure has multiple troubleshooting methods, each troubleshooting methods are mutually juxtaposed, and according to troubleshooting
Scheme, which corresponds to program and arrives from childhood, to be arranged greatly, and establishes software fault identification information level-one specific item to be detected after completing arrangement
Record.
In the present embodiment, in the third step, when software carries out simulation run, continuous operation 2-5 times, respectively to every
Secondary operation carries out operating status complete monitoring.
In the present embodiment, in the 4th step, detecting data in pointer is octal system, in hexadecimal structured data
Any one, and detecting pointer content includes interruption subroutine and identification data segment, and interruption subroutine respectively with identification number
According to section, current simulation run software, software probe information recognized list, software information list to be detected and software fault to be detected
Identification information root establishes data link.
In the present embodiment, the identification data segment includes the identification information of software, probe software fault identification information, inspection
Survey code information.
In the present embodiment, in the 4th step, when detection pointer is two and is more than two, each interruption for detecting pointer
Subprogram is identical, and identification data segment content is different.
In the present embodiment, the interruption subroutine includes software addressing retrieval subprogram, counting statistics subprogram, trusts
Spend counting subroutine and data sorting subprogram.
The method of the present invention is simple, and operation and implementation are easy, and on the one hand when carrying out software probe operation, will not influence software
Equipment operates normally, to effectively raise the convenience of software probe operation, flexibility and reliability, on the other hand into
When row software probe operation, the effective working efficiency and precision for improving detect operation, while being also convenient for directly obtaining and detect
The corresponding processing method of the failure arrived.
The above shows and describes the basic principles and main features of the present invention and the advantages of the present invention.The technology of the industry
Personnel are it should be appreciated that the present invention is not limited to the above embodiments, and the above embodiments and description only describe this
The principle of invention, without departing from the spirit and scope of the present invention, various changes and improvements may be made to the invention, these changes
Change and improvement all fall within the protetion scope of the claimed invention.The claimed scope of the invention by appended claims and its
Equivalent thereof.
Claims (8)
1. a kind of software probe method of software probe, it is characterised in that: the software probe method of the software probe
The following steps are included:
The first step, software identification, will be equipped with first the test equipment of software probe by data communication mechanism with it is to be detected
Software operation terminal room interlinks, and then carries out identification by test equipment and operation terminal room, and know completing identity
After not, the identification information of current runs software is sent from operation terminal to test equipment, and in the software probe of test equipment
After completing identification to software identification information, the software copy backup to be detected in terminal will be run into test equipment, then divided
Not Jian Li software probe information recognized list based on software identification information and software information list to be detected, and by software probe
Information recognized list and software information list to be detected interlink with software probe；
Second step, fault case are collected, after completing first step operation, according to the software identification information that the first step acquires, by testing
Equipment collects the most common failure and troubleshooting case that match with each software identification information by communication network, then in conjunction with the
Software fault identification information root to be detected is established in the software information list to be detected of one step, then to be detected by what is collected
Software most common failure and troubleshooting case are saved under software fault identification information root to be detected, then by software probe
Device interlinks with software fault identification information root to be detected；
After completing the first step, it is to be detected soft in test equipment to directly drive backup by test equipment for third step, software emulation
Part copy backup part carries out simulation run and treats inspection software then during carrying out simulation run by software probe and answer
The operating status of backup processed is monitored；
4th step, software probe are right first according to software identification information collected in the first step after completing second step operation
Current runs software essential information is recognized, and is then started in software probe according to software identification information and is detected generation accordingly
Code, and by the detection code building detection data recognized list of each starting, and at least one is set in detection data recognized list
A detection pointer, then by detection pointer respectively with current simulation run software, software probe information recognized list, to be detected soft
Part information list and software fault identification information root to be detected establish data link, and occur in simulation software operation with
When detecting the corresponding data segment of pointer data, then by software probe software probe information recognized list, software information to be detected
List and software fault identification information root to be detected establish data link, and current simulation software failure is on the one hand prompted to believe
Breath, on the other hand immediately arrives at fault message and corresponding troubleshooting methods, to complete to carry out detect operation to software；
5th step, detection result push, after completing the 4th step operation, by the detection failure result obtained after simulation run and
On the one hand troubleshooting methods information is stored in test equipment, be on the other hand pushed directly to corresponding operation terminal location
Place.
2. a kind of software probe method of software probe according to claim 1, it is characterised in that: the first step
Middle software identification information includes software version information, software check value information, software upgrading policy information.
3. a kind of software probe method of software probe according to claim 1, it is characterised in that: the second step
In, in the software most common failure to be detected collected and troubleshooting methods, when a failure has multiple failure rows
When except scheme, each troubleshooting methods are mutually juxtaposed, and according to troubleshooting methods are corresponded to program and arrived from childhood and arranged greatly, and
Software fault identification information first level subdirectory to be detected is established after completing arrangement.
4. a kind of software probe method of software probe according to claim 1, it is characterised in that: the third step
In, when software carries out simulation run, continuous operation 2-5 times, operating status complete monitoring is carried out to each run respectively.
5. a kind of software probe method of software probe according to claim 1, it is characterised in that: the 4th step
In, detecting data in pointer is octal system, any one in hexadecimal structured data, and is detected during pointer content includes
Disconnected subprogram and identification data segment, and interruption subroutine is believed with identification data segment, current simulation run software, software probe respectively
Breath recognized list, software information list to be detected and software fault identification information root to be detected establish data link.
6. a kind of software probe method of software probe according to claim 5, it is characterised in that: the identification number
It include the identification information, probe software fault identification information, detection code information of software according to section.
7. a kind of software probe method of software probe according to claim 1 or 5, it is characterised in that: described
In four steps, when detection pointer is two and is more than two, each interruption subroutine for detecting pointer is identical, and identification data segment content is each
It is not identical.
8. a kind of software probe method of software probe according to claim 5, it is characterised in that: interruption
Program includes software addressing retrieval subprogram, counting statistics subprogram, degree of belief counting subroutine and data sorting subprogram.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711136725.3A CN107992408B (en) | 2017-11-16 | 2017-11-16 | A kind of software probe method of software probe |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711136725.3A CN107992408B (en) | 2017-11-16 | 2017-11-16 | A kind of software probe method of software probe |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107992408A CN107992408A (en) | 2018-05-04 |
| CN107992408B true CN107992408B (en) | 2019-06-07 |
Family
ID=62030368
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711136725.3A Active CN107992408B (en) | 2017-11-16 | 2017-11-16 | A kind of software probe method of software probe |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107992408B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110503180B (en) * | 2019-08-14 | 2021-09-14 | Oppo广东移动通信有限公司 | Model processing method and device and electronic equipment |
| CN114756429A (en) * | 2022-04-13 | 2022-07-15 | 嘉兴职业技术学院 | Software operation fault detection method |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101001183A (en) * | 2007-01-10 | 2007-07-18 | 网之易信息技术（北京）有限公司 | Test method and system for network application software |
| CN101268448A (en) * | 2005-09-23 | 2008-09-17 | Lm爱立信电话有限公司 | Method and system for dynamic probes for injection and extraction of data for test and monitoring of software |
| CN101617296A (en) * | 2007-02-23 | 2009-12-30 | Lm爱立信电话有限公司 | Be used to test dynamic probe authentication method and system with monitoring of software |
| CN101923510A (en) * | 2010-04-13 | 2010-12-22 | 张克东 | Software detection method as well as software detector and software detection system applying same |
| CN106844194A (en) * | 2016-12-21 | 2017-06-13 | 北京航空航天大学 | A kind of construction method of multi-level software fault diagnosis expert system |
-
2017
- 2017-11-16 CN CN201711136725.3A patent/CN107992408B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101268448A (en) * | 2005-09-23 | 2008-09-17 | Lm爱立信电话有限公司 | Method and system for dynamic probes for injection and extraction of data for test and monitoring of software |
| CN101001183A (en) * | 2007-01-10 | 2007-07-18 | 网之易信息技术（北京）有限公司 | Test method and system for network application software |
| CN101617296A (en) * | 2007-02-23 | 2009-12-30 | Lm爱立信电话有限公司 | Be used to test dynamic probe authentication method and system with monitoring of software |
| CN101923510A (en) * | 2010-04-13 | 2010-12-22 | 张克东 | Software detection method as well as software detector and software detection system applying same |
| CN106844194A (en) * | 2016-12-21 | 2017-06-13 | 北京航空航天大学 | A kind of construction method of multi-level software fault diagnosis expert system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107992408A (en) | 2018-05-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN115118581B (en) | Internet of things data all-link monitoring and intelligent guaranteeing system based on 5G | |
| CN113328872B (en) | Fault repairing method, device and storage medium | |
| US8132053B2 (en) | System and method for grammar based test planning | |
| WO2020198256A1 (en) | Systems and methods for detecting and predicting faults in an industrial process automation system | |
| CN111010291B (en) | Business process abnormity warning method and device, electronic equipment and storage medium | |
| CN104583968A (en) | Management system and management program | |
| CA2101927A1 (en) | Knowledge based machine initiated maintenance system | |
| CN105116870B (en) | Fault analysis method, device and system of air conditioning unit | |
| US20090292951A1 (en) | Method and device for fault location in a system | |
| CN107992408B (en) | A kind of software probe method of software probe | |
| CN114640177B (en) | Electric energy efficiency monitoring method based on electric energy efficiency monitoring device | |
| CN103023028A (en) | Rapid grid failure positioning method based on dependency graph of entities | |
| CN106506226B (en) | A kind of starting method and device of fault detection | |
| CN103713215A (en) | System and method for detecting X-ray tube running state | |
| CN105872118A (en) | Detection method and device of node servers in DNS (Domain Name System) network | |
| CN105827469A (en) | MODBUS TCP implementation defect tester and detection method thereof | |
| CN110489260A (en) | Fault recognition method, device and BMC | |
| CN107957928B (en) | A kind of operation of software synchronization tests and analyzes and troubleshooting methodology | |
| CN103997126A (en) | Fault diagnosis grading method and system based on on-off state | |
| CN100568833C (en) | A kind of method of positioning communication fault location of equipment monitoring system | |
| US8972789B2 (en) | Diagnostic systems for distributed network | |
| CN116541728A (en) | Fault diagnosis method and device based on density clustering | |
| CN113608959B (en) | Method, system, terminal and storage medium for positioning fault hard disk | |
| CN116186976A (en) | Verification method and verification system for accuracy of data collected by equipment platform sensor | |
| CN111552263B (en) | Method, computer-readable storage medium and system for inspecting industrial facilities |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20190509 Address after: 528000 Block B 1501, 37 Fenjiang South Road, Chancheng District, Foshan City, Guangdong Province Applicant after: Guangdong to Network Technology Co., Ltd. Address before: 211100 two, B unit 300, Zhihui Road, Kirin science and Technology Innovation Park, Jiangning District, Nanjing, Jiangsu. Applicant before: Nanjing world Qi Xuan Source Software Technology Co. Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20201216 Address after: 223800 2nd floor, building A5, insurance Town, Hubin New District, Suqian City, Jiangsu Province Patentee after: Jiangsu Santaishan Data Application Research Institute Co., Ltd Address before: 528000 Block B 1501, 37 Fenjiang South Road, Chancheng District, Foshan City, Guangdong Province Patentee before: GUANGDONG MASHANGDAO NETWORK TECHNOLOGY Co.,Ltd. |