Metering system network and method of operation thereof

Abstract

A metering system network is disclosed. The metering system network comprises a head-end system and at least one metering system. The at least one metering system comprises: at least one meter module for metering consumption of a resource; and a communication module communicatively coupled to the at least one meter module and configured to communicate with the head-end system. The head-end system is configured to issue commands to the communication module to control availability of one or more features of the at least one meter module and / or of the communication module based on a configuration of one or more license files received by the head-end system.

Description

[0001] METERING SYSTEM NETWORK AND METHOD OF OPERATION THEREOF

[0002] FIELD OF INVENTION

[0003] The present disclosure is in the field of metering system networks, such as networks comprising metering systems for metering consumption of a resource, e.g. electrical power. The present disclosure relates in particular to metering systems configured to communicate on a network, such as a mesh network, wherein availability of one or more features of the metering systems may be controlled using a license.

[0004] BACKGROUND TO INVENTION

[0005] Centralized electricity meters may be implemented to combat resource theft in high-risk areas. For example, in a centralized electricity meter, one or more electricity meters for metering consumption of electrical power at a premises may be disposed within a secure cabinet, which may be located external to the premises.

[0006] Electricity meters within the cabinet may be in wireless communication with corresponding remote display modules located at the premises to which electrical power is supplied. As such, electrical power consumption information may be relayed to the remote display modules from the corresponding electricity meters.

[0007] Such meters may be managed remotely over a network. For example, the meters may be configured to transmit data corresponding to consumption of a resource to a remote device, such as a head-end system in a network.

[0008] To implement such communication, it is known to implement a communication means coupled to the meters, thereby enabling each meter to be independently responsible for pushing its reading information onto the network.

[0009] A degree of desired functionality of the meters may vary between different customers and different use cases. Furthermore, changes to the functionality of the meters may be required over the lifetime of the meter, e.g. after installation.

[0010] Managing supply and distribution of meters, and more generally of centralized electricity meters, may be complex and inefficient, especially when a range of different functionalities is required.

[0011] It is therefore desirable to provide an efficient, low-cost, low complexity and highly reliable means for supporting supply and distribution of meters having a range of different technical functionalities. It is therefore an aim of at least one embodiment of at least one aspect of the present disclosure to obviate or at least mitigate at least one of the above identified shortcomings of the prior art.

[0012] SUMMARY OF INVENTION

[0013] The present disclosure is in the field of metering system networks, such as networks comprising metering systems for metering consumption of a resource, e.g. electrical power. The present disclosure relates in particular to metering systems configured to communicate on a network, such as a mesh network, wherein availability of one or more features of the metering systems may be controlled using a license.

[0014] According to a fist aspect of the disclosure, there is provided metering system network. The network comprises a head-end system and at least one metering system. The at least one metering system comprises at least one meter module for metering consumption of a resource.

[0015] The at least one metering system comprises a communication module communicatively coupled to the at least one meter module and configured to communicate with the head-end system.

[0016] The head-end system may be configured to issue commands to the communication module to control availability of one or more features of the at least one meter module based on a configuration of one or more license files received by the headend system.

[0017] The head-end system may be configured to issue commands to the communication module to control availability of one or more features of the communication module based on a configuration of one or more license files received by the head-end system.

[0018] Advantageously, such a system may enable metering systems to be deployed containing features that may be selectively enabled, either initially or during lifetime operation, for selected customers. Furthermore, such a system may advantageously simplify supply, distribution and management of metering system products, by minimizing a manufacturing and programming complexity

[0019] That is, the disclosed solution may effectively enable apparent different version of the same device to be distributed. In the disclosed solution, the head-end system effectively extends management of software modules to end-point devices, e.g. meter modules or the communication module, e.g. radio. Thus, the disclosed system advantageously provides a solution to manage features of an end-point device in software, based on licenses, wherein customers may order relevant licenses depending on their specific needs, and without requiring any firmware and / or hardware changes to the end-point devices in the field. Such a solution may enhance commercial opportunities, enabling sales of modular licenses to the customers.

[0020] The commands may comprise a command to enable or disable the one or more features of the at least one meter module and / or the communication module.

[0021] The one of more features of the communication module may comprise a power outage monitoring feature.

[0022] It will be appreciated that such features are provided for purposes of example, and in other embodiments, other features may additionally or alternatively be implemented.

[0023] The one of more features of the at least one meter module may comprises at least one of: a time-of-use feature; a power quality feature; a power control feature; a streetlight control feature; and / or a load profile feature.

[0024] It will be appreciated that such features are provided for purposes of example, and in other embodiments, other features may additionally or alternatively be implemented.

[0025] The at least one metering system and / or the head-end system may be configured to detect an unauthorized availability of the one or more features.

[0026] Optionally, upon such a detection the one or more features may be reconfigured to be unavailable.

[0027] Advantageously, the head-end System effectively provides a single software solution to manage the ordered licenses for all the utility’s devices. That is, the disclosed solution may be the only way to enable and disable features on the endpoint device. Advantageously, the disclosed solution may ensure that it is not possible to enable licensed features those in other ways, such as by tampering with / the end-point devices to forcibly enable a feature.

[0028] Advantageously, should a user attempt to use a feature that has not been paid for, software (e.g. firmware) executing any one or more of the metering module, communication device and / or head-end system, may actively disable the feature.

[0029] A predefined maximum amount of features may be made available for each of the one or more license files received by the head-end system. For example, there may be a predefined limit for the number of devices, e.g. endpoints, assigned into each license. If the predefined maximum number is reached, another new license should be requested by the customer.

[0030] The metering system network may be provided in combination with a license manager. The license manager may be configured to generate the one or more license files.

[0031] In an example, the license manager may comprise a software product. A manufacturer of the metering system may control access to and / or operation of the license manager.

[0032] The metering system network may comprising a plurality of metering systems. Each metering system may comprise: a respective at least one meter module for metering consumption of a resource; and a respective communication module communicatively coupled to the respective at least one meter module and configured to communicate with the head-end system.

[0033] The plurality of metering systems may be configured to form a mesh network.

[0034] The metering system network may comprise a frequency hopping wireless mesh network. The metering system network may be based on an IEEE 802.15.4g / e standard.

[0035] Each meter module may be configured to be addressed by and / or communicate with the head-end system as an individual end-point on the network.

[0036] Each meter module is an electric meter module for metering consumption of single, two or three phase electrical power.

[0037] The at least one metering system may comprises an enclosure, wherein the at least one meter module and at least a portion of the communication module may be disposed within the enclosure.

[0038] According to a second aspect of the disclosure, there is provided a method of operation of a metering system network. The method comprises receiving, at a headend system of the network, one or more license files. The method comprises issuing, by the head-end system and to a communication module of at least one metering system, commands to control availability of one or more features of at least one meter module of the at least one metering system and / or of the communication module based on a configuration of one or more license files

[0039] The method may comprise steps of: requesting, by a user, the one or more license files from a license manager; receiving, from the license manager, the one or more license files; and providing the one or more license files to the head-end system, In some example embodiments, requesting the one or more license files may comprise providing data corresponding to the at least one metering system, wherein the received license is suitable only for controlling availability of features of said at least one metering system.

[0040] Availability of one or more features of the at least one meter module and / or of the communication module may be configured during a process of registration of endpoints on the head-end system.

[0041] Availability of one or more features of the at least one meter module and / or of the communication module may be configured by importing, into the head-end system, and a file comprising data corresponding to the at least one meter module and / or of the communication module.

[0042] The above summary is intended to be merely exemplary and non-limiting. The disclosure includes one or more corresponding aspects, embodiments or features in isolation or in various combinations whether or not specifically stated (including claimed) in that combination or in isolation. It should be understood that features defined above in accordance with any aspect of the present disclosure or below relating to any specific embodiment of the disclosure may be utilized, either alone or in combination with any other defined feature, in any other aspect or embodiment or to form a further aspect or embodiment of the disclosure.

[0043] BRIEF DESCRIPTION OF DRAWINGS

[0044] These and other aspects of the present disclosure will now be described, by way of example only, with reference to the accompanying drawings, wherein:

[0045] Figure 1 depicts a block diagram of an example of a metering systems network, according to an example of the disclosure;

[0046] Figure 2 depicts a block diagram of an example system for pairing an electric meter with a remote display module, according to an embodiment of the disclosure;

[0047] Figure 3 depicts a sequence diagram of a method of operation of a metering system network, according to an embodiment of the disclosure;

[0048] Figure 4 depicts a sequence diagram of a method of operation of a metering system network using MMF file, according to an embodiment of the disclosure; Figure 5 depicts a screenshot of a graphical user interface of the head-end system showing the licenses list; and

[0049] Figure 6 depicts a further screenshot of a graphical user interface of the head-end system showing the “Magno Grid PRO” Meter license features.

[0050] Figure 7 depicts a further screenshot of a graphical user interface of the head-end system showing the “Magno Grid PLUS” Meter license features.

[0051] Figure 8 depicts a further screenshot of a graphical user interface of the head-end system showing the “Magno Grid PLUS” Radio license features.

[0052] DETAILED DESCRIPTION OF DRAWINGS

[0053] Figure 1 depicts an example of a metering systems network 100 according to an example embodiment of the disclosure, wherein the depicted example is a mesh network. The example metering systems network 100 may be a time-synchronized channel hopping (TSCH) network, as defined by IEEE 802.15.4e. The metering systems network 100 may be a network of RF Mesh IP / Wi-SUN (Wireless Smart Utility Network) nodes. The metering systems network 100 is an example of a mesh network upon which the present invention may be implemented. In examples, the metering systems network 100 may comprise a full mesh topology, e.g. where any node can communicate with any node within range, or a partial mesh topology with more limited or selected connectivity between nodes.

[0054] The example metering systems network comprises a head-end system 110. The head-end system 110 may be known in the art as an “AMI Head-End System”, e.g. Advanced Metering Infrastructure Head-End System. The Head-End system 110 may function as a central processing system that transmits and / or receives data, streams of data, data packets and / or messages from nodes 105a - 105h of the metering systems network 100, as described in more detail below. The head-end system 110 may generate and / or process the data. In examples, the head-end system 110 may be communicably coupled to a further system, such as a cloud based system (not shown), for generating and / or processing the data.

[0055] The head-end system 110 may, for example, be configured to acquire meter module data and to monitor parameters that may be acquired from meter modules. The head-end system 110 may, for example, be configured to manage connectivity and scheduling of collection of data from metering modules. The head-end system may also be configured to control / enables secure access to meter modules for configuration and software updates.

[0056] The example metering systems network 100 of Figure 1 may comprise a root node 115. The root node 115 of the metering systems network 100 may be configured for communicating with the nodes 105a - 105h to perform operations such as retrieving data from the nodes 105a - 105h and / or transmitting data to the head-end system 110. In some examples, the root node 115 may also operate as a node similar to other nodes 105a - 105h. In examples, the root node 115 may comprise a gateway device. The root node 115 may be configured to transmit and receive data to / from the head-end system 110 via backhaul 120, such as the Internet, an intranet, or any other data communication network.

[0057] Although only a single root node 115 is depicted for illustrative purposes, it will be understood that the mesh network 100 may comprise more than one root node 115.

[0058] Similarly, the depicted metering systems network 100 comprises multiple nodes 105a-105h. Each node 105a-105h may be an end-node. For purposes of example, only nodes 105a-105h are depicted, but it will be understood that substantially more than eight nodes may be implemented.

[0059] In examples, each node 105a - 105h may comprise a device for metering and / or controlling a resource.

[0060] In examples, each node 105a - 105h may comprise a metering system comprising a communication module communicatively coupled to at least one meter module and configured to communicate with the head-end system

[0061] In some examples, each meter module in a metering system may be configured to effectively operate as an end node, e.g. one or more of example nodes 105a - 105h may be a meter module in a metering system.

[0062] In such examples, each meter module may comprise circuitry and / or components for metering a consumption of a resource, e.g. electricity, and / or controlling access to the resource, such as by a service disconnect switch or the like. In an example, the metering system network 100 may be associated with a utility network. In such an example, the nodes 105a - 105h may comprise circuitry and / or components for metering the resource, for determining various operating characteristics of the utility network, and / or for transmitting collected data through the mesh network 100 to the head-end system 110 via the root node 115.

[0063] The nodes 105a - 105h forming the metering system network 100 may be effectively provided in layers, as annoted in Figure 1. In this example, the root node 115 forms layer 0. Nodes 105a, 105b that are communicably coupled directly to the root node 115 form a first layer, “Layer 1 ”, of the metering system network 100. Similarly, nodes 105c - 105e that are communicably coupled to the metering system network 100 through a “Layer 1 ” node form a second layer, “Layer 2”, of the metering system network 100. Similarly, nodes 105f — 105h that are communicably coupled to the mesh network 100 through a “Layer 2” node form a third layer, “Layer 3”, of the metering system network 100. IN an example, for data to propagate from the root node 115 to a Layer 3 of the metering system network 100 would require three “hops” of the data.

[0064] In the example mesh network 100 of Figure 1 , each node 105a-105h may be configured to implement a protocol stack to enable communication therebetween, e.g. a protocol stack implementing at least a transport layer and a network layer, as defined by the Open Systems Interconnection model (OSI model) or the Transmission Control Protocol / lnternet Protocol (TCP / IP) model.

[0065] Referring to Figure 2, there is depicted a block diagram of an example metering system 200 connected in a metering system network, e.g. the metering system network 100 of Figure 1.

[0066] The example metering system 200 comprises a plurality of electric meters 205- 0..n. In use, each electric meter 205-0..n may be paired with a corresponding remote display module 210-0..n. For example, a first electric meter 205-0 is paired with a first remote display module 210-0, etc.

[0067] In use, each electric meter 205-0..n may be configured for metering electricity consumption by a load at an associated premises. That is, each electric meter 205-0..n may be configured for metering a current and or voltage of at least one phase of an electric power supply, such as an electrical power supply to a domestic, residential or commercial premises. Each electric meter 205-0..n may be for metering a consumption of electrical power.

[0068] In a non-limiting example, the metering system 200 may comprise an enclosure 215. The plurality of electric meters 205-0..n are provided within the enclosure 215. The enclosure 215 may be provided as a robust, secure cabinet, such as a lockable cabinet, e.g. a cabinet of meters. In an example use case, the enclosure 215 may be mounted on a pole, such as a utility pole that may be used to support overhead power lines. In other examples the enclosure 215 may be mounted at ground level, such as on a plinth.

[0069] In the simplified example embodiment of Figure 2, a motherboard 225, denoted “CPU”, is communicatively coupled to each electric meter 205-0..n. The motherboard 225 couples the electric meters 205-0..n to a communications module 230, denoted NIC. In an example embodiment, the communications module 230 comprises a Network Interface Card. The motherboard 225 and the communications module 230 may collectively be considered as a communications module.

[0070] Also depicted is an antenna 235. The antenna is for providing RF communications between the communications module 230 and each remote display module 210-0..n.

[0071] Each remote display module 210-0..n also comprises a respective antenna for receiving communications from the antenna 235 of the metering system 200. In some embodiments, each remote display module 210-0..n may be configured as a receiver only, and may not be configured for transmission of data. In embodiments, more than one antenna may be implemented.

[0072] .Also depicted is a remote device 255, denoted “AMI Head-End System”. The remote device 255 may, for example, be a server or cloud based device. The remote device 255 may correspond to the head-end system 110 of the example metering system network of Figure 1 .

[0073] The remote device 255 may communicate with each end point, e.g. each electric meter 205-0..n and / or the communications module 230 via a network 260. The network 260 may, for example correspond to any of layers 0 to 3 as depicted in the example metering system network of Figure 1 .

[0074] Operation of the example metering system 200 and the head-end system connected in a metering system network is now described with reference to the sequence diagram of Figure 3.

[0075] A “user” is depicted. The user may be, for example, a utility company, hereafter “the utility”.

[0076] Also depicted is a “Command Center”. The command center may be, for example the head-end system as described above. “Command Center” may be a name given to software executing on the head-end system. Hereafter, the Command Center of Figure 3 will be referred to as the head-end system.

[0077] Also depicted is a “CPU”. The CPU may correspond to the motherboard 225 of the example metering system 200 in Figure 2, or more generally may correspond to the communications module of such a metering system 200.

[0078] Also depicted is a “License Manager”. The license manager may, for example, be a software product at a supplier of the metering system 200, or at a supplier of components of the metering system 200 such as meter modules, e.g. electric meters 205-0..n, Also depicted is a “meter”, which may correspond to a meter module, e.g. electric meters 205-0.. n.

[0079] In an initial step, a Meter Module File (MMF) corresponding to a new meter may be imported to the head-end system. The MMF may be based on a file provided by the meter manufacturer (which may also be an entity running the license manager). The MMF may, for example, comprise a meter serial number, or information based on or derived from the meter serial number. According to the Figure 4, it’s also possible to both assign licenses and enable features automatically by importing the same MMF. It produces the same result as represented in the Figure 3, the only difference is that the Head-End System does for each device automatically, without any user dependency.

[0080] That is, in some examples the MMF may be imported into the head-end system (command center) prior to deployment such that when the meter module is later deployed in the field and tries to communicate, the head-end system may perform relevant checks that the meter module is in an inventory, such that a process of authentication may commence.

[0081] In effect, this stage may effectively update an inventory list at the head-end system, wherein the inventory list comprises details of meter modules purchased by the utility.

[0082] As depicted, at a later stage the CPU of the metering system may send an “I n it push”. This may be, for example, a request for authentication by the head-end system of a newly deployed meter module. It will be appreciated that this stage may be depicted as simplified in the sequence diagram of Figure 3, and in other examples such authentication may require further communication between the head-end system and the CPU, such as transfer of information relating to capabilities and features of the meter module.

[0083] In this example, the meter module has Time-of-Use (TOU) and Power Quality features, which are disabled by default as depicted in the top right hand side of Figure 3.

[0084] After authentication the meter module may operate with a “normal status”, as depicted. A process may execute on the head-end system to “Verify Meter Feature Flags”, e.g. verify that TOU and Power Quality features are supported and / or remain disabled.

[0085] At a later stage, the utility may select a feature to be applied to one or more meter modules or radios of metering systems. In the depicted, non-limiting example, the utility may select a license for the TOU and Power Quality features, collectively termed ’’Magno Grid PLUS Meter”. The utility may request the license manager, e.g. the metering system manufacturer, provide such a license. In response, the license manager may generate a license file (denoted “.lie”) and provide said license file to the user.

[0086] The user may subsequently import the license file to the head-end system. The head-end system will then process the lice file, e.g. activate any license defined by the license file.

[0087] In some embodiments, a graphical user interface on the head end system may indicate an allocation of meter modules or communication modules to licenses. This is depicted in Figures 5, 6, 7 and 8, which show screenshots of graphical user interfaces of the head-end system. Figure 5 shows the available licenses to the head-end system. In that example, it can be seen that three example licenses are available: “Magno Grid PLUS Meter” for controlling TOU and Power Quality features at meter modules; “Magno Grid PLUS Radio” for controlling Power Outage Monitoring features by the CPU; and “Magno Grid PRO Meter” for controlling TOU, Power Quality, Power Control, Streetlight Control and Load profile features at meter modules. It will be understood that this is for purposes of example only, and other amounts / types of licenses may be implemented support other combinations of features. Figure 6 shows an example user interface of the head-end system for managing enabling and disabling of features of meter modules.

[0088] In the example graphical user interface, features for each meter module or communication module may be selected based on license availability. The depicted “Endpoint Features Management” screen may be updated to indicate any license file imported to the head-end system.

[0089] In a non-limiting example, the license may be for up to 1000 meter modules. The user may select which meter module a license feature is to be applied to, such as by providing meter module serial number information relating to the selected meter to the head-end system. This is depicted in Figure 3 as “Grant License to customer serial number (MeterNo)”

[0090] Following this, the selected meters may be assigned to the license. Licensed features may remain disabled by default.

[0091] The utility may request that licensed features are enabled. This is depicted in Figure 3 as “Enable TOU, Power Quality”. In some example, the utility may do this by manipulating the graphical user interface, as described above with reference to Figures 5, 6, 7 and 8.

[0092] At this stage, a process denoted “Endpoint Licenses Management” executes at the head-end system, resulting in issuance of a “Meter Feature Reconfiguration” command. In the depicted example, the command is an instruction to enable TOU and Power Quality features.

[0093] In other non-limiting examples (not depicted in Figure 3), the commands may comprise instructions to enable / disable one of more features of the communication module, such as a power outage monitoring feature;

[0094] In other non-limiting examples (not depicted in Figure 3), the commands may comprise instructions to enable / disable one of more features of the module, such as: a time-of-use feature; a power quality feature; a power control feature; a streetlight control feature; and / or a load profile feature.

[0095] That is, the command may be to enable or disable the one or more features of the at least one meter module and / or the communication module.

[0096] Upon receipt of the command by the CPU, firmware / software on the CPU executes to enable the TOU and Power Quality features at the meter module. Following receipt by the meter module, the TOU and Power Quality features at the meter module are enabled.

[0097] In example embodiments, an acknowledgement (denoted “ACK”) may be provided by the meter module to the CPU, which may in turn indicate to the head-end system that reconfiguration of the meter module was successful. This latter stage is indicated in Figure 3 as “Meter Reconfiguration command response (Success)”.

[0098] The head-end system will then update a status of the license from “in Progress” to “Success”, thereby registering that a license has been applied to the relevant meter module to enable the licensed TOU and Power Quality features.

[0099] Thereafter, in some embodiments a verification of feature availability may be carried out. In this example depicted in Figure 3, this may include receiving configuration data from the meter module by issuance of a “Get Endpoint Configuration command”, which may cause the CPU to acquire data from the meter module and subsequently issue a response to the head-end system comprising data corresponding to the acquired data. In this manner, a configuration of the meter module that is stored at the head-end system that was originally provided by the “Send init push” may be updated to reflect the modified configuration of the meter module, following enablement of the TOU and Power Quality features.

[0100] In some examples, such a verification may occur periodically, to ensue only licenses features of the meter and / or communication module are enabled.

[0101] Although the example described with reference to Figure 3 relates to availability of features of the meter module, it will be understood that in other embodiments the described method may additionally or alternatively applicable to availability of features of the communication module, e.g. the CPU or radio coupled to the CPU.

[0102] Advantageously, the described head-end system may provide a single software solution to manage the ordered licenses for all of the utility’s devices. The above described methods may be an only way to enable and disable features on meter modules and / or communication devices in metering systems. Furthermore, the described method / process may ensure that is not possible to enable / disable such features in other ways, such as by hacking the metering system to forcibly enable a feature. Advantageously, the head-end system may automatically detect an unauthorized device that has a feature enabled.

[0103] Although the disclosure has been described in terms of preferred embodiments as set forth above, it should be understood that these embodiments are illustrative only and that the claims are not limited to those embodiments. Those skilled in the art will be able to make modifications and alternatives in view of the disclosure, which are contemplated as falling within the scope of the appended claims. Each feature disclosed or illustrated in the present specification may be incorporated in any embodiments, whether alone or in any appropriate combination with any other feature disclosed or illustrated herein.

Claims

CLAIMS1 . A metering system network comprising: a head-end system; and at least one metering system comprising: at least one meter module for metering consumption of a resource; and a communication module communicatively coupled to the at least one meter module and configured to communicate with the head-end system; wherein the head-end system is configured to issue commands to the communication module to control availability of one or more features of the at least one meter module and / or of the communication module based on a configuration of one or more license files received by the head-end system.

2. The metering system network of claim 1 , wherein the commands comprise a command to enable or disable the one or more features of the at least one meter module and / or the communication module.

3. The metering system network of claim 1 or 2, wherein at least one of: the one of more features of the communication module comprises a power outage monitoring feature; the one of more features of the at least one meter module comprises at least one of: a time-of-use feature; a power quality feature; a power control feature; a streetlight control feature; and / or a load profile feature.

4. The metering system network of any preceding claim, the at least one metering system and / or the head-end system is configured to detect an unauthorized availability of the one or more features, and optionally wherein upon such a detection the one or more features is reconfigured to be unavailable.

5. The metering system network of any preceding claim, wherein a predefined maximum amount of features is made available for each of the one or more license files received by the head-end system.

6. The metering system network of any preceding claim in combination with a license manager, wherein the license manager is configured to generate the one or more license files.

7. The metering system network of any preceding claim, comprising a plurality of metering systems, each metering system comprising: a respective at least one meter module for metering consumption of a resource; and a respective communication module communicatively coupled to the respective at least one meter module and configured to communicate with the head-end system wherein the plurality of metering systems are configured to form a mesh network.

8. The metering system network of any preceding claim, wherein the network is a frequency hopping wireless mesh network, and optionally wherein the network is based on an IEEE 802.15.4g / e standard.

9. The metering system network of any preceding claim, wherein each meter module is configured to be addressed by and / or communicate with the head-end system as an individual end-point on the network.

10. The metering system network of any preceding claim, wherein each meter module is an electric meter module for metering consumption of single, two or three phase electrical power.11 . The metering system network of any preceding claim wherein the at least one metering system comprises an enclosure, wherein the at least one meter module and at least a portion of the communication module are disposed within the enclosure.

12. A method of operation of a metering system network, the method comprising: receiving, at a head-end system of the network, one or more license files; issuing, by the head-end system and to a communication module of at least one metering system, commands to control availability of oneor more features of at least one meter module of the at least one metering system and / or of the communication module based on a configuration of one or more license files13. The method of claim 12, comprising a preceding step of: requesting, by a user, the one or more license files from a license manager, receiving, from the license manager, the one or more license files, and providing the one or more license files to the head-end system,14. The method of claim 13, wherein requesting the one or more license files comprises providing data corresponding to the at least one metering system, wherein the received license is suitable only for controlling availability of features of said at least one metering system.

15. The method of any of claim 12 to 14, wherein: availability of one or more features of the at least one meter module and / or of the communication module is configured during a process of registration of endpoints on the head-end system; and / or availability of one or more features of the at least one meter module and / or of the communication module is configured by importing, into the headend system, and a file comprising data corresponding to the at least one meter module and / or of the communication module.

Images