WO2022198919A1 - 双芯智能电表的超差事件记录方法、装置和计算机设备 - Google Patents

双芯智能电表的超差事件记录方法、装置和计算机设备 Download PDF

Info

Publication number
WO2022198919A1
WO2022198919A1 PCT/CN2021/115086 CN2021115086W WO2022198919A1 WO 2022198919 A1 WO2022198919 A1 WO 2022198919A1 CN 2021115086 W CN2021115086 W CN 2021115086W WO 2022198919 A1 WO2022198919 A1 WO 2022198919A1
Authority
WO
WIPO (PCT)
Prior art keywords
error
real
time
tolerance
dual
Prior art date
Application number
PCT/CN2021/115086
Other languages
English (en)
French (fr)
Inventor
李伟华
尹仕红
赵雪松
刘星廷
吴昊文
张乐平
谢文旺
Original Assignee
深圳供电局有限公司
南方电网数字电网研究院有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 深圳供电局有限公司, 南方电网数字电网研究院有限公司 filed Critical 深圳供电局有限公司
Publication of WO2022198919A1 publication Critical patent/WO2022198919A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
    • G01R35/00—Testing or calibrating of apparatus covered by the other groups of this subclass
    • G01R35/04—Testing or calibrating of apparatus covered by the other groups of this subclass of instruments for measuring time integral of power or current
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/544—Buffers; Shared memory; Pipes

Definitions

  • the present application relates to the technical field of electric energy measurement, and in particular, to a method, device, computer equipment and storage medium for recording out-of-tolerance events of a dual-core smart electric meter.
  • the new generation of dual-core smart meters uses two chips, that is, the management core and the metering core operate independently and are isolated from each other.
  • the metering core can be responsible for the metering function of the meter and the management core. It is responsible for expanding the function, so that when the error self-monitoring by the management core will not affect the normal measuring function of the measuring core.
  • the current out-of-tolerance event recording for the electric meter is based on the integrated design of the smart meter, and for the dual-core smart meter, the current out-of-tolerance event recording method for the electric meter cannot be applied, and it is impossible to realize the voltage event of the dual-core smart meter. Accurate records.
  • the current state identifier is replaced with the real-time state identifier, and the out-of-tolerance event corresponding to the real-time state identifier is recorded.
  • the preset out-of-tolerance event state identification conditions include an error over-limit threshold and an out-of-limit times threshold for identifying the event state of the out-of-tolerance event;
  • the determination of the real-time state identifier of the out-of-tolerance event of the dual-core smart meter based on the real-time error self-monitoring data, the current state identifier, and the preset out-of-tolerance event state identification conditions includes:
  • the real-time status identifier of the out-of-tolerance event of the dual-core smart meter is determined according to the total number of error overruns and the threshold of overruns.
  • the current state identifier includes an occurrence identifier and an end identifier
  • the determination of the total number of error overruns based on the real-time error self-monitoring data, the current state identifier and the error overrun threshold includes:
  • the current state identifier is an occurrence identifier, determine the total number of times of the first error overrun based on the real-time error self-monitoring data and the error overrun threshold;
  • the current state flag is an end flag, based on the real-time error self-monitoring data and the error overrun threshold, determine the second total number of error overruns.
  • determining the total number of first error overruns based on the real-time error self-monitoring data and the error overrun threshold including:
  • the current state flag is an occurrence flag, and the real-time error self-monitoring data is less than or equal to the error overrun threshold, perform an operation of adding one to the current accumulated first error overrun times to obtain the first error overrun total number of times;
  • the first total number of error overruns is set to zero.
  • determining the second total number of error overruns including:
  • the current state flag is an end flag, and the real-time error self-monitoring is greater than the error overrun threshold, perform an operation of adding one to the current accumulated second error overrun times to obtain the second total error overrun times;
  • the second total number of error overruns is set to zero.
  • determining the real-time status identifier of the out-of-tolerance event of the dual-core smart meter according to the total number of error overruns and the threshold of overruns includes:
  • the method before acquiring real-time error self-monitoring data from the metering unit of the dual-core smart meter, the method includes:
  • the dual-core smart meter is powered on and initialized, and the current state flag of the out-of-tolerance event is set as the end flag.
  • the management unit of the dual-core smart meter carries an event recording application
  • the method further includes:
  • the out-of-tolerance event corresponding to the recording of the real-time status identifier including:
  • the out-of-tolerance event corresponding to the real-time status identifier is recorded by the out-of-tolerance event recording thread.
  • a data acquisition module for acquiring real-time error self-monitoring data from the metering unit of the dual-core smart meter
  • the identification determination module is used to obtain the current state identification of the out-of-tolerance event of the dual-core smart meter, and based on the real-time error self-monitoring data, the current state identification and the preset out-of-tolerance event state identification conditions, determine the Real-time status identification of out-of-tolerance events of dual-core smart meters;
  • Out-of-tolerance event recording module for if the real-time status mark does not match with the current status mark, then replace the current status mark with the real-time status mark, and record the out-of-tolerance event corresponding to the real-time status mark .
  • a computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:
  • the current state identifier is replaced with the real-time state identifier, and the out-of-tolerance event corresponding to the real-time state identifier is recorded.
  • the current state identifier is replaced with the real-time state identifier, and the out-of-tolerance event corresponding to the real-time state identifier is recorded.
  • the above-mentioned method, device, computer equipment and storage medium for recording out-of-tolerance events of a dual-core smart meter through the management unit of the dual-core smart meter, obtain real-time error self-monitoring data from the measurement unit of the dual-core smart meter, and obtain the dual-core smart meter.
  • the real-time state identification of the out-of-tolerance event of the electric meter based on the real-time error self-monitoring data, the current state identification and the preset identification condition of the out-of-tolerance event, the real-time state identification of the out-of-tolerance event of the dual-core smart meter is determined, and the real-time state identification is further matched with the out-of-tolerance event.
  • the current state identifier is matched, and the current state identifier is replaced or maintained according to the matching result, so as to realize the accurate and real-time recording of out-of-tolerance events under the dual-core software architecture.
  • FIG. 1 is a block diagram of the internal structure of a dual-core smart meter in one embodiment
  • FIG. 2 is a schematic flowchart of a method for recording out-of-tolerance events of a dual-core smart meter in one embodiment
  • Fig. 3 is the schematic flow chart of the real-time state identification determination step of out-of-tolerance event in one embodiment
  • FIG. 4 is a schematic flowchart of a method for recording out-of-tolerance events of a dual-core smart meter in another embodiment
  • 5 is an overall architecture diagram of out-of-tolerance event recording of a dual-core smart meter in one embodiment
  • Fig. 6 is the realization flow chart of the out-of-tolerance event record of the dual-core smart meter in one embodiment
  • FIG. 7 is a structural block diagram of an out-of-tolerance event recording device of a dual-core smart meter in one embodiment
  • FIG. 8 is a diagram of the internal structure of a computer device in one embodiment.
  • the dual-core smart meter includes a management unit 102 (management core) and a metering unit 104 (measuring core), wherein the management unit 102 and the metering unit Unit 104 is communicatively connected.
  • the method for recording out-of-tolerance events of a dual-core smart meter provided by the present application can be applied to the application environment shown in FIG. 1 , and is specifically applied to the management unit 102 shown in FIG. 1 .
  • the measurement unit 104 can measure the error self-monitoring data in real time, and push the obtained real-time error self-monitoring data to the management unit 102, so that the management unit 102 can use the real-time error self-monitoring data and the out-of-tolerance dual-core smart meter
  • the current state identifier of the event and the preset out-of-tolerance event state identification conditions determine the real-time state identifier of the out-of-tolerance event of the dual-core smart meter.
  • the status is updated, and the out-of-tolerance events corresponding to the real-time status identification are recorded, so as to realize the accurate recording of out-of-tolerance events under the dual-core software architecture.
  • a method for recording out-of-tolerance events of a dual-core smart meter is provided, and the method is applied to the management unit 102 in FIG. 1 as an example for description, including the following steps:
  • Step S202 acquiring real-time error self-monitoring data from the metering unit of the dual-core smart meter.
  • the metering unit 104 of the dual-core smart meter is a unit for realizing the metering function.
  • the metering unit 104 can periodically push error self-monitoring data to the management unit 102 so that the management unit 102 can read the error self-monitoring data in real time.
  • the error self-monitoring data represents the running error value of the electric meter obtained by the metering unit 104 by monitoring the electric meter in real time.
  • Step S204 Obtain the current state identifier of the out-of-tolerance event of the dual-core smart meter, and determine the real-time state identifier of the out-of-tolerance event of the dual-core smart meter based on the real-time error self-monitoring data, the current state identifier, and the preset out-of-tolerance event state identification conditions.
  • an out-of-tolerance event can be understood as an event in which the number of error overruns is greater than the set threshold of overrun times, and the error overrun indicates that the error self-monitoring data exceeds the set error overrun threshold.
  • the current state identifier may be the state identifier stored in the management unit 102 at the last time point, the state identifier may include an occurrence state and an end state, and 0 and 1 may be used to represent the state identifier.
  • the flag 1 is used to indicate that an out-of-tolerance event currently occurs
  • the indicator of 0 is used to indicate that the current out-of-tolerance event has ended.
  • the real-time status identifier represents the status identifier of the out-of-tolerance event obtained by the management unit 102 in real time according to the real-time error self-monitoring data.
  • condition for identifying the status of the out-of-tolerance event includes an error-over-limit threshold and a threshold for over-limit times.
  • the error overrun threshold is used to compare with the error self-monitoring data to determine whether the error overrun occurs.
  • the threshold for the number of overruns is used to compare with the accumulated occurrences of error overruns to determine the real-time status identifier of the overrun event of the dual-core smart meter.
  • the current state identifier of the out-of-tolerance event of the dual-core smart meter after obtaining the current state identifier of the out-of-tolerance event of the dual-core smart meter, it can be determined whether an error over-limit has occurred currently based on the acquired real-time error self-monitoring data, the current state identifier and the preset error over-limit threshold. According to the judgment result and the current accumulated number of error overruns, determine the total number of error overruns, and compare the total number of error overruns with the threshold of overrun times to determine whether an overrun event occurs or ends, that is, to determine the real-time overrun of the overrun event. The state identifier is further matched with the real-time state identifier and the current state identifier to determine whether the current state identifier needs to be replaced and updated.
  • Step S206 if the real-time state identifier does not match the current state identifier, replace the current state identifier with the real-time state identifier, and record the out-of-tolerance event corresponding to the real-time state identifier.
  • the mismatch between the real-time state identifier and the current state identifier includes two situations: the current state identifier is the occurrence identifier (denoted as 1), but the real-time state identifier is determined by analyzing the real-time error self-monitoring data and related judgment parameters.
  • the real-time status mark is the occurrence mark (marked as 1)
  • the current state identifier matches the current state identifier, the current state identifier does not need to be replaced, and the current state identifier can be maintained, and the out-of-tolerance event corresponding to the real-time state identifier is recorded at the same time.
  • real-time error self-monitoring data is obtained from the measurement unit of the dual-core smart meter through the management unit of the dual-core smart meter, and the current state of the out-of-tolerance event of the dual-core smart meter is acquired.
  • the real-time state identification of the out-of-tolerance event of the dual-core smart meter is determined, and the real-time state identification and the current state identification are further matched.
  • the matching result replaces or maintains the current state identification, and realizes accurate and real-time recording of out-of-tolerance events under the dual-core software architecture.
  • the preset out-of-tolerance event state identification conditions include an error over-limit threshold and an over-limit times threshold for identifying the event state of the out-of-tolerance event; as shown in Figure 3, the above-mentioned step S204 specifically includes:
  • Step S302 based on the real-time error self-monitoring data, the current state identifier and the error overrun threshold, determine the total number of error overruns;
  • Step S304 Determine the real-time status identifier of the out-of-tolerance event of the dual-core smart meter according to the total number of error overruns and the threshold of overruns.
  • the total number of error overruns is the total number of overruns obtained according to the overrun determination result of the real-time error self-monitoring data and the current accumulated error overruns after determining whether the real-time error self-monitoring data exceeds the limit.
  • the implementation of determining whether the real-time error self-monitoring data exceeds the limit is to compare the real-time error self-monitoring data with the error over-limit threshold, and determine the over-limit result of the real-time error self-monitoring data based on the comparison result and the current state identifier, and the over-limit result Including adding one to the current accumulated error overrun times, or clearing the current accumulated error overrun times to zero, after obtaining the total error overrun times based on the overrun result, compare the total error overrun times with the threshold overrun times , according to the comparison result, determine the real-time status identification of the out-of-tolerance event of the dual-core smart meter.
  • the obtained total number of error overruns is associated with the current state identifier. , so that only the total number of error overruns that do not match the current state identifier can be counted. For example, if the current state identifier is occurrence, the counted number of error overruns is the number of error overruns that do not occur an overrun event, that is, to count real-time errors.
  • the self-monitoring data is less than or equal to the error overrun threshold, which greatly reduces the workload.
  • the dual core can be quickly determined. Whether the real-time status identifier of the out-of-tolerance event of the smart meter matches the current status identifier, and then it is determined whether the current status identifier needs to be updated.
  • the current state identification includes an occurrence identification and an end identification; the above-mentioned step S302 specifically includes: if the current state identification is an occurrence identification, based on the real-time error self-monitoring data and the error overrun threshold, determine the first total number of error overruns ; If the current state flag is the end flag, based on the real-time error self-monitoring data and the error overrun threshold, determine the second total number of error overruns.
  • the total number of times of the first error overrun is the total number of times used to determine whether to trigger the overrun event of the dual-core smart meter to turn to the end state.
  • the total number of times of the second error overrun is the total number of times used to determine whether to trigger the overrun event of the dual-core smart meter to turn into an occurrence state.
  • the current state identifier in order to directly determine whether the current state identifier needs to be updated, only the error overrun conditions that are opposite to the current state identifier can be counted. Therefore, after obtaining the real-time error self-monitoring data from the metering unit, it is necessary to combine the current state identifier to determine The corresponding total number of error overruns. Specifically, when the current state is identified as the occurrence of the identification, based on the real-time error self-monitoring data and the error overrun threshold, the determined total number of error overruns is recorded as the first total error overrun, which is used to compare the number of overruns.
  • the thresholds are compared to determine whether the out-of-tolerance event is over; when the current state is identified as the end indicator, based on the real-time error self-monitoring data and the error over-limit threshold, the determined total number of error over-limit times is recorded as the second error over-limit total number of times, using It is compared with the threshold for the number of overruns to determine whether an overrun event occurs.
  • the corresponding total error overrun times are respectively determined, so that the corresponding error overrun times and overruns are determined according to the corresponding total error overruns. Threshold of times to determine the real-time status flag of out-of-tolerance events.
  • the above-mentioned step of determining the total number of times of the first error overruns based on real-time error self-monitoring data and the error overrun threshold value if the current state indication is an occurrence indication specifically includes: if the current state indication is an occurrence indication, and The real-time error self-monitoring data is less than or equal to the error over-limit threshold, then the current accumulated first error over-limit times are added by one to obtain the first error over-limit total times; If the monitoring data is greater than the error overrun threshold, the total number of first error overruns is set to zero.
  • an out-of-tolerance event when the current state of the out-of-tolerance event of the dual-core smart meter is marked as an occurrence indicator, it means that the number of error overruns is greater than the set threshold of overrun times, and the error overrun indicates error self-monitoring The data is greater than the error overrun threshold. Therefore, when the current status indicator is an occurrence indicator, it is not necessary to obtain a situation where the real-time error self-monitoring data obtained by statistics is greater than the error overrun threshold, because in this case, the real-time status indicator is also an occurrence indicator, and there is no need to update the current status indicator. Alternatively, when the current state flag is the occurrence flag, and the real-time error self-monitoring data is greater than the error overrun threshold, the total number of times of the first error overrun can be set to zero.
  • a rule is provided for determining the total number of times of the first error exceeding the limit based on the comparison result between the real-time error self-monitoring data and the error overrun threshold when the current state is marked as the occurrence mark.
  • the total number of times of the first error overrun is set to zero, and the current status is marked as the occurrence mark, and the real-time error self-monitoring data is less than or equal to the error overrun threshold.
  • the above step of determining the total number of times the second error exceeds the limit based on the real-time error self-monitoring data and the error overrun threshold value if the current state sign is the end sign specifically includes: if the current state sign is the end sign, and If the real-time error self-monitoring data is greater than the error overrun threshold, add one to the current accumulated second error overrun times to obtain the total second error overrun times; When it is less than or equal to the error overrun threshold, the total number of times of the second error overrun is set to zero.
  • the current status of the out-of-tolerance event of the dual-core smart meter when marked as the end indicator, it means that the number of times of error overrun is less than or equal to the set threshold of overrun times, and the error overrun indicates that the error
  • the self-monitoring data is greater than the error overrun threshold. Therefore, when the current state flag is the end flag, it is not necessary to count the obtained real-time error self-monitoring data that is less than or equal to the error overrun threshold, because in this case, the real-time state flag is also the end flag, and there is no need to quantify the current state flag. Update and replace is performed, so when the current state flag is the end flag and the real-time error self-monitoring data is less than or equal to the error overrun threshold, the total number of second error overruns can be set to zero.
  • the rule for determining the total number of times of the second error overrun is provided.
  • the total number of second error overruns is set to zero; when the current state is marked as the end mark, and the real-time error self-monitoring data is greater than the error overrun threshold, Then add one to the current accumulated second error overrun times, so that only when the real-time error self-monitoring data is greater than the error overrun threshold for N consecutive occurrences of N times (N> error overrun times), will the current state be executed.
  • the identity is replaced with the action in which the identity occurred.
  • the above-mentioned step S304 specifically includes: when the total number of overruns of the first error is greater than the threshold of the number of overruns, determining that the real-time status indicator of the out-of-tolerance event of the dual-core smart meter is an end indicator; When the number of times is greater than the threshold for the number of overruns, it is determined that the real-time status indicator of the out-of-tolerance event of the dual-core smart meter is the occurrence indicator.
  • the first total number of error overruns is the total number of error overruns counted when the current state is marked as an occurrence mark, and the real-time error self-monitoring data is less than or equal to the error overrun threshold
  • the first error overrun When the total number of times is greater than the threshold of the number of overruns, the number of occurrences of the real-time error self-monitoring data less than or equal to the error overrun threshold is greater than the threshold of the number of overruns, indicating that the real-time error self-monitoring data obtained for N consecutive times (N> the number of error overruns) There is no error exceeding the limit, that is, no out-of-tolerance event occurs, so it can be determined that the real-time status indicator of the out-of-tolerance event of the dual-core smart meter is the end indicator.
  • the second total number of error overruns is the total number of error overruns counted when the current state is marked as the end mark, and the real-time error self-monitoring protective gear is greater than the error overrun threshold
  • the second total error overrun count is greater than the overrun
  • the limit number threshold the number of occurrences of the real-time error self-monitoring data greater than the error over-limit threshold is greater than the over-limit number threshold, indicating that the real-time error self-monitoring data obtained for N consecutive times (N> error over-limit times) have error over-limits.
  • an out-of-tolerance event will be triggered, so it can be determined that the real-time status of the out-of-tolerance event of the dual-core smart meter is identified as the occurrence indicator.
  • the real-time status identifier of the corresponding dual-core smart meter overrun event is provided, so as to facilitate the real-time status
  • the identifier is matched with the current state identifier to realize real-time update of the current state identifier.
  • the method before step S202, further includes: power-on initialization of the dual-core smart meter through the management unit 102, and setting the current state flag of the out-of-tolerance event as the end flag.
  • the management unit 102 can read the event state identifier of the out-of-tolerance event during power-down storage. If the read event state identifier is the occurrence identifier, the event state identifier needs to be forcibly set as The end flag of the out-of-tolerance event is used as the current state flag of the dual-core smart meter when it is powered on and initialized.
  • the management unit of the dual-core smart meter carries an event recording application; after the step of power-on initialization of the dual-core smart meter, the method further includes: creating an out-of-tolerance event through the main thread of the event recording application.
  • the above-mentioned steps of recording the out-of-tolerance events corresponding to the real-time status identifiers further include: recording the out-of-tolerance events corresponding to the real-time status identifiers through the out-of-tolerance event recording thread.
  • the event recording application is an application program used to perform certain actions or generate certain faults to record data during the operation of the dual-core smart meter.
  • the event recording application can be implemented in the management unit 102, interacts with the metering unit 104 and other applications in the management unit 102, and realizes the action recording of each module function of each meter application.
  • the main thread of the event recording application can create an event thread specially used for recording out-of-tolerance events through the main thread, that is, an out-of-tolerance event recording thread.
  • the management unit 102 can use the out-of-tolerance event recording thread to complete the out-of-tolerance event recording, instead of directly performing the out-of-tolerance event recording through the main thread.
  • the management unit can set the current state flag of the out-of-tolerance event as the end flag, so as to ensure the accurate operation of the out-of-tolerance event record after the dual-core smart meter is powered on and initialized.
  • this embodiment adopts the out-of-tolerance event recording thread created by the main thread of the event recording application to realize out-of-tolerance event recording, which can save program thread resources and optimize the out-of-tolerance event recording function.
  • a method for recording out-of-tolerance events of a dual-core smart meter is provided, which is applied to a management unit of a dual-core smart meter.
  • the method includes the following steps:
  • Step S402 acquiring real-time error self-monitoring data from the metering unit of the dual-core smart meter;
  • Step S404 obtaining the current state identifier of the out-of-tolerance event of the dual-core smart meter, and if the current state identifier is the occurrence identifier, determine the first total number of error overruns based on the real-time error self-monitoring data and the error overrun threshold;
  • Step S406 if the current state mark is the end mark, based on the real-time error self-monitoring data and the error overrun threshold, determine the second total number of error overruns;
  • Step S408 when the total number of overruns of the first error is greater than the threshold of overruns, it is determined that the real-time status indicator of the out-of-tolerance event of the dual-core smart meter is an end indicator;
  • Step S410 when the second total error overrun times is greater than the overrun times threshold, determine that the real-time status indicator of the out-of-tolerance event of the dual-core smart meter is the occurrence indicator;
  • Step S412 if the real-time state identifier does not match the current state identifier, replace the current state identifier with the real-time state identifier, and record the out-of-tolerance event corresponding to the real-time state identifier.
  • the real-time error self-monitoring data is obtained from the metering unit of the dual-core smart meter through the management unit of the dual-core smart meter, and after acquiring the current state identifier of the out-of-tolerance event of the dual-core smart meter, based on the real-time error self-monitoring
  • the data, the current state identifier and the preset out-of-tolerance event state identification conditions are used to determine the real-time state identifier of the out-of-tolerance event of the dual-core smart meter, further match the real-time state identifier with the current state identifier, and replace the current state identifier according to the matching result.
  • this method records out-of-tolerance events in real time and at the same time, adopts out-of-tolerance event recording thread created by the main thread of the event recording application to realize out-of-tolerance event recording, which can save program thread resources. , to optimize the recording function of out-of-tolerance events.
  • a method for realizing out-of-tolerance event recording of a dual-core smart electric meter is also provided, and the error self-monitoring out-of-tolerance event belongs to the application layer event recording function of the software system of the electric energy meter management unit.
  • the main functions of error self-monitoring over-tolerance event recording are: when the error self-monitoring value of the electric energy meter is higher than the error over-limit threshold, and the total number of error over-limit times exceeds the over-limit times threshold, it is recorded as an error self-monitoring over-tolerance event, which can be recorded recently. 10 error self-monitoring out-of-tolerance events.
  • FIG. 5 it is the overall architecture diagram of the error self-monitoring out-of-tolerance event recording, which is mainly to obtain real-time data in the shared memory every second, according to the error self-monitoring value in the real-time data, and then according to the error overrun threshold set by the communication module and error over-limit judgment times, to judge and record error self-monitoring over-tolerance events.
  • the communication module is responsible for parsing the control code and data identification, and calling the read and write operation interface provided by the event recording module.
  • error over-limit judgment threshold ie, error over-limit threshold
  • error over-limit judgment times That is, the threshold for the number of overruns.
  • error overrun judgment threshold ie error overrun threshold
  • error overrun judgment times ie overrun times threshold
  • Event recording module total event recording clearing, error self-monitoring out-of-tolerance event sub-item clearing.
  • FIG. 6 it is a flow chart for realizing the error self-monitoring out-of-tolerance event recording of the dual-core smart meter management unit.
  • the specific steps include:
  • Step 1 after the electric energy meter is powered on, the main thread creates an event recording thread
  • Step 2 After the event record thread is started, first determine and create a working directory, and then initialize the relevant parameters of the event record (mainly the threshold and initial state of each event, etc.)
  • Step 3 wait for the signal that the time-sharing metering module has been running normally (it is necessary to ensure that the real-time data used is accurate and effective when performing event recording processing);
  • Step 4 After obtaining the message that the time-sharing metering has been running normally, create a timer task (start with a delay of 1 second, the timer period is 1 second, and the timer task sends a message to the event recording thread every second), and send the second task. message and wait;
  • Step 5 the event recording thread obtains the error self-monitoring data in the shared memory of the metering management service every second;
  • Step 6 Compare the pushed error self-monitoring data with the set out-of-tolerance event state identification condition, determine whether the number of determinations (ie, the threshold of out-of-limit times) is exceeded, and determine and process the event record.
  • the management unit When the meter is powered on and initialized, first clear the event status word (that is, the current status flag), that is, record the current status word as 0, indicating that the out-of-tolerance event is over. In normal operation, the management unit first reads the error over-limit threshold and the over-limit times threshold per second, and reads the status word of the error self-monitoring over-tolerance event.
  • the event status word that is, the current status flag
  • the read error self-monitoring data is lower than the error overrun threshold, and the current accumulated first error overrun times are incremented by 1. Otherwise, the error overrun times are cleared to zero, and the first error is obtained. The total number of overruns.
  • the first error overrun times is greater than the judgment times (ie, the overrun times threshold)
  • the error overrun event is recorded as over, the write event ends, and the status word is set to 0.
  • the read error self-monitoring data exceeds the error overrun threshold, add 1 to the current accumulated second error overrun times, or clear the error overrun times to get the second error The total number of overruns.
  • the total number of times of the second error overrun is greater than the number of judgments (that is, the threshold of overrun times)
  • record the occurrence of error self-monitoring out-of-tolerance events increase the total number of error self-monitoring out-of-tolerance events by 1, set the current status word to 1 and Actively report the status word.
  • the above-mentioned error self-monitoring out-of-tolerance event record adopts the method of creating an event recording thread, and can read the event status word to judge and count the number of error over-limit times.
  • the error self-monitoring data is processed, and the event record is processed.
  • the method for realizing the error self-monitoring and out-of-tolerance event recording of the present application is to obtain the real-time data pushed by the metering management service when the electric meter management unit is running, according to the error self-monitoring value in the real-time data, and then according to the Through the threshold value set by the communication module and the number of error over-limit determinations, the error self-monitoring over-tolerance events are judged and recorded.
  • the implementation method of the management unit event record is adopted, that is, the recorded data is stored in the management unit through the event thread.
  • the event record application is created by the main thread after the meter is powered on, and the error self-monitoring out-of-tolerance event record is created by the sub-thread for statistics, and the timer task is created to record the event by judging the signals of the time-sharing metering and other modules. Save program thread resources.
  • the event is judged and processed according to the error over-limit judgment threshold and the number of error over-limit judgments to ensure the accuracy and real-time of the results.
  • steps in the above flow charts are displayed in sequence according to the arrows, these steps are not necessarily executed in the sequence indicated by the arrows. Unless explicitly stated herein, the execution of these steps is not strictly limited to the order, and these steps may be performed in other orders. Moreover, at least a part of the steps in the above flow chart may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same time, but may be executed at different times. The execution sequence of these steps or stages It is also not necessarily performed sequentially, but may be performed alternately or alternately with other steps or at least a portion of a step or phase within the other steps.
  • an out-of-tolerance event recording device for a dual-core smart meter including: a data acquisition module 702, an identification determination module 704, and an out-of-tolerance event recording module 706, wherein:
  • a data acquisition module 702 configured to acquire real-time error self-monitoring data from the metering unit of the dual-core smart meter;
  • the identification determination module 704 is used to obtain the current state identification of the out-of-tolerance event of the dual-core smart meter, and based on the real-time error self-monitoring data, the current state identification and the preset identification condition of the out-of-tolerance event, determine the out-of-tolerance event of the dual-core smart meter real-time status identification;
  • the out-of-tolerance event recording module 706 is configured to replace the current state identifier with the real-time state identifier if the real-time state identifier does not match the current state identifier, and record the out-of-tolerance event corresponding to the real-time state identifier.
  • the preset out-of-tolerance event state identification conditions include an error over-limit threshold and an over-limit times threshold for identifying the event state of an out-of-tolerance event; the above-mentioned identification determination module 704 specifically includes:
  • the number of times determination sub-module is used to determine the total number of error overruns based on the real-time error self-monitoring data, the current state identifier and the error overrun threshold;
  • the identification determination sub-module is used to determine the real-time status identification of the over-tolerance event of the dual-core smart meter according to the total number of error overruns and the threshold of overruns.
  • the current state indicator includes an occurrence indicator and an end indicator; the above-mentioned number of times determination submodule is specifically configured to, if the current state indicator is an occurrence indicator, based on real-time error self-monitoring data and an error overrun threshold, determine that the first error exceeds the limit value. The total number of times of the limit is determined; if the current state flag is the end flag, based on the real-time error self-monitoring data and the error over-limit threshold, the second total number of error over-limit times is determined.
  • the above-mentioned number of times determination sub-module is further configured to execute the addition of the current accumulated first error over-limit times if the current state flag is the occurrence flag and the real-time error self-monitoring data is less than or equal to the error over-limit threshold.
  • the first total number of error overruns is obtained; if the current status flag is an occurrence flag and the real-time error self-monitoring data is greater than the error overrun threshold, the first total number of error overruns is set to zero.
  • the above-mentioned number of times determination sub-module is further configured to perform an operation of adding one to the current accumulated second error over-limit times if the current state flag is the end flag and the real-time error self-monitoring data is greater than the error over-limit threshold , to obtain the second total number of error overruns; if the current state flag is the end flag and the real-time error self-monitoring data is less than or equal to the error overrun threshold, the second total number of error overruns is set to zero.
  • the above-mentioned identification determination sub-module is specifically configured to determine the real-time status identification of the out-of-tolerance event of the dual-core smart meter as the end identification when the total number of overruns of the first error is greater than the threshold of overruns; When the total number of overruns is greater than the threshold of overruns, it is determined that the real-time status indicator of the out-of-tolerance event of the dual-core smart meter is the occurrence indicator.
  • the above-mentioned apparatus further includes an initialization module, configured to power on the dual-core smart meter and initialize it, and set the current state flag of the out-of-tolerance event as the end flag.
  • the management unit of the dual-core smart meter carries an event recording application; the above device also includes a thread creation module for creating an out-of-tolerance event recording thread for recording out-of-tolerance events through the main thread of the event recording application;
  • the above-mentioned out-of-tolerance event recording module 706 is further configured to record out-of-tolerance events corresponding to the real-time status identifiers through an out-of-tolerance event recording thread.
  • out-of-tolerance event recording device of the dual-core smart meter of the present application corresponds to the out-of-tolerance event recording method of the dual-core smart meter of the present application.
  • the technical features and beneficial effects described in the examples are applicable to the embodiments of the out-of-tolerance event recording device of the dual-core smart meter.
  • each module in the above-mentioned out-of-tolerance event recording device of the dual-core smart meter can be implemented in whole or in part by software, hardware, and combinations thereof.
  • the above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.
  • a computer device is provided, and the computer device may be a terminal, and its internal structure diagram may be as shown in FIG. 8 .
  • the computer equipment includes a processor, memory, a communication interface, a display screen, and an input device connected by a system bus.
  • the processor of the computer device is used to provide computing and control capabilities.
  • the memory of the computer device includes a non-volatile storage medium, an internal memory.
  • the nonvolatile storage medium stores an operating system and a computer program.
  • the internal memory provides an environment for the execution of the operating system and computer programs in the non-volatile storage medium.
  • the communication interface of the computer device is used for wired or wireless communication with an external terminal, and the wireless communication can be realized by WIFI, operator network, NFC (Near Field Communication) or other technologies.
  • WIFI Wireless Fidelity
  • NFC Near Field Communication
  • the computer program is executed by the processor, a method for recording out-of-tolerance events of a dual-core smart meter is realized.
  • the display screen of the computer equipment may be a liquid crystal display screen or an electronic ink display screen
  • the input device of the computer equipment may be a touch layer covered on the display screen, or a button, a trackball or a touchpad set on the shell of the computer equipment , or an external keyboard, trackpad, or mouse.
  • FIG. 8 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied. Include more or fewer components than shown in the figures, or combine certain components, or have a different arrangement of components.
  • a computer device including a memory and a processor, where a computer program is stored in the memory, and the processor implements the steps in the foregoing method embodiments when the processor executes the computer program.
  • a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements the steps in the foregoing method embodiments.
  • Non-volatile memory may include read-only memory (Read-Only Memory, ROM), magnetic tape, floppy disk, flash memory, or optical memory, and the like.
  • Volatile memory may include random access memory (RAM) or external cache memory.
  • the RAM may be in various forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Remote Monitoring And Control Of Power-Distribution Networks (AREA)
  • Debugging And Monitoring (AREA)
  • Arrangements For Transmission Of Measured Signals (AREA)

Abstract

一种双芯智能电表的超差事件记录方法、装置和计算机设备。超差事件记录方法包括：从双芯智能电表的计量单元中获取实时误差自监测数据(S202，S402)；获取双芯智能电表超差事件的当前状态标识，并基于实时误差自监测数据、当前状态标识和预设的超差事件状态识别条件，确定双芯智能电表超差事件的实时状态标识(S204)；若实时状态标识与当前状态标识不匹配，则将当前状态标识替换为实时状态标识，并记录实时状态标识对应的超差事件(S206，S412)。超差事件记录方法能够实现双芯软件架构下，对超差事件的准确、实时的记录。

Description

双芯智能电表的超差事件记录方法、装置和计算机设备 技术领域
本申请涉及电能计量技术领域，特别是涉及一种双芯智能电表的超差事件记录方法、装置、计算机设备和存储介质。
背景技术
目前，我国电能表为一体式设计，即计量部分和非计量部分不做独立工作要求。这种电能表软件系统比较固化，且与硬件平台强耦合，不满足电表运行过程中需要实时监测电表运行误差状态的需求，且一体化的电能表在进行误差自监测时，容易造成误差超差影响电表正常计量功能。因此一体化设计智能电表已无法满足日益复杂多变的计量需求。
基于此，新一代双芯智能电表应运而生，新一代双芯智能电表采用两块芯片，即管理芯和计量芯独立运行，相互隔离的结构，可由计量芯负责表计的计量功能，管理芯负责扩展功能，由此，由管理芯进行误差自监测时，将不会影响计量芯的正常计量功能。然而，由于目前对电表的超差事件记录都是基于一体化设计智能电表，而对于双芯智能电表，目前针对电表的超差事件记录方法无法适用，无法实现对双芯智能电表的电压事件的准确记录。
发明内容
基于此，有必要针对上述技术问题，提供一种双芯智能电表的超差事件记录方法、装置、计算机设备和存储介质。
一种双芯智能电表的超差事件记录方法，应用于所述双芯智能电表的管理单元，所述方法包括：
从所述双芯智能电表的计量单元中获取实时误差自监测数据；
获取所述双芯智能电表超差事件的当前状态标识，并基于所述实时误差自监测数据、所述当前状态标识和预设的超差事件状态识别条件，确定所述双芯智能电表超差事件的实时状态标识；
若所述实时状态标识与所述当前状态标识不匹配，则将所述当前状态标识替换为所述实时状态标识，并记录所述实时状态标识对应的超差事件。
在其中一个实施例中，所述预设的超差事件状态识别条件包括用于识别超差事件的事件状态的误差超限阈值和超限次数阈值；
所述基于所述实时误差自监测数据、所述当前状态标识和预设的超差事件状态识别条件，确定所述双芯智能电表超差事件的实时状态标识，包括：
基于所述实时误差自监测数据、所述当前状态标识和所述误差超限阈值，确定误差超限总次数；
根据所述误差超限总次数和所述超限次数阈值，确定所述双芯智能电表超差事件的实时状态标识。
在其中一个实施例中，所述当前状态标识包括发生标识和结束标识；
所述基于所述实时误差自监测数据、所述当前状态标识和所述误差超限阈值，确定误差超限总次数，包括：
若所述当前状态标识为发生标识，基于所述实时误差自监测数据和所述误差超限阈值，确定第一误差超限总次数；
若所述当前状态标识为结束标识，基于所述实时误差自监测数据和所述误差超限阈值，确定第二误差超限总次数。
在其中一个实施例中，所述若所述当前状态标识为发生标识，基于所述实时误差自监测数据和所述误差超限阈值，确定第一误差超限总次数，包括：
若所述当前状态标识为发生标识，且所述实时误差自监测数据小于或等于所述误差超限阈值，则将当前累计的第一误差超限次数执行加一操作，得到第一误差超限总次数；
若所述当前状态标识为发生标识，且所述实时误差自监测数据大于所述误差超限阈值，则将第一误差超限总次数置为零。
在其中一个实施例中，所述若所述当前状态标识为结束标识，基于所述实时误差自监测数据和所述误差超限阈值，确定第二误差超限总次数，包括：
若所述当前状态标识为结束标识，且所述实时误差自监测大于所述误差超限阈值，则将当前累计的第二误差超限次数执行加一操作，得到第二误差超限总次数；
若所述当前状态标识为结束标识，且所述实时误差自监测小于或等于所述误差超限阈值时，则将第二误差超限总次数置为零。
在其中一个实施例中，所述根据所述误差超限总次数和所述超限次数阈值，确定所述双芯智能电表超差事件的实时状态标识，包括：
当第一误差超限总次数大于所述超限次数阈值时，确定所述双芯智能电表超差事件的实时状态标识为结束标识；
当第二误差超限总次数大于所述超限次数阈值时，确定所述双芯智能电表超差事件的实时状态标识为 发生标识。
在其中一个实施例中，在从所述双芯智能电表的计量单元中获取实时误差自监测数据之前，包括：
对所述双芯智能电表进行上电初始化，并将所述超差事件的当前状态标识设定为结束标识。
在其中一个实施例中，所述双芯智能电表的管理单元携带有事件记录应用；
在对所述双芯智能电表进行上电初始化之后，还包括：
通过所述事件记录应用的主线程创建用于记录超差事件的超差事件记录线程；
所述记录所述实时状态标识对应的超差事件，包括：
通过所述超差事件记录线程记录所述实时状态标识对应的超差事件。
一种双芯智能电表的超差事件记录装置，应用于所述双芯智能电表的管理单元，所述装置包括：
数据获取模块，用于从所述双芯智能电表的计量单元中获取实时误差自监测数据；
标识确定模块，用于获取所述双芯智能电表超差事件的当前状态标识，并基于所述实时误差自监测数据、所述当前状态标识和预设的超差事件状态识别条件，确定所述双芯智能电表超差事件的实时状态标识；
超差事件记录模块，用于若所述实时状态标识与所述当前状态标识不匹配，则将所述当前状态标识替换为所述实时状态标识，并记录所述实时状态标识对应的超差事件。
一种计算机设备，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器执行所述计算机程序时实现以下步骤：
从所述双芯智能电表的计量单元中获取实时误差自监测数据；
获取所述双芯智能电表超差事件的当前状态标识，并基于所述实时误差自监测数据、所述当前状态标识和预设的超差事件状态识别条件，确定所述双芯智能电表超差事件的实时状态标识；
若所述实时状态标识与所述当前状态标识不匹配，则将所述当前状态标识替换为所述实时状态标识，并记录所述实时状态标识对应的超差事件。
一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现以下步骤：
从所述双芯智能电表的计量单元中获取实时误差自监测数据；
获取所述双芯智能电表超差事件的当前状态标识，并基于所述实时误差自监测数据、所述当前状态标识和预设的超差事件状态识别条件，确定所述双芯智能电表超差事件的实时状态标识；
若所述实时状态标识与所述当前状态标识不匹配，则将所述当前状态标识替换为所述实时状态标识，并记录所述实时状态标识对应的超差事件。
上述双芯智能电表的超差事件记录方法、装置、计算机设备和存储介质，通过双芯智能电表的管理单元，从双芯智能电表的计量单元中获取实时误差自监测数据，在获取双芯智能电表超差事件的当前状态标识后，基于实时误差自监测数据、当前状态标识和预设的超差事件状态识别条件，确定双芯智能电表超差事件的实时状态标识，进一步将实时状态标识与当前状态标识进行匹配，根据匹配结果对当前状态标识进行替换或维持，实现了在双芯软件架构下，对超差事件的准确实时的记录。
附图说明
图1为一个实施例中双芯智能电表的内部结构框图；
图2为一个实施例中双芯智能电表的超差事件记录方法的流程示意图；
图3为一个实施例中超差事件的实时状态标识确定步骤的流程示意图；
图4为另一个实施例中双芯智能电表的超差事件记录方法的流程示意图；
图5为一个实施例中双芯智能电表的超差事件记录的总体架构图；
图6为一个实施例中双芯智能电表的超差事件记录的实现流程图；
图7为一个实施例中双芯智能电表的超差事件记录装置的结构框图；
图8为一个实施例中计算机设备的内部结构图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
在一个实施例中，如图1所示，为双芯智能电表的内部结构框图，双芯智能电表包括管理单元102(管理芯)和计量单元104(计量芯)，其中，管理单元102与计量单元104通信连接。本申请提供的双芯智能电表的超差事件记录方法，可以应用于如图1所示的应用环境中，具体应用于图1所示的管理单元102。具体地，计量单元104可以实时对误差自监测数据进行计量，并将得到的实时误差自监测数据推送给管理单元102，使管理单元102可基于实时误差自监测数据，以及双芯智能电表超差事件的当前状态标识和预设的超差事件状态识别条件，确定双芯智能电表超差事件的实时状态标识，根据实时状态标识与当前状态标识的匹配结果，实现对状态标识的实时更新以供状态更新，并记录实时状态标识对应的超差事件，从而 实现在双芯软件架构下，对超差事件的准确记录。
在一个实施例中，如图2所示，提供了一种双芯智能电表的超差事件记录方法，以该方法应用于图1中的管理单元102为例进行说明，包括以下步骤：
步骤S202，从双芯智能电表的计量单元中获取实时误差自监测数据。
其中，双芯智能电表的计量单元104为用于实现电表计量功能的单元，计量单元104可定时向管理单元102推送误差自监测数据，使管理单元102可实时读取误差自监测数据。
其中，误差自监测数据表示计量单元104通过对电表进行实时监控得到的电表的运行误差值。
步骤S204，获取双芯智能电表超差事件的当前状态标识，基于实时误差自监测数据、当前状态标识和预设的超差事件状态识别条件，确定双芯智能电表超差事件的实时状态标识。
其中，超差事件可理解为误差超限的次数大于设定的超限次数阈值的事件，误差超限表示误差自监测数据超出了设定的误差超限阈值。
其中，当前状态标识可以为上一时间点存储于管理单元102的状态标识，状态标识可包括发生状态和结束状态，并可用0和1表示状态标识。例如，用标识1表示当前发生了超差事件，用标识0表示当前超差事件已结束。
其中，实时状态标识表示管理单元102根据实时误差自监测数据实时得到的超差事件的状态标识。
其中，超差事件状态识别条件包括误差超限阈值和超限次数阈值。
其中，误差超限阈值用于与误差自监测数据进行比对，确定是否发生误差超限。
其中，超限次数阈值用于与累计的误差超限的发生次数进行比对，确定双芯智能电表超差事件的实时状态标识。
具体实现中，在获取双芯智能电表超差事件的当前状态标识后，可基于获取的实时误差自监测数据、当前状态标识和预设的误差超限阈值，判定当前是否发生了误差超限，根据判定结果和当前累计的误差超限次数，确定误差超限总次数，并将误差超限总次数与超限次数阈值进行对比，确定超差事件是发生还是结束，即确定超差事件的实时状态标识，进一步将实时状态标识与当前状态标识进行匹配，确定是否需要对当前状态标识进行替换更新。
步骤S206，若实时状态标识与当前状态标识不匹配，则将当前状态标识替换为实时状态标识，并记录实时状态标识对应的超差事件。
具体实现中，实时状态标识与当前状态标识不匹配包括有两种情况：当前状态标识为发生标识(记为1)，但通过对实时误差自监测数据与相关判定参数的分析，确定实时状态标识为结束标识(记为0)；或者 当前状态标识为结束标识(记为0)，但通过对实时误差自监测数据与相关判定参数的分析，确定实时状态标识为发生标识(记为1)，这两种情况下，则需将双芯智能电表当前状态标识替换为实时状态标识，并记录实时状态标识对应的超差事件，实现对超差事件状态的实时更新，便于根据实时状态标识确定当前的超差事件状态。反之，若实时状态标识与当前状态标识相匹配，则无需将当前状态标识进行替换，继续保持当前状态标识即可，同时记录实时状态标识对应的超差事件。
上述双芯智能电表的超差事件记录方法中，通过双芯智能电表的管理单元，从双芯智能电表的计量单元中获取实时误差自监测数据，在获取双芯智能电表超差事件的当前状态标识后，基于实时误差自监测数据、当前状态标识和预设的超差事件状态识别条件，确定双芯智能电表超差事件的实时状态标识，进一步将实时状态标识与当前状态标识进行匹配，根据匹配结果对当前状态标识进行替换或维持，实现了在双芯软件架构下，对超差事件的准确实时的记录。
在一个实施例中，预设的超差事件状态识别条件包括用于识别超差事件的事件状态的误差超限阈值和超限次数阈值；如图3所示，上述步骤S204具体包括：
步骤S302，基于实时误差自监测数据、当前状态标识和误差超限阈值，确定误差超限总次数；
步骤S304，根据误差超限总次数和超限次数阈值，确定双芯智能电表超差事件的实时状态标识。
具体地，误差超限总次数为在判定实时误差自监测数据是否超限后，根据实时误差自监测数据的超限判定结果与当前累计的误差超限次数，得到的超限总次数。其中，判定实时误差自监测数据是否超限的实施方式是将实时误差自监测数据与误差超限阈值进行对比，基于对比结果和当前状态标识确定实时误差自监测数据的超限结果，超限结果包括将当前累计的误差超限次数加一，或者将当前累计的误差超限次数清零，在根据超限结果得到误差超限总次数后，将误差超限总次数与超限次数阈值进行对比，根据对比结果确定双芯智能电表超差事件的实时状态标识。
本实施例中，通过将实时误差自监测数据和超限次数阈值的对比结果，与双芯智能电表超差事件的当前状态标识结合，使得所得到的误差超限总次数与当前状态标识相关联，以便于可仅统计与当前状态标识不相符的误差超限总次数，例如，当前状态标识为发生，则统计的误差超限次数为不发生超差事件的误差超限次数，即统计实时误差自监测数据小于或等于误差超限阈值的超限次数，极大地减少了工作量，进一步可根据统计的与当前状态标识相反的误差超限总次数与超限次数阈值的对比，快速确定双芯智能电表超差事件的实时状态标识与当前状态标识是否匹配，进而确定是否需要对当前状态标识进行更新。
在一个实施例中，当前状态标识包括发生标识和结束标识；上述步骤S302具体包括：若当前状态标识为发生标识，基于实时误差自监测数据和误差超限阈值，确定第一误差超限总次数；若当前状态标识为结束标识，基于实时误差自监测数据和误差超限阈值，确定第二误差超限总次数。
其中，第一误差超限总次数为用于确定是否触发双芯智能电表的超差事件转为结束状态的总次数。
其中，第二误差超限总次数为用于确定是否触发双芯智能电表的超差事件转为发生状态的总次数。
具体地，为了便于直接确定是否需要对当前状态标识进行更新，可仅统计与当前状态标识相反的误差超限情况，故在从计量单元获取实时误差自监测数据后，需结合当前状态标识，确定对应的误差超限总次数。具体来说，可分别将当前状态标识为发生标识时，基于实时误差自监测数据和误差超限阈值，确定的误差超限总次数记为第一误差超限总次数，用于与超限次数阈值进行对比，确定超差事件是否结束；将当前状态标识为结束标识时，基于实时误差自监测数据和误差超限阈值，确定的误差超限总次数记为第二误差超限总次数，用于与超限次数阈值进行对比，确定超差事件是否发生。
本实施例中，通过在不同的当前状态标识下，基于实时误差自监测数据和误差超限阈值，分别确定对应的误差超限总次数，以便于根据该对应的误差超限总次数和超限次数阈值，确定超差事件的实时状态标识。
在一个实施例中，上述若当前状态标识为发生标识，基于实时误差自监测数据和误差超限阈值，确定第一误差超限总次数的步骤，具体包括：若当前状态标识为发生标识，且实时误差自监测数据小于或等于误差超限阈值，则将当前累计的第一误差超限次数执行加一操作，得到第一误差超限总次数；若当前状态标识为发生标识，且实时误差自监测数据大于误差超限阈值，则将第一误差超限总次数置为零。
具体地，基于超差事件的定义，在双芯智能电表超差事件的当前状态标识为发生标识时，说明误差超限的次数大于设定的超限次数阈值，而误差超限表示误差自监测数据大于误差超限阈值。因此，在当前状态标识为发生标识时，则无需统计获取的实时误差自监测数据大于误差超限阈值的情况，因为这种情况下，实时状态标识也为发生标识，无需对当前状态标识进行更新替换，故可在当前状态标识为发生标识，且实时误差自监测数据大于误差超限阈值时，将第一误差超限总次数置为零。
本实施例中，提供了在当前状态标识为发生标识时，基于实时误差自监测数据与误差超限阈值不同的对比结果，确定第一误差超限总次数的规则，通过在当前状态标识为发生标识，且实时误差自监测数据大于误差超限阈值时，则将第一误差超限总次数置为零，在当前状态标识为发生标识，且实时误差自监测数据小于或等于误差超限阈值时，则将当前累计的第一误差超限次数执行加一操作，使得只有在连续发生N 次(N>误差超限次数)实时误差自监测数据小于或等于误差超限阈值的情况下，才执行将当前状态标识替换为结束标识的操作。
在一个实施例中，上述若当前状态标识为结束标识，基于实时误差自监测数据和误差超限阈值，确定第二误差超限总次数的步骤，具体包括：若当前状态标识为结束标识，且实时误差自监测数据大于误差超限阈值，则将当前累计的第二误差超限次数执行加一操作，得到第二误差超限总次数；若当前状态标识为结束标识，且实时误差自监测数据小于或等于误差超限阈值时，则将第二误差超限总次数置为零。
具体地，与前一实施例类似，在双芯智能电表超差事件的当前状态标识为结束标识时，说明误差超限的次数小于或等于设定的超限次数阈值，而误差超限表示误差自监测数据大于误差超限阈值。因此，在当前状态标识为结束标识时，则无需统计获取的实时误差自监测数据小于或等于误差超限阈值的情况，因为这种情况下，实时状态标识也为结束标识，无需对当前状态标识进行更新替换，故可在当前状态标识为结束标识，且实时误差自监测数据小于或等于误差超限阈值时，将第二误差超限总次数置为零。
本实施例中，提供了在当前状态标识为结束标识时，基于实时误差自监测数据与误差超限阈值不同的对比结果，确定第二误差超限总次数的规则，通过在当前状态标识为结束标识，且实时误差自监测数据小于或等于误差超限阈值时，将第二误差超限总次数置为零；在当前状态标识为结束标识，且实时误差自监测数据大于误差超限阈值时，则将当前累计的第二误差超限次数执行加一操作，使得只有在连续发生N次(N>误差超限次数)实时误差自监测数据大于误差超限阈值的情况下，才执行将当前状态标识替换为发生标识的操作。
在一个实施例中，上述步骤S304具体包括：当第一误差超限总次数大于超限次数阈值时，确定双芯智能电表超差事件的实时状态标识为结束标识；当第二误差超限总次数大于超限次数阈值时，确定双芯智能电表超差事件的实时状态标识为发生标识。
具体地，由于第一误差超限总次数为在当前状态标识为发生标识，且实时误差自监测数据小于或等于误差超限阈值时所统计的误差超限总次数，因此，第一误差超限总次数大于超限次数阈值的情况为实时误差自监测数据小于或等于误差超限阈值的发生次数大于超限次数阈值，表明连续N次(N>误差超限次数)获取的实时误差自监测数据都未发生误差超限，也即不会发生超差事件，故可确定双芯智能电表超差事件的实时状态标识为结束标识。
由于第二误差超限总次数为在当前状态标识为结束标识，且实时误差自监测护具大于误差超限阈值时 所统计的误差超限总次数，因此，第二误差超限总次数大于超限次数阈值的情况为实时误差自监测数据大于误差超限阈值的发生次数大于超限次数阈值，表明连续N次(N>误差超限次数)获取的实时误差自监测数据都发生了误差超限，将会触发超差事件，故可确定双芯智能电表超差事件的实时状态标识为发生标识。
本实施例中，提供了第一误差超限总次数和第二误差超限总次数分别大于超限次数阈值时，对应的双芯智能电表超差事件的实时状态标识，以便于将该实时状态标识与当前状态标识进行匹配，实现对当前状态标识的实时更新。
在一个实施例中，在步骤S202之前，还包括：通过管理单元102对双芯智能电表进行上电初始化，并将超差事件的当前状态标识设定为结束标识。
具体地，在电表进行上电初始化时，管理单元102可以读取掉电保存时超差事件的事件状态标识，若读取的事件状态标识为发生标识，则需要将该事件状态标识强制设置为超差事件的结束标识，作为双芯智能电表在上电初始化时的当前状态标识。
在一个实施例中，双芯智能电表的管理单元携带有事件记录应用；在对双芯智能电表进行上电初始化的步骤之后，还包括：通过事件记录应用的主线程创建用于记录超差事件的超差事件记录线程；上述记录实时状态标识对应的超差事件的步骤，还包括：通过超差事件记录线程记录实时状态标识对应的超差事件。
其中，事件记录应用是用于在双芯智能电表的运行过程中，执行某种动作或者产生某些故障而进行数据记录的应用程序。事件记录应用可以在管理单元102中实现，与计量单元104和以及管理单元102的其他应用产生交互，实现各电表应用的各个模块功能的动作记录。管理单元102对双芯智能电表进行上电初始化之后，事件记录应用的主线程可以通过主线程创建用于专门用于记录超差事件的事件线程，即超差事件记录线程，在需要对超差事件进行记录时，管理单元102则可以利用超差事件记录线程完成超差事件的记录，而不是通过主线程直接执行超差事件的记录。
上述实施例中，在双芯智能电表上电初始化后，管理单元可以将超差事件的当前状态标识设定为结束标识，从而可以保证双芯智能电表上电初始化后超差事件记录的准确运行，同时本实施例采取由事件记录应用的主线程创建的超差事件记录线程实现超差事件记录，可以节省程序线程资源，优化超差事件的记录功能。
在另一个实施例中，如图4所示，提供了一种双芯智能电表的超差事件记录方法，应用于双芯智能电 表的管理单元，本实施例中，该方法包括以下步骤：
步骤S402，从双芯智能电表的计量单元中获取实时误差自监测数据；
步骤S404，获取双芯智能电表超差事件的当前状态标识，若当前状态标识为发生标识，基于实时误差自监测数据和误差超限阈值，确定第一误差超限总次数；
步骤S406，若当前状态标识为结束标识，基于实时误差自监测数据和误差超限阈值，确定第二误差超限总次数；
步骤S408，当第一误差超限总次数大于超限次数阈值时，确定双芯智能电表超差事件的实时状态标识为结束标识；
步骤S410，当第二误差超限总次数大于超限次数阈值时，确定双芯智能电表超差事件的实时状态标识为发生标识；
步骤S412，若实时状态标识与当前状态标识不匹配，则将当前状态标识替换为实时状态标识，并记录实时状态标识对应的超差事件。
本实施例中，通过双芯智能电表的管理单元，从双芯智能电表的计量单元中获取实时误差自监测数据，在获取双芯智能电表超差事件的当前状态标识后，基于实时误差自监测数据、当前状态标识和预设的超差事件状态识别条件，确定双芯智能电表超差事件的实时状态标识，进一步将实时状态标识与当前状态标识进行匹配，根据匹配结果对当前状态标识进行替换或维持，该方法在双芯软件架构下，对超差事件的实时准确的记录的同时，采取由事件记录应用的主线程创建的超差事件记录线程实现超差事件记录，可以节省程序线程资源，优化超差事件的记录功能。
在一个应用实施例中，还提供了一种双芯智能电表的超差事件记录的实现方法，误差自监测超差事件属于电能表管理单元软件系统应用层事件记录功能。误差自监测超差事件记录的主要功能有：当电能表误差自监测值高于误差超限阈值，误差超限总次数超过超限次数阈值时，记录为误差自监测超差事件，可最近记录10次误差自监测超差事件。
参考图5，为误差自监测超差事件记录的总体架构图，主要为每秒获取共享内存里的实时数据，根据实时数据里的误差自监测值，再根据通过通信模块设置的误差超限阈值和误差超限判定次数，进行误差自监测超差事件的判断和记录。如图5所示，基础功能应用中，通信模块负责解析控制码和数据标识，调用事件记录模块提供的读写操作接口。
读取：误差自监测超差事件总次数、上1次----上10次误差自监测超差事件记录、误差超限判断阀值 (即误差超限阈值)、误差超限判定次数(即超限次数阈值)。
设置：误差超限判断阀值(即误差超限阈值)、误差超限判定次数(即超限次数阈值)。
操作：事件记录模块，事件记录总清、误差自监测超差事件分项清零。
参考图6，为双芯智能电表管理单元误差自监测超差事件记录实现流程图，具体步骤包括：
步骤1，电能表上电后，由主线程创建事件记录线程；
步骤2，事件记录线程启动后，先判断并创建工作目录，再初始化事件记录的相关参数(主要是各事件的阈值与初始状态等)
步骤3，等待分时计量模块已经正常运行的信号(需保证进行事件记录处理时，使用的实时数据准确有效)；
步骤4，当获取到分时计量已正常运行的消息后，创建定时器任务(延时1秒启动，定时器周期为1秒，定时器任务每秒向事件记录线程发送一个消息)，发送秒消息并进行等待；
步骤5，事件记录线程，每秒钟获取计量管理服务共享内存里的误差自监测数据；
步骤6，推送的误差自监测数据与设置的超差事件状态识别条件进行比较，判断是否超过判定次数(即超限次数阈值)，进行事件记录的判断与处理。
进一步地，误差自监测超差事件记录的运行流程如下：
电表上电初始化时，先清该事件状态字(即当前状态标识)，即记当前状态字为0，表明超差事件结束。正常运行中，每秒管理单元先读取误差超限阈值、超限次数阈值，读取误差自监测超差事件的状态字。
电表正常运行时，如果当前状态字为发生，读取的误差自监测数据低于误差超限阈值，当前累计的第一误差超限次数加1，否则误差超限次数清零，得到第一误差超限总次数。当第一误差超限次数大于判定次数(即超限次数阈值)时，记误差超限事件结束，写事件结束，将状态字置为0。
电表正常运行时，如果当前状态字为结束，读取的误差自监测数据超过误差超限阈值，将当前累计的第二误差超限次数加1，否则误差超限次数清零，得到第二误差超限总次数。当第二误差超限总次数大于判定次数(即超限次数阈值)时，记录误差自监测超差事件发生，且将误差自监测超差事件总次数增加1，将当前状态字置为1并主动上报状态字。
上述误差自监测超差事件记录采用创建事件记录线程的方法，并能读取事件状态字判断统计误差超限次数，同时能通过创建事件结构体用于保存电能表运行实时数据，使用实时数据中的误差自监测数据，进行事件记录的处理。相对于传统的电表软件系统，本申请的误差自监测超差事件记录的实现方法在电表管理单元运行时，通过获取计量管理服务推送的实时数据，根据实时数据里的误差自监测值，再根据通过 通信模块设置的阀值和误差超限判定次数，进行误差自监测超差事件的判断和记录。同时采用了管理单元事件记录的实现方法，即通过事件线程将记录的数据存储在管理单元中。事件记录应用在电表上电后通过主线程创建，而误差自监测超差事件记录由创建分线程来进行统计，通过判断分时计量等模块的信号，创建定时器任务来进行该事件的记录，节省程序线程资源，在判断误差自监测是否超差时根据误差超限判断阀值、误差超限判定次数等进行事件判断和处理，保证结果的准确性和实时性。
应该理解的是，虽然上述流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，这些步骤可以以其它的顺序执行。而且，上述流程图中的至少一部分步骤可以包括多个步骤或者多个阶段，这些步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，这些步骤或者阶段的执行顺序也不必然是依次进行，而是可以与其它步骤或者其它步骤中的步骤或者阶段的至少一部分轮流或者交替地执行。
在一个实施例中，如图7所示，提供了一种双芯智能电表的超差事件记录装置，包括：数据获取模块702、标识确定模块704和超差事件记录模块706，其中：
数据获取模块702，用于从双芯智能电表的计量单元中获取实时误差自监测数据；
标识确定模块704，用于获取双芯智能电表超差事件的当前状态标识，并基于实时误差自监测数据、当前状态标识和预设的超差事件状态识别条件，确定双芯智能电表超差事件的实时状态标识；
超差事件记录模块706，用于若实时状态标识与当前状态标识不匹配，则将当前状态标识替换为实时状态标识，并记录实时状态标识对应的超差事件。
在一个实施例中，预设的超差事件状态识别条件包括用于识别超差事件的事件状态的误差超限阈值和超限次数阈值；上述标识确定模块704，具体包括：
次数确定子模块，用于基于实时误差自监测数据、当前状态标识和误差超限阈值，确定误差超限总次数；
标识确定子模块，用于根据误差超限总次数和超限次数阈值，确定双芯智能电表超差事件的实时状态标识。
在一个实施例中，当前状态标识包括发生标识和结束标识；上述次数确定子模块，具体用于若当前状态标识为发生标识，基于实时误差自监测数据和误差超限阈值，确定第一误差超限总次数；若当前状态标识为结束标识，基于实时误差自监测数据和误差超限阈值，确定第二误差超限总次数。
在一个实施例中，上述次数确定子模块，还用于若当前状态标识为发生标识，且实时误差自监测数据小于或等于误差超限阈值，则将当前累计的第一误差超限次数执行加一操作，得到第一误差超限总次数；若当前状态标识为发生标识，且实时误差自监测数据大于误差超限阈值，则将第一误差超限总次数置为零。
在一个实施例中，上述次数确定子模块，还用于若当前状态标识为结束标识，且实时误差自监测数据大于误差超限阈值，则将当前累计的第二误差超限次数执行加一操作，得到第二误差超限总次数；若当前状态标识为结束标识，且实时误差自监测数据小于或等于误差超限阈值时，则将第二误差超限总次数置为零。
在一个实施例中，上述标识确定子模块，具体用于当第一误差超限总次数大于超限次数阈值时，确定双芯智能电表超差事件的实时状态标识为结束标识；当第二误差超限总次数大于超限次数阈值时，确定双芯智能电表超差事件的实时状态标识为发生标识。
在一个实施例中，上述装置还包括初始化模块，用于对双芯智能电表进行上电初始化，并将超差事件的当前状态标识设定为结束标识。
在一个实施例中，双芯智能电表的管理单元携带有事件记录应用；上述装置还包括线程创建模块，用于通过事件记录应用的主线程创建用于记录超差事件的超差事件记录线程；上述超差事件记录模块706还用于通过超差事件记录线程记录实时状态标识对应的超差事件。
需要说明的是，本申请的双芯智能电表的超差事件记录装置与本申请的双芯智能电表的超差事件记录方法一一对应，在上述双芯智能电表的超差事件记录方法的实施例阐述的技术特征及其有益效果均适用于双芯智能电表的超差事件记录装置的实施例中，具体内容可参见本申请方法实施例中的叙述，此处不再赘述，特此声明。
此外，上述双芯智能电表的超差事件记录装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。上述各模块可以硬件形式内嵌于或独立于计算机设备中的处理器中，也可以以软件形式存储于计算机设备中的存储器中，以便于处理器调用执行以上各个模块对应的操作。
在一个实施例中，提供了一种计算机设备，该计算机设备可以是终端，其内部结构图可以如图8所示。该计算机设备包括通过系统总线连接的处理器、存储器、通信接口、显示屏和输入装置。其中，该计算机设备的处理器用于提供计算和控制能力。该计算机设备的存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统和计算机程序。该内存储器为非易失性存储介质中的操作系统和计算机程序的运行提供环境。该计算机设备的通信接口用于与外部的终端进行有线或无线方式的通信，无线方式可 通过WIFI、运营商网络、NFC(近场通信)或其他技术实现。该计算机程序被处理器执行时以实现一种双芯智能电表的超差事件记录方法。该计算机设备的显示屏可以是液晶显示屏或者电子墨水显示屏，该计算机设备的输入装置可以是显示屏上覆盖的触摸层，也可以是计算机设备外壳上设置的按键、轨迹球或触控板，还可以是外接的键盘、触控板或鼠标等。
本领域技术人员可以理解，图8中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备的限定，具体的计算机设备可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
在一个实施例中，还提供了一种计算机设备，包括存储器和处理器，存储器中存储有计算机程序，该处理器执行计算机程序时实现上述各方法实施例中的步骤。
在一个实施例中，提供了一种计算机可读存储介质，其上存储有计算机程序，该计算机程序被处理器执行时实现上述各方法实施例中的步骤。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的计算机程序可存储于一非易失性计算机可读取存储介质中，该计算机程序在执行时，可包括如上述各方法的实施例的流程。其中，本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和易失性存储器中的至少一种。非易失性存储器可包括只读存储器(Read-Only Memory，ROM)、磁带、软盘、闪存或光存储器等。易失性存储器可包括随机存取存储器(Random Access Memory，RAM)或外部高速缓冲存储器。作为说明而非局限，RAM可以是多种形式，比如静态随机存取存储器(Static Random Access Memory，SRAM)或动态随机存取存储器(Dynamic Random Access Memory，DRAM)等。
以上实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (11)

  1. 一种双芯智能电表的超差事件记录方法，其特征在于，应用于所述双芯智能电表的管理单元，所述方法包括：
    从所述双芯智能电表的计量单元中获取实时误差自监测数据；
    获取所述双芯智能电表超差事件的当前状态标识，并基于所述实时误差自监测数据、所述当前状态标识和预设的超差事件状态识别条件，确定所述双芯智能电表超差事件的实时状态标识；
    若所述实时状态标识与所述当前状态标识不匹配，则将所述当前状态标识替换为所述实时状态标识，并记录所述实时状态标识对应的超差事件。
  2. 根据权利要求1所述的方法，其特征在于，所述预设的超差事件状态识别条件包括用于识别超差事件的事件状态的误差超限阈值和超限次数阈值；
    所述基于所述实时误差自监测数据、所述当前状态标识和预设的超差事件状态识别条件，确定所述双芯智能电表超差事件的实时状态标识，包括：
    基于所述实时误差自监测数据、所述当前状态标识和所述误差超限阈值，确定误差超限总次数；
    根据所述误差超限总次数和所述超限次数阈值，确定所述双芯智能电表超差事件的实时状态标识。
  3. 根据权利要求2所述的方法，其特征在于，所述当前状态标识包括发生标识和结束标识；
    所述基于所述实时误差自监测数据、所述当前状态标识和所述误差超限阈值，确定误差超限总次数，包括：
    若所述当前状态标识为发生标识，则基于所述实时误差自监测数据和所述误差超限阈值，确定第一误差超限总次数；
    若所述当前状态标识为结束标识，则基于所述实时误差自监测数据和所述误差超限阈值，确定第二误差超限总次数。
  4. 根据权利要求3所述的方法，其特征在于，所述若所述当前状态标识为发生标识，则基于所述实时误差自监测数据和所述误差超限阈值，确定第一误差超限总次数，包括：
    若所述当前状态标识为发生标识，且所述实时误差自监测数据小于或等于所述误差超限阈值，则将当前累计的第一误差超限次数执行加一操作，得到第一误差超限总次数；
    若所述当前状态标识为发生标识，且所述实时误差自监测数据大于所述误差超限阈值，则将第一误差超限总次数置为零。
  5. 根据权利要求3所述的方法，其特征在于，所述若所述当前状态标识为结束标识，则基于所述实时误差自监测数据和所述误差超限阈值，确定第二误差超限总次数，包括：
    若所述当前状态标识为结束标识，且所述实时误差自监测数据大于所述误差超限阈值，则将当前累计的第二误差超限次数执行加一操作，得到第二误差超限总次数；
    若所述当前状态标识为结束标识，且所述实时误差自监测数据小于或等于所述误差超限阈值时，则将第二误差超限总次数置为零。
  6. 根据权利要求3所述的方法，其特征在于，所述根据所述误差超限总次数和所述超限次数阈值，确定所述双芯智能电表超差事件的实时状态标识，包括：
    当第一误差超限总次数大于所述超限次数阈值时，确定所述双芯智能电表超差事件的实时状态标识为结束标识；
    当第二误差超限总次数大于所述超限次数阈值时，确定所述双芯智能电表超差事件的实时状态标识为发生标识。
  7. 根据权利要求1所述的方法，其特征在于，在从所述双芯智能电表的计量单元中获取实时误差自监测数据之前，包括：
    对所述双芯智能电表进行上电初始化，并将所述超差事件的当前状态标识设定为结束标识。
  8. 根据权利要求7所述的方法，其特征在于，所述双芯智能电表的管理单元携带有事件记录应用；
    在对所述双芯智能电表进行上电初始化之后，还包括：
    通过所述事件记录应用的主线程创建用于记录超差事件的超差事件记录线程；
    所述记录所述实时状态标识对应的超差事件，包括：
    通过所述超差事件记录线程记录所述实时状态标识对应的超差事件。
  9. 一种双芯智能电表的超差事件记录装置，其特征在于，应用于所述双芯智能电表的管理单元，所述装置包括：
    数据获取模块，用于从所述双芯智能电表的计量单元中获取实时误差自监测数据；
    标识确定模块，用于获取所述双芯智能电表超差事件的当前状态标识，并基于所述实时误差自监测数据、所述当前状态标识和预设的超差事件状态识别条件，确定所述双芯智能电表超差事件的实时状态标识；
    超差事件记录模块，用于若所述实时状态标识与所述当前状态标识不匹配，则将所述当前状态标识替换为所述实时状态标识，并记录所述实时状态标识对应的超差事件。
  10. 一种计算机设备，包括存储器和处理器，所述存储器存储有计算机程序，其特征在于，所述处理器执行所述计算机程序时实现权利要求1至8中任一项所述方法的步骤。
  11. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现权利要求1至8中任一项所述的方法的步骤。
PCT/CN2021/115086 2021-03-25 2021-08-27 双芯智能电表的超差事件记录方法、装置和计算机设备 WO2022198919A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110321338.7A CN113050020B (zh) 2021-03-25 2021-03-25 双芯智能电表的超差事件记录方法、装置和计算机设备
CN202110321338.7 2021-03-25

Publications (1)

Publication Number Publication Date
WO2022198919A1 true WO2022198919A1 (zh) 2022-09-29

Family

ID=76515264

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/115086 WO2022198919A1 (zh) 2021-03-25 2021-08-27 双芯智能电表的超差事件记录方法、装置和计算机设备

Country Status (2)

Country Link
CN (1) CN113050020B (zh)
WO (1) WO2022198919A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115542238A (zh) * 2022-11-30 2022-12-30 北京志翔科技股份有限公司 超差表检测方法及装置

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113050020B (zh) * 2021-03-25 2024-05-03 深圳供电局有限公司 双芯智能电表的超差事件记录方法、装置和计算机设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102881143A (zh) * 2012-10-22 2013-01-16 杭州海兴电力科技股份有限公司 Ami系统中读取电能表事件记录的方法
US20170219639A1 (en) * 2016-01-29 2017-08-03 Landis+Gyr, Inc. Detecting Current Measurement Tampering by Current Transformer Parallel Impedance
CN112098924A (zh) * 2020-11-04 2020-12-18 南方电网数字电网研究院有限公司 基于双芯智能电表的交互功能测试方法和装置
CN112230052A (zh) * 2020-08-03 2021-01-15 青岛鼎信通讯股份有限公司 一种满足ir46要求的电能表计量芯方案设计
CN112433861A (zh) * 2020-11-02 2021-03-02 南方电网数字电网研究院有限公司 双芯智能电表的事件记录方法和双芯智能电表
CN113050020A (zh) * 2021-03-25 2021-06-29 深圳供电局有限公司 双芯智能电表的超差事件记录方法、装置和计算机设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102881143A (zh) * 2012-10-22 2013-01-16 杭州海兴电力科技股份有限公司 Ami系统中读取电能表事件记录的方法
US20170219639A1 (en) * 2016-01-29 2017-08-03 Landis+Gyr, Inc. Detecting Current Measurement Tampering by Current Transformer Parallel Impedance
CN112230052A (zh) * 2020-08-03 2021-01-15 青岛鼎信通讯股份有限公司 一种满足ir46要求的电能表计量芯方案设计
CN112433861A (zh) * 2020-11-02 2021-03-02 南方电网数字电网研究院有限公司 双芯智能电表的事件记录方法和双芯智能电表
CN112098924A (zh) * 2020-11-04 2020-12-18 南方电网数字电网研究院有限公司 基于双芯智能电表的交互功能测试方法和装置
CN113050020A (zh) * 2021-03-25 2021-06-29 深圳供电局有限公司 双芯智能电表的超差事件记录方法、装置和计算机设备

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115542238A (zh) * 2022-11-30 2022-12-30 北京志翔科技股份有限公司 超差表检测方法及装置

Also Published As

Publication number Publication date
CN113050020A (zh) 2021-06-29
CN113050020B (zh) 2024-05-03

Similar Documents

Publication Publication Date Title
US8141053B2 (en) Call stack sampling using a virtual machine
WO2022198919A1 (zh) 双芯智能电表的超差事件记录方法、装置和计算机设备
WO2019104854A1 (zh) 性能测试评价方法、装置、终端设备及存储介质
US10534692B2 (en) Tagged tracing, logging and performance measurements
US9740541B2 (en) Information processing apparatus and method of collecting performance analysis data
US8869118B2 (en) System aware performance counters
CN110727556A (zh) 一种bmc健康状态监控方法、系统、终端及存储介质
CN107066390A (zh) 一种动态内存泄漏检测方法及系统
WO2017215557A1 (zh) 一种采集性能监视单元pmu事件的方法及装置
WO2018233170A1 (zh) 日志记录方法、装置、计算机设备及存储介质
CN112035314B (zh) 内存泄漏的监控方法、装置及电子设备
CN112583610B (zh) 系统状态的预测方法、装置、服务器及存储介质
EP2735970B1 (en) Dynamic library profiling method
CN109634822B (zh) 一种函数耗时统计方法、装置、存储介质及终端设备
CN110069562B (zh) 数据展示方法、装置、存储介质及计算机设备
CN115576831A (zh) 一种测试案例推荐方法、装置、设备及存储介质
CN114356764A (zh) 软件调测方法、装置、设备、系统和介质
CN113064765B (zh) 节点异常处理方法、装置、电子设备及机器可读存储介质
US20120240128A1 (en) Memory Access Performance Diagnosis
CN113376564A (zh) 基于数据分析的智能电表计量校正方法、装置及终端
US9182958B2 (en) Software code profiling
CN111427747A (zh) 一种Redis客户端性能监测方法及装置
CN113009407B (zh) 双芯智能电表的电压事件记录方法、装置和双芯智能电表
RU2552177C2 (ru) Способ оценки влияния работы приложений и их функций на энергопотребление во встраиваемых системах
CN112782642B (zh) 双芯智能电表的电压合格率记录方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21932531

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE