CN107992408A - A kind of software probe method of software probe - Google Patents
A kind of software probe method of software probe Download PDFInfo
- Publication number
- CN107992408A CN107992408A CN201711136725.3A CN201711136725A CN107992408A CN 107992408 A CN107992408 A CN 107992408A CN 201711136725 A CN201711136725 A CN 201711136725A CN 107992408 A CN107992408 A CN 107992408A
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 33
- 238000001514 detection method Methods 0.000 claims abstract description 30
- 238000012360 testing method Methods 0.000 claims description 27
- 238000013024 troubleshooting Methods 0.000 claims description 23
- 238000004088 simulation Methods 0.000 claims description 18
- 238000004891 communication Methods 0.000 claims description 6
- 230000007246 mechanism Effects 0.000 claims description 3
- 238000012544 monitoring process Methods 0.000 claims description 3
- 238000005259 measurement Methods 0.000 claims 1
- 238000003672 processing method Methods 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000004888 barrier function Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
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
Abstract
The present invention relates to a kind of software probe method of software probe, including software to identify, fault case is collected, software emulation, five steps such as software probe and result of detection push.The method of the present invention is simple, operation and implementation are easy, on the one hand when carrying out software probe operation, software equipment normal operation is not interfered with, so as to effectively raise convenience, flexibility and the reliability of software probe operation, on the other hand when carrying out software probe operation, the work efficiency and precision of effective raising detect operation, while also allow for the corresponding processing method of the failure that directly obtains with detect.
Description
Technical field
The present invention relates to a kind of software probe method of software probe, belongs to computer software technical field.
Background technology
The various kinds of equipment based on computer software operation all kinds of at present are in the fields such as routine office work, automated control
It is widely used, in real work, in order to improve equipment reliability of operation and stability, and meets equipment to not
With the needs of working status operation, the operating status for being required to the software to being run in each equipment carries out failure detection, but currently
When carrying out software systems detect operation, mainly by being run by dedicated software probe class software to target software
During detected, although this mode can meet the needs to software probe operation, detect operation efficiency is relatively
It is low, at the same easily led to during one side detect operation detected software can not normal operation, on the other hand also easily lead to detect operation
Result be often only capable of obtaining simple fault message and the failure to detecting lacks effective counter-measure, so as to cause to work as
The preceding work 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 brand-new software probe method, to meet the needs of actual use.
The content of the invention
The object of the invention, which is that, overcomes above-mentioned deficiency, there is provided 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, comprises the following steps：
The first step, software identification, will be provided with first the test equipment of software probe by data communication mechanism with it is to be detected
Running software 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 identification being completed to software identification information, by the software copy backup to be detected run in terminal into test equipment, Ran Houfen
Do not establish the 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 of first step collection, 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
The software to be detected identification root directory contents of two steps establish software fault identification information root to be detected, then will collect
Software most common failure and troubleshooting case to be detected are saved under software fault identification information root to be detected, then by soft
Part detector interlinks with software fault identification information root to be detected；
3rd step, software emulation, after completing the first step, it is to be detected soft in test equipment to directly drive backup by test equipment
Part copy backup part carries out simulation run, then during simulation run is carried out, treats inspection software by software probe and answers
The operating status of backup processed is monitored；
4th step, software probe are right first according to the software identification information collected in the first step after completing second step operation
Current runs software essential information is recognized, and then starts corresponding detection generation in software probe according to software identification information
Code, and the detection code building of each startup is detected into data recognized list, and set at least one in data recognized list is detected
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 peace operation
During data segment corresponding with detection pointer data, then believed by software probe software probe information recognized list, software to be detected
Breath list and software fault identification information root to be detected establish data link, on the one hand prompt current simulation software failure to believe
Breath, on the other hand immediately arrives at fault message and corresponding troubleshooting methods, so as to complete to carry out detect operation to software；
5th step, result of detection 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.
Further, software identification information includes software version information, software check value information, soft in the first step
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 possesses 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 to arrange
Record.
Further, in the 3rd step, when software carries out simulation run, continuously run 2-5 times, respectively to each
Operation carries out operating status complete monitoring.
Further, in the 4th step, it is appointing in octal system, hexadecimal structured data to detect data in pointer
Meaning is a kind of, and detects pointer content and include main interruption subroutine and identification data segment, and main interruption subroutine respectively with identification
Data segment, current simulation run software, software probe information recognized list, software information list to be detected and software to be detected event
Barrier identification information root establishes data link.
Further, the identification data segment includes the identification information, probe software fault identification information, detection of software
Code information.
Further, in the 4th step, when detection pointer is two and two or more, 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 program.
The method of the present invention is simple, and operation and implementation are easy, on the one hand when carrying out software probe operation, do not interfere with software
Equipment normal operation, so as to effectively raise the convenience of software probe operation, flexibility and reliability, on the other hand into
It is effective to improve the work efficiency and precision of detect operation during row software probe operation, while also allow for directly obtaining and detect
The corresponding processing method of failure arrived.
Brief description of the drawings
Fig. 1 is flow diagram of the present invention；
Fig. 2 links schematic diagram for detection pointer data.
Embodiment
As illustrated in fig. 1 and 2, a kind of software probe method of software probe, comprises the following steps：
The first step, software identification, will be provided with first the test equipment of software probe by data communication mechanism with it is to be detected
Running software 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 identification being completed to software identification information, by the software copy backup to be detected run in terminal into test equipment, Ran Houfen
Do not establish the 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 of first step collection, 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
The software to be detected identification root directory contents of two steps establish software fault identification information root to be detected, then will collect
Software most common failure and troubleshooting case to be detected are saved under software fault identification information root to be detected, then by soft
Part detector interlinks with software fault identification information root to be detected；
3rd step, software emulation, after completing the first step, it is to be detected soft in test equipment to directly drive backup by test equipment
Part copy backup part carries out simulation run, then during simulation run is carried out, treats inspection software by software probe and answers
The operating status of backup processed is monitored；
4th step, software probe are right first according to the software identification information collected in the first step after completing second step operation
Current runs software essential information is recognized, and then starts corresponding detection generation in software probe according to software identification information
Code, and the detection code building of each startup is detected into data recognized list, and set at least one in data recognized list is detected
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 peace operation
During data segment corresponding with detection pointer data, then believed by software probe software probe information recognized list, software to be detected
Breath list and software fault identification information root to be detected establish data link, on the one hand prompt current simulation software failure to believe
Breath, on the other hand immediately arrives at fault message and corresponding troubleshooting methods, so as to complete to carry out detect operation to software；
5th step, result of detection 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.
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 possesses 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 to arrange
Record.
In the present embodiment, in the 3rd step, when software carries out simulation run, continuously run 2-5 times, respectively to every
Secondary operation carries out operating status complete monitoring.
In the present embodiment, in the 4th step, it is octal system, in hexadecimal structured data to detect data in pointer
Any one, and detects pointer content and includes main interruption subroutine and identification data segment, and main interruption subroutine respectively with knowledge
Other data segment, current simulation run software, software probe information recognized list, software information list to be detected and software to be detected
Fault identification information root establishes data link.
In the present embodiment, the identification data segment includes the identification information, probe software fault identification information, inspection of software
Survey code information.
In the present embodiment, in the 4th step, when detection pointer is two and two or more, 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 program.
The method of the present invention is simple, and operation and implementation are easy, on the one hand when carrying out software probe operation, do not interfere with software
Equipment normal operation, so as to effectively raise the convenience of software probe operation, flexibility and reliability, on the other hand into
It is effective to improve the work efficiency and precision of detect operation during row software probe operation, while also allow for directly obtaining and detect
The corresponding processing method of failure arrived.
The basic principles, main features and the advantages of the invention have been shown and described above.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 modifications of the present invention are possible, 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)
- A kind of 1. software probe method of software probe, it is characterised in that：The software probe method of the software probe Comprise the following steps：The first step, software identification, will be provided with first the test equipment of software probe by data communication mechanism with it is to be detected Running software 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 identification being completed to software identification information, by the software copy backup to be detected run in terminal into test equipment, Ran Houfen Do not establish the 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 of first step collection, 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 The software to be detected identification root directory contents of two steps establish software fault identification information root to be detected, then will collect Software most common failure and troubleshooting case to be detected are saved under software fault identification information root to be detected, then by soft Part detector interlinks with software fault identification information root to be detected；3rd step, software emulation, after completing the first step, it is to be detected soft in test equipment to directly drive backup by test equipment Part copy backup part carries out simulation run, then during simulation run is carried out, treats inspection software by software probe and answers The operating status of backup processed is monitored；4th step, software probe are right first according to the software identification information collected in the first step after completing second step operation Current runs software essential information is recognized, and then starts corresponding detection generation in software probe according to software identification information Code, and the detection code building of each startup is detected into data recognized list, and set at least one in data recognized list is detected 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 peace operation During data segment corresponding with detection pointer data, then believed by software probe software probe information recognized list, software to be detected Breath list and software fault identification information root to be detected establish data link, on the one hand prompt current simulation software failure to believe Breath, on the other hand immediately arrives at fault message and corresponding troubleshooting methods, so as to complete to carry out detect operation to software；5th step, result of detection 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.
- A kind of 2. software probe method for the software probe stated according to claim 1, it is characterised in that：In the first step Software identification information includes software version information, software check value information, software upgrading policy information.
- A kind of 3. software probe method for the software probe stated 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 possesses multiple failure rows During 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 to arrange.
- A kind of 4. software probe method for the software probe stated according to claim 1, it is characterised in that：3rd step In, when software carries out simulation run, continuously run 2-5 times, operating status complete monitoring is carried out to each run respectively.
- A kind of 5. software probe method for the software probe stated according to claim 1, it is characterised in that：4th step In, it is any one in octal system, hexadecimal structured data to detect data in pointer, and detects pointer content including master Interruption subroutine and identification data segment, and main interruption subroutine is visited with identification data segment, current simulation run software, software respectively Measurement information recognized list, software information list to be detected and software fault identification information root to be detected establish data link.
- A kind of 6. software probe method for the software probe stated according to claim 5, it is characterised in that：The identification data Section includes the identification information, probe software fault identification information, detection code information of software.
- A kind of 7. software probe method for the software probe stated according to claim 1, it is characterised in that：4th step In, for detection pointer when be two and two or more, the interruption subroutine of each detection pointer is identical, each not phase of identification data segment content Together.
- A kind of 8. software probe method for the software probe stated according to claim 5 or 7, it is characterised in that：The interruption Subprogram includes software addressing retrieval subprogram, counting statistics subprogram, degree of belief counting subroutine and data sorting program.
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 true CN107992408A (en) | 2018-05-04 |
| CN107992408B 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) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110503180A (en) * | 2019-08-14 | 2019-11-26 | Oppo广东移动通信有限公司 | Model treatment method, apparatus 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 |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110503180A (en) * | 2019-08-14 | 2019-11-26 | Oppo广东移动通信有限公司 | Model treatment method, apparatus and electronic equipment |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107992408B (en) | 2019-06-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101856543B1 (en) | Failure prediction system based on artificial intelligence | |
| KR102011620B1 (en) | Importance determination device of abnormal data and importance determination method of abnormal data | |
| CN102713861B (en) | Operation management device, operation management method and program recorded medium | |
| US9310345B2 (en) | Sensor system, computer, and machine | |
| CN101533276B (en) | System for monitoring and diagnosing remote devices | |
| WO2013136739A1 (en) | Operation administration device, operation administration method, and program | |
| CN113328872B (en) | Fault repairing method, device and storage medium | |
| CN106789306B (en) | Method and system for detecting, collecting and recovering software fault of communication equipment | |
| CN103797468A (en) | Automated detection of a system anomaly | |
| CN115118581B (en) | Internet of things data all-link monitoring and intelligent guaranteeing system based on 5G | |
| CN105202704B (en) | The display methods and device of air-conditioning fault message | |
| CN103674286A (en) | In-station communication device fault diagnosis method based on infrared image | |
| CN103023028A (en) | Rapid grid failure positioning method based on dependency graph of entities | |
| US20090292951A1 (en) | Method and device for fault location in a system | |
| CN113271224A (en) | Node positioning method and device, storage medium and electronic device | |
| CN107992408B (en) | A kind of software probe method of software probe | |
| CN106506226A (en) | A kind of startup method and device of fault detect | |
| CN115037603A (en) | Diagnosis evaluation method, device and system of electricity consumption information acquisition equipment | |
| KR20210044657A (en) | Method of preserving the prediction of a device through distribution chart | |
| CN114860518A (en) | Detection method and system of function safety system, electronic equipment and storage medium | |
| CN110489260A (en) | Fault recognition method, device and BMC | |
| CN107957928B (en) | A kind of operation of software synchronization tests and analyzes and troubleshooting methodology | |
| CN107561470A (en) | A kind of fault detector evaluation of running status system | |
| CN115766402B (en) | Method and device for filtering server fault root cause, storage medium and electronic device | |
| CN113608959B (en) | Method, system, terminal and storage medium for positioning fault hard disk |
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. |