Method, signaling packet processing method and system for active reporting of power out-of-limit events

Abstract

The present application relates to a kind of power over-limit event active reporting method, signaling packet processing method and system in the technical field of smart meter, comprising the following steps: judging whether the power over-limit event of smart meter occurs, if yes, then the communication channel of smart meter carries out silence period processing;Get the address tail number of smart meter, and determine the reporting time of power over-limit event according to the parity of address tail number;Based on reporting time, discrete reporting power over-limit event;Judge whether the response frame of power over-limit event that main station is correctly received is received, if yes, then stop reporting operation;If no, then repeat silence period processing, and execute in this discrete reporting power over-limit event operation, solve the problem that smart meter power over-limit event active reporting is easily lost.

Description

Technical Field

[0001] This invention relates to the field of smart meter technology, specifically to a method for actively reporting power limit exceedance events, a signaling packet processing method, and a system. Background Technology

[0002] Traditional centralized power consumption information collection systems involve collection devices such as collectors, concentrators, and collection terminals. For downstream power metering devices, such as electricity meters, metering modules, and metering devices, they typically passively receive reporting tasks from the collection system via a RS485 interface. During periods of sustained high temperatures, when power consumption by equipment and users surges, line overload occurs. This leads to relatively delayed handling of power limit violations and data loss due to RS485 data frame link congestion during centralized reporting. Furthermore, traditional centralized collection requires significant storage space from the collection devices, and storage chips are expensive. For applications with concentrated school dormitories and high power safety requirements, while traditional collection devices can collect data, they are less effective at timely reporting of safety incidents. Frequent collection also increases system bandwidth consumption and storage space requirements, leading to higher costs and lower timeliness.

[0003] In recent years, with the centralized and large-scale installation of smart meters, there have been frequent occurrences of related events or message frame loss during the centralized data collection process. This makes it impossible to quickly report energy safety-related events, or to obtain timely information on smart meter malfunctions. Therefore, it is necessary to address these energy consumption conditions. Summary of the Invention

[0004] This invention addresses the shortcomings of existing technologies by providing a method for proactively reporting power limit exceedance events, a signaling packet processing method, and a system, thus resolving the problem of easily lost proactive reports of power limit exceedance events from smart meters.

[0005] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0006] A method for proactively reporting power limit exceedance events includes the following steps:

[0007] Determine whether a power limit violation event has occurred in the smart meter; if so, the communication channel of the smart meter is put into a silent period.

[0008] Obtain the last digit of the smart meter's address and determine the reporting time for the power limit overrun event based on the parity of the last digit of the address.

[0009] Based on the reporting time, the power limit exceeding event is reported discretely;

[0010] Judging whether a response frame of a master station correct received power out of limit event is received, if yes, stopping reporting operation, if no, repeating silence period processing and performing power out of limit event reporting operation in the discrete period.

[0011] Optionally, the communication channel of the smart meter performs silence period processing, including the following steps:

[0012] Setting a silence period length, after the power out of limit event occurs, the smart meter waits for the silence period length after the time is divided.

[0013] Optionally, the reporting time of the power out of limit event is determined according to the parity of the last digit of the address, including the following steps:

[0014] If the last digit of the address is odd, the a-th second of the next minute after the silence period is reported;

[0015] If the last digit of the address is even, the b-th second of the next minute after the silence period is reported;

[0016] Wherein, a = 1 + {(reporting times - 1) * 2}; b = (reporting times - 1) * 2, the reporting times is the number of times reported before this power out of limit event reporting.

[0017] Optionally, judging whether the smart meter has a power out of limit event, including the following steps:

[0018] Setting a power out of limit threshold and an out of limit duration threshold;

[0019] If the active power of the smart meter is greater than or equal to the power out of limit threshold and the duration reaches the out of limit duration threshold, it is determined that the smart meter has a power out of limit event.

[0020] A signaling packet processing method for power out of limit event active reporting, the signaling packet processing method is applied to the power out of limit event active reporting method as described in any one of the above, including the following steps:

[0021] Judging whether a signaling appears, if yes, the smart meter performs silence period processing;

[0022] Reading smart meter data and performing smart meter registration;

[0023] Judging whether the smart meter is successfully registered, if yes, judging whether the channel is busy; if no, returning to the step of judging whether a signaling appears;

[0024] If the channel is busy, returning to the step of judging whether a signaling appears, if the channel is idle, receiving the signaling and judging the validity of the signaling;

[0025] If the signaling is valid, the message frames are buffered according to the signaling priority, and the received message frames are processed in groups and rounds.

[0026] Message frames are sent according to the channel state, wherein the message frames include either response messages or SOS message frames.

[0027] Optionally, according to signaling priority, message frames are buffered and received messages are processed in rounds, including the following steps:

[0028] The signaling node of the next lower priority sends signaling data to the signaling node of the next higher priority, and the signaling node sends signaling data level by level according to the priority of the signaling, wherein the signaling data includes message frames.

[0029] Optionally, sending the message frame according to the channel state includes the following steps:

[0030] Set the avoidance delay duration and start the delay avoidance timer;

[0031] After the delay avoidance timer expires, the channel is determined to be busy or idle. If the channel is busy, the delay avoidance timer is restarted. If the channel is idle, the response message or SOS message is sent.

[0032] Optional, also includes:

[0033] If a signaling termination or signaling failure is received, the channel is reset, and processing of response messages or SOS messages ceases.

[0034] A signaling packet processing system for actively reporting power limit exceedance events, wherein the signaling packet processing system executes the signaling packet processing method as described in any one of the above, including the physical layer, link layer and network layer;

[0035] The physical layer is used to transmit and receive binary data bits;

[0036] The link layer is used to process the received message frames in groups and switch the data receiving mode or the signaling listening mode according to the link information in the message frames.

[0037] The link layer is also used to send response messages and SOS messages;

[0038] The network layer is used to determine whether the reported power over-limit time is valid and to send a response message or an SOS message.

[0039] A computer-readable storage medium storing a computer program, characterized in that, when the computer program is executed by a processor, it performs the power limit over-limit event active reporting method described in any one of the above-mentioned methods.

[0040] Compared with the prior art, the technical solution provided by this invention has the following advantages:

[0041] By setting parity to determine the reporting time of power limit exceedance events, and performing time-discrete reporting, the problem of information loss caused by centralized RS485 bus reporting when power limit exceedance occurs in a multi-device centralized acquisition system is solved. Furthermore, by using the smart meter address to actively report data frames, the system's active recall actions are reduced, and the read events can be stored and erased in a timely manner, reducing storage space costs. Attached Figure Description

[0042] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0043] Figure 1 This is a flowchart of a method for actively reporting power limit exceedance events proposed in Embodiment 1.

[0044] Figure 2 This is a flowchart of a signaling packet processing method for proactively reporting power limit exceedance events, as proposed in Embodiment 2.

[0045] Figure 3 This is a diagram showing the five state transitions of the smart meter proposed in Embodiment 2. Detailed Implementation

[0046] The present invention will be further described in detail below with reference to the embodiments. The following embodiments are explanations of the present invention, but the present invention is not limited to the following embodiments.

[0047] Example 1

[0048] like Figure 1 As shown, a method for actively reporting power limit exceedance events includes the following steps: determining whether a power limit exceedance event has occurred in a smart meter; if so, the communication channel of the smart meter is processed to enter a silent period. The determination of whether a power limit exceedance event has occurred includes the following steps: setting a power limit exceedance threshold and a limit exceedance duration threshold; if the active power of the smart meter is greater than or equal to the power limit exceedance threshold, and the duration reaches the limit exceedance duration threshold, then it is determined that a power limit exceedance event has occurred in the smart meter.

[0049] The communication channel of a smart meter undergoes a silent period, which includes the following steps: setting the silent period duration. After a power over-limit event occurs, the smart meter waits for the silent period after the time has passed a whole minute. Taking a silent period of 10 seconds as an example, the silent period refers to the time period from the first to the tenth second after the smart meter passes a whole minute.

[0050] Further, the last digit of the smart meter's address is obtained, and the reporting time for the power limit violation event is determined based on the parity of the last digit. Specifically, this includes the following steps: if the last digit is odd, the report is made at the 'a'th second of the next minute after the silent period; if the last digit is even, the report is made at the 'b'th second of the next minute after the silent period; where a = 1 + {(number of reports - 1) * 2}; b = (number of reports - 1) * 2, and the number of reports is the number of times the event has already been reported before this power limit violation event is reported.

[0051] Specifically, the smart meter determines whether the last digit of the meter address is odd or even based on its own set "meter communication address" parameter. It then reports the data to the master station in discrete frames based on the determined parity. When a power limit violation event occurs, the data is reported. The parity of the last digit of the smart meter address is determined: if it is odd, the power limit violation event is reported at the 1+{(reporting times - 1)*2}th second of the next minute; if it is even, the power limit violation event is reported at the {(reporting times - 1)*2}th second of the next minute.

[0052] Furthermore, based on the reporting time, power limit exceedance events are reported discretely; it is determined whether a response frame indicating that the master station has correctly received the power limit exceedance event is received. If so, the reporting operation is stopped; if not, the silent period processing is repeated, and the operation of reporting power limit exceedance events discretely is performed.

[0053] After a power limit violation event is reported, it is determined whether an ACK confirmation symbol has been received. If not, the process returns to the previous step; if yes, the process ends after reporting. Specifically, regardless of whether the smart meter's 485 bus is in a silent or non-silent period, within the current minute when a power limit violation occurs, it is not necessary to send a power limit violation event message to the 485 bus. Instead, the power limit violation event message is sent to the 485 bus after the next full minute of the silent period. After sending, the smart meter waits for the master station to confirm that the "power limit violation event message has been correctly received" response frame.

[0054] Furthermore, if the master station receives a correct response frame within the current time, that is, it has correctly received the power over-limit event message sent by the smart meter to the 485 bus, then the smart meter will no longer report the power over-limit event message; if the smart meter does not receive a correct response frame from the master station indicating that the power over-limit event message has been received, then the smart meter will continue to wait for 1 minute (the first 1 minute) and report discretely for the last two digits of the meter's communication address, which are either odd or even.

[0055] For example, if the smart meter waits for the master station for the first minute, it will proactively report a power limit overrun event message to the 485 bus for the first time during the 3-7 second silence period after the minute. If the last digit of the meter's communication address is odd, the proactive reporting will be done discretely at the 3rd, 5th, and 7th second after the minute. If the last digit of the meter's address is even, the proactive reporting will be done discretely at the 4th second after the minute. If the meter still does not receive a correct response frame from the master station indicating that the power limit overrun event message has been received, it will continue to wait for another minute, i.e., the second minute, and perform the above operation.

[0056] If the master station replies correctly, it will no longer actively report the power limit exceeding event of the meter. If the meter waits for the master station for a second 1 minute, it will actively report the power limit exceeding event message to the 485 bus for the second time during the 3-7 second silence period after the minute. For meters with odd-numbered communication address digits, the active reporting will be done discretely at the 3rd, 5th, and 7th second after the minute. For meters with even-numbered address digits, the active reporting will be done discretely at the 4th second after the minute. If the master station still does not respond with a "power limit exceeding event message received" frame, it will continue to wait for 1 minute, i.e., the third 1 minute, and perform the above operation.

[0057] If the master station responds correctly, it will no longer proactively report the power limit exceeding event. If the meter waits for the master station for the third 1 minute, it will proactively report the power limit exceeding event message to the 485 bus for the third time during the 3-7 second silence period after the minute. For meters with odd-numbered communication address digits, the proactive reporting will be done at the 3rd, 5th, and 7th second after the minute; for meters with even-numbered address digits, the proactive reporting will be done at the 4th second after the minute. If the master station does not respond with a "power limit exceeding event message received" frame, the meter will no longer proactively report the power limit exceeding event and will discard the event.

[0058] Specifically, for example, if the current time of the smart energy meter is 20:36:00, then the 10 seconds from 20:36:01 to 20:36:10 are the silent period of the 485 bus. Then the clock continues to run until 20:37:00, which is a minute past the hour. From this moment, the 10 seconds from 20:37:00 to 20:37:10 are again the silent period of the 485 bus. Other minutes past the hour are described in the same way.

[0059] In this embodiment, if the current time of the electricity meter is 20:48:01, and the electricity meter exceeds the power limit at this time, the electricity meter must not actively send a power limit event message frame to the 485 bus within the time range of 20:48:01 to 20:48:59. Only when the smart meter passes the minute mark, i.e., the minute mark is 20:49:00, the smart meter's 485 bus is in a silent period for 10 seconds from 20:49:01 to 20:49:10. During the silent period from 20:49:13 to 20:49:17 (within 3 to 7 seconds after the minute mark), the smart meter should actively send a power limit event message to the 485 bus. After the power limit event message is sent, the smart meter is in a state of waiting for a reply from the master station.

[0060] If the master station does not respond the first time, the smart meter continues to wait until 20:50:00. During the second quiet period (20:50:01 to 20:50:10), between the 3rd and 7th second after the minute, it sends a second power limit overrun event report message to the 485 bus. After sending the message, it continues to wait for the master station's response between 20:50:11 and 20:50:59. If the master station does not respond, it continues to wait for the next quiet period, and so on. The staff can set the number of reports according to the actual situation. For example, the maximum number of power limit overrun events can be set to be reported three times. If the master station responds correctly once within the first three reports, no further reports are needed. If no response is received from the master station after three reports, the event is discarded.

[0061] It should be noted that the electrical components mentioned above are all devices with relatively mature existing technology. The specific models can be selected according to actual needs. At the same time, the power supply can be powered by the built-in power supply or by the mains power. The specific power supply method will be selected according to the situation and will not be elaborated here.

[0062] Example 2

[0063] like Figure 2 As shown, a signaling packet processing method for proactively reporting power limit exceedance events is provided. This signaling packet processing method is applied to the proactive power limit exceedance time reporting method described in any of Embodiment 1, and includes the following steps: determining whether a signaling event has occurred; if so, the smart meter undergoes a silent period; reading the smart meter data and registering the smart meter; and determining whether the smart meter registration is successful.

[0064] Specifically, in the data network link, when the link layer receives a command frame, it executes the signaling information in the command frame and waits for the signaling to appear. If the signaling appears, it accesses the electricity meter after the smart meter reaches the silent period, reads the smart meter data, including the smart meter time or communication address, and then performs electricity meter registration. If the registration is successful, it can proceed to the next step; if it is unsuccessful, it continues to wait for the signaling. On the other hand, if a node that has successfully registered a smart meter still has not received any signaling after the default waiting time, it attempts to send an SOS message.

[0065] If registration is successful, the channel is checked for busy status; if unsuccessful, the process returns to the step of checking for signaling. If the channel is busy, the process returns to the step of checking for signaling. If the channel is idle, the signaling is received and its validity is checked. If the signaling is valid, the message frames are buffered according to the signaling priority, and the received message frames are processed in groups in rounds. Message frames are sent according to the channel status, where the message frames include either response messages or SOS message frames.

[0066] Specifically, if a node receives an active access message on the serial port, after parsing and discovering that the message was sent by the concentrator, it immediately marks itself as a level 0 node and stops accessing the meters. Simultaneously, it sends a level 0 signaling invalid command, then calculates the delay time based on the number of meters Nk provided in the concentrator message: T0 = 2 × Nk / 100 (seconds), performs the delay, and sends a level 0 signaling valid command after the delay.

[0067] Furthermore, the node sending the level 0 signaling calculates the total data transmission time based on the number of electricity meters Nk and the number of electricity meters that have already transmitted data at each level of the node. After this time, it sends a level 0 signaling invalid command. At the same time, after a delay of T0, it changes the signaling round and sends a level 0 signaling valid command again.

[0068] For example, a node sending a level 0 signaling message first calculates the maximum signaling level Lmax based on the number of electricity meters Nk, assuming that each level of signaling message can be received by 100 nodes. Then, it re-determines the maximum signaling level Lmax based on the level of the electricity meters that have already sent data at each level. A node that receives a signaling message with the maximum level Lmax will no longer send a signaling message.

[0069] According to the signaling priority, the message frames are cached and the received message frames are processed in groups in rounds, including the following steps: the signaling node of the next lower priority sends signaling data to the signaling node of the next higher priority, and the signaling node sends signaling data level by level according to the signaling priority, wherein the signaling data includes message frames.

[0070] Upon receiving a signaling message, the node determines the signaling flag and records the signaling level, signaling round, signaling time, and signaling address. Based on the signaling flag, the node handles the signaling as valid, invalid, lost, discarded, or conflicting. If the signaling is valid, the node compares the signaling rounds received in the previous two meetings. If the signaling round has changed, it indicates that the previous signaling message was invalid and may have been lost. The node updates the records of the signaling round, signaling time, and signaling address, terminates any ongoing processes for this round, and restarts the contention for sending the current level of signaling and the execution of subsequent steps.

[0071] If the round number has not changed, check if the signaling time is less than the previous time. If it is less than the previous time, terminate any ongoing processes in this round and restart the contention for sending signaling at this level and the execution of subsequent steps. If it is greater than the previous time, check if the signaling address has changed. If it has changed, it indicates that the previous signaling may have been lost. In this case, the node updates the signaling time and signaling address and uses the new signaling address when sending subsequent data frames.

[0072] Sending message frames according to channel status includes the following steps: setting the avoidance delay duration and starting the delay avoidance timer; after the delay avoidance timer expires, determining whether the channel is busy or idle. If the channel is busy, the delay avoidance timer continues to start; if the channel is idle, a response message or an SOS message is sent.

[0073] Furthermore, after the link layer receives a data frame, the signaling holding node must be responsible for forwarding it immediately. Non-signaling nodes at the same level as the signaling node listen to whether the signaling node has already forwarded the data. If the listening time limit is exceeded, they compete to forward the data.

[0074] The link layer needs to process two uplink data frame statistics. One is a counter value that counts the number of uplink data frames. Each time a data frame is received, the counter value is incremented by one. The link layer saves this counter value and fills it in the link information field when sending its own data frame. It also reports this counter value to the network layer. The other uplink data frame statistics value is the statistics value filled in by other nodes in the message when an uplink data frame is received. This value is used to calculate the message frame retransmission delay time. At the same time, the link layer records the average value of each received counter value as a criterion for deciding whether to submit the command frame to the network layer.

[0075] After processing the signaling of the command frame, determine whether to submit the command frame to the network layer for address-related operations based on the conditions given in Table 1.

[0076]

[0077] Table 1

[0078] After receiving a data frame from the network layer of this node, the link layer should add link information to the beginning of the data frame before sending it. At this time, it is necessary to calculate the retransmission delay count to ensure correct transmission collision avoidance and delayed retransmission.

[0079] If a command frame is submitted to the network layer, the link layer should calculate the retransmission delay count after receiving the response frame from the network layer, request the transmission of data, and then transmit signaling. If the network layer does not respond within the timeout period, the link layer should immediately transmit signaling and no longer process the network layer's service request.

[0080] On the other hand, all nodes that receive the message, i.e., the signaling or uplink data frame, first use a random algorithm with a random delay C. ym The transmission delay is calculated using the timing unit μ1, within the delay time interval: t τ (=C ym ×μ L After completion, check if the channel is busy. If not, send a message; if the channel is busy, send a message according to the timing unit δ. L Time interval, in terms of channel detection coefficient N BL Continuous detection channel N BL Next, if the channel is detected to be not busy, a message is sent; otherwise, in N... BL After the first test, press t again. τ Delay until the message can be sent.

[0081] The formula for calculating the channel detection coefficient is as follows:

[0082] N BL = (Link packet statistics + Uplink packet statistics of this node) / MAX(Link packet statistics), where the link packet statistics are the same as the uplink packet statistics of this node.

[0083] The determination of the range of random numbers for the delay is as follows: For the minimum random number, considering an average node delay of K = 1, meaning the node only needs to delay once to send data, let the total number of nodes be N_total, and the message length be fixed at 80 bytes. The message time t... σ = 1.28 seconds, set the minimum random delay time interval for node conflict avoidance as t τ That is, the minimum difference t between the random delays of two nodes. τ / 0.2.

[0084] Considering the channel frame synchronization word has a fixed time of 5 bytes, T t = 2ms × 8 × 5 = 80ms, therefore, the time required for a message to be prepared for transmission and to remain on the channel until other nodes receive it is: T b =K×t τ +t σ +Tt = 1.36 seconds + K × t τ In the formula, K is the average number of delays.

[0085] Furthermore, the solution parameters K and t are calculated. τ The process includes the following steps: First, calculation begins when the master node sends a signaling message, and when node Nd... j The time required for the master node to receive the i-th level signaling message and begin uploading data frames is: T. d =2×i×T b .

[0086] Compared to the centralized mode, where the maximum interval between each message transmission by the concentrator is 0.5 seconds, if node Nd i If the concentrator message is received and successfully transmitted, the required time is T'. d =2×i×1.36 seconds + 0.5 = 2.72×i seconds + 0.5.

[0087] Obviously, the time T for data to be uploaded by a single node d >T' d Considering the number of nodes N 总 Maximum signaling level L p (Equivalent to the number of relay levels in centralized mode), average number of nodes per level N n =N 总 / L p In the case of this, the time required to collect data from all i-th level nodes is as follows in signaling mode:

[0088] T i =(N n +1)×i×T b

[0089] =(N n +1)×i×(1.36 seconds + K×t) τ )

[0090] =(N n +1)×i×1.36 seconds+(N n +1)×i×K×t τ

[0091] The maximum random number at this point is: C ym =C y0 +rand()%C tz ; where rand() is a mathematical random number generator that generates an average random number between 0 and 4294967295, C tz It is the range coefficient of the designed random number.

[0092] To consider the total number of different nodes N总 Both have a balanced delay range, and C tz This should be applicable to every level of signaling, using the golden ratio (0.618) as the compression factor, then design C... tz =K×(1-S×0.382)×N 总 / Current signaling level; where K is carried in the message by the concentrator and ranges from 1 to 16; S is a flag and is given in the message by the concentrator, with a value of 0 or 1. It is worth noting that since division will produce decimals, the final result in the above formula should be rounded to the nearest whole number.

[0093] For example, N 总 =1000, current signaling level =4, then with K=1 and S618=1, C tz =1000×0.618 / 4=618 / 4=153.5, in the limiting case, N 总 =2000, signaling level =1, C tz =1236; while C ym =1246, maximum limit delay time: t τ = 1246 × 0.2 = 249.2 seconds = 4.15 minutes. Conversely, the relatively reasonable minimum delay time is: N 总 =100, signaling level =29, C tz =2.06, C ym =12.06, t τ = 2.412 (seconds). Since the total signaling level N is included in the link information field of the message frame, it can be calculated dynamically.

[0094] In packet mode, when a node sends data, it must listen to the channel to see if it is in a quiet period or not, delay and avoid, and confirm that the channel is idle before sending data. The application layer function must complete the active reporting message frame of the electricity meter reading and the electricity meter self-discovery function. It is a function oriented towards system application. However, when a new electricity meter is discovered or an electricity meter has not been accessed for a long time, the network layer needs to be notified. If the signaling termination or signaling failure is received, the channel is reset and the processing of response messages or SOS messages is stopped.

[0095] Furthermore, such as Figure 3As shown, the application layer should establish a status for each electricity meter within the specified capacity range. The electricity meter status is defined as follows: The first is the unknown state, which means that the storage location of the unregistered meter address represents a virtual electricity meter. The status of this electricity meter is "unknown". In this case, after responding to the meter reading command frame or successfully accessing the address wildcard, the meter will change to "registered" or "self-discovered" respectively. The second is the self-discovered state, which means that the meter address is successfully obtained through a wildcard access to the meter address. The status of this electricity meter is "self-discovered". This electricity meter will change to "self-discovered" after passing the "new electricity meter report" or failing to report within the specified time. If a meter has not been read and reported, its status is changed to "Long-term inaccessible". The third type is the registered test status, which means that if a meter reading command frame is received and the meter status is not "alarm", the meter status is "registered". The fourth type is the long-term inaccessible status, which means that if a meter with a status of "self-discovery" or "registered" does not receive a meter reading command within a specified time, the meter status is "Long-term inaccessible". The fifth type is the alarm status, which means that if the number of failed frame reports by the meter with a status of "self-discovery" or "registered" exceeds the specified limit, the meter status is "alarm".

[0096] Furthermore, for newly discovered electricity meter reports, when the application layer responds to the meter reading command, if there is an electricity meter in the "self-discovered" state, it should set the "new electricity meter" flag to 1 in the response message frame and report the newly discovered electricity meter. After the application layer receives the "read new electricity meter" data item command, it needs to return the address of the new electricity meter. The electricity meter completes the "new electricity meter report"; the electricity meter status is changed to "long-term inaccessible".

[0097] For electricity meters, SOS means that the meter is in a "long-term inaccessible" state. When the SOS interval expires, the network layer sends an SOS request.

[0098] Example 3

[0099] A signaling packet processing system for proactively reporting power limit exceedance events, wherein the signaling packet processing system executes the signaling packet processing method as described in any one of Embodiment 2, including a physical layer, a link layer, and a network layer; the physical layer is used to transmit and receive binary data bits; the link layer is used to process the received message frames and switch the data reception mode or signaling listening mode according to the link information in the message frame; the link layer is also used to send response messages and SOS messages; the network layer is used to determine whether the reported power limit exceedance time is valid and to send response messages or SOS messages.

[0100] On the multi-device centralized data acquisition system side, the concentrator adopts a group inspection method to participate in the quiet period processing of the electricity meter through the physical layer, link layer, and network layer to actively report data frames for power limit exceeding events, ensuring the safety of the equipment at the power consumption site and playing an effective role in monitoring whether the site is in a safe power consumption state.

[0101] The physical layer's main function is to send and receive actual binary data bits. The physical layer should have a link data send and receive buffer of appropriate length, and the send and receive buffer is the interface for data exchange between the physical layer and the link layer.

[0102] The main function of the link layer is to process the link information in the link data message frames and process the actively reported data frames from the energy meter based on the packets in the link information. Upon power-on or reset, the link layer communication function is in "packet mode"; subsequently, it switches to data receiving or signaling listening state based on the link information in the received message frames.

[0103] The link layer should constantly check whether there is valid signaling being received in the channel and monitor whether the network layer has response messages or SOS message requests to be sent. When a received message is found in the channel, the link layer should update the link information data stored in the link layer for the received message and for the signaling message that actively reports the function exceeding the limit. When a message request to be sent is detected in the network layer, or when the link layer needs to send a signaling message, the delay avoidance timer should be started first.

[0104] When the timer expires, the link layer should check the channel status. If the channel is not busy, it should request message transmission. If the channel is busy, the delay timer should be restarted. If the network requests transmission again during the message transmission delay period, the link layer should return an error, informing the network layer to wait.

[0105] After the signaling is valid, if the signaling is terminated or invalidated, the network layer's transmission request will no longer be processed, and a link reset message will be returned to inform the network layer to cancel the current processing.

[0106] Furthermore, the signaling of the group inspection nodes under the centralized acquisition system is sent by nodes that meet specific conditions according to the prescribed rules. The signaling level indicates the logical position of the node that sends a certain level of signaling in the network, that is, the node has the same level number. Its function is to instruct the node that receives a certain level of signaling to identify itself and mark itself as being in a lower level of logical position. The node that sends the N-level signaling is responsible for collecting data from the lower-level nodes and forwarding this data to the higher-level nodes at the appropriate time.

[0107] The highest level signaling is defined as level 0 signaling, which is issued by the concentrator. The concentrator is a level 0 node. The node that receives the level 0 signaling is a level 1 node, and its level is 1. The signaling issued by the level 1 node can only be level 1 signaling, and the next level cannot be any other level, and so on. The node that issues the signaling of the maximum level Lmax is the lowest level node. The node that receives the Lmax level signaling is logically the end node in the network. The system defines the maximum level Lmax.

[0108] Signaling flags are used to indicate whether a signaling signal is valid. When a valid signaling signal appears, if the node receiving the valid signaling signal is a node at the same level, it will stop trying to send the signaling signal. A valid signaling signal indicates that the node that sent the signaling is responsible for collecting data from all the lower-level nodes that received the signaling signal and is responsible for forwarding it to the next higher level. An invalid signaling signal indicates that other nodes at the same level are allowed to send the signaling signal.

[0109] The conditions for signaling to be valid are that it is the first time it is run, or when the signaling is invalid, the link layer can initiate the output of the N-level signaling of this node and become an N-level node. The conditions for output are: it has received the N-1 level signaling, and the "current signaling level" in the message is less than the "maximum signaling level"; it has not received any other valid N-level signaling messages after the random delay ends; it has received invalid same-level signaling messages from other nodes, and has not received any new round of N-1 level signaling.

[0110] The condition for invalid signaling refers to the condition for invalid signaling at this level. After issuing signaling, the node should receive an uplink message or a signaling message from the next level within the valid confirmation time of the signaling. If no uplink message or signaling message from the next level is received, the node that issues the N-level signaling should issue an N-level signaling invalid message.

[0111] Forced invalidation of signaling means that upon receiving a new N-1 level signaling message, it is treated as an invalid N-1 level signaling message. If the new N-1 level signaling message is invalid, all N-level nodes compete to send an invalid N-1 level signaling message. After receiving an invalid N-1 level signaling message, they stop competing. If the new N-1 level signaling message is valid, all N-level nodes restart the competition to send a valid N-1 level signaling message.

[0112] Signaling termination refers to the master node using a signaling termination command. At this time, the maximum level in the signaling is set to 0, informing the child nodes to stop sending any uplink messages. The child nodes will no longer send any uplink messages except for competing to forward the signaling termination command.

[0113] Regarding the handling of multiple signaling messages and signaling conflicts, when all N-level nodes that have received N-1 level signaling messages compete for N-level signaling messages, since these nodes may not necessarily receive each other's messages, two nodes may send signaling messages. This situation can be further divided into two cases:

[0114] If two signaling messages are sent at the same time, a conflict will occur. If the node does not receive any signaling message after the valid confirmation period, it is equivalent to the signaling being lost. In this case, peer nodes will still compete for the signaling and send a new signaling message when the conditions are met.

[0115] If two signaling messages appear one after the other, a node that receives both signaling messages will treat the first one as the signaling message and will treat it as if it has only received one signaling message. A node that receives only one signaling message will not be affected by multiple signaling messages.

[0116] Discarding signaling means that if a node has already received a valid signaling message of level N-1 and has become an N-level node, then regardless of whether it holds N-level signaling, it will simply discard the signaling message if it receives another signaling message of level N or higher, without taking any action.

[0117] It should be noted that the signaling address refers to the address of the node that sends the signaling; the signaling time refers to the time when the node sends the signaling, in minutes; and the signaling round refers to the order of signaling, which is a flag. When the signaling round is odd, the flag is 0; when the signaling round is even, the flag is 1.

[0118] A computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, a method for actively reporting power limit exceedance events as described above is executed.

[0119] More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wire segments, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0120] In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless segments, wire segments, optical cables, RF, etc., or any suitable combination thereof.

[0121] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules, units, or units is merely a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units, modules, or components may be combined or integrated into another device, or some features may be ignored or not executed.

[0122] The units may or may not be physically separate. The components shown as units can be one or more physical units, meaning they can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0123] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0124] In particular, according to embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication component, and / or installed from a removable medium. When the computer program is executed by a central processing unit (CPU), it performs the functions defined in the methods of this application. It should be noted that the computer-readable medium described above in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof.

[0125] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0126] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions within the technical scope disclosed in the present invention should be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A signaling packet processing method for proactively reporting power limit exceedance events, characterized in that, Includes the following steps: Determine if a signal has been received; if so, the smart meter will enter a silent period. Read smart meter data and register the smart meter; Determine if the smart meter has been successfully registered; if successful, determine if the channel is busy. If unsuccessful, return to the step of determining whether a signaling has occurred; If the channel is busy, return to the step of determining whether a signaling has occurred; if the channel is idle, receive the signaling and determine its validity. If the signaling is valid, the message frames are buffered according to the signaling priority, and the received message frames are processed in rounds. The condition for valid signaling is that the link layer can initiate the output of the N-level signaling of this node and become an N-level node. The output conditions are: the node has received the (N-1)-level signaling, and the "current signaling level" in the message is less than the "maximum signaling level"; no other valid N-level signaling messages have been received after the random delay; invalid same-level signaling messages from other nodes have been received, and no new round of N-1-level signaling has been received. Message frames are sent according to the channel state, wherein the message frames include either response messages or SOS message frames; If a signaling termination or signaling failure is received, the channel is reset, and processing of response messages or SOS messages ceases.

2. The signaling packet processing method for proactively reporting power limit exceedance events according to claim 1, characterized in that, Based on signaling priority, the received packets are buffered and processed in rounds, including the following steps: The signaling node of the next lower priority sends signaling data to the signaling node of the next higher priority, and the signaling node sends signaling data level by level according to the priority of the signaling, wherein the signaling data includes message frames.

3. The signaling packet processing method for proactively reporting power limit exceedance events according to claim 1, characterized in that, Sending the message frame according to the channel state includes the following steps: Set the avoidance delay duration and start the delay avoidance timer; After the delay avoidance timer expires, the channel is determined to be busy or idle. If the channel is busy, the delay avoidance timer is restarted. If the channel is idle, the response message or SOS message is sent.

4. A signaling packet processing system for proactively reporting power limit exceedance events, characterized in that, The signaling packet processing system executes the signaling packet processing method as described in any one of claims 1-3, including the physical layer, link layer, and network layer; The physical layer is used to transmit and receive binary data bits; The link layer is used to process the received message frames in groups and switch the data receiving mode or the signaling listening mode according to the link information in the message frames. The link layer is also used to send response messages and SOS messages; The network layer is used to determine whether the reported power limit violation event is valid and to send a response message or an SOS message.

5. A method for actively reporting power limit exceedance events, wherein the method is based on the signaling packet processing method for actively reporting power limit exceedance events as described in any one of claims 1-3, characterized in that, Includes the following steps: Determine whether a power limit violation event has occurred in the smart meter; if so, the communication channel of the smart meter is put into a silent period. Obtain the last digit of the smart meter's address and determine the reporting time for the power limit overrun event based on the parity of the last digit of the address. Based on the reporting time, the power limit exceeding event is reported discretely; Determine whether a response frame indicating that the power limit event has been correctly received from the master station has been received. If yes, stop the reporting operation; otherwise, repeat the silent period processing and perform discrete reporting of the power limit event.

6. The method for actively reporting power limit exceedance events according to claim 5, characterized in that, The communication channel of a smart meter undergoes a silent period processing, including the following steps: The duration of the quiet period is set. After a power over-limit event occurs, the smart meter waits for the specified quiet period after the time has passed the whole minute.

7. The method for actively reporting power limit exceedance events according to claim 5, characterized in that, The reporting time for power limit violations is determined based on the parity of the last digit of the address, including the following steps: If the last digit of the address is odd, it will be reported in the a-th second of the next minute after the silence period; If the last digit of the address is even, it will be reported in the b-th second of the next minute after the silence period; Where a = 1 + {(number of reports - 1) * 2}; b = (number of reports - 1) * 2, and the number of reports refers to the number of times the power limit violation event had been reported before this power limit violation event was reported.

8. The method for actively reporting power limit exceedance events according to claim 5, characterized in that, Determining whether a smart meter has experienced a power limit over-limit event includes the following steps: Set the power over-limit threshold and the over-limit duration threshold; If the active power of the smart meter is greater than or equal to the power over-limit threshold, and the duration reaches the over-limit duration threshold, then the smart meter is determined to have experienced a power over-limit event.

9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it performs the signaling packet processing method for actively reporting power limit exceedance events as described in any one of claims 1-3.

Images