CN110740190A - 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
- CN110740190A CN110740190A CN201911032603.9A CN201911032603A CN110740190A CN 110740190 A CN110740190 A CN 110740190A CN 201911032603 A CN201911032603 A CN 201911032603A CN 110740190 A CN110740190 A CN 110740190A
- Authority
- CN
- China
- Prior art keywords
- event
- reporting
- reported
- allowed
- 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.)
- Granted
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Telephone Function (AREA)
- Alarm Systems (AREA)
Abstract
The utility model provides an event reporting method, an electric power terminal and a computer readable storage medium, which relate to the field of electric power terminals and are applied to the electric power terminal, the method detects at least target events allowed to be reported within a preset time, the target events have allowed reporting marks, event records allowed to be reported in at least target events are obtained, the event records have effective marks, and the event records are reported.
Description
Technical Field
The present application relates to the field of power terminals, and in particular, to event reporting methods, a power terminal, and a computer-readable storage medium.
Background
The method has the advantages that the operation and maintenance efficiency of the power acquisition terminal is improved and the maintenance cost is reduced along with the general application of the power terminal, and has important significance, the application requirements of various departments on the terminal acquisition equipment are continuously increased, terminal events are taken as the most basic requirements and are brought into assessment indexes, and because the judgment and reporting methods of the departments on the events are different, the accuracy of event judgment and the reporting accuracy need to be guaranteed in order to meet the requirements of the departments.
Disclosure of Invention
To overcome at least the above-mentioned deficiencies in the prior art, of the present application is directed to providing event reporting methods, power terminals and computer readable storage media.
In an aspect, an embodiment of the present application provides a event reporting method, which is applied to an electric power terminal, and the method includes detecting at least target events allowed to be reported within a preset time, where the target events have identifiers allowed to be reported, acquiring an event record allowed to be reported from the at least target events, where the event record has an effective identifier, 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 the event records allowed to be reported in the at least target events includes obtaining the number of event records allowed to be reported of the at least target events, determining whether there are event records required to be reported from the number of event records, if not, detecting at least target events allowed to be reported again within a preset time, and if so, reporting the event records.
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 target events allowed to be reported within a preset time, the method further includes, when at least events are obtained, detecting whether an event record of the event is abnormal and allowed to be reported, and if so, configuring the allowed reporting identifier and the valid identifier for the event and the event record respectively.
In a second aspect, an embodiment of the present application provides power terminals, which include a detection module, an acquisition module, and a reporting module.
The detection module is used for detecting at least target events allowed to be reported in a preset time, wherein the target events have reporting identifications;
the acquisition module is used for acquiring event records which are allowed to be reported in the at least target events, wherein the event records have effective identifiers;
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 found to be valid; 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 completely.
Optionally, the obtaining module is further configured to obtain the number of event records of the at least target events, the determining module is further configured to determine whether there is an event record of the at least target events, and if not, the detecting module is further configured to detect at least target events allowed to be reported again within a preset time.
In a third aspect, computer readable storage media of this application, having stored thereon a computer program that, when executed by a processor, performs the method of any of the embodiments described above.
The event reporting methods, the power terminal and the computer readable storage medium are applied to the power terminal, the method detects at least target events which are allowed to be reported within preset time, the target events have allowed reporting identifications, then event records which are allowed to be reported in the at least target events are obtained, the event records have effective identifications, and then the event records are reported.
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 event reporting methods provided in the embodiments of the present application;
fig. 2 is a schematic flow chart of another event reporting methods provided in the embodiments of the present application;
fig. 3 is a schematic flow chart of another event reporting methods provided in the embodiments of the present application;
fig. 4 is a schematic flow chart of another event reporting methods provided in the embodiments of the present application;
fig. 5 is a schematic flow chart of another event reporting methods provided in the embodiments of the present application;
fig. 6 is a block diagram of power terminals provided in the embodiments of the present application;
fig. 7 is a block diagram of another kinds of power terminals provided in the embodiments of the present application;
fig. 8 is a block diagram of another power terminals provided in an embodiment of the present application.
Icon: 30-electric power terminal, 301-detection module, 302-acquisition module, 303-reporting module, 304-judgment module and 305-configuration module.
Detailed Description
To further clarify the objects, aspects and advantages of the embodiments of the present application, reference will now be made in detail to the present embodiments of the application illustrated in the accompanying drawings, which form a part hereof, and to show by way of illustration, and not by way of limitation, some embodiments of the application .
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 numerals and letters refer to like items in the following figures, and thus once a item is defined in figures, it need not be further defined and explained by in subsequent figures.
In the description of the present application, it should also be noted that unless otherwise expressly stated or limited, the terms "disposed," "mounted," "connected," and "connected" shall be construed , and for example, may be a fixed connection, a removable connection, or a body connection, a mechanical connection, an electrical connection, a direct connection, an indirect connection via an intermediary, and a communication between two elements.
Based on the problems proposed by the background art, in order to achieve the purpose of timely reporting a terminal event, an embodiment of the present application provides event reporting methods, which are applied to an electric power terminal, please refer to fig. 1, where fig. 1 is a schematic flowchart of event reporting methods provided by the embodiment of the present application, and 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 times every 30 seconds for any event that needs to be reported, in the field, the 30 seconds detection time may be times for timely detecting and reporting the event that needs to be reported in the power terminal.
When the power terminal detects that the power-off event is allowed to be reported within 30 seconds, it can be understood that the power-off event allowed to be reported may have an identifier allowing reporting, for example, the identifier allowing reporting may be "TRUE", and assuming that there are 6 event records allowed to be reported by the power-off event, it can be understood that the 6 event records allowed to be reported may have valid identifiers, 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 event reporting methods are applied to an electric power terminal, detect at least target events allowed to be reported in preset time, wherein the target events have allowed reporting identifications, then obtain event records allowed to be reported in the at least target events, wherein the event records have effective identifications, and then report the event records.
Optionally, before the power terminal detects whether an event allowing reporting exists, the master station may also search for the reported event, and after the master station finds that the event allowing reporting exists, 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 reporting the event record, 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 classified into three main categories: detecting events after circulation detection events, external module trigger events and related tasks are executed. The cyclic detection events (i.e. internal timing detection events) may include 3106 a terminal power-off event, a 3110 month communication flow overrun event, and a 3119 terminal current loop abnormal event; external module trigger events may include 3114 terminal time tick events (e.g., setting 40000200 issued and successful, accurate time tick successful), 3201 electrical control trip records (e.g., monthly electrical control, trip caused by purchasing electrical control), 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, which are used to represent state information after an event occurs.
Optionally, to avoid the problem that the reporting speed is slow due to an excessively large reporting file, on the basis of fig. 1, possible implementation manners are provided, referring to fig. 2, fig. 2 is a schematic flowchart of event reporting methods provided in this 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 event records.
And step 204-3, performing frame 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 event reporting, the master station can allow the reported file size to be 500M, then when the power terminal reports, the first N records in the file may be reported first, where N may be defined according to the 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, on the basis of fig. 1, possible implementation manners are given, referring to fig. 3, where fig. 3 is a schematic flowchart of another event reporting methods provided in this embodiment of the present application, and the event reporting method further includes:
step 203-1, obtaining the number of event records allowed to be reported of at least target events.
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, when events occur, the event may generate event records at the terminal, but the event may be abnormal events, for example, when the power loss occurs and the power is restored immediately after the power loss occurs when the voltage of the electric meter shakes, blackout event records are available at the electric terminal, but the electric meter has recovered to be normal, so that blackout events generated at the terminal are abnormal event records, which do not affect the electric terminal or the master station, and therefore may not be reported.
It should be noted that, after the power terminal obtains the number of event records allowed to be reported of at least target events, it may also be determined whether the number of event records exceeds the file depth of storing the event, and if so, it is necessary to overwrite the th event in the file with the event to achieve the purpose of cyclic overwriting.
Optionally, to confirm whether the event has been reported completely, on the basis of fig. 1, possible implementation manners are given, referring to fig. 4, where fig. 4 is a schematic flowchart of another event reporting methods provided in this 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 the event allowed to be reported within the detection time, on the basis of fig. 1, possible implementation manners are given, referring to fig. 5, and fig. 5 is a schematic flow chart of another event reporting methods provided by the embodiment of the present application, where the method further includes:
and 200, when at least events are obtained, detecting whether the event record of the events is abnormal or not and allowing to report.
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 the 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, the event type and the 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 needs 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 confirming that the event record is not abnormal and reporting is allowed, the power terminal may add a reporting service number of the event to 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 to generate the event when the power 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, acquire 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 the embodiment of the present application, power terminals may be provided for the method example by adopting a manner of dividing corresponding functions into function modules, and in possible implementation manners, fig. 6 shows a block schematic diagram of power terminals 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.
The detection module 301 is configured to detect at least target events allowed to be reported within a preset time;
the target event has a reporting identifier.
An obtaining module 302, configured to obtain event records that are allowed to be reported among at least target events;
the event record has a valid identification.
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 electric power terminals comprise a detection module, an acquisition module and a reporting module, wherein the detection module is used for detecting at least target events which are allowed to be reported within preset time, the target events are provided with marks which are allowed to be reported, the acquisition module is used for acquiring event records which are allowed to be reported in at least target events, the event records are provided with effective marks, and the reporting module is used for reporting the event records.
Optionally, to determine whether the file size reported by the event exceeds the file reporting threshold, on the basis of fig. 7, possible implementation manners are provided, for example, fig. 7 is a block diagram of another power terminals provided in this embodiment, where the power terminal 30 further includes a determining module 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 the target event allowed to be reported, on the basis of fig. 7, possible implementations are provided, for example, fig. 8 is a block diagram of another power terminals provided in this embodiment of the present application, and 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 that are allowed to be reported of at least target events, the determining module 304 is further configured to obtain the event records that are allowed to be reported according to the number of records, and if not, the detecting module 301 is further configured to detect at least target events that are 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 events are obtained, detect that an event record of the event is abnormal and is allowed to be reported, configure the configuration module 305 to configure an identifier allowing reporting and a valid identifier for the event and the event record, respectively.
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.
The embodiment of the present application further provides computer-readable storage media, on which a computer program is stored, and when the computer program is executed by a processor, the method for reporting an event is implemented as any of items in the foregoing embodiments.
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.
The above-described apparatus embodiments are merely illustrative, and for example, the flowcharts and block diagrams in the figures may 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 addition, each functional module in the embodiments of the present application may be integrated in to form independent parts, or each module may exist separately, or two or more modules may be integrated to form independent parts.
Based on the understanding that the technical solutions of the present application, in essence or a part thereof contributing to the prior art, may be embodied in the form of a software product stored in storage media, which includes several instructions for causing computer devices (which may be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods described in 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, event reporting method, characterized in that, applying to the power terminal, the method includes:
detecting at least target events allowed to be reported in a preset time, wherein the target events have allowed reporting identifications;
obtaining event records which are allowed to be reported in the at least target events, wherein the event records have effective identifications;
and reporting the event record.
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 target events comprises:
acquiring the number of event records allowed to be reported of the at least target events;
judging whether an event record allowing to be reported exists in the event record number;
if not, detecting at least target events allowed to be reported again in preset time;
and if so, reporting the event record.
4. The method for reporting an event according to claim 1, wherein after the step of reporting the event record, the method further comprises:
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.
5. The method for reporting an event according to claim 1, wherein before the step of detecting at least target events allowed to be reported within a preset time, the method further comprises:
when at least events are obtained, detecting whether the event record of the events is abnormal or not and allowing to be reported;
if yes, the allowed reporting identification and the effective identification are respectively configured for the event and the event record.
The electric power terminals are characterized by comprising a detection module, an acquisition module and a reporting module;
the detection module is used for detecting at least target events allowed to be reported in a preset time, wherein the target events have reporting identifications;
the acquisition module is used for acquiring event records which are allowed to be reported in the at least target events, wherein the event records have effective identifiers;
and the reporting module is used for reporting the event record.
7. The power terminal of claim 6, 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 found to be valid; and if not, performing frame reporting on the event record.
8. The power terminal of claim 7, 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 completely.
9. The power terminal of claim 7,
the obtaining module is configured to obtain the number of event records that are allowed to be reported for the at least target events;
the judging module is also used for acquiring the event record allowed to be reported according to the record number;
if not, the detection module is further configured to detect at least target events allowed to be reported again within a preset time.
10, 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 of claims 1-5, .
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 true CN110740190A (en) | 2020-01-31 |
| CN110740190B 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) |
Cited By (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 |
| CN112463746A (en) * | 2020-12-11 | 2021-03-09 | 杭州海康汽车软件有限公司 | File storage and generation method and device and electronic equipment |
Citations (9)
| 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 |
| CN110212645A (en) * | 2019-06-20 | 2019-09-06 | 国网湖南省电力有限公司 | A kind of power information acquisition terminal power-off event report method and device |
-
2019
- 2019-10-28 CN CN201911032603.9A patent/CN110740190B/en active Active
Patent Citations (9)
| 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 |
| CN110212645A (en) * | 2019-06-20 | 2019-09-06 | 国网湖南省电力有限公司 | A kind of power information acquisition terminal power-off event report method and device |
Cited By (4)
| 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 |
| CN111782416B (en) * | 2020-06-08 | 2024-05-31 | Oppo广东移动通信有限公司 | Data reporting method, device, system, terminal and computer readable storage medium |
| CN112463746A (en) * | 2020-12-11 | 2021-03-09 | 杭州海康汽车软件有限公司 | File storage and generation method and device and electronic equipment |
| CN112463746B (en) * | 2020-12-11 | 2023-11-03 | 杭州海康汽车软件有限公司 | File storage and generation method and device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110740190B (en) | 2022-07-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11327734B2 (en) | Download system of app, determination method of installation type and storage medium | |
| CN108872762B (en) | Electronic equipment leakage detection method and device, electronic equipment and storage medium | |
| CN110609780B (en) | Data monitoring method and device, electronic equipment and storage medium | |
| CN109669798B (en) | Crash analysis method, crash analysis device, electronic equipment and storage medium | |
| CN110545292B (en) | Abnormal flow monitoring method and device | |
| CN110203155B (en) | Early warning method and device for abnormal vehicle fuel consumption, terminal equipment and storage medium | |
| CN110740190A (en) | Event reporting method, power terminal and computer readable storage medium | |
| US20170255244A1 (en) | Systems and methods for operating a virtual power environment | |
| CN113992340B (en) | User abnormal behavior identification method, device, equipment and storage medium | |
| CN111163073A (en) | Flow data processing method and device | |
| CN111141971A (en) | Charging alarm system and method | |
| CN110191097B (en) | Method, system, equipment and storage medium for detecting security of login page | |
| CN113386609A (en) | Charging pile maintenance method and related equipment | |
| CN104767876A (en) | Safety software processing method and user terminal | |
| CN104021340A (en) | Method and device for detecting installation of malicious applications | |
| CN106899977B (en) | Abnormal flow detection method and device | |
| CN104268231B (en) | A kind of file access method, device and Intelligent File System | |
| CN109598525B (en) | Data processing method and device | |
| CN110781146A (en) | Event storage method, power terminal and computer-readable storage medium | |
| CN109842850A (en) | Electric vehicle monitoring method and device | |
| CN113009407B (en) | Voltage event recording method and device for double-core intelligent ammeter and double-core intelligent ammeter | |
| CN114237959A (en) | Robot life cycle management method, device, terminal and storage medium | |
| CN110460723B (en) | Screen protection method and device, computer equipment and computer readable storage medium | |
| CN114138615A (en) | Service alarm processing method, device, equipment and storage medium | |
| CN113561835B (en) | Charging and billing method for electric automobile and related 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 |