CN110955547A - Management method, system, equipment and readable storage medium for interface abnormal information - Google Patents
Management method, system, equipment and readable storage medium for interface abnormal information Download PDFInfo
- Publication number
- CN110955547A CN110955547A CN201911055059.XA CN201911055059A CN110955547A CN 110955547 A CN110955547 A CN 110955547A CN 201911055059 A CN201911055059 A CN 201911055059A CN 110955547 A CN110955547 A CN 110955547A
- Authority
- CN
- China
- Prior art keywords
- interface
- information
- abnormal information
- abnormal
- error code
- 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
Images
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/0706—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 the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0745—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 the processing taking place on a specific hardware platform or in a specific software environment in an input/output transactions management context
-
- 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
Abstract
The application discloses a management method of interface abnormal information, which comprises the following steps: detecting whether the interface is in an abnormal state; when the interface is in an abnormal state, acquiring abnormal information; judging whether the abnormal information has an error code; if not, setting a corresponding default error code for the abnormal information, and recording the default error code and the abnormal information into the database. According to the method and the device, when the interface is in an abnormal state, the abnormal information is obtained, the corresponding default error code is set for the abnormal information when the abnormal information does not have the error code, and finally the default error code and the abnormal information are recorded into the database, so that the standard system default error code can be provided for the interface abnormality under the condition that the code is not modified and the service is not stopped, and a user can obtain an error prompt according to the error code to complete the processing work of the abnormal interface. The application also provides a management system, equipment and a readable storage medium for the interface abnormal information, and the management system, the equipment and the readable storage medium have the beneficial effects.
Description
Technical Field
The present application relates to the field of management of interface exception information, and in particular, to a method, a system, a device, and a readable storage medium for managing interface exception information.
Background
With the development of information technology, cloud computing has gradually become a development hotspot in the industry, and the cloud computing technology is also gradually applied to multiple fields of education, science, culture, public security, government, sanitation, high-performance computing, electronic commerce, internet of things and the like, and accordingly, the usage amount and the activity of cloud computing service platforms are increasing day by day. With the development of cloud computing, a cloud computing management platform system is gradually huge, and hundreds of services are faced after the cloud computing management platform is micro-serviced. There is a concern as to how the interfaces of the service are effectively managed.
However, as the functional modules of the cloud platform system are increasingly complex, the scale of the system is not in an order of magnitude from the number, the scale and the front, and as the third-party service calls too much, the error information cannot be effectively collected and the system abnormal information display cannot be standardized, so that unknown abnormal codes are not processed, the prompt information is unfriendly, and finally, the system service interface is abnormal and the loss of online management classification analysis is caused.
Therefore, how to manage the interface abnormality information is a technical problem that needs to be solved by those skilled in the art at present.
Disclosure of Invention
The application aims to provide a management method, a system, equipment and a readable storage medium for interface abnormal information, which are used for managing the interface abnormal information.
In order to solve the above technical problem, the present application provides a method for managing interface exception information, where the method includes:
detecting whether the interface is in an abnormal state;
when the interface is in an abnormal state, acquiring abnormal information;
judging whether the abnormal information has an error code;
if not, setting a corresponding default error code for the abnormal information, and recording the default error code and the abnormal information into a database.
Optionally, the method further includes:
receiving an input query instruction;
determining an interface type and an error code according to the query instruction;
determining corresponding interface information according to the interface type, and determining corresponding abnormal information according to the error code;
and outputting the interface information and the abnormal information.
Optionally, after the obtaining of the abnormal information, the method further includes:
judging whether the abnormal information is a messy code;
if so, marking the current abnormal state of the interface as an original abnormal state;
and outputting the original abnormal state to a preset position so that a user sets a standard error code and standard abnormal information for the original abnormal state.
Optionally, the method further includes:
receiving an input record deleting instruction, and determining a part to be deleted of the abnormal information historical record according to the record deleting instruction;
and deleting the part to be deleted of the abnormal information historical record.
The present application further provides a system for managing interface abnormality information, the system including:
the detection module is used for detecting whether the interface is in an abnormal state;
the acquisition module is used for acquiring abnormal information when the interface is in the abnormal state;
the first judging module is used for judging whether the abnormal information has error codes or not;
and the setting module is used for setting a corresponding default error code for the abnormal information when the abnormal information does not have the error code, and recording the default error code and the abnormal information into a database.
Optionally, the method further includes:
the first receiving module is used for receiving an input query instruction;
the first determining module is used for determining the interface type and the error code according to the query instruction;
the second determining module is used for determining corresponding interface information according to the interface type and determining corresponding abnormal information according to the error code;
and the first output module is used for outputting the interface information and the abnormal information.
Optionally, the method further includes:
the second judgment module is used for judging whether the abnormal information is a messy code;
the marking module is used for marking the current abnormal state of the interface as an original abnormal state when the abnormal information is messy codes;
and the second output module is used for outputting the original abnormal state to a preset position so that a user sets a standard error code and standard abnormal information for the original abnormal state.
Optionally, the method further includes:
the second receiving module is used for receiving an input record deleting instruction and determining a part to be deleted of the abnormal information historical record according to the record deleting instruction;
and the deleting module is used for deleting the part to be deleted of the abnormal information historical record.
The present application further provides a management device of interface abnormality information, including:
a memory for storing a computer program;
a processor, configured to implement the steps of the method for managing interface abnormality information according to any one of the above-mentioned items when the computer program is executed.
The present application also provides a readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the method for managing interface abnormality information according to any one of the above-mentioned embodiments.
The management method for the interface abnormal information comprises the following steps: detecting whether the interface is in an abnormal state; when the interface is in an abnormal state, acquiring abnormal information; judging whether the abnormal information has an error code; if not, setting a corresponding default error code for the abnormal information, and recording the default error code and the abnormal information into the database.
According to the technical scheme provided by the application, whether the interface is in an abnormal state or not is detected; when the interface is in an abnormal state, acquiring abnormal information, setting a corresponding default error code for the abnormal information when the abnormal information does not have the error code, and finally recording the default error code and the abnormal information into the database. The application also provides a management system, equipment and a readable storage medium for the interface abnormal information, which have the beneficial effects and are not repeated herein.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a method for managing interface exception information according to an embodiment of the present disclosure;
fig. 2 is a flowchart of another interface exception information management method according to an embodiment of the present disclosure;
fig. 3 is a structural diagram of a management system for interface exception information according to an embodiment of the present disclosure;
fig. 4 is a structural diagram of another interface exception information management system according to an embodiment of the present application;
fig. 5 is a structural diagram of a management device for interface abnormality information according to an embodiment of the present application.
Detailed Description
The core of the application is to provide a management method, a system, equipment and a readable storage medium for interface abnormal information, which are used for managing the interface abnormal information.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart illustrating a method for managing interface exception information according to an embodiment of the present disclosure.
The method specifically comprises the following steps:
s101: detecting whether the interface is in an abnormal state;
based on the fact that in the prior art, each functional module of a cloud platform system is increasingly complex, the scale of the system is not in an order of magnitude from the number, the scale and the front, and due to too many third-party services, error information cannot be effectively collected and system abnormal information display cannot be standardized, unknown abnormal codes are not processed, prompt information is unfriendly, and finally system service interface abnormality and on-line management classification analysis are caused to be missing, the method for managing the interface abnormal information is provided for managing the interface abnormal information.
S102: when the interface is in an abnormal state, acquiring abnormal information;
the abnormal information is the description information of the abnormal state of the type recorded in the system, for example, when an unknown abnormal code is not processed, the prompt information is unfriendly, the application can directly provide a maintenance function through the abnormal information on the basis of the abnormal information under the condition that the code is not modified to be continuously served, and a standard system error code and an easily understood error prompt are provided.
S103: judging whether the abnormal information has an error code;
if not, the step S104 is executed;
when the abnormal information does not have the error code, it indicates that the abnormal state of the type is not recorded, and then the method enters step S104, a corresponding default error code is set for the abnormal information, and the default error code and the abnormal information are recorded in the database, so that the default error code and the abnormal information can be directly output when the abnormal state of the type is detected next time.
S104: and setting a corresponding default error code for the abnormal information, and recording the default error code and the abnormal information into a database.
Optionally, the method may further include the steps of:
receiving an input query instruction;
determining the interface type and the error code according to the query instruction;
determining corresponding interface information according to the interface type, and determining corresponding abnormal information according to the error code;
and outputting the interface information and the abnormal information.
Based on the above embodiment, when receiving an input query instruction, the method and the device can determine the interface type and the error code according to the query instruction, then determine the corresponding interface information according to the interface type, determine the corresponding abnormal information according to the error code, and finally output the interface information and the abnormal information, so that a user can obtain an error prompt according to the error code to complete processing of the abnormal interface.
Optionally, the method may further include the steps of:
receiving an input record deleting instruction, and determining a part to be deleted of the abnormal information historical record according to the record deleting instruction;
and deleting the part to be deleted of the abnormal information historical record.
Based on the embodiment, when the input record deleting instruction is received, the part to be deleted of the abnormal information historical record can be determined according to the record deleting instruction, and then the part to be deleted of the abnormal information historical record is deleted, so that the storage space of the database is saved.
Based on the technical scheme, the interface abnormal information management method provided by the application detects whether the interface is in an abnormal state; when the interface is in an abnormal state, acquiring abnormal information, setting a corresponding default error code for the abnormal information when the abnormal information does not have the error code, and finally recording the default error code and the abnormal information into the database.
With respect to step S103 of the previous embodiment, after acquiring the abnormality information, the steps shown in fig. 2 may also be executed, which will be described below with reference to fig. 2.
Referring to fig. 2, fig. 2 is a flowchart illustrating another method for managing interface exception information according to an embodiment of the present disclosure.
The method specifically comprises the following steps:
s201: judging whether the abnormal information is a messy code;
if yes, the process proceeds to step S202.
S202: marking the current abnormal state of the interface as an original abnormal state;
s203: and outputting the original abnormal state to a preset position so that a user sets a standard error code and standard abnormal information for the original abnormal state.
Based on the above technical scheme, after the abnormal information is obtained, the embodiment of the application judges whether the abnormal information is a messy code, if so, the current abnormal state of the interface is marked as an original abnormal state, and the original abnormal state is output to a preset position, so that a user sets a standard error code and standard abnormal information for the original abnormal state, the correction of the messy code information is completed, and the system error information is standardized.
Referring to fig. 3, fig. 3 is a structural diagram of a management system for interface exception information according to an embodiment of the present application.
The system may include:
a detection module 100, configured to detect whether an interface is in an abnormal state;
an obtaining module 200, configured to obtain exception information when the interface is in an exception state;
a first determining module 300, configured to determine whether the abnormal information has an error code;
the setting module 400 is configured to set a corresponding default error code for the abnormal information when the abnormal information does not have the error code, and record the default error code and the abnormal information in the database.
Referring to fig. 4, fig. 4 is a structural diagram of another interface exception information management system according to an embodiment of the present disclosure.
The system may further comprise:
the first receiving module is used for receiving an input query instruction;
the first determining module is used for determining the interface type and the error code according to the query instruction;
the second determining module is used for determining corresponding interface information according to the interface type and determining corresponding abnormal information according to the error code;
the first output module is used for outputting the interface information and the abnormal information.
The system may further comprise:
the second judging module is used for judging whether the abnormal information is a messy code;
the marking module is used for marking the current abnormal state of the interface as an original abnormal state when the abnormal information is messy codes;
and the second output module is used for outputting the original abnormal state to a preset position so that a user sets a standard error code and standard abnormal information for the original abnormal state.
The system may further comprise:
the second receiving module is used for receiving the input record deleting instruction and determining a part to be deleted of the abnormal information historical record according to the record deleting instruction;
and the deleting module is used for deleting the part to be deleted of the abnormal information historical record.
The various components of the above system may be practically applied in the following embodiments:
the detection module detects whether the interface is in an abnormal state; when the interface is in an abnormal state, the acquisition module acquires abnormal information; the second judging module judges whether the abnormal information is a messy code; when the abnormal information is messy codes, the marking module marks the current abnormal state of the interface as an original abnormal state; the second output module outputs the original abnormal state to a preset position so that a user can set a standard error code and standard abnormal information for the original abnormal state; the first judging module judges whether the abnormal information has an error code; when the abnormal information does not have the error code, the setting module sets a corresponding default error code for the abnormal information and records the default error code and the abnormal information into the database.
The first receiving module receives an input query instruction; the first determining module determines the interface type and the error code according to the query instruction; the second determining module determines corresponding interface information according to the interface type and determines corresponding abnormal information according to the error code; the first output module outputs interface information and abnormal information.
The second receiving module receives an input record deleting instruction and determines a part to be deleted of the abnormal information historical record according to the record deleting instruction; and the deleting module deletes the part to be deleted of the abnormal information historical record.
Referring to fig. 5, fig. 5 is a structural diagram of a management device for interface abnormality information according to an embodiment of the present application.
The management apparatus 500 for the interface exception information may have a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 522 (e.g., one or more processors) and a memory 532, one or more storage media 530 (e.g., one or more mass storage devices) storing applications 542 or data 544. Memory 532 and storage media 530 may be, among other things, transient storage or persistent storage. The program stored on the storage medium 530 may include one or more modules (not shown), each of which may include a sequence of instruction operations for the device. Further, the central processor 522 may be configured to communicate with the storage medium 530, and execute a series of instruction operations in the storage medium 530 on the interface abnormality information management device 500.
The management apparatus 500 for interface exception information may also include one or more power supplies 525, one or more wired or wireless network interfaces 550, one or more input-output interfaces 558, and/or one or more operating systems 541, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
The steps in the management method of interface abnormality information described in fig. 1 to 2 above are implemented by the management device of interface abnormality information based on the structure shown in fig. 5.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the apparatus and the module described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus, device and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of modules is merely a division of logical functions, and an actual implementation may have another division, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
Modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.
The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a function calling device, or a network device) to execute all or part of the steps of the method of the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The detailed description is given above of a method, a system, a device and a readable storage medium for managing interface exception information provided by the present application. The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. A management method for interface abnormal information is characterized by comprising the following steps:
detecting whether the interface is in an abnormal state;
when the interface is in an abnormal state, acquiring abnormal information;
judging whether the abnormal information has an error code;
if not, setting a corresponding default error code for the abnormal information, and recording the default error code and the abnormal information into a database.
2. The method of claim 1, further comprising:
receiving an input query instruction;
determining an interface type and an error code according to the query instruction;
determining corresponding interface information according to the interface type, and determining corresponding abnormal information according to the error code;
and outputting the interface information and the abnormal information.
3. The method of claim 1, after obtaining the exception information, further comprising:
judging whether the abnormal information is a messy code;
if so, marking the current abnormal state of the interface as an original abnormal state;
and outputting the original abnormal state to a preset position so that a user sets a standard error code and standard abnormal information for the original abnormal state.
4. The method of claim 1, further comprising:
receiving an input record deleting instruction, and determining a part to be deleted of the abnormal information historical record according to the record deleting instruction;
and deleting the part to be deleted of the abnormal information historical record.
5. A system for managing interface abnormality information, comprising:
the detection module is used for detecting whether the interface is in an abnormal state;
the acquisition module is used for acquiring abnormal information when the interface is in the abnormal state;
the first judging module is used for judging whether the abnormal information has error codes or not;
and the setting module is used for setting a corresponding default error code for the abnormal information when the abnormal information does not have the error code, and recording the default error code and the abnormal information into a database.
6. The system of claim 5, further comprising:
the first receiving module is used for receiving an input query instruction;
the first determining module is used for determining the interface type and the error code according to the query instruction;
the second determining module is used for determining corresponding interface information according to the interface type and determining corresponding abnormal information according to the error code;
and the first output module is used for outputting the interface information and the abnormal information.
7. The system of claim 5, further comprising:
the second judgment module is used for judging whether the abnormal information is a messy code;
the marking module is used for marking the current abnormal state of the interface as an original abnormal state when the abnormal information is messy codes;
and the second output module is used for outputting the original abnormal state to a preset position so that a user sets a standard error code and standard abnormal information for the original abnormal state.
8. The system of claim 5, further comprising:
the second receiving module is used for receiving an input record deleting instruction and determining a part to be deleted of the abnormal information historical record according to the record deleting instruction;
and the deleting module is used for deleting the part to be deleted of the abnormal information historical record.
9. An interface abnormality information management apparatus, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the method for managing interface abnormality information according to any one of claims 1 to 4 when executing the computer program.
10. A readable storage medium, characterized in that the readable storage medium has stored thereon a computer program which, when being executed by a processor, implements the steps of the method for managing interface abnormality information according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911055059.XA CN110955547B (en) | 2019-10-31 | 2019-10-31 | Management method, system, equipment and readable storage medium for interface abnormal information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911055059.XA CN110955547B (en) | 2019-10-31 | 2019-10-31 | Management method, system, equipment and readable storage medium for interface abnormal information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110955547A true CN110955547A (en) | 2020-04-03 |
| CN110955547B CN110955547B (en) | 2022-03-22 |
Family
ID=69976579
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911055059.XA Active CN110955547B (en) | 2019-10-31 | 2019-10-31 | Management method, system, equipment and readable storage medium for interface abnormal information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110955547B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111930584A (en) * | 2020-08-14 | 2020-11-13 | 山东云海国创云计算装备产业创新中心有限公司 | SD card controller function verification method, device and related components |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100262814A1 (en) * | 2009-04-10 | 2010-10-14 | Microsoft Corporation | Handling exceptions related to corrupt application state |
| CN104199819A (en) * | 2014-07-03 | 2014-12-10 | 北京思特奇信息技术股份有限公司 | WEB system error processing method and device |
| CN106603520A (en) * | 2016-12-08 | 2017-04-26 | 深圳Tcl数字技术有限公司 | Abnormal information interception method and apparatus thereof |
| CN107948744A (en) * | 2017-12-13 | 2018-04-20 | 深圳市雷鸟信息科技有限公司 | Interface detection method, interface detection device and computer-readable recording medium |
| CN109240703A (en) * | 2018-08-28 | 2019-01-18 | 郑州云海信息技术有限公司 | A kind of system mistake reminding method and device |
-
2019
- 2019-10-31 CN CN201911055059.XA patent/CN110955547B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100262814A1 (en) * | 2009-04-10 | 2010-10-14 | Microsoft Corporation | Handling exceptions related to corrupt application state |
| CN104199819A (en) * | 2014-07-03 | 2014-12-10 | 北京思特奇信息技术股份有限公司 | WEB system error processing method and device |
| CN106603520A (en) * | 2016-12-08 | 2017-04-26 | 深圳Tcl数字技术有限公司 | Abnormal information interception method and apparatus thereof |
| CN107948744A (en) * | 2017-12-13 | 2018-04-20 | 深圳市雷鸟信息科技有限公司 | Interface detection method, interface detection device and computer-readable recording medium |
| CN109240703A (en) * | 2018-08-28 | 2019-01-18 | 郑州云海信息技术有限公司 | A kind of system mistake reminding method and device |
Non-Patent Citations (2)
| Title |
|---|
| XU WU ET AL.: "Polot Attention Allocation Modeling under Multiple Factors Condition", 《SPRINGE-VERLAG BERLIN HEIDELBERG 2013》 * |
| 杨继武: "对车载通信单元（OCU）设备的接口监测", 《铁道通信信号》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111930584A (en) * | 2020-08-14 | 2020-11-13 | 山东云海国创云计算装备产业创新中心有限公司 | SD card controller function verification method, device and related components |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110955547B (en) | 2022-03-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107908494B (en) | Abnormal event processing method and device, electronic equipment and storage medium | |
| CN110225036B (en) | Account detection method, device, server and storage medium | |
| CN110633977A (en) | Payment exception processing method and device and terminal equipment | |
| CN112328631A (en) | Production fault analysis method and device, electronic equipment and storage medium | |
| CN110955547B (en) | Management method, system, equipment and readable storage medium for interface abnormal information | |
| CN103902543A (en) | Database inquiry method and device and database system | |
| CN111581235B (en) | Method and system for identifying common incidence relation | |
| CN110955562A (en) | Data recovery method, system, equipment and readable storage medium | |
| CN110764985A (en) | Method, system, equipment and readable storage medium for recording command line | |
| US20200118016A1 (en) | Data attribution using frequent pattern analysis | |
| CN111435326A (en) | Method and device for analyzing crash logs | |
| CN113051127B (en) | Abnormal power consumption detection method and device, electronic equipment and storage medium | |
| CN111400245B (en) | Art resource migration method and device | |
| CN113138960A (en) | Data storage method and system based on cloud storage space adjustment | |
| CN107578297B (en) | Member information aggregation method and device | |
| CN111045983B (en) | Nuclear power station electronic file management method, device, terminal equipment and medium | |
| CN112380115A (en) | Regression testing method and device, electronic equipment and storage medium | |
| CN108629610B (en) | Method and device for determining popularization information exposure | |
| CN111143156A (en) | Large data platform garbage task acquisition system and method and computer system | |
| CN113434754A (en) | Method and device for determining recommended API (application program interface) service, electronic equipment and storage medium | |
| CN111176903B (en) | Commodity data recovery method, system, equipment and readable storage medium | |
| CN112579638B (en) | Behavior tag information processing method and device, computer equipment and storage medium | |
| CN110264211B (en) | Wind control method, system, device and equipment | |
| CN111881200A (en) | Commodity data processing method, device and system | |
| CN114240224A (en) | Service strategy generation method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |