METHODS AND DEVICES FOR MANAGING LOAD SHEDDING IN A RESOURCE DISTRIBUTION NETWORK

Abstract

Load shedding is implemented in a distribution network to prevent overconsumption. The network includes at least one main distribution point and multiple meters configured to measure a customer's consumption of that resource and to periodically transmit customer information to the main distribution point, representing the customer's consumption over a defined time period. An overall forecast consumption is determined, based on the customer information transmitted by the meters, for all meters within the defined time period. One or more load shedding periods are determined by comparing the overall forecast consumption to a predefined overall threshold. For each period, a number of meters to be shed is determined, along with a list of eligible meters. The meters to be shed are selected from this list.And a load shedding command is sent to them which concerns one or more future occurrences within the specified time range. FIG.4.

Description

Title of the invention: METHODS AND DEVICES FOR MANAGING LOAD SHEDDING IN A RESOURCE DISTRIBUTION NETWORK Technical field

[0001] The various exemplary embodiments described in the present disclosure relate to load shedding in a distribution network of a resource, for example a distribution network of electricity, gas, heat, etc. in order to control demand and avoid overconsumption which could lead to a collapse of the distribution network.

[0002] BACKGROUND

[0003] Document US2022 / 0376504A1 describes a load shedding method in an electrical network triggered following detection of an event leading to insufficient energy generation in the network.

[0004] There is a need for a method of managing load shedding in a distribution network that responds to variations in demand.

[0005] SUMMARY

[0006] A first aspect of the present disclosure relates to a method for managing load shedding in a distribution network of a resource, the network comprising at least one network head and a plurality of meters configured to measure consumption of said resource by a customer, transmit to the network head information representative of the customer's consumption, receive a load shedding command from the network head and trigger a switch from an operating mode without load shedding to an operating mode with load shedding as a function of said command.This load shedding management method further comprises steps for determining, from the information representative of the customer's consumption, an overall forecast consumption over a time range for all the meters; determining one or more load shedding periods for said time range, by comparing the overall forecast consumption with a predefined overall threshold; determining one or more meters eligible for load shedding, for the load shedding period(s), by comparing the information representative of the customer's consumption over the load shedding period with a predefined customer threshold; selecting one or more meters to be load shedding from among the meters eligible for load shedding, to obtain a target gain making it possible to compensate for a difference between a maximum of the overall forecast consumption over the load shedding period and the predefined overall threshold; sending a load shedding command to the . selected counters, said command relating to one or more future occurrences of said time range and specifying one or more load shedding periods for said time range.

[0007] Advantageously, only information representative of the customer's consumption in non-load shedding mode is taken into account, for determining the overall forecast consumption and / or for determining the meters eligible for load shedding.

[0008] According to a first embodiment, the load shedding management method comprises a step of calculating a number of meters to be shedding as a function of the ratio between the difference to be compensated and the predefined customer threshold, the selection of said number of meters to be shedding from among the eligible meters being done for example randomly.

[0009] According to this first embodiment, the load shedding command comprises, for example, a start and end indication, or duration, for each load shedding period for said time range. For example, the start indications transmitted to different meters for the same load shedding period are offset in time relative to each other.

[0010] According to a second embodiment, the load shedding management method comprises a step for determining a load shedding gain for the eligible meters, by comparing information representative of the customer's consumption in non-load shedding mode, with information, learned during a learning phase, representative of the customer's consumption in load shedding mode, and the selection of the meters to be load shedding is a function of said load shedding gains.

[0011] For example, during the learning phase, for each time range considered, a load shedding command is sent to each meter in time slots, in order to obtain information representative of the customer's consumption in load shedding mode, for each time slot of each time range, the load shedding periods being timed to said time slots.

[0012] For example, the selection of the meters to be unloaded comprises a determination of a first number of counters greater than the number of counters necessary to obtain the target gain, and a random selection of a second number of counters, less than the first number, to obtain the target gain.

[0013] For example, the selection of the meters to be shed comprises a determination from among the eligible meters taken in order of decreasing load shedding gain, of a first, second, and third group comprising respectively Q1, Q2 and Q3 eligible meters, the sum of the load shedding gains of the Q1+Q2 meters of the first and second groups making it possible to reach the target gain, and the sum of the load shedding gains of the Q2+Q3 meters of the second and third groups making it possible to reach the target gain, then a selection from among the Q1+Q2+Q3 eligible meters of Q2+Q3 meters to be unloaded.

[0014] According to this second embodiment, the load shedding command comprises, for example, a number of load shedding periods for said time range and an identifier of each load shedding period.

[0015] Also disclosed is a computer program product comprising instructions which when executed by at least one processor cause the implementation of such a load shedding management method.

[0016] Also disclosed is a computer-readable storage medium comprising instructions that when executed by a processor cause such a load shedding management method to be implemented. In one embodiment, the storage medium is non-transitory.

[0017] A second aspect of the present disclosure relates to a network head device which comprises means for implementing such a load shedding management method in a distribution network.

[0018] A third aspect of the present disclosure relates to a method of load shedding by a meter belonging to a distribution network of a resource, the meter being configured to measure a consumption of said resource by a customer and to transmit to a network head of the distribution network customer information representative of the consumption of the customer over a determined time range. The method further comprises a step of receiving a load shedding command from the network head, the load shedding command specifying one or more load shedding periods to be implemented during one or more future occurrences of the determined time range.

[0019] In a first example, the load shedding command comprises a start and end, or duration, indication for each load shedding period. In a second example, the load shedding command comprises a number of load shedding periods for said time range and an identifier of each load shedding period. Advantageously, the load shedding is triggered and / or terminated at a random time relative to the load shedding periods specified in the load shedding command.

[0020] Also disclosed is a computer program product comprising instructions which when executed by at least one processor cause the implementation of such a load shedding method.

[0021] Also disclosed is a computer-readable storage medium comprising instructions that when executed by a processor cause such a load shedding method to be implemented. In one embodiment, the storage medium is non-transitory.

[0022] A fourth aspect of the present disclosure relates to a metering device comprising means for implementing such a load shedding method.

[0023] The headend and meter devices may be constituted by software means, i.e. instructions intended to be executed by a circuitry to carry out one or more or all of the operations or steps to be carried out by the headend and / or the meter, in application of the methods described in the present disclosure. The circuitry may be constituted by dedicated circuitry. It may also be constituted from one or more processors and one or more memories comprising one or more computer program codes, said processors, memories and computer codes being configured to cause the headend and / or the meter to carry out one or more or all of the steps of the methods described in the present disclosure. BRIEF DESCRIPTION OF THE FIGURES

[0024] The exemplary embodiments will be better understood in light of the detailed description which follows and the accompanying drawings, which are given for illustration purposes only and are therefore not limiting of the present disclosure.

[0025] Figure [Fig.l] is a diagram of an example distribution network.

[0026] Figure [Fig.2] shows several customer load curves over a range of determined time.

[0027] Figure [Fig.3] represents an overall forecast curve over the same determined time range.

[0028] Figure [Fig.4] is a diagram describing the steps of a load shedding management method intended to be implemented in a network head of a distribution network.

[0029] Figure [Fig.5] describes the step of selecting the meters to be unloaded in a first embodiment.

[0030] Figure [Fig.6] describes the step of selecting the meters to be unloaded in a second embodiment.

[0031] [Fig.7] describes a particular implementation of the step of selecting the meters to be unloaded in the second embodiment.

[0032] [Fig.8] reproduces the load curves of [Fig.2] showing two load shedding periods corresponding to two time slices of the determined time range.

[0033] Figure [Fig.9] is a diagram describing the steps of a load shedding method intended to be implemented in a meter of a distribution network.

[0034] Figure [Fig.10] is a block diagram of a device for implementing a network head or a meter according to the present disclosure. DETAILED DESCRIPTION

[0035] Various exemplary embodiments will now be described in more detail, as of non-limiting examples, with reference to the drawings which accompany the present disclosure and which illustrate certain exemplary embodiments.

[0036] The specific structural and functional details described herein are non-limiting examples. The exemplary embodiments described herein are subject to various modifications and alternative forms. The subject matter of the disclosure may be embodied in many different forms and should not be construed as being limited to only the embodiments presented herein as illustrative examples. It should be understood that there is no intention to limit the embodiments to the particular forms described in the remainder of this document.

[0037] The present disclosure applies to any distribution network of a resource comprising at least one network head and a plurality of meters measuring the consumption of said resource. This may be, for example, a distribution network for electricity, gas, water, heat, etc. In the remainder of the description, the distribution network which will be described is an electricity distribution network. This is an illustrative example which is not limiting.

[0038] In the non-limiting example of [Fig.l], a distribution network 10 comprises at least one network head 11 which is provided to communicate via a sub-distributor 12 with a plurality of meters 13 which are installed at customers' premises 14. For example, the network head 11 communicates with the sub-distributor 12 via a wireless telecommunications network 15. The wireless communications network 15 may be a GPRS, UMTS, LTE, 5G network, or a narrowband loT (Internet-of-Things) network. For example, the sub-distributor 12 communicates with the meters 13 via the powerline network by powerline communication (PLC).

[0039] A meter 13 installed at a customer 14 is configured to measure consumption by the customer 14 of the resource which is distributed via the distribution network 10. For example, when the network 10 is an electricity distribution network, the meter 13 measures the electricity consumption of the customer 14.

[0040] The meters 13 are further configured to transmit to the network head 11 customer information representative of the consumption of the customer 14 over a determined time range. For example, the meters 13 transmit information representative of the daily consumption every day. This customer information includes, for example, a consumption value per time slot of a determined duration, for example every 15 minutes. The values ​​transmitted for each 15-minute time slot during the day make it possible to establish a load curve for the customer for the day.

[0041] The network head 11 is configured to transmit load shedding commands to one or more meters 13.

[0042] The meters 13 are configured to carry out load shedding, in accordance with the load shedding commands that they receive from the network head 11. For example, a meter 13 can carry out load shedding by disconnecting one or more electricity-consuming elements at a customer 14, for example a hot water tank and / or one or more radiators. Such load shedding makes it possible to reduce consumption and thus avoid a risk of collapse of the distribution network.

[0043] For example, the exchange of data between the meters 13 and the network head 11 is done by data frames conforming to the DLMS / COSEM protocol.

[0044] In the embodiments which will be described below by way of example, a determined time range corresponds to a specific day of the week (i.e. Sunday, Monday, etc.). The network head 11 then stores the customer information for each of the days of the week taken separately. This embodiment makes it possible to take into account the differences in consumption profiles depending on the day of the week.

[0045] Other embodiments are possible, using other determined time ranges. For example, a determined time range may correspond to any working day or any non-working day. In this case, the network head 11 stores on the one hand the customer information for working days and on the other hand the customer information for non-working days. In another example, the determined time range corresponds to a specific week or month of the year. In this case, the network head 11 stores the customer information for each week or for each month of the year taken separately. In this example, it is possible to take into account differences in consumption profiles depending on the weeks of holidays or the seasons of the year.

[0046] [Fig.2] represents the load curves of four customers C2i, C22, C23 and C24 over a given time range, which in this example corresponds to a given day of the week (day D). In this example, it is assumed that day D for which the customer information was collected is a day without load shedding for customers C2[ to C24. In [Fig.2], a threshold SL, called a predefined customer threshold, has been represented, which corresponds to a theoretical maximum consumption for a customer.

[0047] [Fig.3] represents a forecast curve representing the overall forecast consumption, obtained for the same time range, i.e. for day D, from the load curves of the four customers in [Fig.2].

[0048] In [Fig.3], a threshold SG is shown, called the predefined global threshold, which corresponds to a theoretical maximum consumption for all customers C2i to C24. We observe in [Fig.3] that the predefined global threshold SG is exceeded during two periods, called the overconsumption period, Pi between 7:30 a.m. and 10:05 a.m. and P2 between 4:00 p.m. and 8:00 p.m. The maximum consumption during the overconsumption period Pi is noted Maxi and the maximum consumption during the period of overconsumption P2 is noted Max2.

[0049] The overconsumption periods Pi and P2 are reported in [Fig.2]. We then observe that the customers who exceed the predefined customer threshold SL during the overconsumption period Pi are customers C2i and C23. And the customers who exceed the predefined customer threshold SL during the overconsumption period P2 are customers C2i and C22. In other words: customer C2i exceeds the predefined customer threshold SL during the two overconsumption periods Pi and P2; customer C22 exceeds the predefined customer threshold SL during the overconsumption period P2; customer C23 exceeds the predefined customer threshold SL during the overconsumption period Pi; and customer C24 never exceeds the predefined customer threshold SL.

[0050] According to the embodiment, each period of overconsumption may give rise to one or more load shedding periods. For example, a period of overconsumption may constitute a single load shedding period or may correspond to a plurality of load shedding periods.

[0051] [Fig. 4] is a flowchart representing the main steps of a load shedding management method intended to be implemented by the network head 11. In step 40, the network head 11 receives from a plurality of meters of the distribution network customer information representative of the customer's consumption over a determined time range (for example a day D of the week). In step 41, the network head 11 determines, from the information representative of the customers' consumption, an overall forecast consumption over a time range for all the meters. In step 42, the network head 11 determines one or more load shedding periods D; from the received customer information. In step 43, the network head 11 determines one or more meters eligible for load shedding for each load shedding period D;, by comparing the customer information over the load shedding period with the predefined customer threshold SL.In step 44, the network head 11 selects the meters to be load shed from among the eligible meters. In step 45, the network head 11 sends a load shedding command to the selected meters concerning one or more future occurrences of the determined time range (for example for day D of the following week).

[0052] In the remainder of the description, two embodiments will be described in detail as non-limiting examples.

[0053] In the first embodiment, the overconsumption periods each constitute a single load shedding period. Thus, using the example described in figures [Fig.2] and [Fig.3], in step 42, the network head 11 determines two load shedding periods Di=Pi and D2=P2. And in step 43, it determines the eligible meters for each of the two periods Di and D2 by comparing the customer consumption information over the load shedding periods Di and D2 with the predefined customer threshold SL. In the example from [Fig.2], it results from this comparison that: customer 21 is eligible for load shedding during both periods Di and D2; customer 22 is eligible for load shedding during period D2; customer 23 is eligible for load shedding during period Di; and customer 24 is not eligible for load shedding.

[0054] [Fig.5] describes the following step 44 in this first embodiment. As illustrated in [Fig.5], step 44 is broken down into two steps 51 and 52 which are executed for each load shedding period D; identified in step 42.

[0055] In step 51, the network head 11 determines a number Ni of meters to be unloaded over the period D; to compensate for the difference A , between the maximum of the overall forecast consumption Max; over each unloading period D; and the predefined overall threshold SG: A ; = MaXi - SG . For example, the number of meters Ni to be unloaded is a function of the ratio between the difference to be compensated A ; and the predefined customer threshold SL. For example N^INT^j + l-

[0056] Then in step 52, the network head 11 selects Ni meters to be load shed for the load shedding period D; from among the meters which have been determined as eligible for load shedding for the period D; in step 43. The selection can be random. It can also take into account the type of subscription of the customer, and / or the number of load sheddings carried out in a given past for the eligible customers, and / or the number of load shedding periods identified for each eligible customer, etc.

[0057] Then, in step 45, the network head sends a load shedding command to the selected meters for at least one future occurrence of the time range considered (for example day D of one or more following weeks). For example, in the example of [Fig.2], assuming that the selected meters are the meters of customers C2[ and C22, the command sent to the meter of customer C2[ specifies two load shedding periods Di and D2 and the command sent to the meter of customer C22 specifies one load shedding period D2.

[0058] For example, the load shedding command includes a start indication Td and an end indication Tf (or alternatively a duration indication) for each load shedding period of the determined time range. This command is for example transmitted in a DLMS / COSEM data frame in the form of a COSEM object with a load shedding OBIS code, i.e. a “Limit” object with the OBIS code indicated in the table below: OBIS IC object code ABCDEF Limit 71, limit 0 b 17 0 e 255

[0059] The data frame includes a field containing the useful data (payload in English). This field includes for example:

[0060] - one byte to indicate the number of load shedding periods applicable to the meter to which the order is intended;

[0061] - for each load shedding period, one byte to indicate the time and one byte for indicate the minute of the start of the load shedding; and one byte to indicate the hour and one byte to indicate the minute of the end of the load shedding.

[0062] Advantageously, it is ensured that all the meters concerned by the same load shedding period do not start load shedding at exactly the same time and do not stop their load shedding at exactly the same time. This would in fact cause load changes that would be detrimental to the balance of the distribution network.

[0063] In a first example, the commands sent to the different meters contain start indications Td for the same load shedding period offset in time relative to each other. For example, the meter of customer C2i receives a load shedding start command with a start indication at 4:00 p.m. and an end indication at 8:00 p.m. for the period P2. And the meter of customer C22 receives a load shedding start command with a start indication at 4:01 p.m. offset by one minute in time for the same period P2. In the case where the command contains an end indication, this is offset by the same duration (so in this example the end indication is equal to 8:01 p.m. for the meter of customer C22).

[0064] In another example, the start and end indications Td and Tf are the same for all selected meters. And each meter starts and stops the load shedding according to a random variable managed by the meter which implies a start and an end at a random time included in an interval around the start indications Td and end Tf respectively. For example, each meter starts the load shedding randomly in the interval [Td-2'30”; Td+2'30”] and stops it randomly in the interval [Tr2'30”; Tf+2'30”].

[0065] In the second embodiment, during a learning phase, the network head 11 learns the impact of load shedding for each meter. This learning is independent of the load shedding needs. It can be done once or regularly, for example every year, once in summer and once in winter. The learning is done on real data. For example, during the learning phase, for each time range considered, a load shedding command is sent to each meter in time slices, in order to obtain information representative of the customer's consumption in load shedding mode for each time slice of each time range. For example, when the time range considered corresponds to a specific day of the week, a load shedding command is sent to all the meters every 15 minutes for each specific day of the week in order to learn the response of the meters to the load shedding commands.For example when the time range . considered is a day, it can be divided into 96 time slots of 15 minutes each.

[0066] [Fig. 6] describes step 44 in this second embodiment. As illustrated in [Fig. 7] step 44 is broken down into two steps 61 and 62 which are executed for each load shedding period D; identified in step 42. In step 61, the network head 11 determines a load shedding gain for the meters eligible for load shedding, by comparing the consumption information transmitted by the meters in non-load shedding mode, with the information learned during the learning phase, which is representative of the customer's consumption in load shedding mode. The network head 11 then selects in step 62 the meters to be load shedding, according to the load shedding gains obtained for the meters eligible for load shedding.

[0067] For example, the network head determines a number of meters necessary to obtain the target gain, from the load shedding gains of the eligible meters taken in order of decreasing load shedding gain. For example, the network head adds the load shedding gains of the meters in the decreasing direction until reaching the target gain and selects the corresponding meters for load shedding. This embodiment makes it possible to target the customers for whom the load shedding will have the greatest impact.

[0068] In another example, the network head determines, from the load shedding gains of the eligible meters, a number of meters greater than the number of meters necessary to obtain the target gain, then makes a selection from among the meters determined to achieve the target gain. The selection is for example random or can take into account various parameters as mentioned above. This embodiment makes it possible to target the customers for whom the load shedding will have the greatest impact while avoiding always selecting the same customers.

[0069] [Fig. 7] describes an exemplary embodiment of the selection step 62. In this example, step 62 is broken down into two steps 71 and 72. In step 71, the network head 11 determines, from among the eligible meters taken in order of decreasing load shedding gain, a first, a second, and a third group of meters comprising respectively Q1, Q2 and Q3 eligible meters, such that the sum of the load shedding gains of the Q1+Q2 meters of the first and second groups makes it possible to achieve the target gain, and that the sum of the load shedding gains of the Q2+Q3 meters of the second and third groups makes it possible to achieve the target gain. In step 72, a selection of Q2+Q3 meters to be load shedding is then carried out from among the Q1+Q2+Q3 meters determined, for example randomly. For example, the Q1+Q2 counters of the first and second groups are obtained by adding the load shedding gains of the counters in decreasing order until the target gain is reached.Then the Q2+Q3 counters of the second and third group are obtained by adding the load shedding gains of the counters in decreasing order from the start of the second. group until the target gain is reached.

[0070] Preferably, the load shedding periods are aligned with the time slots used during the learning phase. The simplest method is to use learning time slots and load shedding periods that have the same duration (for example 15 minutes). It is also possible to use load shedding periods whose duration is a multiple of the learning time slots. Thus, in this second embodiment, the overconsumption periods Pi and P2 shown in figures [Fig. 2] and [Fig. 3] correspond to one or more load shedding periods D;. [Fig. 8] represents the same load curves as [Fig.2], on which we have shown, as an example, two load shedding periods corresponding to two learning time slots: a load shedding period D,_A which is part of the first overconsumption period Pi and which is between 9:30 and 9:45, and a load shedding period D,_H which is part of the second overconsumption period P2 and which is between 17:30 and 17:45 (with 0 < A < B < 96). We observe in [Fig.8] that during the load shedding period D,_A, only customer C2i is eligible for load shedding. And during the load shedding period Di=B, customers C2i and C22 are both eligible.

[0071] In this second embodiment, the load shedding command sent in step 45 includes an indication of a number of load shedding periods for the time range concerned as well as an identifier of each of the load shedding periods. For example, if the time range corresponds to a day, and the load shedding periods are set at 15 minutes, there are 96 possible load shedding periods over the day. The command will indicate how many load shedding periods are planned for the recipient of the command, as well as the identifiers of the periods to be subject to load shedding among the 96 possibilities. In this embodiment, advantageously, each counter starts and stops the load shedding according to a random variable managed by the counter which implies a start and an end at a random time relative to the start and end of the load shedding period.

[0072] For the sake of simplicity, the embodiments described here relate to load shedding controls with a single load shedding level (the control is binary). This is not limiting. The embodiments described here can be easily adapted by those skilled in the art to allow several load shedding levels (in the case of customer installations with several load shedding circuits).

[0073] Preferably, for the determination of the overall forecast consumption and for the determination of the customers eligible for load shedding, only the information representative of the customer's consumption in non-load shedding mode is taken into account. For example, if the customer was subject to load shedding on day D of the current week, the network head 11 uses for this customer the information from the last day D which was not subject to load shedding for this customer (instead of using the information transmitted for the day of the current week).

[0074] [Fig. 9] is a flowchart representing the main steps of a load shedding method intended to be implemented by a meter in the distribution network. In step 90, the meter receives the command that was transmitted by the network head in step 45. In step 91, the meter reads the contents of the command and programs one or more load sheddings from the load shedding start and end indications contained in the command.

[0075] In one embodiment, the meter programs the load shedding(s) so that they are triggered and / or stopped according to a random variable managed by the meter which involves a start and end of load shedding at a random time relative to the start and end of the load shedding period specified in the load shedding command.

[0076] The network head 11 and the meters 13 can for example be implemented in the form of a device as described in the figure [Fig.10]. This device referenced 100 comprises a printed circuit board 101 on which a communication bus 102 connects a processor 103, a random access memory 104, a storage medium 111, possibly an interface 105 for connecting a screen 106, a series of connectors 107 for connecting user interface devices or modules such as a mouse or a trackpad 108 and a keyboard 109, a wireless network interface 110 and / or a wired network interface 112. Depending on the required functionalities, in particular depending on whether the device 100 is used in a network head 11 or a meter 13, the device may implement only part of the above.For example, a meter 13 is generally not connected to a mouse, trackpad, or keyboard, nor to a wireless network or a wired network, as information exchanges with the meter are usually carried out by powerline communication. Some modules in FIG. [Fig. 10] may be internal or externally connected, in which case they are not necessarily an integral part of the device itself. For example, the display 106 may be a display that is only connected to the device 100 under specific circumstances, or the device 100 may be controlled by another device having a display, and in this case the device 100 does not have a display 106 or an interface 105.

[0077] The memory 111 contains one or more software codes that, when executed by the processor 103, enable the head-end 11 to perform the load shedding management method described herein. In an exemplary embodiment, a removable storage medium 113, such as a USB flash drive, may also be connected. For example, the detachable storage medium 113 may contain the software codes to be downloaded into the memory 111.

[0078] The processor 103 may be any type of processor such as a central processing unit ("CPU") or a dedicated microprocessor such as an embedded microcontroller or a digital signal processor ("DSP").

[0079] The device 100 may also include other components commonly found in computer systems, such as an operating system, queue managers, device drivers, or one or more network protocols that are stored in the memory 111 and executed by the processor 103.

[0080] Those skilled in the art will understand that all block diagrams presented herein represent conceptual, exemplary views of circuits incorporating the principles of the disclosure.

[0081] Each described function, block, step may be implemented in hardware, software, firmware, middleware, microcode, or any suitable combination thereof. If implemented in software, the functions or blocks of the block diagrams and flowcharts may be implemented by computer program instructions / software codes, which may be stored or transmitted on a computer-readable medium, or loaded onto a general-purpose computer, a special-purpose computer, or other programmable processing apparatus and / or a system, such that the computer program instructions or software codes executing on the computer or other programmable processing apparatus create the means to implement the functions described in this disclosure.

[0082] Although aspects of the present disclosure have been described with reference to particular embodiments, it should be understood that these embodiments only illustrate the principles and applications of the present disclosure. It is therefore understood that numerous modifications may be made to the illustrative embodiments and that other arrangements may be devised without departing from the spirit and scope of the disclosure as determined on the basis of the claims and their equivalents.

[0083] The advantages and solutions to the problems have been described above with respect to specific embodiments of the invention. However, the advantages, benefits, solutions to the problems, and any element that may cause or result in such advantages, benefits, or solutions, or cause such advantages, benefits, or solutions to become more pronounced, should not be construed as a critical, required, or essential feature or element of any or all of the claims.

Claims

Claims

1. Method for managing load shedding in a distribution network of a resource, the network comprising at least one network head and a plurality of meters configured to: - measure consumption of said resource by a customer, - transmit to the network head information representative of the customer's consumption, - receive a load shedding command from the network head and trigger a switch from an operating mode without load shedding to an operating mode with load shedding as a function of said command, characterized in that it comprises steps for: - determining, from the information representative of the customers' consumption, an overall forecast consumption over a time range for all the meters, - determining one or more load shedding periods for said time range, by comparing the overall forecast consumption with a predefined overall threshold,- determine one or more meters eligible for load shedding, for the load shedding period(s), by comparing information representative of the customer's consumption over the load shedding period with a predefined customer threshold, - select one or more meters to be load shedding from among the meters eligible for load shedding, to obtain a target gain to compensate for a difference between a maximum of the overall forecast consumption over the load shedding period and the predefined overall threshold, - send a load shedding command to the selected meters, said command relating to one or more future occurrences of said time range and specifying one or more load shedding periods for said time range.,

2. Load shedding management method according to claim 1, characterized in that it comprises a step of calculating a number of meters to be load shedding as a function of the ratio between the difference to be compensated and the predefined customer threshold.

3. Load shedding management method according to claim 2, characterized in that the selection of said number of meters from among the eligible meters is random.

4. A load shedding management method according to claim 1, characterized in that the load shedding command comprises an indication of start and end, or duration, for each load shedding period for said time range.

5. Load shedding management method according to one of claims 1 to 4, characterized in that only information representative of the customer's consumption in non-load shedding mode is taken into account for determining the overall forecast consumption.

6. Load shedding management method according to one of claims 1 to 5, characterized in that only information representative of the customer's consumption in non-load shedding mode is taken into account for determining the meters eligible for load shedding.

7. Network head device comprising means for implementing a load shedding management method in a distribution network according to any one of claims 1 to 6.

8. Method of load shedding by a meter belonging to a distribution network of a resource, the meter being configured to measure consumption of said resource by a customer and to transmit to a network head of the distribution network customer information representative of the consumption of the customer over a determined time range, the method comprising a step of receiving a load shedding command from the network head, the load shedding command specifying one or more load shedding periods to be implemented during one or more future occurrences of the determined time range.

9. A load shedding method according to claim 8, characterized in that the load shedding command comprises an indication of start and end, or duration, for each load shedding period for said time range.

10. Load shedding method according to one of claims 8 or 9, characterized in that the load shedding is triggered and / or terminated at a random time relative to the load shedding periods specified in the load shedding command.

11. Metering device comprising means for implementing a load shedding method according to any one of claims 8 to 10.

12. Computer program product comprising instructions which when executed by at least one processor cause the implementation of a load shedding management method according to any one of claims 1 to 6.

13. Computer program product comprising instructions which when executed by at least one processor cause the implementation of a load shedding method according to any one of claims 8 to 10.

14. A non-transitory computer-readable storage medium comprising instructions which when executed by a processor cause implementation of a load shedding management method according to any one of claims 1 to 6.

15. A non-transitory computer-readable storage medium comprising instructions which when executed by a processor cause an offloading method according to any one of claims 8 to 10 to be implemented.

Images