CN110781146A - Event storage method, power terminal and computer-readable storage medium - Google Patents
Event storage method, power terminal and computer-readable storage medium Download PDFInfo
- Publication number
- CN110781146A CN110781146A CN201911033544.7A CN201911033544A CN110781146A CN 110781146 A CN110781146 A CN 110781146A CN 201911033544 A CN201911033544 A CN 201911033544A CN 110781146 A CN110781146 A CN 110781146A
- Authority
- CN
- China
- Prior art keywords
- event
- storing
- storage
- file
- module
- 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
- 238000000034 method Methods 0.000 title claims abstract description 55
- 230000002159 abnormal effect Effects 0.000 claims description 17
- 238000004590 computer program Methods 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 17
- 230000006870 function Effects 0.000 description 6
- 230000000694 effects Effects 0.000 description 2
- 230000005611 electricity Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/172—Caching, prefetching or hoarding of files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/06—Energy or water supply
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Economics (AREA)
- Public Health (AREA)
- Water Supply & Treatment (AREA)
- General Health & Medical Sciences (AREA)
- Human Resources & Organizations (AREA)
- Marketing (AREA)
- Primary Health Care (AREA)
- Strategic Management (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Human Computer Interaction (AREA)
- Telephone Function (AREA)
Abstract
The application provides an event storage method, an electric power terminal and a computer readable storage medium, which relate to the field of electric power terminals, and are characterized in that when at least one event is obtained, a file for storing the event is determined according to an event identifier of the at least one event; judging whether the file has the storage allowance of the storage event; if yes, storing the event to the rest storage positions of the file; and if not, storing the event to the storage position of the first event in the file so as to enable the event to cover the first event. Compared with the prior art, the purpose of controlling the storage size of the file can be achieved in an event covering mode in the event storage process.
Description
Technical Field
The application relates to the field of power acquisition terminals, in particular to an event storage method, a power terminal and a computer-readable storage medium.
Background
In recent years, with the steady development of the economy of China, the nation is forced to be 2020, a strong smart grid is built comprehensively, and the technology and equipment comprehensively achieve the goal of the international leading level. The operation and maintenance efficiency of the power acquisition terminal is improved, the maintenance cost is reduced, and the method has important significance.
With the wide application of the power terminal, the terminal event is also brought into the terminal assessment index, and the terminal event is various, so that the event is stored in time after the event occurs, the size of an event storage file cannot be controlled by a traditional event storage method, and important information is easy to clear when more stored event data need to be cleared.
Disclosure of Invention
In order to overcome at least the above-mentioned deficiencies in the prior art, an object of the present application is to provide an event storage method, a power terminal and a computer-readable storage medium.
In a first aspect, an embodiment of the present application provides an event storage method, which is applied to an electric power terminal, and the method includes:
when at least one event is obtained, determining a file for storing the event according to the event identification of the at least one event;
judging whether the file has a storage allowance for storing the event;
if yes, storing the event to the rest storage positions of the file;
and if not, storing the event to the storage position of the first event in the file so as to enable the event to cover the first event.
Optionally, before the step of determining whether the file has a storage margin for storing the event, the method further includes: acquiring parameter information of the event; the parameter information comprises any one or combination of the following items: event content, event sequence number, occurrence time, end time, event occurrence source and associated data information; and storing the parameter information of the event.
Optionally, before the step of obtaining the parameter information of the event, the method further includes: judging whether the event is finished or not; and if not, storing the configured end time identifier for the event.
Optionally, before the step of obtaining the parameter information of the event, the method further includes: judging whether the event is an abnormal event or not; and if so, storing the event exception identifier configured for the event.
Optionally, before the step of obtaining the parameter information of the event, the method further includes: judging whether the event needs to be reported or not; and if not, storing the configured event reporting identifier for the event.
Optionally, after the step of storing the event, the method further includes: judging whether the message content and the message length of the event are correct or not; and if not, storing the event message identification configured for the event.
In a second aspect, an embodiment of the present application provides an electric power terminal, including: the device comprises a determining module, a judging module and a storage module;
the determining module is used for determining a file for storing at least one event according to the event identifier of the at least one event when the at least one event is obtained;
and the judging module is used for judging whether the file has the storage allowance for storing the event.
The storage module is used for storing the event to the rest storage position of the file if the storage allowance for storing the event exists; and if the storage allowance for storing the event does not exist, storing the event to the storage position of the first event in the file so as to enable the event to cover the first event.
Optionally, the determining module is further configured to determine whether the event is ended; and the storage module is further used for storing the configured end time identifier for the event if the event is not detected.
Optionally, the determining module is further configured to determine whether the event is an abnormal event; and if so, storing the event exception identifier configured for the event.
In a third aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the method according to any one of the foregoing embodiments.
According to the event storage method, the power terminal and the computer-readable storage medium, firstly, when at least one event is obtained, a file for storing the event is determined according to an event identifier of the at least one event; judging whether the file has a storage allowance for storing the event; if yes, storing the event to the rest storage positions of the file; and if not, storing the event to the storage position of the first event in the file so as to enable the event to cover the first event. In the event storage process, the purpose of controlling the file storage size can be achieved in an event covering mode.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic flow chart of an event storage method according to an embodiment of the present application;
FIG. 2 is a schematic flow chart diagram of another event storage method provided by the embodiment of the application;
FIG. 3 is a schematic flow chart diagram of another event storage method provided by an embodiment of the present application;
FIG. 4 is a schematic flow chart diagram of another event storage method provided by the embodiments of the present application;
FIG. 5 is a schematic flow chart of another event storage method provided in the embodiments of the present application;
FIG. 6 is a schematic flow chart diagram of another event storage method provided by the embodiments of the present application;
fig. 7 is a schematic block diagram of an electric power terminal according to an embodiment of the present disclosure;
fig. 8 is a block diagram of another power terminal according to an embodiment of the present disclosure.
Icon: 30-power terminal, 301-determination module, 302-judgment module, 303-storage module, 304-acquisition module.
Detailed Description
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 but not all embodiments of the present application. The components of embodiments of the present application, generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. 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.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
In the description of the present application, it is further noted that, unless expressly stated or limited otherwise, the terms "disposed," "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be connected internally or indirectly. The specific meaning of the above terms in the present application can be understood in a specific case by those of ordinary skill in the art.
Based on the problems in the background art, in order to control the size of an event storage file in the process of storing an event, an embodiment of the present application provides an event storage method, which is applied to an electric power terminal, please refer to fig. 1, where fig. 1 is a schematic flow diagram of the event storage method provided in the embodiment of the present application. The event storage method comprises the following steps:
Alternatively, the event identification may be used to distinguish between different events.
If so, go to step 208; if not, go to step 209.
For example, when the event needs to be stored after the power-off event occurs, the power terminal may set an event identifier for the power-off event, where 3106 indicates the power-off event. From the event identifier 3106, it may be determined that a file with the file name EVT3106 may be used to store the power off event. The power-off event may be stored directly into the file with the file name EVT3106 provided that the file has storage margin, and may be overwritten on the first event in the file if the file has no storage margin.
The event storage method is applied to the power terminal, and when at least one event is obtained, a file for storing the event is determined according to an event identifier of the at least one event; then judging whether the file has the storage allowance of the storage event; if yes, storing the event to the rest storage positions of the file; and if not, storing the event to the storage position of the first event in the file so as to enable the event to cover the first event. When the file storage allowance for storing the event is insufficient in the storage process, the event is covered, and the effect of controlling the size of the stored file is achieved.
Alternatively, for the way of storing the event to the storage location of the first event in the file in step 209 so that the event covers the first event, it can be understood as follows: assuming that the file EVT3106 is available for storing 20 events, when the 21 st power-off event occurs and needs to be stored, the 21 st event is overwritten on the first event in the file, then the sequence number of the 21 st event is changed to 1, and so on, and when the 22 nd event is generated, the 22 nd event can overwrite the 2 nd event and change the event sequence number to 2. Thus, the purpose of controlling the file size can be realized when storing the event.
Optionally, all events obtained by the power terminal may be stored in a file form, and each event may be stored in a classified manner according to an event identifier, for example: assuming that the event identifier of the power off event is 3106 and the event identifier of the power meter power off event is 310E, when a file is created for the power off event, the file may be named by the event identifier, that is, the file name may be EVT3106, and when a file is created for the power meter power off event, the file name may be EVT 310E.
Optionally, when storing an event, in order to store parameter information of the event to facilitate searching and reporting of a subsequent event, a possible implementation manner is provided on the basis of fig. 1, referring to fig. 2, where fig. 2 is a schematic flow diagram of another event storage method provided by the present application, and the event storage method further includes:
and step 205, acquiring parameter information of the event.
The parameter information may include any one or a combination of the following: event content, event sequence number, occurrence time, end time, event occurrence source and associated data information.
And step 206, storing the parameter information of the event.
For example, the power terminal generates a 6 th event record at 20:00, the event content is: the electricity meter 1 is powered off, which may cause the failure of the terminal meter reading. When storing the event, the event parameter information that can be read is the occurrence time: 20: 00; the content of the event: power failure; event sequence number: 6; the event occurrence source: an electricity meter 1; and (3) associated data information: and the terminal meter reading fails.
It can be understood that the subsequent events can be conveniently searched and reported by storing the parameter information of the events.
Optionally, in order to obtain and store the end time information of the event, a possible implementation manner is provided on the basis of fig. 2, for example, fig. 3, and fig. 3 is a schematic flow diagram of another event storage method provided in the embodiment of the present application, where the event storage method further includes:
If not, go to step 202 a.
For example, after the power-on stopping event occurs, it may be determined whether the power-on stopping event has ended or not when the event is stored, the determining may be performed by searching whether the record of the event has an end time or not, if the end time of the event is searched, it may be determined that the event has ended, the end time of the event is read, if the end time of the event is not searched, it indicates that the event has not ended, an end time identifier may be configured for the event, for example, the end time identifier may be "empty" or "none", it is understood that the end time identifier is only used to indicate that the event has not ended after the event occurs, and a specific configuration manner of the end time identifier is not limited herein.
Optionally, in order to obtain an abnormal situation of an event to be stored, a possible implementation manner is provided on the basis of fig. 2, referring to fig. 4, fig. 4 is a schematic flow diagram of another event storage method provided in the embodiment of the present application, where the event storage method further includes:
and step 201b, judging whether the event is abnormal or not.
If yes, go to step 202 b.
For example, after an abnormal event of the terminal current loop occurs, before the event is stored, it may be determined whether the event is an abnormal event, for example, when the power loss occurs when the electric meter is jittered, and then the power is restored, then there is a record of a power failure event at the electric power terminal, but the electric meter is already restored to normal, so that a power failure event generated at the terminal is an abnormal event, when such an abnormal event occurs, the terminal may determine that the event is an abnormal event according to the event parameter information of the event, and then configure an event abnormal identifier for the event, for example: the event exception flag is set to "1", and of course, the exception flag may be marked in other forms, so as to indicate that the event with the exception flag is an exception event.
Optionally, before storing an event, in order to determine whether the event to be stored needs to be reported, a possible implementation manner is provided on the basis of fig. 2, referring to fig. 5, where fig. 5 is a schematic flow diagram of another event storage method provided in the embodiment of the present application, and the event storage method further includes:
step 201c, determining whether the event needs to be reported.
If not, go to step 202 c.
Step 202c, storing the report identifier configured for the event.
For example, after a power-off event occurs and before storage, according to a reporting flag in a parameter of a read power-off event, the reporting flag may be represented as "TRUE", and may also be represented as "yes" or "TRUE", which is not limited herein, it is assumed that when a reporting flag bit "TRUE" of the event is read, it indicates that the event needs to be reported, and when the reporting flag is not read, the reporting flag may be configured as "0" for the event, or may be in another form, and the purpose of the reporting flag may be used to indicate that the event does not need to be reported.
It can be understood that, by storing the reporting identifier of the event, the event to be reported can be quickly located in the process of searching and reporting the event.
It should be noted that, for the three different implementations of the steps 201a, 201b, and 201c provided in fig. 3, fig. 4, and fig. 5 above, they may be executed as independent implementations, or may be implemented in combination of any two or all of them, which is not limited herein, and for the case that includes at least two implementations, the order of execution is not limited herein. For example, when the flows of fig. 3, 4 and 4 are combined, step 202a in fig. 3 may be determined first, when it is determined that the event is not ended, step 201b in fig. 4 is performed after step 202a is performed, step 202b is performed after the event is determined to be abnormal, and then step 201c and step 202c in fig. 5 are performed after step 202b is performed. Of course, the sequence of such determinations may be adjustable based on the scene requirements.
Optionally, after the event storage is completed, in order to determine whether the content of the event storage is correct, on the basis of fig. 1, a possible implementation is given, referring to fig. 6, where fig. 6 is a schematic flow chart of another event storage method provided by an embodiment of the present application, and the event storage method further includes:
If not, go to step 211.
And step 211, storing the event message identifier configured for the event.
In order to implement the steps of the foregoing embodiment to achieve the corresponding technical effect, in an embodiment of the present application, a power terminal may be provided for the foregoing method example by dividing corresponding functions into function modules, and in a possible implementation manner, fig. 7 shows a block diagram of the power terminal provided in the embodiment of the present application, and as shown in fig. 7, the power terminal 30 may include: a determining module 301, a judging module 302 and a storing module 303.
A determining module 301, configured to determine, when at least one event is obtained, a file for storing the event according to an event identifier of the at least one event.
The determining module 302 is configured to determine whether the file has a storage margin of the storage event.
The storage module 303 is configured to store the event to a remaining storage location of the file if a storage margin exists; and if the storage margin does not exist, storing the event to the storage position of the first event in the file so as to enable the event to cover the first event.
It is understood that in the above embodiment, the determining module 301 may be configured to perform the step 200, the determining module 302 may be configured to perform the step 207, and the storing module 303 may perform the step 208 and the step 209.
The power terminal comprises a determining module, a judging module and a storing module, wherein the determining module is used for determining a file for storing an event according to an event identifier of at least one event when the at least one event is obtained; the judging module is used for judging whether the file has the storage allowance of the storage event; the storage module is used for storing the event to the residual storage position of the file if the storage allowance exists; if the storage allowance does not exist, storing the event to the storage position of the first event in the file so that the event covers the first event, and realizing the beneficial effect of controlling the size of the stored file through the event covering mode.
Optionally, in order to store the relevant parameters of the event that needs to be stored, on the basis of fig. 7, a possible implementation is given, for example, fig. 8, and fig. 8 is a block schematic diagram of another power terminal provided in the embodiment of the present application. The power terminal 30 further includes: an acquisition module 304.
The obtaining module 304 is configured to obtain parameter information of an event, where the parameter information includes any one or a combination of the following: event content, event sequence number, occurrence time, end time, event occurrence source and associated data information. The storage module 303 is further configured to store parameter information of the event.
It is understood that the obtaining module 304 may be configured to perform the step 205 in the foregoing embodiment, and the storing module 303 may also perform the step 206 in the foregoing embodiment.
Optionally, before storing the event, in order to determine the ending state of the event acquisition event, the determining module 302 is further configured to determine whether the event ends, and the storing module 303 is further configured to store the ending time identifier after configuring the ending time identifier for the event if the event does not end.
It is understood that the determining module 302 and the storing module 303 can also be used to cooperatively perform the step 201a and the step 202a in the above embodiments.
Optionally, before storing the event, in order to determine the abnormal event, the determining module 302 is further configured to determine whether the event is an abnormal event; the storage module 303 is further configured to, if the event is abnormal, store the event abnormal identifier after configuring the event abnormal identifier for the event.
It is understood that the determining module 302 and the storing module 303 can also be used to cooperatively perform the step 201b and the step 202b in the above embodiments.
Optionally, in order to know whether an event that needs to be stored needs to be reported, the determining module 302 is further configured to determine whether the event needs to be reported; the storage module 303 is further configured to report the event identifier after the event identifier configured for the event is passed when the event needs to be reported.
It is understood that the determining module 302 and the storing module 303 can also be used to cooperatively perform the step 201c and the step 202c in the above embodiments.
Optionally, in order to determine whether the event is successfully stored and whether the stored content is correct, the determining module 302 is further configured to determine whether the message content and the message length of the event are correct, and if so, the storing module 303 is further configured to store the event message identifier after configuring the event message identifier for the event.
It is understood that the determining module 302 and the storing module 303 can also be used to cooperatively perform the step 210 and the step 211 in the above embodiments.
Embodiments of the present application further provide a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the event storage method according to any one of the foregoing embodiments is implemented.
The computer-readable storage medium may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Read Only Memory (EPROM), an electrically Erasable Read Only Memory (EEPROM), a usb disk, a removable hard disk, a magnetic disk, or an optical disk.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative and, for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, the functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application.
The above description is only for various embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the present application, and all such changes or substitutions are included in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. An event storage method is applied to a power terminal, and comprises the following steps:
when at least one event is obtained, determining a file for storing the event according to the event identification of the at least one event;
judging whether the file has a storage allowance for storing the event;
if yes, storing the event to the rest storage positions of the file;
and if not, storing the event to the storage position of the first event in the file so as to enable the event to cover the first event.
2. The event storage method according to claim 1, further comprising, before the step of determining whether the file has a storage margin for storing the event:
acquiring parameter information of the event; the parameter information comprises any one or combination of the following items: event content, event sequence number, occurrence time, end time, event occurrence source and associated data information;
and storing the parameter information of the event.
3. The event storage method according to claim 2, further comprising, before the step of acquiring the parameter information of the event:
judging whether the event is finished or not;
and if not, storing the configured end time identifier for the event.
4. The event storage method according to claim 2, wherein before the step of obtaining the parameter information of the event, the method further comprises:
judging whether the event is an abnormal event or not;
and if so, storing the event exception identifier configured for the event.
5. The event storage method according to claim 2, wherein before the step of obtaining the parameter information of the event, the method further comprises:
judging whether the event needs to be reported or not;
and if not, storing the event reporting identification configured for the event.
6. The event storage method according to claim 1, wherein the step of storing the event is followed by further comprising:
judging whether the message content and the message length of the event are correct or not;
and if not, storing the event message identifier configured for the event.
7. An electrical power terminal, comprising: the device comprises a determining module, a judging module and a storage module;
the determining module is used for determining a file for storing at least one event according to the event identifier of the at least one event when the at least one event is obtained;
the judging module is used for judging whether the file has storage allowance for storing the event;
the storage module is used for storing the event to the residual storage position of the file if the storage allowance exists; and if the storage margin does not exist, storing the event to the storage position of the first event in the file so as to enable the event to cover the first event.
8. The power terminal of claim 7, further comprising an acquisition module;
the acquisition module is used for acquiring the parameter information of the event; the parameter information comprises any one or combination of the following items: event content, event sequence number, occurrence time, end time, event occurrence source and associated data information;
the storage module is further used for storing the parameter information of the event.
9. The power terminal of claim 7, comprising:
the judging module is also used for judging whether the event is finished or not;
and the storage module is further used for storing the configured end time identifier for the event if the event is not detected.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911033544.7A CN110781146A (en) | 2019-10-28 | 2019-10-28 | Event storage method, power terminal and computer-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911033544.7A CN110781146A (en) | 2019-10-28 | 2019-10-28 | Event storage method, power terminal and computer-readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110781146A true CN110781146A (en) | 2020-02-11 |
Family
ID=69387119
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911033544.7A Pending CN110781146A (en) | 2019-10-28 | 2019-10-28 | Event storage method, power terminal and computer-readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110781146A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112685424A (en) * | 2021-01-04 | 2021-04-20 | 潍柴动力股份有限公司 | Processing method and device for engine fault storage |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101334667A (en) * | 2007-06-26 | 2008-12-31 | 株洲南车时代电气股份有限公司 | Locomotive status messages checking and diagnosis recording method and device |
| CN102981944A (en) * | 2012-12-12 | 2013-03-20 | 青岛海信宽带多媒体技术有限公司 | Log storage method based on file system |
| CN107526674A (en) * | 2017-08-31 | 2017-12-29 | 郑州云海信息技术有限公司 | A kind of method and apparatus of embedded system log recording |
| CN109254733A (en) * | 2018-09-04 | 2019-01-22 | 北京百度网讯科技有限公司 | Methods, devices and systems for storing data |
| CN109542844A (en) * | 2018-12-03 | 2019-03-29 | 郑州云海信息技术有限公司 | A kind of event log collection method, system and electronic equipment and storage medium |
-
2019
- 2019-10-28 CN CN201911033544.7A patent/CN110781146A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101334667A (en) * | 2007-06-26 | 2008-12-31 | 株洲南车时代电气股份有限公司 | Locomotive status messages checking and diagnosis recording method and device |
| CN102981944A (en) * | 2012-12-12 | 2013-03-20 | 青岛海信宽带多媒体技术有限公司 | Log storage method based on file system |
| CN107526674A (en) * | 2017-08-31 | 2017-12-29 | 郑州云海信息技术有限公司 | A kind of method and apparatus of embedded system log recording |
| CN109254733A (en) * | 2018-09-04 | 2019-01-22 | 北京百度网讯科技有限公司 | Methods, devices and systems for storing data |
| CN109542844A (en) * | 2018-12-03 | 2019-03-29 | 郑州云海信息技术有限公司 | A kind of event log collection method, system and electronic equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112685424A (en) * | 2021-01-04 | 2021-04-20 | 潍柴动力股份有限公司 | Processing method and device for engine fault storage |
| CN112685424B (en) * | 2021-01-04 | 2022-08-23 | 潍柴动力股份有限公司 | Processing method and device for engine fault storage |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11158143B2 (en) | Vehicle diagnostic method and device, and computer readable storage medium | |
| CN112311617A (en) | Configured data monitoring and alarming method and system | |
| CN109165170B (en) | Method and system for automatic request test | |
| CN109669798B (en) | Crash analysis method, crash analysis device, electronic equipment and storage medium | |
| KR102168212B1 (en) | Apparatus and method for application log data processing | |
| CN109733238B (en) | Fault detection method, device, storage medium and processor | |
| CN108632108B (en) | Monitoring method and device based on polling protocol and readable storage medium | |
| CN105512562B (en) | Vulnerability mining method and device and electronic equipment | |
| CN111367584B (en) | Power supply adaptation method and device and computer readable storage medium | |
| CN110069925A (en) | Software monitors method, system and computer readable storage medium | |
| CN110209529A (en) | The guard method of radio frequency parameter and electronic equipment | |
| CN110749027B (en) | Monitoring method and device for electrical equipment, air conditioner and storage medium | |
| CN107357619B (en) | Method, device, equipment and storage medium for generating card configuration file | |
| CN110740190B (en) | Event reporting method, power terminal and computer readable storage medium | |
| CN110781146A (en) | Event storage method, power terminal and computer-readable storage medium | |
| CN111143317A (en) | Log storage method, device and equipment and readable storage medium | |
| CN113434915A (en) | Case intrusion state detection device and method and edge server | |
| CN111049824B (en) | Resource environment big data management method, storage medium and control device | |
| CN112162908A (en) | Program call link monitoring implementation method and device based on bytecode injection technology | |
| CN115271764B (en) | Safety management and control method and system for smart phone maintenance | |
| CN111158769A (en) | Method and device for checking and modifying BIOS (basic input output System) options | |
| CN111258608A (en) | Software upgrading method and device for terminal equipment and electronic system | |
| CN107590044B (en) | Testing method, device and equipment for distributed storage cluster | |
| CN110597688A (en) | Monitoring information acquisition method and system | |
| CN109766235A (en) | Configuration file detection method, system, equipment and medium based on software supervision |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200211 |