CN106815089A - Malfunction elimination method and device based on daily record - Google Patents
Malfunction elimination method and device based on daily record Download PDFInfo
- Publication number
- CN106815089A CN106815089A CN201611203422.4A CN201611203422A CN106815089A CN 106815089 A CN106815089 A CN 106815089A CN 201611203422 A CN201611203422 A CN 201611203422A CN 106815089 A CN106815089 A CN 106815089A
- Authority
- CN
- China
- Prior art keywords
- log
- journal file
- daily record
- sdk
- process log
- 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.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0787—Storage of error reports, e.g. persistent data storage, storage using memory protection
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
Abstract
The present invention provides a kind of malfunction elimination method and device based on daily record.The method includes:Terminal device generates the process log of operation flow, and the service procedure that operation flow is provided by SDK, terminal device exports into the journal file of default disk process log, and malfunction elimination is carried out according to journal file for SDK developer.So as to, journal file can be sent to SDK developer by terminal device from after the taking-up of default disk, greatly facilitate SDK developer's investigation problem, SDK developer only needs to check journal file in chronological order, the procedure links for going wrong can be quickly oriented, the efficiency that SDK developer repairs problem is improved.And remote analysis problem can be realized, and as long as SDK developer gets journal file, the business side of integrated service is completely independent of, realize remote failure investigation and process problem.
Description
Technical field
The present invention relates to communication technical field, more particularly to a kind of malfunction elimination method and device based on daily record.
Background technology
SDK (Software Develop Kit, hereinafter referred to as:SDK auxiliary development) is generally comprised a certain
The set of the relevant documentation, example and instrument of class application, the application programming interface that developer can be provided by SDK
(Application Programming Interface, hereinafter referred to as:API the quick exploitation of association area application) is realized,
Development and application program (Application, hereinafter referred to as:APP serviced, it is necessary to investigate SDK and provide during the SDK for) using
Produced problem in journey, directly in console output journal information, or can typically be carried out at debugging to program on stream
Reason.But when in the software that Services Integration has arrived business side, SDK developer cannot just obtain log information or enter line program
Debugging.
Existing solution is, the flow that the phenomenon and problem for collecting problem by the business side of access service occur and then
SDK developer is fed back to, the scene that SDK developer goes wrong according to the simulation reduction of the feedback information of business side enters one
Step is inferred, investigation questions and prospect;Or it is supplied to SDK developer to analyze reason by the mobile phone that business side will appear from problem.
On the one hand, investigation problem depends on the feedback information of business side, but feedback information not necessarily has with essential reason
Relation, if problem can not reappear or be difficult reproduction, then the difficulty of SDK developer's investigation is very big.On the other hand, industry
The problems such as business side is due to time and space, it is impossible to which the mobile phone for going wrong is provided.
The content of the invention
The present invention provides a kind of malfunction elimination method and device based on daily record, facilitates developer to investigate SDK and provides clothes
Produced problem during business.
In a first aspect, the present invention provides a kind of malfunction elimination method based on daily record, including:
Terminal device generates the process log of operation flow, and the operation flow is provided by SDK SDK
Service procedure;
The terminal device exports into the journal file of default disk the process log, for SDK developer
Malfunction elimination is carried out according to the journal file.
Further, the operation flow includes:
The corresponding page of service initiation request, business shows and service response result.
Further, when the service procedure is business login process, the operation flow includes:Access side is by application
Program Interfaces API initiations logging request, middle control distribution, account login page show and log in interaction response.
Further, the terminal device exports into the journal file of default disk the process log, including:
The terminal device stores in first queue the process log;
The process log that the terminal device will be stored in the first queue writes core buffer;
The terminal device monitors capacity and the write operation of the core buffer, if listening to the core buffer
There is no write operation or reach capacity threshold, then trigger the input and output thread of daily record, will be current in the core buffer
All of process log one-time write journal file.
Further, the type of the process log is text log or storehouse daily record.
Second aspect, the present invention provides a kind of malfunction elimination device based on daily record, including:
Generation module, the process log for generating operation flow, the operation flow is SDK SDK institutes
The service procedure of offer;
Processing module, for the process log to be exported into the journal file of default disk, for SDK developer
Malfunction elimination is carried out according to the journal file.
Further, the operation flow includes:
The corresponding page of service initiation request, business shows and service response result.
Further, when the service procedure is business login process, the operation flow includes:Access side is by application
Program Interfaces API initiations logging request, middle control distribution, account login page show and log in interaction response.
Further, the processing module specifically for:
By process log storage in first queue;
The process log that will be stored in the first queue writes core buffer;
Capacity and the write operation of the core buffer are monitored, if listening to the core buffer does not have write operation
Or reach capacity threshold, then the input and output thread of daily record is triggered, by current all of flow day in the core buffer
Will one-time write journal file.
Further, the type of the process log is text log or storehouse daily record.
The malfunction elimination method and device based on daily record that the present invention is provided, the stream of operation flow is generated by terminal device
Cheng Zhi, process log is exported into the journal file of default disk.So as to terminal device can be by journal file from default magnetic
Disk take out after be sent to SDK developer, greatly facilitate SDK developer investigation problem, SDK developer only need to by
Time sequencing checks journal file, can quickly orient the procedure links for going wrong, and improves SDK developer and repairs problem
Efficiency.And remote analysis problem can be realized, as long as SDK developer gets journal file, it is completely independent of integrated clothes
The business side of business, realizes remote failure investigation and process problem.
Brief description of the drawings
In order to illustrate more clearly of technical scheme of the invention or of the prior art, below will be to embodiment or prior art
The accompanying drawing to be used needed for description is briefly described, it should be apparent that, drawings in the following description are of the invention one
A little embodiments, for those of ordinary skill in the art, without having to pay creative labor, can also be according to this
A little accompanying drawings obtain other accompanying drawings.
Fig. 1 is the flow chart of malfunction elimination embodiment of the method one of the present invention based on daily record;
Fig. 2 is the flow chart of malfunction elimination embodiment of the method two of the present invention based on daily record;
Fig. 3 is the structural representation of malfunction elimination device embodiment one of the present invention based on daily record.
Specific embodiment
To make the object, technical solutions and advantages of the present invention clearer, below in conjunction with the accompanying drawing in the present invention, to this
Technical scheme in invention is clearly and completely described, it is clear that described embodiment is a part of embodiment of the invention,
Rather than whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art are not making creative labor
The every other embodiment obtained under the premise of dynamic, belongs to the scope of protection of the invention.
Fig. 1 is the flow chart of malfunction elimination embodiment of the method one of the present invention based on daily record, the execution master in the present embodiment
Body can be the business side of access service, namely be mounted with the terminal device of APP, as shown in figure 1, the method for the present embodiment can be with
Including:
S101, terminal device generate the process log of operation flow, the service procedure that operation flow is provided by SDK, stream
Cheng Zhi carries the daily record generation time.
Specifically, the service procedure that operation flow is provided by SDK, that is, be exactly by traffic log, service flow
Each key link of journey will generate corresponding process log information, for example, operation flow includes:Service initiation request, industry
The corresponding page of being engaged in shows and service response result.When terminal device generates the process log of operation flow, the flow day of generation
Will carries the daily record generation time.
Specifically, when service procedure is business login process, operation flow includes:Initiate to log in by API and ask in access side
Ask, middle control is distributed, account login page shows and log in interaction response.
S102, terminal device export into the journal file of default disk process log, for SDK developer according to
Journal file carries out malfunction elimination.
Specifically, can be that terminal device successively exports process log according to the daily record generation time sequencing of process log
Into the journal file of default disk, as long as having monitored that process log is generated, that is, export into the journal file of default disk.
Default disk herein is, for example, the storage card of mobile phone or the hard disk of computer.
Optionally, as another enforceable mode, terminal device exports process log to the daily record of default disk
In file, it is specifically as follows:
S102a, terminal device store in first queue process log.
The process log write-in core buffer that S102b, terminal device will be stored in first queue.
S102c, terminal device monitor capacity and the write operation of core buffer, if listen to core buffer not writing
Enter operation or reach capacity threshold, then the input and output thread of daily record is triggered, by current all of flow in core buffer
Daily record one-time write journal file.
Process log is write by core buffer by using a thread, a thread monitors core buffer not to be had
Write operation or when reaching capacity threshold by the process log one-time write journal file in core buffer, daily record is delayed
Deposit and write in working sub-line journey at two respectively.So as to the frequency of core buffer data write-in journal file is low, reduces
The Thread Count that treatment daily record is used is small to system I/O pressure.
In the present embodiment, the type of process log can be text log or storehouse daily record.In being exactly the present embodiment
Support process daily record is text log or storehouse daily record.Storehouse daily record contains contextual information when program is run, such as exist
In which class, that method, the daily record of which code call.Storehouse daily record is due to containing context letter when program is run
Breath, therefore it is more beneficial for malfunction elimination.
In the present embodiment, after process log is exported into the journal file of default disk, the terminal device (industry of access service
Business side) journal file is sent to SDK developer, the mesh that can be such as specified on mobile phone memory card from after the taking-up of default disk
Finding journal file is sent to SDK developer below for record, and SDK developer carries out malfunction elimination according to journal file, specifically
Ground, after SDK developer receives journal file, analysis process daily record, the path that location tasks are performed, which step occurs in that assorted
Problem, investigates software source code, then provide recovery scenario after the clue for finding problem.
Process log can be unified to be collected into journal file, in addition it is also necessary to which docking port does some extensions, it is supported terminal
The configuration of equipment (the business side of access service), it is allowed to terminal device monitoring journal information, also allows the automation inside closing
Daily record, for information security, log collection is to close under default situations.
The malfunction elimination method based on daily record that the present embodiment is provided, the flow day of operation flow is generated by terminal device
Will, process log is exported into the journal file of default disk.So as to terminal device can take journal file from default disk
SDK developer is sent to after going out, SDK developer's investigation problem is greatly facilitated, SDK developer only needs to temporally
Order checks journal file, can quickly orient the procedure links for going wrong, and improves the effect that SDK developer repairs problem
Rate.And remote analysis problem can be realized, as long as SDK developer gets journal file, it is completely independent of integrated service
Business side, realizes remote failure investigation and process problem.
A specific embodiment, the technical scheme to embodiment of the method shown in Fig. 1 is used to be described in detail below.
Fig. 2 is the flow chart of malfunction elimination embodiment of the method two of the present invention based on daily record, with service procedure in this implementation
To be illustrated as a example by business login process, operation flow includes:Access side logging request, middle control distribution, account are initiated by API
Number login page shows and logs in interaction response, as shown in Fig. 2 the method for the present embodiment can include:
S201, terminal device generate the process log of operation flow.
Wherein, operation flow includes:Access side is shown by API initiations logging request, middle control distribution, account login page
With log in interaction response, each flow all generates corresponding process log.Exported by log interface.
S202, log processing.
Specifically, the process log of generation carries out Log Types configuration (at Logger.Log after log interface is exported
Reason) and daily record output configuration.The process log of generation is text log, and Log Types include text log and storehouse daily record, day
Will type configuration is specifically that process log is set into text log or storehouse daily record, and it is to pre-set to be configured to which kind of type
, Log Types setting is carried out if storehouse daily record is configured to, do not processed if text log is configured to.Text log is only wrapped
Containing the incoming text log data of called side.What storehouse daily record was represented be it is internal automatic obtain after program context it is more detailed
Daily record, compared to text log, storehouse daily record is additionally contained such as:The lines of code that log request is initiated, category information, method
Information etc..Daily record output includes that console (console) standard output and outside log interface are intercepted, and it is use that external interface is intercepted
Family self defined interface.Daily record exports configuration and is to determine by console (console) standard output, then performs S203, or
Exported by User Defined interface.
S203, daily record filing, i.e., terminal device exports into the journal file of default disk process log.
Daily record filing is specifically included:
S203a, terminal device store in first queue process log.
The process log write-in core buffer that S203b, terminal device will be stored in first queue.
S203c, I/O single thread write journal file.
Specially:Terminal device monitors capacity and the write operation of core buffer, if listen to core buffer not having
Write operation reaches capacity threshold, then the input and output thread of daily record is triggered, by current all of stream in core buffer
Cheng Zhi one-time write journal files.
The malfunction elimination method based on daily record that the present embodiment is provided, the flow day of operation flow is generated by terminal device
Will, process log is exported into the journal file of default disk.So as to terminal device can take journal file from default disk
SDK developer is sent to after going out, SDK developer's investigation problem is greatly facilitated, SDK developer only needs to temporally
Order checks journal file, can quickly orient the procedure links for going wrong, and improves the effect that SDK developer repairs problem
Rate.And remote analysis problem can be realized, as long as SDK developer gets journal file, it is completely independent of integrated service
Business side, realizes remote failure investigation and process problem.
Fig. 3 is the structural representation of malfunction elimination device embodiment one of the present invention based on daily record, as shown in figure 3, this reality
The device for applying example can include:Generation module 11 and processing module 12, wherein, generation module 11 is used to generate the stream of operation flow
Cheng Zhi, the service procedure that operation flow is provided by SDK SDK.Processing module 12 is used for process log is defeated
Go out into the journal file of default disk, malfunction elimination is carried out according to journal file for SDK developer.
Further, operation flow includes:The corresponding page of service initiation request, business shows and service response result.
Optionally, when service procedure is business login process, operation flow includes:Access side is connect by application programming
Mouth API initiations logging request, middle control distribution, account login page show and log in interaction response.
Further, processing module 12 specifically for:
By process log storage in first queue;
The process log write-in core buffer that will be stored in first queue;
Capacity and the write operation of core buffer are monitored, if listen to core buffer and there is no write operation or reaching
Capacity threshold, then trigger the input and output thread of daily record, by current all of process log one-time write in core buffer
Journal file.
Optionally, the type of process log is text log or storehouse daily record.
The device of the present embodiment, can be used for performing the technical scheme of embodiment of the method shown in Fig. 1, its realization principle class
Seemingly, here is omitted.
The malfunction elimination device based on daily record that the present embodiment is provided, the flow day of operation flow is generated by terminal device
Will, process log is exported into the journal file of default disk.So as to terminal device can take journal file from default disk
SDK developer is sent to after going out, SDK developer's investigation problem is greatly facilitated, SDK developer only needs to temporally
Order checks journal file, can quickly orient the procedure links for going wrong, and improves the effect that SDK developer repairs problem
Rate.And remote analysis problem can be realized, as long as SDK developer gets journal file, it is completely independent of integrated service
Business side, realizes remote failure investigation and process problem.
One of ordinary skill in the art will appreciate that:Realizing all or part of step of above-mentioned each method embodiment can lead to
The related hardware of programmed instruction is crossed to complete.Foregoing program can be stored in a computer read/write memory medium.The journey
Sequence upon execution, performs the step of including above-mentioned each method embodiment;And foregoing storage medium includes:ROM, RAM, magnetic disc or
Person's CD etc. is various can be with the medium of store program codes.
Finally it should be noted that:Various embodiments above is merely illustrative of the technical solution of the present invention, rather than its limitations;To the greatest extent
Pipe has been described in detail with reference to foregoing embodiments to the present invention, it will be understood by those within the art that:Its according to
The technical scheme described in foregoing embodiments can so be modified, or which part or all technical characteristic are entered
Row equivalent;And these modifications or replacement, the essence of appropriate technical solution is departed from various embodiments of the present invention technology
The scope of scheme.
Claims (10)
1. a kind of malfunction elimination method based on daily record, it is characterised in that including:
Terminal device generates the process log of operation flow, the clothes that the operation flow is provided by SDK SDK
Business flow, the process log carries the daily record generation time;
The terminal device exports into the journal file of default disk the process log, for SDK developer according to
The journal file carries out malfunction elimination.
2. method according to claim 1, it is characterised in that the operation flow includes:
The corresponding page of service initiation request, business shows and service response result.
3. method according to claim 2, it is characterised in that when the service procedure is business login process, the industry
Business flow includes:Access side is shown by application programming interface API initiations logging request, middle control distribution, account login page
Show and log in interaction response.
4. method according to claim 1, it is characterised in that the terminal device exports to default the process log
In the journal file of disk, including:
The terminal device stores in first queue the process log;
The process log that the terminal device will be stored in the first queue writes core buffer;
The terminal device monitors capacity and the write operation of the core buffer, if listen to the core buffer not having
Write operation reaches capacity threshold, then trigger the input and output thread of daily record, will currently own in the core buffer
Process log one-time write journal file.
5. method according to claim 1, it is characterised in that the type of the process log is text log or storehouse day
Will.
6. a kind of malfunction elimination device based on daily record, it is characterised in that including:
Generation module, the process log for generating operation flow, the operation flow is provided by SDK SDK
Service procedure, the process log carries the daily record generation time;
Processing module, for the process log to be exported into the journal file of default disk, for SDK developer according to
The journal file carries out malfunction elimination.
7. device according to claim 6, it is characterised in that the operation flow includes:
The corresponding page of service initiation request, business shows and service response result.
8. device according to claim 7, it is characterised in that when the service procedure is business login process, the industry
Business flow includes:Access side is shown by application programming interface API initiations logging request, middle control distribution, account login page
Show and log in interaction response.
9. device according to claim 6, it is characterised in that the processing module specifically for:
By process log storage in first queue;
The process log that will be stored in the first queue writes core buffer;
Monitor capacity and the write operation of the core buffer, if listen to the core buffer do not have write operation or
Capacity threshold is reached, then the input and output thread of daily record is triggered, by current all of process log one in the core buffer
Secondary property writes journal file.
10. device according to claim 6, it is characterised in that the type of the process log is text log or storehouse
Daily record.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201611203422.4A CN106815089A (en) | 2016-12-23 | 2016-12-23 | Malfunction elimination method and device based on daily record |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201611203422.4A CN106815089A (en) | 2016-12-23 | 2016-12-23 | Malfunction elimination method and device based on daily record |
Publications (1)
Publication Number | Publication Date |
---|---|
CN106815089A true CN106815089A (en) | 2017-06-09 |
Family
ID=59109642
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201611203422.4A Pending CN106815089A (en) | 2016-12-23 | 2016-12-23 | Malfunction elimination method and device based on daily record |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN106815089A (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108111880A (en) * | 2017-12-21 | 2018-06-01 | 蛮蛮天下(北京)网络科技有限公司 | Troubleshooting method and troubleshooting system |
CN108235083A (en) * | 2018-01-16 | 2018-06-29 | 青岛海信电器股份有限公司 | TV log information acquisition methods and device |
CN109800098A (en) * | 2018-12-13 | 2019-05-24 | 平安普惠企业管理有限公司 | Service exception node positioning method, device, computer equipment and storage medium |
CN112115019A (en) * | 2020-08-26 | 2020-12-22 | 上海汇付数据服务有限公司 | Application log monitoring method and system for application program |
CN112289345A (en) * | 2020-11-19 | 2021-01-29 | 四川长虹电器股份有限公司 | Visual intelligent terminal voice diagnosis method |
US11113138B2 (en) | 2018-01-02 | 2021-09-07 | Carrier Corporation | System and method for analyzing and responding to errors within a log file |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1829366A (en) * | 2005-03-02 | 2006-09-06 | 华为技术有限公司 | Wireless network controller log recording system and its method |
CN102891873A (en) * | 2011-07-21 | 2013-01-23 | 腾讯科技(深圳)有限公司 | Method for storing log data and log data storage system |
CN105871574A (en) * | 2015-01-21 | 2016-08-17 | 中国移动通信集团浙江有限公司 | Method, device and system for monitoring log based on software development kit |
CN105975376A (en) * | 2016-04-28 | 2016-09-28 | 广州市锲致智能技术有限公司 | Log processing based numerical control system security processing method |
CN106155864A (en) * | 2016-07-29 | 2016-11-23 | 北京北信源软件股份有限公司 | A kind of extension Apache Log4j daily record output stage method for distinguishing |
-
2016
- 2016-12-23 CN CN201611203422.4A patent/CN106815089A/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1829366A (en) * | 2005-03-02 | 2006-09-06 | 华为技术有限公司 | Wireless network controller log recording system and its method |
CN102891873A (en) * | 2011-07-21 | 2013-01-23 | 腾讯科技(深圳)有限公司 | Method for storing log data and log data storage system |
CN105871574A (en) * | 2015-01-21 | 2016-08-17 | 中国移动通信集团浙江有限公司 | Method, device and system for monitoring log based on software development kit |
CN105975376A (en) * | 2016-04-28 | 2016-09-28 | 广州市锲致智能技术有限公司 | Log processing based numerical control system security processing method |
CN106155864A (en) * | 2016-07-29 | 2016-11-23 | 北京北信源软件股份有限公司 | A kind of extension Apache Log4j daily record output stage method for distinguishing |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108111880A (en) * | 2017-12-21 | 2018-06-01 | 蛮蛮天下(北京)网络科技有限公司 | Troubleshooting method and troubleshooting system |
CN108111880B (en) * | 2017-12-21 | 2020-08-11 | 河南蛮蛮云计算技术有限公司 | Obstacle removing method and obstacle removing system |
US11113138B2 (en) | 2018-01-02 | 2021-09-07 | Carrier Corporation | System and method for analyzing and responding to errors within a log file |
CN108235083A (en) * | 2018-01-16 | 2018-06-29 | 青岛海信电器股份有限公司 | TV log information acquisition methods and device |
CN109800098A (en) * | 2018-12-13 | 2019-05-24 | 平安普惠企业管理有限公司 | Service exception node positioning method, device, computer equipment and storage medium |
CN112115019A (en) * | 2020-08-26 | 2020-12-22 | 上海汇付数据服务有限公司 | Application log monitoring method and system for application program |
CN112289345A (en) * | 2020-11-19 | 2021-01-29 | 四川长虹电器股份有限公司 | Visual intelligent terminal voice diagnosis method |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106815089A (en) | Malfunction elimination method and device based on daily record | |
CN100412802C (en) | Planned computer problem diagnosis and solvement and its automatic report and update | |
CN109491860A (en) | Method for detecting abnormality, terminal device and the medium of application program | |
CN103023693A (en) | Behaviour log data management system and behaviour log data management method | |
CN104111870B (en) | Interrupt processing device and method | |
CN103268183A (en) | Processing method and device for information report | |
CN103544095A (en) | Server program monitoring method and system of server program | |
Arpasat et al. | Improvement of call center customer service in a thai bank using disco fuzzy mining algorithm | |
CN108197032A (en) | Main thread interim card monitoring method, medium, equipment and the system of IOS applications | |
CN103514075A (en) | Method and device for monitoring API function calling in mobile terminal | |
CN104077328B (en) | The operation diagnostic method and equipment of MapReduce distributed system | |
CN107733710A (en) | Construction method, device, computer equipment and the storage medium of link call relation | |
CN108228461A (en) | A kind of daily record generation method, device, computer equipment and storage medium | |
CN113570468A (en) | Enterprise payment wind control service platform | |
US11113385B2 (en) | Communicating trace information between security zones | |
CN111324480B (en) | Large-scale host transaction fault positioning system and method | |
CN106844182A (en) | Method, system and mobile terminal for recording user behavior | |
CN107861821B (en) | Mining method and device for module call relation and computer readable medium | |
CN112463266A (en) | Execution policy generation method and device, electronic equipment and storage medium | |
CN111913861A (en) | Performance test method, device, equipment and medium of Internet of things system | |
CN107451435B (en) | Management and control method, management and control machine and management and control system of hardware encryption machine | |
CN115757639A (en) | Data source synchronization method and device, electronic equipment and storage medium | |
CN105187519A (en) | Socket transmission system based on AIO | |
CN106933718B (en) | Method for monitoring performance and device | |
CN107729056A (en) | The program store method and relevant apparatus of a kind of read-only storage |
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 | ||
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170609 |
|
RJ01 | Rejection of invention patent application after publication |