CN110740190B - Event reporting method, power terminal and computer readable storage medium - Google Patents
Event reporting method, power terminal and computer readable storage medium Download PDFInfo
- Publication number
- CN110740190B CN110740190B CN201911032603.9A CN201911032603A CN110740190B CN 110740190 B CN110740190 B CN 110740190B CN 201911032603 A CN201911032603 A CN 201911032603A CN 110740190 B CN110740190 B CN 110740190B
- Authority
- CN
- China
- Prior art keywords
- event
- reporting
- reported
- record
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
Abstract
The application provides an event reporting method, an electric power terminal and a computer readable storage medium, relates to the field of electric power terminals, and is applied to the electric power terminal; the target event has a report permission identification; obtaining an event record which is allowed to be reported in at least one target event; the event record has a valid identifier; and reporting the event record. According to the method and the device, the phenomenon that the event is not reported timely can be avoided by setting the reporting detection time.
Description
Technical Field
The present application relates to the field of power terminals, and in particular, to an event reporting method, a power terminal, and a computer-readable storage medium.
Background
With the wide application of the power terminal, the operation and maintenance efficiency of the power acquisition terminal is improved, the maintenance cost is reduced, and the method has important significance. The application requirements of various provinces on terminal acquisition equipment are increasing. The terminal event is taken as the most basic requirement and is brought into the assessment index, and because the judging and reporting methods of the events of all the bureaus are different, the accuracy of the event judgment and the accuracy of the reporting need to be ensured in order to meet the requirements of all the bureaus. Because the terminal events are various in types and have various possibilities, when a large number of events occur simultaneously and need to be reported, the phenomena of untimely reporting and slow reporting speed are easy to occur.
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 reporting method, an electrical terminal and a computer-readable storage medium.
In a first aspect, an embodiment of the present application provides an event reporting method, which is applied to an electric power terminal, and the method includes: detecting at least one target event allowed to be reported within preset time; the target event has a reporting permission identification; obtaining an event record which is allowed to be reported in the at least one target event; the event record has a valid identification; and reporting the event record.
Optionally, the step of reporting the event record includes: judging whether the file for storing the event record is smaller than a reported file threshold value or not; if so, reporting all the event records; and if not, performing frame reporting on the event record.
Optionally, the step of obtaining an event record that allows reporting in the at least one target event includes: acquiring the number of event records allowed to be reported of the at least one target event; judging whether the event records needing to be reported exist in the event record number; if not, detecting at least one target event allowed to be reported again within preset time; and if so, reporting the event record.
Optionally, after the step of reporting the event record, the method further includes: configuring a reporting state identifier for the target event allowed to be reported; the reporting state identifier is used for indicating that the target event is reported completely.
Optionally, before the step of detecting at least one target event allowed to be reported within a preset time, the method further includes: when at least one event is obtained, detecting whether the event record of the event is abnormal or not and allowing to report; if yes, the allowed reporting identification and the effective identification are respectively configured for the event and the event record.
In a second aspect, an embodiment of the present application provides an electric power terminal, which includes a detection module, an acquisition module, and a reporting module.
The detection module is used for detecting at least one target event allowed to be reported in a preset time; the target event has a reporting identifier;
the acquisition module is configured to acquire an event record that is allowed to be reported in the at least one target event; the event record has a valid identification;
and the reporting module is used for reporting the event record.
Optionally, the power terminal further includes a determination module; the judging module is used for judging whether the file for storing the event record is smaller than a reported file threshold value; the reporting module is further configured to report all the event records if the event records are available; and if not, performing frame reporting on the event record.
Optionally, the power terminal further comprises a configuration module; the configuration module is configured to configure a reporting status identifier for the target event allowed to be reported; and the reporting state identifier represents that the target event is reported and finished.
Optionally, the obtaining module is further configured to obtain a number of event records of the at least one target event, the number of event records being allowed to be reported; the judging module is also used for judging whether the event record which is allowed to be reported exists in the event record number; and if not, the detection module is further used for detecting at least one target event allowed to be reported again in the preset time.
In a third aspect, an embodiment of the present application is 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.
The application provides an event reporting method, an electric power terminal and a computer readable storage medium, which are applied to the electric power terminal, wherein the method detects at least one target event allowed to be reported within a preset time; the target event has an identifier allowing reporting; then obtaining an event record which is allowed to be reported in the at least one target event; the event record has a valid identification; and reporting the event record. According to the method and the device, the phenomenon that the event is not reported timely can be avoided by setting the reporting detection time.
In order to make the aforementioned objects, features and advantages of the present application comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
To more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed 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 those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a schematic flowchart of an event reporting method according to an embodiment of the present application;
fig. 2 is a schematic flow chart of another event reporting method provided in the embodiment of the present application;
fig. 3 is a schematic flowchart of another event reporting method provided in an embodiment of the present application;
fig. 4 is a schematic flow chart of another event reporting method provided in the embodiment of the present application;
fig. 5 is a schematic flowchart of another event reporting method according to an embodiment of the present application;
fig. 6 is a schematic block diagram of an electric power terminal according to an embodiment of the present disclosure;
fig. 7 is a schematic block diagram of another 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-electric power terminal, 301-detection module, 302-acquisition module, 303-reporting module, 304-judgment module and 305-configuration module.
Detailed Description
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. The components of the embodiments of the present application, as generally described and illustrated in the figures herein, could 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 should also be noted that, unless expressly stated or limited otherwise, the terms "disposed," "mounted," "connected," and "connected" are to be construed broadly and can include, for example, fixed connections, detachable connections, or integral connections; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. 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 achieve the purpose of timely reporting a terminal event, an embodiment of the present application provides an event reporting method, which is applied to an electric power terminal, please refer to fig. 1, where fig. 1 is a schematic flowchart of an event reporting method provided in an embodiment of the present application, where the event reporting method includes:
The target event has a reporting permission identifier.
The event record has a valid identification.
And step 204, reporting the event record.
For example, the preset time may be set to 30 seconds, that is, the power terminal detects whether there is an event that needs to be reported every 30 seconds. In the field, 30 seconds of detection time can be used for timely detecting and reporting events needing to be reported in the power terminal.
When the power terminal detects that the power-off event allows reporting within 30 seconds, it can be understood that the power-off event that allows reporting may have an identifier that allows reporting, for example, the identifier that allows reporting may be "TRUE", and it is assumed that there are 6 event records that allow reporting of the power-off event, and it can be understood that the 6 event records that allow reporting may have a valid identifier, which may be represented by "TRUE", and the power terminal may report the 6 event records to the master station, so that the master station obtains the state information of the terminal event.
The method is applied to the electric power terminal, and detects at least one target event allowed to be reported within preset time; the target event has an identifier allowing reporting; then obtaining an event record which is allowed to be reported in the at least one target event; the event record has a valid identification; and reporting the event record. The method and the device can avoid the phenomenon that the event is not reported timely by setting the reporting detection time.
Optionally, before the power terminal detects whether an event that allows reporting exists, the master station may also search for the reporting event, and after the master station finds that the event allows reporting, the master station may set the reporting identifier of the event to "FALSE" to indicate that the event has been reported, so as to prevent a phenomenon of repeated reporting of the event. Meanwhile, the master station may determine whether the power terminal is online and allows reporting, for example, the master station may determine whether an event allows reporting according to whether the power terminal turns on a reporting flag, and when the master station determines that the terminal is offline and does not allow reporting, the terminal does not report the event.
Optionally, when the event record is reported, the parameter information of the event may be used as the report content, for example, the parameter information may be the type of the event, the event recording unit, and the like, and the power terminal may report the parameter information as the report message content to the master station.
It should be noted that, in the embodiment of the present application, the event types may be divided into three main categories: the method comprises the steps of circularly detecting events, external module triggering events and detection events after execution of related tasks. The cyclic detection events (i.e. internal timing detection events) may include a terminal power-off event 3106, a communication flow overrun event in month 3110, and a terminal current loop abnormal event 3119; external module trigger events may include 3114 terminal time tick events (e.g., issuing set 40000200 and success, accurate time tick success), 3201 electrical control trip records (e.g., monthly electrical control, purchase electrical control cause trip), 310A device fault records (e.g., 485, carrier fault triggered by dread module), etc.; the detection events after the execution of the associated task may include a 310B power meter indication degree drop event (for example, the current power reading value of a certain event occurrence source is smaller than the last reading value), a 310E power meter stop event (for example, the total power consumption or current is not zero, the two power reading values of the certain event occurrence source greater than the threshold interval time are the same), a 310F terminal meter reading failure event (for example, the number of times of re-reading after the reading failure of the certain event occurrence source reaches the retry round is unsuccessful), and the like. It should be noted that the value 3106 represents an event id or an event sequence number of the power-off event of the terminal, and other values similarly represent the event id or the event sequence number of the corresponding event.
It should be further noted that, in the embodiment of the present application, the event recording unit may include event parameters such as an event serial number, a reporting service serial number, an event reporting identifier, and an event record valid identifier, and the event parameters are used to represent state information after an event occurs.
Optionally, to avoid a problem that a reporting speed is slow due to an excessively large reporting file, a possible implementation manner is provided on the basis of fig. 1, referring to fig. 2, fig. 2 is a schematic flowchart of an event reporting method provided in an embodiment of the present application, where step 202 specifically includes:
step 204-1, judging whether the file for storing the event record is smaller than a reported file threshold value.
If yes, go to step 204-2; if not, go to step 204-3.
And step 204-2, reporting all the event records.
And step 204-3, performing framing reporting on the event record.
For example, assuming that the file size for storing the power-off event is 1G, but in the reporting process, in order to ensure the efficiency of reporting the event, the master station can allow the reported file size to be 500M, so that when the power terminal reports, the first N records in the file may be reported first, where N may be defined according to actual scene requirements. It can be understood that the file size occupied by the first N event records is less than 500M, and then the remaining event records are reported. By performing frame reporting on the event records, the phenomenon of low reporting speed caused by overlarge reported files can be avoided.
Optionally, in order to obtain an event record allowed to be reported, a possible implementation is given on the basis of fig. 1, referring to fig. 3, fig. 3 is a schematic flow chart of another event reporting method provided in an embodiment of the present application, where the event reporting method further includes:
step 203-1, obtaining the number of event records allowed to be reported of at least one target event.
Step 203-2, judging whether there is an event record allowed to be reported from the event record number.
If not, go to step 202; if yes, go to step 204.
For example, when the power terminal detects that a power-off event needs to be reported, assuming that 30 event records of the power-off event occur, the power terminal may determine, from the 30 event records, an event record that is allowed to be reported.
It can be understood that, after an event occurs, the event may generate an event record at the terminal, but the event may be an abnormal event, for example, when the power meter is powered down when voltage jitter occurs and then power is restored, then there is a record of a power failure event at the power terminal, but the power meter is restored to normal, so that a power failure event generated at the terminal is an abnormal event record, and the abnormal event record does not affect the power terminal or the master station, so that the abnormal event record may not be reported. Therefore, the power terminal determines the event record allowed to be reported among all the event records to report the event. If the event record allowing the reporting does not exist, the electric power terminal will detect the event allowing the reporting again within the preset detection time.
It should be noted that, after the electric power terminal obtains the number of event records of at least one target event that are allowed to be reported, it may also be determined whether the number of event records exceeds the file depth of storing the event, and if the number of event records exceeds the file depth of storing the event, the first event in the event coverage file needs to be covered to achieve the purpose of circular coverage. For example, the file storage depth is 30 events that can be stored, and when the 31 st event needs to be stored, the 1 st event is overwritten by the 31 st event, and the storage sequence number of the 31 st event is set to 1.
Optionally, in order to determine whether an event has been reported completely, a possible implementation is given on the basis of fig. 1, referring to fig. 4, where fig. 4 is a schematic flow chart of another event reporting method provided in an embodiment of the present application, and the event reporting method further includes:
The reporting status identifier is used for indicating that the target event is reported completely.
For example, after the power-off event reporting process is completed, the power terminal may modify a reporting identifier "TREU" of the event to "FALSE" to prevent the event from being repeatedly reported, and then the power terminal may search a recording unit storing the power-off event, and configure a reporting status identifier, such as "complete" or "end", for the event in the recording unit, so as to indicate that the event has been reported completely.
Optionally, in order that the power terminal can detect an event that is allowed to be reported within the detection time, a possible implementation manner is provided on the basis of fig. 1, referring to fig. 5, and fig. 5 is a schematic flow chart of another event reporting method provided in the embodiment of the present application, where the method further includes:
And step 201, if yes, respectively configuring a report permission identifier and an effective identifier for the event and the event record.
For example, when 100 events occur, and the power terminal obtains the events, it first confirms that there is no exception in the event record in the 100 events and allows reporting, and configures a reporting identifier and a valid identifier for the event, which may be represented by "tune".
Through the description of the above embodiment, before an event is reported, that is, after the event occurs, the power terminal needs to detect whether the event is allowed to be reported according to event parameters, such as an event reporting identifier and an effective identifier, and meanwhile, an event type and an event recording unit of the event need to be prepared into a message for reporting, so that after the event occurs, the terminal needs to obtain parameter information, such as the event type and the event recording unit, that need to be reported.
Optionally, after the event occurs, the power terminal may add the event type, the event recording unit, and the unfinished identifier to the event parameter, and then report the parameter of the event as the report content. For example, after the electric terminal confirms that the event record is not abnormal and allows reporting, the electric terminal may add a reporting service number of the event in the event recording unit, record the content of the event in the event recording unit, and notify the warning lamp to flash to prompt the master station of the occurrence of the event when the electric terminal records the event.
Optionally, after the event occurs, the power terminal may further determine, according to the event identifier, whether the event after the event occurs is that the same event has occurred and is ended at the terminal, and if the event is not the same event, the power terminal may further add an event sequence number and a report service sequence number to the event recording unit.
Alternatively, after the event occurs, the power terminal may further search a file of the stored event for whether there is an unfinished event record of the event, and if so, obtain associated data information about the event in the file and add the associated data information to the event recording unit. By adding the relevant information of the event recording unit, the state information parameters of the event can be improved, so that the reported event content is more complete and accurate.
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. 6 shows a block schematic diagram of the power terminal provided in the embodiment of the present application, and as shown in fig. 6, the power terminal 30 may include: a detection module 301, an acquisition module 302 and a reporting module 303.
A detecting module 301, configured to detect at least one target event allowed to be reported within a preset time;
the target event has a reporting identifier.
An obtaining module 302, configured to obtain an event record that allows reporting in at least one target event;
the event record has a valid identifier.
A reporting module 303, configured to report the event record.
Optionally, the detecting module 301, the obtaining module 302, and the reporting module 303 may cooperatively perform steps 202 to 203 in the above embodiment.
The application provides an electric power terminal which comprises a detection module, an acquisition module and a reporting module. The detection module is used for detecting at least one target event which is allowed to be reported within preset time; the target event has an allowed reporting identification; the acquisition module is used for acquiring an event record which is allowed to be reported in at least one target event; the event record has a valid identifier; the reporting module is used for reporting the event record. According to the method and the device, the phenomenon that the event is not reported timely can be avoided by setting the reporting detection time.
Optionally, in order to determine whether the file size reported by the event exceeds the file reporting threshold, a possible implementation manner is provided on the basis of fig. 7, for example, fig. 7, where fig. 7 is a schematic block diagram of another power terminal provided in the embodiment of the present application, and the power terminal 30 further includes: a decision block 304.
The determining module 304 is configured to determine whether a file used for storing the event record is smaller than a reporting file threshold.
The reporting module 303 is further configured to report all event records if the file of the event record is smaller than the reporting file threshold; and if not, the event record is subjected to frame reporting.
It is understood that the determining module 304 can be used to perform the step 204-1, and the reporting module 303 can be used to perform the steps 204-2 and 204-3.
Optionally, in order to facilitate detecting a target event that is allowed to be reported, a possible implementation manner is provided on the basis of fig. 7, for example, fig. 8 is a block diagram of another power terminal provided in this embodiment of the present application. The power terminal 30 further includes: a configuration module 305.
A configuring module 305, configured to configure a reporting status identifier for the target event allowed to be reported.
The reporting state identifier represents that the target event is reported completely.
It will be appreciated that the configuration module 305 may be used to perform step 205 to achieve a corresponding technical effect.
Optionally, the obtaining module 302 is further configured to obtain the number of event records allowed to be reported of at least one target event; the determining module 304 is further configured to obtain an event record allowed to be reported according to the record number. If not, the detecting module 301 is further configured to detect at least one target event allowed to be reported again within a preset time.
It is understood that the obtaining module 302 can also perform the step 203-1, and the determining module can also be used for performing the step 203-2.
Optionally, the detecting module 301 is further configured to, when at least one event is obtained, detect that an event record of the event is abnormal and allow reporting, configure the identifier allowing reporting and the valid identifier for the event and the event record respectively by the configuring module 305.
It is to be appreciated that the detection module 301 may also be configured to perform step 200 and the configuration module 305 may also be configured to perform step 201 to achieve a corresponding technical effect.
An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the method for reporting an event as in 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, which may store program codes.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The apparatus embodiments described above are merely illustrative and, for example, the flowcharts 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, 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 may be stored in a computer-readable storage medium if they are implemented in the form of software functional modules and sold or used as separate products. 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 think of the changes or substitutions within the technical scope of the present application, and shall be covered by 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 (9)
1. An event reporting method is applied to an electric power terminal, and the method comprises the following steps:
detecting at least one target event allowed to be reported within preset time; the target event has a reporting permission identification;
obtaining an event record which is allowed to be reported in the at least one target event; the event record has a valid identification; the effective identifier represents that the event record is a non-abnormal event record; the non-abnormal event record can affect the power terminal or the master station;
searching whether an unfinished event record of the target event exists in a stored file, if so, acquiring associated data information of the target event in the file, adding the associated data information to an event recording unit, judging whether the target event is the same event at a terminal and is finished according to an event identifier, and if not, adding a sequence number of the target event and a reporting service sequence number to the event recording unit; reporting the event record;
configuring a reporting state identifier for the target event allowed to be reported; the reporting status identifier is used to indicate that the target event is reported completely, and the reporting status identifier is used to prevent the target event from being reported repeatedly.
2. The method of claim 1, wherein reporting the event record comprises:
judging whether the file for storing the event record is smaller than a reported file threshold value or not;
if so, reporting all the event records; and if not, performing frame reporting on the event record.
3. The method for reporting an event according to claim 1, wherein the step of obtaining the event record allowed to be reported in the at least one target event includes:
acquiring the number of event records of the at least one target event, which are allowed to be reported;
judging whether an event record allowing to be reported exists in the event record number;
if not, detecting at least one target event allowed to be reported again within preset time;
and if so, reporting the event record.
4. The method for reporting an event according to claim 1, wherein before the step of detecting at least one target event allowed to be reported within a preset time, the method further comprises:
when at least one event is obtained, detecting whether the event record of the event is abnormal or not and allowing to report;
if yes, the allowed reporting identification and the effective identification are respectively configured for the event and the event record.
5. An electrical power terminal, comprising: the device comprises a detection module, an acquisition module and a reporting module;
the detection module is used for detecting at least one target event which is allowed to be reported within preset time; the target event has a reporting identifier;
the acquisition module is configured to acquire an event record that is allowed to be reported in the at least one target event; the event record has a valid identification; the effective identifier represents that the event record is a non-abnormal event record; the non-abnormal event records can influence the power terminal or the master station; searching whether an unfinished event record of the target event exists in a stored file, if so, acquiring associated data information of the target event in the file, adding the associated data information to an event recording unit, judging whether the target event is the same event at a terminal and is finished according to an event identifier, and if not, adding a sequence number of the target event and a reporting service sequence number to the event recording unit;
the reporting module is used for reporting the event record;
a configuration module, configured with a reporting status identifier for the target event allowed to be reported; the reporting state identifier is used for indicating that the target event is reported completely, and the reporting state identifier is used for preventing the event from being reported repeatedly when the target event is reported.
6. The power terminal of claim 5, further comprising a determination module;
the judging module is used for judging whether the file for storing the event record is smaller than a reported file threshold value;
the reporting module is further configured to report all the event records if the event records are available; and if not, performing frame reporting on the event record.
7. The power terminal of claim 6, further comprising a configuration module;
the configuration module is configured to configure a reporting status identifier for the target event allowed to be reported; and the reporting state identifier represents that the target event is reported and finished.
8. The power terminal of claim 6,
the acquisition module is configured to acquire the number of event records of the at least one target event, which are allowed to be reported;
the judging module is also used for acquiring the event record allowed to be reported according to the record number;
and if not, the detection module is further configured to detect at least one target event allowed to be reported again within a preset time.
9. 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-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911032603.9A CN110740190B (en) | 2019-10-28 | 2019-10-28 | Event reporting method, power terminal and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911032603.9A CN110740190B (en) | 2019-10-28 | 2019-10-28 | Event reporting method, power terminal and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110740190A CN110740190A (en) | 2020-01-31 |
| CN110740190B true CN110740190B (en) | 2022-07-26 |
Family
ID=69271747
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911032603.9A Active CN110740190B (en) | 2019-10-28 | 2019-10-28 | Event reporting method, power terminal and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110740190B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111782416A (en) * | 2020-06-08 | 2020-10-16 | Oppo广东移动通信有限公司 | Data reporting method, device, system, terminal and computer readable storage medium |
| CN112463746B (en) * | 2020-12-11 | 2023-11-03 | 杭州海康汽车软件有限公司 | File storage and generation method and device and electronic equipment |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102714814A (en) * | 2012-03-06 | 2012-10-03 | 华为终端有限公司 | Data transmission method and system, electrical gateway and master station |
| CN103368907A (en) * | 2012-03-29 | 2013-10-23 | 腾讯科技（深圳）有限公司 | Event report request system, method thereof, client device and report request method thereof |
| CN105656714A (en) * | 2015-12-25 | 2016-06-08 | 北京京东尚科信息技术有限公司 | Data collection and reporting method and device of mobile device |
| EP3082365A4 (en) * | 2013-12-10 | 2016-12-28 | Zte Corp | Method for implementing soft handover of user equipment, and radio network controller |
| CN107422181A (en) * | 2017-08-04 | 2017-12-01 | 北方智能装备有限公司 | A kind of electric energy meter for supporting 698 communications protocol |
| CN108713348A (en) * | 2018-06-05 | 2018-10-26 | 北京小米移动软件有限公司 | Information uploading method, device, terminal and storage medium |
| CN109147284A (en) * | 2018-10-30 | 2019-01-04 | 宁波三星智能电气有限公司 | A kind of report method of intelligent electric meter |
| CN109548125A (en) * | 2019-01-21 | 2019-03-29 | 上海鸿研物流技术有限公司 | The data reporting method and its system of physical distribution apparatus |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110212645B (en) * | 2019-06-20 | 2023-04-28 | 国网湖南省电力有限公司 | Power consumption information acquisition terminal power failure event reporting method and device |
-
2019
- 2019-10-28 CN CN201911032603.9A patent/CN110740190B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102714814A (en) * | 2012-03-06 | 2012-10-03 | 华为终端有限公司 | Data transmission method and system, electrical gateway and master station |
| CN103368907A (en) * | 2012-03-29 | 2013-10-23 | 腾讯科技（深圳）有限公司 | Event report request system, method thereof, client device and report request method thereof |
| EP3082365A4 (en) * | 2013-12-10 | 2016-12-28 | Zte Corp | Method for implementing soft handover of user equipment, and radio network controller |
| CN105656714A (en) * | 2015-12-25 | 2016-06-08 | 北京京东尚科信息技术有限公司 | Data collection and reporting method and device of mobile device |
| CN107422181A (en) * | 2017-08-04 | 2017-12-01 | 北方智能装备有限公司 | A kind of electric energy meter for supporting 698 communications protocol |
| CN108713348A (en) * | 2018-06-05 | 2018-10-26 | 北京小米移动软件有限公司 | Information uploading method, device, terminal and storage medium |
| CN109147284A (en) * | 2018-10-30 | 2019-01-04 | 宁波三星智能电气有限公司 | A kind of report method of intelligent electric meter |
| CN109548125A (en) * | 2019-01-21 | 2019-03-29 | 上海鸿研物流技术有限公司 | The data reporting method and its system of physical distribution apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110740190A (en) | 2020-01-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110661659A (en) | Alarm method, device and system and electronic equipment | |
| CN110740190B (en) | Event reporting method, power terminal and computer readable storage medium | |
| CN106682162B (en) | Log management method and device | |
| CN112311617A (en) | Configured data monitoring and alarming method and system | |
| CN110609780B (en) | Data monitoring method and device, electronic equipment and storage medium | |
| CN108923972B (en) | Weight-reducing flow prompting method, device, server and storage medium | |
| CN112395156A (en) | Fault warning method and device, storage medium and electronic equipment | |
| CN110545292B (en) | Abnormal flow monitoring method and device | |
| CN108574839B (en) | Bayonet equipment abnormity detection method and device | |
| CN108073499B (en) | Application program testing method and device | |
| CN111666273B (en) | Meter reading system data validity analysis method and device | |
| CN113625945A (en) | Distributed storage slow disk processing method, system, terminal and storage medium | |
| CN112285478B (en) | Method and device for detecting vehicle static current, medium, equipment and vehicle | |
| CN110855484B (en) | Method, system, electronic device and storage medium for automatically detecting traffic change | |
| CN111163073A (en) | Flow data processing method and device | |
| CN110781146A (en) | Event storage method, power terminal and computer-readable storage medium | |
| CN109766235A (en) | Configuration file detection method, system, equipment and medium based on software supervision | |
| CN107025148B (en) | Mass data processing method and device | |
| CN114138615A (en) | Service alarm processing method, device, equipment and storage medium | |
| CN111176946B (en) | SEL log recording method, device, equipment and storage medium | |
| CN110460723B (en) | Screen protection method and device, computer equipment and computer readable storage medium | |
| CN111186337A (en) | Battery fault judging method and device | |
| CN111222928A (en) | Method and system for monitoring enterprise standard invoicing | |
| CN109992483A (en) | A kind of temperature monitoring method, device, equipment and readable storage medium storing program for executing | |
| CN114385387B (en) | Access information generation method and device and computer equipment |
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 |