CA2851003A1 - Utility meter with utility-configurable sealed data - Google Patents
Utility meter with utility-configurable sealed data Download PDFInfo
- Publication number
- CA2851003A1 CA2851003A1 CA2851003A CA2851003A CA2851003A1 CA 2851003 A1 CA2851003 A1 CA 2851003A1 CA 2851003 A CA2851003 A CA 2851003A CA 2851003 A CA2851003 A CA 2851003A CA 2851003 A1 CA2851003 A1 CA 2851003A1
- Authority
- CA
- Canada
- Prior art keywords
- utility meter
- sealed
- meter
- data
- memory
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01D—MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
- G01D4/00—Tariff metering apparatus
- G01D4/02—Details
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/66—Updates of program code stored in read-only memory [ROM]
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02B—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO BUILDINGS, e.g. HOUSING, HOUSE APPLIANCES OR RELATED END-USER APPLICATIONS
- Y02B90/00—Enabling technologies or technologies with a potential or indirect contribution to GHG emissions mitigation
- Y02B90/20—Smart grids as enabling technology in buildings sector
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
- Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
- Y04S20/00—Management or operation of end-user stationary applications or the last stages of power distribution; Controlling, monitoring or operating thereof
- Y04S20/30—Smart metering, e.g. specially adapted for remote reading
Abstract
A system is provided with a utility meter. The utility meter includes a memory storing a table, wherein the table specifies modifiable data that may be modified when the utility meter is sealed and non-modifiable data that may not be modified when the utility meter is sealed. The utility meter also includes a processing device configured to access the table stored on the memory or another memory to determine whether specific data stored on the memory or another memory may be modified when the utility meter is sealed.
Description
UTILITY METER WITH UTILITY-CONFIGURABLE SEALED DATA
BACKGROUND
100011 The subject matter disclosed herein relates to utility meters, and more particularly to methods and systems for specifying data that may or may not be modified upon sealing of the utility meters.
BACKGROUND
100011 The subject matter disclosed herein relates to utility meters, and more particularly to methods and systems for specifying data that may or may not be modified upon sealing of the utility meters.
[0002] In certain markets where utility meters (e.g., electricity meters) are sold, regulatory requirements dictate that certain metering parameters and/or firmware (e.g., firmware components or functions) must be sealed. In a sealed state, the metering parameter and/or firmware cannot be changed (e.g., data cannot be modified over a communication port) without certification or recertification by a governing body. These regulatory requirements make it difficult for meter manufacturers to define which metering parameters and/or firmware functions need to be sealed for each market. In current meters, the list of metering parameters and/or firmware functions that must be sealed is hard-coded (i.e., program statements written into a computer program itself). As a result, a meter manufacturer may have to utilize different, e.g., firmware packages for different regions based on differences in the regulatory requirements due to a lack of flexibility available to the meter manufacturer in defining what parameters and/or firmware functions are to be sealed.
BRIEF DESCRIPTION
BRIEF DESCRIPTION
[0003] Certain embodiments commensurate in scope with the originally claimed invention are summarized below. These embodiments are not intended to limit the scope of the claimed invention, but rather these embodiments are intended only to provide a brief summary of possible forms of the invention. Indeed, the invention may encompass a variety of forms that may be similar to or different from the embodiments set forth below.
100041 In accordance with a first embodiment, a system is provided with a utility meter. The utility meter includes a memory storing a table, wherein the table specifies modifiable data that may be modified when the utility meter is sealed and non-modifiable data that may not be modified when the utility meter is sealed. The utility meter also includes a processing device configured to access the table stored on the memory or another memory to determine whether specific data stored on the memory or another memory may be modified when the utility meter is sealed.
100051 In accordance with a second embodiment, a non-transitory computer-readable medium having computer executable code stored thereon is provided. The code includes instructions for accessing an external table stored on a memory of a utility meter or another memory external to the utility meter. The external table specifies modifiable data that may be modified when the utility meter is sealed and non-modifiable data that may not be modified when the utility meter is sealed. The code also includes instructions for determining, based on the external table, whether specific data stored on the memory or another memory may be modified when the utility meter is sealed.
100061 In accordance with a third embodiment, a system is provided with a memory.
The memory stores a table, wherein the table specifies modifiable data that may be modified when a utility meter is sealed or non-modifiable data that may not be modified when the utility meter is sealed or both the modifiable data and the non-modifiable data.
The system also includes a processing device configured to access the table stored on the memory or another memory to determine whether specific data stored on the memory or another memory may be modified when the utility meter is sealed.
BRIEF DESCRIPTION OF THE DRAWINGS
[0007] These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
[0008] FIG. 1 is a system-level diagram of an embodiment of a utility network with smart meters (e.g., utility meters) connected to an advanced metering infrastructure (AMI) network;
[0009] FIG. 2 is a detailed diagram of an embodiment of a smart meter (e.g., utility meter) of FIG. I connected to the AMI network;
[0010] FIG. 3 is an example of a table (e.g., seal table) specifying a seal flag protection status of data (e.g., of other tables);
[0011] FIG. 4 is an example of a table (e.g., seal table) specifying a seal flag protection status of data (e.g., functions, procedures, parameters, etc.);
[0012] FIG. 5 is an example of a table (e.g., seal table) specifying a seal flag protection status of data (e.g., procedure steps); and [0013] FIG. 6 is flow diagram illustrating an embodiment of a method for determining whether specific data may be modified when the smart meter (e.g., utility meter) is sealed.
DETAILED DESCRIPTION
[0014] One or more specific embodiments of the present invention will be described below. In an effort to provide a concise description of these embodiments, all features of an actual implementation may not be described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another.
Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.
[0015] When introducing elements of various embodiments of the present invention, the articles "a," "an," "the," and "said" are intended to mean that there are one or more of the elements. The terms "comprising," "including," and "having" are intended to be inclusive and mean that there may be additional elements other than the listed elements.
[0016] Certain markets impose regulatory requirements that designate that specific metering parameters and/or firmware (e.g., firmware components or functions) for utility meters (e.g., electricity meters) must be sealed. Sealing a meter may consist of setting a flag in the meter's non-volatile memory via a communication port. Once sealed, the meter cannot be unsealed until its cover is removed (this typically involves removing a physical seal first). Unsealing the meter may consist of pressing a series of buttons (e.g., RESET and TEST buttons) in an appropriate sequence. In a sealed state, the metering parameter and/or firmware cannot be changed (e.g., data cannot be modified over a communication port) without certification or recertification of the meter by a governing body. These regulatory requirements make it difficult for meter manufacturers to define which metering parameters and/or firmware functions need to be sealed for each market.
In addition, in current meters, the list of metering parameters and/or firmware functions that must be sealed is hard-coded (i.e., program statements written into a computer program itself), e.g., within the firmware. As a result, a meter manufacturer may have to utilize different, e.g., firmware packages for different regions based on different regulatory requirements. This limits the flexibility available to the meter manufacturer in defining what parameters and/or firmware functions are to be sealed.
[0017] Present embodiments relate to a utility meter (e.g., smart meter such as a smart electricity meter, water meter, natural gas meter, etc.), which includes a memory that stores a table (e.g., seal table) that specifies which data (e.g., metering data, metering parameters, firmware functions or components, etc.) may be modified when the utility meter is sealed. In particular, the seal table may specify modifiable data that may be modified when the utility meter is sealed and non-modifiable data that may not be modified when the utility meter is sealed. In certain embodiments, the seal table is an
100041 In accordance with a first embodiment, a system is provided with a utility meter. The utility meter includes a memory storing a table, wherein the table specifies modifiable data that may be modified when the utility meter is sealed and non-modifiable data that may not be modified when the utility meter is sealed. The utility meter also includes a processing device configured to access the table stored on the memory or another memory to determine whether specific data stored on the memory or another memory may be modified when the utility meter is sealed.
100051 In accordance with a second embodiment, a non-transitory computer-readable medium having computer executable code stored thereon is provided. The code includes instructions for accessing an external table stored on a memory of a utility meter or another memory external to the utility meter. The external table specifies modifiable data that may be modified when the utility meter is sealed and non-modifiable data that may not be modified when the utility meter is sealed. The code also includes instructions for determining, based on the external table, whether specific data stored on the memory or another memory may be modified when the utility meter is sealed.
100061 In accordance with a third embodiment, a system is provided with a memory.
The memory stores a table, wherein the table specifies modifiable data that may be modified when a utility meter is sealed or non-modifiable data that may not be modified when the utility meter is sealed or both the modifiable data and the non-modifiable data.
The system also includes a processing device configured to access the table stored on the memory or another memory to determine whether specific data stored on the memory or another memory may be modified when the utility meter is sealed.
BRIEF DESCRIPTION OF THE DRAWINGS
[0007] These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
[0008] FIG. 1 is a system-level diagram of an embodiment of a utility network with smart meters (e.g., utility meters) connected to an advanced metering infrastructure (AMI) network;
[0009] FIG. 2 is a detailed diagram of an embodiment of a smart meter (e.g., utility meter) of FIG. I connected to the AMI network;
[0010] FIG. 3 is an example of a table (e.g., seal table) specifying a seal flag protection status of data (e.g., of other tables);
[0011] FIG. 4 is an example of a table (e.g., seal table) specifying a seal flag protection status of data (e.g., functions, procedures, parameters, etc.);
[0012] FIG. 5 is an example of a table (e.g., seal table) specifying a seal flag protection status of data (e.g., procedure steps); and [0013] FIG. 6 is flow diagram illustrating an embodiment of a method for determining whether specific data may be modified when the smart meter (e.g., utility meter) is sealed.
DETAILED DESCRIPTION
[0014] One or more specific embodiments of the present invention will be described below. In an effort to provide a concise description of these embodiments, all features of an actual implementation may not be described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another.
Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.
[0015] When introducing elements of various embodiments of the present invention, the articles "a," "an," "the," and "said" are intended to mean that there are one or more of the elements. The terms "comprising," "including," and "having" are intended to be inclusive and mean that there may be additional elements other than the listed elements.
[0016] Certain markets impose regulatory requirements that designate that specific metering parameters and/or firmware (e.g., firmware components or functions) for utility meters (e.g., electricity meters) must be sealed. Sealing a meter may consist of setting a flag in the meter's non-volatile memory via a communication port. Once sealed, the meter cannot be unsealed until its cover is removed (this typically involves removing a physical seal first). Unsealing the meter may consist of pressing a series of buttons (e.g., RESET and TEST buttons) in an appropriate sequence. In a sealed state, the metering parameter and/or firmware cannot be changed (e.g., data cannot be modified over a communication port) without certification or recertification of the meter by a governing body. These regulatory requirements make it difficult for meter manufacturers to define which metering parameters and/or firmware functions need to be sealed for each market.
In addition, in current meters, the list of metering parameters and/or firmware functions that must be sealed is hard-coded (i.e., program statements written into a computer program itself), e.g., within the firmware. As a result, a meter manufacturer may have to utilize different, e.g., firmware packages for different regions based on different regulatory requirements. This limits the flexibility available to the meter manufacturer in defining what parameters and/or firmware functions are to be sealed.
[0017] Present embodiments relate to a utility meter (e.g., smart meter such as a smart electricity meter, water meter, natural gas meter, etc.), which includes a memory that stores a table (e.g., seal table) that specifies which data (e.g., metering data, metering parameters, firmware functions or components, etc.) may be modified when the utility meter is sealed. In particular, the seal table may specify modifiable data that may be modified when the utility meter is sealed and non-modifiable data that may not be modified when the utility meter is sealed. In certain embodiments, the seal table is an
4 external (i.e., separate from the computer program or code) table (e.g., that holds values and parameters used by the computer program) that is not hard-coded into the computer program (e.g., firmware). When the utility meter is unsealed, the seal table may be modified (e.g., the seal table and all other tables are writable). When the utility meter is sealed, the seal table may not be modified. The utility meter also includes a processor that accesses the seal table stored on the memory to determine whether specific data (e.g., stored on the memory or another memory) may be modified when the utility meter is sealed. In certain embodiments, the processor may block modification of the non-modifiable data when the utility meter is sealed, while enabling modification of the modifiable data when the utility meter is sealed. The seal table provides flexibility to the meter manufacturer in defining what metering parameters and functions are to be sealed without having to use multiple, different firmwares for different regions with different regulatory requirements. Instead, the meter manufacturer may utilize a common seal table and modify it to specify the sealed metering parameters and functions for a specific region.
[0018] With the foregoing in mind, it may be useful to describe an embodiment of a utility network 10 with smart meters 18 (e.g., smart utility meters such as smart electrical meters, water meter, natural gas meter, etc.) connected to an AMI network 14, such as the system illustrated in FIG. 1. As described in greater detail below, each of the smart meters 18 may include a memory that stores a table (e.g., seal table) that specifies whether certain data (e.g., metering data, metering parameters, firmware functions or components, etc.) may be modified when the smart meter 18 is sealed. The data specified as modifiable by the seal table may be modified via the utility network 10, e.g., to modify metering data or parameters, modify procedures, and/or update firmware. Each of the smart meters 18 may also include a processing device (e.g., one or more processors for conducting metering operations) to access the seal table to determine what data may be modified when the utility meter 18 is sealed. In certain embodiments, the meter 18 may include multiple memory blocks. Some of the memory blocks may be internal to the processing device, while other memory blocks may be external to the processing device.
[0019] As depicted, the AMI network system 10 may include one or more host units 12 that are connected to an AMI network 14 and designed to provide oversight operations of the AMI network system 10. Each host unit 12 in the AMI network system 10 may include processors and/or other data processing circuitry that may be operably coupled to a storage and a memory to execute instructions for carrying out a variety of oversight operations of other utilities in the AMI network system 10. For example, in certain embodiments, each host unit 12 may be a utility control center. In addition to sending commands and data to other utilities in the AMI network system 10, utility control centers may provide oversight operations of a smart grid system, such as monitoring and directing power produced by one or more power generation stations. In other embodiments, the utility control centers may report data about the AMI network system to external sources, such as operation centers or other hosts of other AMI
networks.
[0020] In addition to host units 12, the AMI network system 10 may include customer residences 16 that include utility meters 18. Utility meters 18 may be located on commercial buildings, apartment residences, or any other entity that is connected to the utility network 10. The host unit 12 may issue commands or send data, such as firmware updates, to a plurality of utility meters 18. In certain embodiments, the host unit 12 may include a table in storage to maintain status information of the utility meters 18 connected to the AMI network 14. The host unit 12 may monitor the table to monitor the status of each utility meter 18 and determine which utility meters 18 require updates (e.g., firmware updates).
[0021] Moving from a system level to a specific component, further detail of the hardware of the utility meter 18 is illustrated in FIG. 2. In the embodiments illustrated in FIGS. 1 and 2, the utility meter 18 is a smart meter (e.g., electricity meter, water meter, natural gas meter, etc.). Smart meters may record the consumption of utilities (e.g., electricity, water, natural gas, etc.), report utility consumption values back to host units 12 on the AMI network 14, and receive data and commands from hosts on the AMI
network 14. The utility meter 18 of FIG. 2 includes a main board 22 and a network interface 28. The main board 22 includes a microprocessor 24 and a memory 26 and may include other components of a microcontroller or embedded system. The microprocessor 24 may execute instructions to carry out the operation of the smart meter 18.
As noted above, the utility meter 18 may include a processing device that includes one or more microprocessors 24. These instructions may be encoded in programs or code stored in a tangible non-transitory computer-readable medium, such as the memory 26 and/or other storage. As noted above, the memory 26 may include one or more memory blocks.
Some memory blocks may be internal to the microprocessor 24 or processing device, while other memory block may be external to the microprocessor 24 or processing device.
[0022] The memory 26 stores metering data (e.g., meter configuration data, calibration data, kWh usage, water usage, natural gas usage, etc.), metering parameters (e.g., measuring quantities, demand interval length, etc.), and firmware components (e.g., functions, tasks, modules, threads, etc.), which are read from the utility meter 18 in a plurality of tables. The memory 26 also stores an additional table (e.g., seal table) that identifies modifiable data that may be modified when the utility meter 18 is sealed and/or non-modifiable data that may not be modified when the utility meter 18 is sealed. The seal table may specify the modifiable and/or non-modifiable data. In certain embodiments, the seal table may be stored in a memory separate from the other metering tables. In certain embodiments, the granularity or resolution of the seal table may vary from a table level to an individual table entry level as described in greater detail below.
The seal table specifically specifies what metering data, metering parameters, and/or firmware components may or may not be modified when the utility meter 18 is sealed. In certain embodiments, all of the tables (including the seal table) are external tables (i.e., not hard-coded into the programs or instructions stored on the memory 26) that hold values and parameters for the metering data, metering parameters, and/or firmware components. In addition, in certain embodiments, all of the tables (including the seal table) may be defined in accordance with the ANSI C12.19 standard. The ANSI
C12.19 allows for manufacturer-defined tables as well as standard tables, all of which may be defined in the seal table. The seal table itself cannot be modified when the utility meter 18 is sealed. Instead, the seal table or seal table portion can only be modified when the utility meter 18 is unsealed.
[0023] As mentioned above, the memory 26 stores instructions for the microprocessor 24 to execute. For example, the memory 26 stores instructions for accessing the seal table (e.g., external table) stored on the memory 26. The memory 26 also stores instructions for determining, based on the seal table, whether specific data (e.g., metering data, metering parameters, firmware components, etc.) stored on the memory 26 may be modified when the utility meter 18 is sealed. The memory 26 further stores instructions for blocking modification of the seal table when the utility meter 18 is sealed. The memory 26 yet further stores instructions for blocking modification of the non-modifiable .
data when the utility meter 18 is sealed and/or for enabling modification of the modifiable data when the utility meter 18 is sealed.
[0024] Based on the instructions stored in the memory 26, the microprocessor 24 may access the seal table (e.g., external table) stored on the memory 26 to determine whether specific data (e.g., metering data, metering parameters, firmware components, etc.) stored on the memory 26 or another memory may be modified when the utility meter 18 is sealed. The microprocessor 24 may block modification of non-modifiable data (including the seal table) when the utility meter is sealed. The microprocessor 24 may also enable modification of the modifiable data when the utility meter 18 is sealed. As mentioned above, the seal table provides flexibility to a meter manufacturer in defining what metering parameters and functions are to be sealed without having to use multiple, different firmwares for different regions with different regulatory requirements. Instead, the meter manufacturer may utilize a common seal table and modify it to specify the sealed metering parameters and functions for a specific region. In certain embodiments, a memory external to the utility meter 18 may include the seal table. For example, the seal table may be included in a remote location from the utility meter 18. In addition, in certain embodiments, a processing device external to the utility meter 18 may access a memory (e.g., internal or external to the utility meter 18) to access the seal table. For example, a third party radio (e.g., SSN) may include the seal table and control access to the meter's tables.
100251 To enable communication over the AMI network 14, the microprocessor 24 may be connected to a network interface 28. The network interface 28 may enable the microprocessor 24 to communicate over the AMI network 14. The network interface 28 may send information related to what data is sealed and receive update data (e.g., firmware update data) over the AMI network 14 and communicate with the microprocessor 24 to record time stamps and time intervals between communications over the AMI network 14. The time data may be stored in the memory 26 of the utility meter 18 in any appropriate data structure such as a table, an array, a linked list, specified registers, variables, or a combination thereof.
[00261 As mentioned above, the granularity or resolution of the seal table may vary from a table level to an individual table entry level. FIGS. 3-5 provide examples of seal tables specifying a seal flag protection status of data. Other embodiments of the seal tables are contemplated. The number of columns and rows in the seal tables may vary.
Also, the information included in the seal tables may vary. FIG. 3 illustrates a seal table 30 with a resolution at the table level. The seal table 30 includes columns for a standard table number 32, a table name 34, and a seal flag protection status 36. The seal flag protection status 36 indicates whether a specific table is modifiable (not seal flag protected) or non-modifiable (seal flag protected) when the utility meter 18 is sealed. For example, in seal table 30, tables 1 and 3 are seal flag protected. A general configuration table, a unit of measure table, and a demand control table represent a few examples of tables that may be listed among the tables on the seal table 30.
100271 FIG. 4 illustrates a seal table 38 with a resolution at an individual table entry level. The seal table 38 includes columns for a name 40 of a particular function, procedure, or parameter, a description 42 of the particular function, procedure, or parameter, and a seal flag protection status 44. The seal flag protection status 44 is as described above in FIG. 3. In the seal table 38, the function, procedure, or parameter B is seal flag protected. Entries in the general configuration table, a unit of measure table, and a demand control table represent a few examples of tables that may include individual entries that may be listed on the seal table 38. This could be specified as an entry name, an entry index, or an offset into the table.
[0028] FIG. 5 illustrates a seal table 46 with a resolution at an individual table entry level. The seal table 46 includes columns for a procedure step number 48 for a particular procedure, a step description 50, and a seal flag protection status 52. The seal flag protection status 52 is as described above in FIG. 3. In the seal table 46, procedure step 2 is seal flag protected. Steps in a cold start procedure (e.g., to return the meter 18 to its default state) or a clear data procedure (e.g., to clear billing and diagnostic data in the meter 18) represent a few examples of procedures that may include individual entries that may be listed on the seal table 46.
[0029] FIG. 6 is flow diagram illustrating an embodiment of a computer-implemented method 54 for determining whether specific data may be modified when the utility meter 18 is sealed. In the method 54, the microprocessor 24 receives a request from the AMI
network 14, via the network interface 28, to modify (or update) data (e.g., metering data, metering parameters, firmware components, etc.) (block 56). Alternatively, the microprocessor 24 may receive a request to provide an indication of what data may be modified and/or what data may not be modified. In response to the request, the microprocessor 24 accesses an external table (e.g., seal table) from the memory 26 (block 58). As mentioned above, the seal table specifies what data (e.g., metering data, metering parameters, firmware components, etc.) may or may not be modified when the utility meter 18 is sealed. Based on the seal table, the microprocessor 24 determines whether the data specified for modification may be modified when the utility meter 18 is sealed (block 60). Upon determining whether the data is modifiable (block 62), the microprocessor 24 determines the seal flag protection status of the data from the seal table. If the data is modifiable (i.e., not seal flag protected), the microprocessor 24 modifies or updates the specified data stored on the memory 26 (e.g., in the other tables excluding the seal table) (block 64). If the data is non-modifiable (i.e., seal flag protected), the microprocessor 24 blocks modification or updating of the specified data (block 66).
[00301 Technical effects of the disclosed embodiments include providing techniques and systems to provide flexibility to the meter manufacturer in defining what metering parameters and functions are to be sealed without having to use multiple, different firmwares for different regions with different regulatory requirements.
Specifically, the disclosed embodiments include providing the utility meter 18 (e.g., smart meter such as a smart electricity meter, water meter, natural gas meter, etc.) with memory 26 storing a table (e.g., seal table) that specifies whether certain data (e.g., metering data, metering parameters, firmware functions or components, etc.) may be modified when the utility meter 18 is sealed. The seal table is an external table (i.e., separate from the computer programs or code) that is not hard-encoded into the computer programs or code stored on the memory 26. This allows the meter manufacturer to utilize a common seal table that may be modified to specify the sealed metering parameters and functions for a specific region without having to utilize multiple, different firmwares. In certain embodiments, the seal table may be stored external to the utility meter 18.
100311 While there have been described herein what are considered to be preferred and exemplary embodiments of the present invention, other modifications of these embodiments falling within the scope of the invention described herein shall be apparent to those skilled in the art.
[0018] With the foregoing in mind, it may be useful to describe an embodiment of a utility network 10 with smart meters 18 (e.g., smart utility meters such as smart electrical meters, water meter, natural gas meter, etc.) connected to an AMI network 14, such as the system illustrated in FIG. 1. As described in greater detail below, each of the smart meters 18 may include a memory that stores a table (e.g., seal table) that specifies whether certain data (e.g., metering data, metering parameters, firmware functions or components, etc.) may be modified when the smart meter 18 is sealed. The data specified as modifiable by the seal table may be modified via the utility network 10, e.g., to modify metering data or parameters, modify procedures, and/or update firmware. Each of the smart meters 18 may also include a processing device (e.g., one or more processors for conducting metering operations) to access the seal table to determine what data may be modified when the utility meter 18 is sealed. In certain embodiments, the meter 18 may include multiple memory blocks. Some of the memory blocks may be internal to the processing device, while other memory blocks may be external to the processing device.
[0019] As depicted, the AMI network system 10 may include one or more host units 12 that are connected to an AMI network 14 and designed to provide oversight operations of the AMI network system 10. Each host unit 12 in the AMI network system 10 may include processors and/or other data processing circuitry that may be operably coupled to a storage and a memory to execute instructions for carrying out a variety of oversight operations of other utilities in the AMI network system 10. For example, in certain embodiments, each host unit 12 may be a utility control center. In addition to sending commands and data to other utilities in the AMI network system 10, utility control centers may provide oversight operations of a smart grid system, such as monitoring and directing power produced by one or more power generation stations. In other embodiments, the utility control centers may report data about the AMI network system to external sources, such as operation centers or other hosts of other AMI
networks.
[0020] In addition to host units 12, the AMI network system 10 may include customer residences 16 that include utility meters 18. Utility meters 18 may be located on commercial buildings, apartment residences, or any other entity that is connected to the utility network 10. The host unit 12 may issue commands or send data, such as firmware updates, to a plurality of utility meters 18. In certain embodiments, the host unit 12 may include a table in storage to maintain status information of the utility meters 18 connected to the AMI network 14. The host unit 12 may monitor the table to monitor the status of each utility meter 18 and determine which utility meters 18 require updates (e.g., firmware updates).
[0021] Moving from a system level to a specific component, further detail of the hardware of the utility meter 18 is illustrated in FIG. 2. In the embodiments illustrated in FIGS. 1 and 2, the utility meter 18 is a smart meter (e.g., electricity meter, water meter, natural gas meter, etc.). Smart meters may record the consumption of utilities (e.g., electricity, water, natural gas, etc.), report utility consumption values back to host units 12 on the AMI network 14, and receive data and commands from hosts on the AMI
network 14. The utility meter 18 of FIG. 2 includes a main board 22 and a network interface 28. The main board 22 includes a microprocessor 24 and a memory 26 and may include other components of a microcontroller or embedded system. The microprocessor 24 may execute instructions to carry out the operation of the smart meter 18.
As noted above, the utility meter 18 may include a processing device that includes one or more microprocessors 24. These instructions may be encoded in programs or code stored in a tangible non-transitory computer-readable medium, such as the memory 26 and/or other storage. As noted above, the memory 26 may include one or more memory blocks.
Some memory blocks may be internal to the microprocessor 24 or processing device, while other memory block may be external to the microprocessor 24 or processing device.
[0022] The memory 26 stores metering data (e.g., meter configuration data, calibration data, kWh usage, water usage, natural gas usage, etc.), metering parameters (e.g., measuring quantities, demand interval length, etc.), and firmware components (e.g., functions, tasks, modules, threads, etc.), which are read from the utility meter 18 in a plurality of tables. The memory 26 also stores an additional table (e.g., seal table) that identifies modifiable data that may be modified when the utility meter 18 is sealed and/or non-modifiable data that may not be modified when the utility meter 18 is sealed. The seal table may specify the modifiable and/or non-modifiable data. In certain embodiments, the seal table may be stored in a memory separate from the other metering tables. In certain embodiments, the granularity or resolution of the seal table may vary from a table level to an individual table entry level as described in greater detail below.
The seal table specifically specifies what metering data, metering parameters, and/or firmware components may or may not be modified when the utility meter 18 is sealed. In certain embodiments, all of the tables (including the seal table) are external tables (i.e., not hard-coded into the programs or instructions stored on the memory 26) that hold values and parameters for the metering data, metering parameters, and/or firmware components. In addition, in certain embodiments, all of the tables (including the seal table) may be defined in accordance with the ANSI C12.19 standard. The ANSI
C12.19 allows for manufacturer-defined tables as well as standard tables, all of which may be defined in the seal table. The seal table itself cannot be modified when the utility meter 18 is sealed. Instead, the seal table or seal table portion can only be modified when the utility meter 18 is unsealed.
[0023] As mentioned above, the memory 26 stores instructions for the microprocessor 24 to execute. For example, the memory 26 stores instructions for accessing the seal table (e.g., external table) stored on the memory 26. The memory 26 also stores instructions for determining, based on the seal table, whether specific data (e.g., metering data, metering parameters, firmware components, etc.) stored on the memory 26 may be modified when the utility meter 18 is sealed. The memory 26 further stores instructions for blocking modification of the seal table when the utility meter 18 is sealed. The memory 26 yet further stores instructions for blocking modification of the non-modifiable .
data when the utility meter 18 is sealed and/or for enabling modification of the modifiable data when the utility meter 18 is sealed.
[0024] Based on the instructions stored in the memory 26, the microprocessor 24 may access the seal table (e.g., external table) stored on the memory 26 to determine whether specific data (e.g., metering data, metering parameters, firmware components, etc.) stored on the memory 26 or another memory may be modified when the utility meter 18 is sealed. The microprocessor 24 may block modification of non-modifiable data (including the seal table) when the utility meter is sealed. The microprocessor 24 may also enable modification of the modifiable data when the utility meter 18 is sealed. As mentioned above, the seal table provides flexibility to a meter manufacturer in defining what metering parameters and functions are to be sealed without having to use multiple, different firmwares for different regions with different regulatory requirements. Instead, the meter manufacturer may utilize a common seal table and modify it to specify the sealed metering parameters and functions for a specific region. In certain embodiments, a memory external to the utility meter 18 may include the seal table. For example, the seal table may be included in a remote location from the utility meter 18. In addition, in certain embodiments, a processing device external to the utility meter 18 may access a memory (e.g., internal or external to the utility meter 18) to access the seal table. For example, a third party radio (e.g., SSN) may include the seal table and control access to the meter's tables.
100251 To enable communication over the AMI network 14, the microprocessor 24 may be connected to a network interface 28. The network interface 28 may enable the microprocessor 24 to communicate over the AMI network 14. The network interface 28 may send information related to what data is sealed and receive update data (e.g., firmware update data) over the AMI network 14 and communicate with the microprocessor 24 to record time stamps and time intervals between communications over the AMI network 14. The time data may be stored in the memory 26 of the utility meter 18 in any appropriate data structure such as a table, an array, a linked list, specified registers, variables, or a combination thereof.
[00261 As mentioned above, the granularity or resolution of the seal table may vary from a table level to an individual table entry level. FIGS. 3-5 provide examples of seal tables specifying a seal flag protection status of data. Other embodiments of the seal tables are contemplated. The number of columns and rows in the seal tables may vary.
Also, the information included in the seal tables may vary. FIG. 3 illustrates a seal table 30 with a resolution at the table level. The seal table 30 includes columns for a standard table number 32, a table name 34, and a seal flag protection status 36. The seal flag protection status 36 indicates whether a specific table is modifiable (not seal flag protected) or non-modifiable (seal flag protected) when the utility meter 18 is sealed. For example, in seal table 30, tables 1 and 3 are seal flag protected. A general configuration table, a unit of measure table, and a demand control table represent a few examples of tables that may be listed among the tables on the seal table 30.
100271 FIG. 4 illustrates a seal table 38 with a resolution at an individual table entry level. The seal table 38 includes columns for a name 40 of a particular function, procedure, or parameter, a description 42 of the particular function, procedure, or parameter, and a seal flag protection status 44. The seal flag protection status 44 is as described above in FIG. 3. In the seal table 38, the function, procedure, or parameter B is seal flag protected. Entries in the general configuration table, a unit of measure table, and a demand control table represent a few examples of tables that may include individual entries that may be listed on the seal table 38. This could be specified as an entry name, an entry index, or an offset into the table.
[0028] FIG. 5 illustrates a seal table 46 with a resolution at an individual table entry level. The seal table 46 includes columns for a procedure step number 48 for a particular procedure, a step description 50, and a seal flag protection status 52. The seal flag protection status 52 is as described above in FIG. 3. In the seal table 46, procedure step 2 is seal flag protected. Steps in a cold start procedure (e.g., to return the meter 18 to its default state) or a clear data procedure (e.g., to clear billing and diagnostic data in the meter 18) represent a few examples of procedures that may include individual entries that may be listed on the seal table 46.
[0029] FIG. 6 is flow diagram illustrating an embodiment of a computer-implemented method 54 for determining whether specific data may be modified when the utility meter 18 is sealed. In the method 54, the microprocessor 24 receives a request from the AMI
network 14, via the network interface 28, to modify (or update) data (e.g., metering data, metering parameters, firmware components, etc.) (block 56). Alternatively, the microprocessor 24 may receive a request to provide an indication of what data may be modified and/or what data may not be modified. In response to the request, the microprocessor 24 accesses an external table (e.g., seal table) from the memory 26 (block 58). As mentioned above, the seal table specifies what data (e.g., metering data, metering parameters, firmware components, etc.) may or may not be modified when the utility meter 18 is sealed. Based on the seal table, the microprocessor 24 determines whether the data specified for modification may be modified when the utility meter 18 is sealed (block 60). Upon determining whether the data is modifiable (block 62), the microprocessor 24 determines the seal flag protection status of the data from the seal table. If the data is modifiable (i.e., not seal flag protected), the microprocessor 24 modifies or updates the specified data stored on the memory 26 (e.g., in the other tables excluding the seal table) (block 64). If the data is non-modifiable (i.e., seal flag protected), the microprocessor 24 blocks modification or updating of the specified data (block 66).
[00301 Technical effects of the disclosed embodiments include providing techniques and systems to provide flexibility to the meter manufacturer in defining what metering parameters and functions are to be sealed without having to use multiple, different firmwares for different regions with different regulatory requirements.
Specifically, the disclosed embodiments include providing the utility meter 18 (e.g., smart meter such as a smart electricity meter, water meter, natural gas meter, etc.) with memory 26 storing a table (e.g., seal table) that specifies whether certain data (e.g., metering data, metering parameters, firmware functions or components, etc.) may be modified when the utility meter 18 is sealed. The seal table is an external table (i.e., separate from the computer programs or code) that is not hard-encoded into the computer programs or code stored on the memory 26. This allows the meter manufacturer to utilize a common seal table that may be modified to specify the sealed metering parameters and functions for a specific region without having to utilize multiple, different firmwares. In certain embodiments, the seal table may be stored external to the utility meter 18.
100311 While there have been described herein what are considered to be preferred and exemplary embodiments of the present invention, other modifications of these embodiments falling within the scope of the invention described herein shall be apparent to those skilled in the art.
Claims (20)
1. A system comprising:
a utility meter, comprising:
a memory storing a table, wherein the table specifies modifiable data that may be modified when the utility meter is sealed and non-modifiable data that may not be modified when the utility meter is sealed; and a processing device configured to access the table stored on the memory or another memory to determine whether specific data stored on the memory or the another memory may be modified when the utility meter is sealed.
a utility meter, comprising:
a memory storing a table, wherein the table specifies modifiable data that may be modified when the utility meter is sealed and non-modifiable data that may not be modified when the utility meter is sealed; and a processing device configured to access the table stored on the memory or another memory to determine whether specific data stored on the memory or the another memory may be modified when the utility meter is sealed.
2. The system of claim 1, wherein the table cannot be modified when the utility meter is sealed.
3. The system of claim 1, wherein the processing device is configured to block modification of the non-modifiable data when the utility meter is sealed.
4. The system of claim 1, wherein the processing device is configured to enable modification of the modifiable data when the utility meter is sealed.
5. The system of claim 1, wherein the utility meter comprises an electricity meter, a water meter, a natural gas meter, or a combination thereof.
6. The system of claim 1, wherein the specific data comprises metering data, parameters, or a combination thereof.
7. The system of claim 6, wherein the specific data comprises meter configuration data, calibration data, measuring quantities, or a combination thereof.
8. The system of claim 1, wherein the specific data comprises a component of firmware.
9. The system of claim 1, wherein the table is an external table that is not hard-coded into a computer program.
10. The system of claim 1, wherein the table is modifiable when the utility meter is unsealed.
11. A non-transitory computer-readable medium having computer executable code stored thereon, the code comprising instructions for:
accessing an external table stored on a memory of a utility meter or another memory external to the utility meter, wherein the external table specifies modifiable data that may be modified when the utility meter is sealed and non-modifiable data that may not be modified when the utility meter is sealed; and determining, based on the external table, whether specific data stored on the memory or the another memory may be modified when the utility meter is sealed.
accessing an external table stored on a memory of a utility meter or another memory external to the utility meter, wherein the external table specifies modifiable data that may be modified when the utility meter is sealed and non-modifiable data that may not be modified when the utility meter is sealed; and determining, based on the external table, whether specific data stored on the memory or the another memory may be modified when the utility meter is sealed.
12. The non-transitory computer-readable medium of claim 11, wherein the code comprises instructions for:
blocking modification of the external table when the utility meter is sealed.
blocking modification of the external table when the utility meter is sealed.
13. The non-transitory computer-readable medium of claim 11, wherein the code comprises instructions for:
blocking modification of the non-modifiable data when the utility meter is sealed.
blocking modification of the non-modifiable data when the utility meter is sealed.
14. The non-transitory computer-readable medium of claim 11, wherein the code comprises instructions for:
enabling modification of the modifiable data when the utility meter is sealed.
enabling modification of the modifiable data when the utility meter is sealed.
15. The non-transitory computer-readable medium of claim 11, wherein the utility meter comprises an electricity meter, a water meter, a natural gas meter, or a combination thereof.
16. The non-transitory computer-readable medium of claim 11, wherein the specific data comprises metering data, parameters, or a combination thereof.
17. The non-transitory computer-readable medium of claim 11, wherein the specific data comprises a component of firmware.
18. A system comprising:
a memory storing a table, wherein the table specifies modifiable data that may be modified when a utility meter is sealed or non-modifiable data that may not be modified when the utility meter is sealed; and a processing device configured to access the table stored on the memory or another memory to determine whether specific data stored on the memory or the another memory may be modified when the utility meter is sealed.
a memory storing a table, wherein the table specifies modifiable data that may be modified when a utility meter is sealed or non-modifiable data that may not be modified when the utility meter is sealed; and a processing device configured to access the table stored on the memory or another memory to determine whether specific data stored on the memory or the another memory may be modified when the utility meter is sealed.
19. The system of claim 18, comprising the utility meter comprising the memory or the processing device.
20. The system of claim 18, wherein the table specifies the modifiable data that may be modified when the utility meter is sealed and the non-modifiable data that may not be modified when the utility meter is sealed.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US13/898,290 | 2013-05-20 | ||
| US13/898,290 US20140344796A1 (en) | 2013-05-20 | 2013-05-20 | Utility meter with utility-configurable sealed data |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2851003A1 true CA2851003A1 (en) | 2014-11-20 |
Family
ID=50828692
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2851003A Abandoned CA2851003A1 (en) | 2013-05-20 | 2014-05-08 | Utility meter with utility-configurable sealed data |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US20140344796A1 (en) |
| EP (1) | EP2806250A1 (en) |
| JP (1) | JP2014229309A (en) |
| AU (1) | AU2014202571B2 (en) |
| CA (1) | CA2851003A1 (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105900024B (en) * | 2014-01-06 | 2018-12-21 | 三菱电机株式会社 | FA apparatus structure Design assistant device and program |
| AU2018203426A1 (en) * | 2018-05-15 | 2019-12-05 | 369 Labs Pty Ltd | Electricity meter |
| US11385074B2 (en) * | 2020-03-18 | 2022-07-12 | Landis+Gyr Innovations, Inc. | Programming electric meter global positioning system coordinates using smart device |
Family Cites Families (30)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4283772A (en) * | 1979-03-30 | 1981-08-11 | Westinghouse Electric Corp. | Programmable time registering AC electric energy meter having electronic accumulators and display |
| MX9206230A (en) * | 1992-02-21 | 1993-09-01 | Abb Power T & D Co | IMPROVEMENTS IN AN ELECTRICAL ACTIVITY METER AND METHODS FOR THE USE OF THE SAME. |
| DE4447404C2 (en) * | 1994-12-23 | 1998-08-20 | Francotyp Postalia Gmbh | Method for entering data into a balance and arrangement for carrying out the method |
| JPH08263226A (en) * | 1995-03-23 | 1996-10-11 | Toshiba Corp | Information storage device |
| JPH103421A (en) * | 1995-11-20 | 1998-01-06 | Matsushita Electric Ind Co Ltd | Virtual file management system |
| US5761477A (en) * | 1995-12-04 | 1998-06-02 | Microsoft Corporation | Methods for safe and efficient implementations of virtual machines |
| US6366917B1 (en) * | 1998-04-01 | 2002-04-02 | Webputty, Inc. | Method of modifying a populated database structure by modifying metadata describing the database structure |
| US6457021B1 (en) * | 1998-08-18 | 2002-09-24 | Microsoft Corporation | In-memory database system |
| US7065633B1 (en) * | 1999-01-28 | 2006-06-20 | Ati International Srl | System for delivering exception raised in first architecture to operating system coded in second architecture in dual architecture CPU |
| US6704933B1 (en) * | 1999-02-03 | 2004-03-09 | Masushita Electric Industrial Co., Ltd. | Program configuration management apparatus |
| US6778920B1 (en) * | 1999-06-30 | 2004-08-17 | General Electric Company | Methods and apparatus for metering energy consumption |
| US6823273B2 (en) * | 2000-07-28 | 2004-11-23 | General Electric Company | Methods and apparatus for secure programming of an electricity meter |
| US6832372B1 (en) * | 2000-09-29 | 2004-12-14 | Hewlett-Packard Development Company, L.P. | Updating system ROM configuration utility using NVRAM |
| US20030182328A1 (en) * | 2001-10-29 | 2003-09-25 | Jules Paquette | Apparatus and method for sharing data between multiple, remote sites of a data network |
| US8666902B2 (en) * | 2003-12-05 | 2014-03-04 | Landis+Gyr Inc. | System and method for accessing read only ANSI tables in an electricity meter |
| US7262709B2 (en) * | 2004-04-26 | 2007-08-28 | Elster Electricity, Llc | System and method for efficient configuration in a fixed network automated meter reading system |
| US7502698B2 (en) * | 2004-07-05 | 2009-03-10 | Ip Power Systems Corporation | Power consumption measuring device and power control system |
| US9080894B2 (en) * | 2004-10-20 | 2015-07-14 | Electro Industries/Gauge Tech | Intelligent electronic device for receiving and sending data at high speeds over a network |
| US7996442B2 (en) * | 2005-10-17 | 2011-08-09 | Oracle International Corporation | Method and system for comparing and re-comparing data item definitions |
| US8453243B2 (en) * | 2005-12-28 | 2013-05-28 | Websense, Inc. | Real time lockdown |
| US7376521B2 (en) * | 2006-02-22 | 2008-05-20 | Fmc Technologies, Inc. | Flow computer with networked I/O modules |
| US9464917B2 (en) * | 2007-07-18 | 2016-10-11 | Silver Spring Networks, Inc. | Method and system of reading utility meter data over a network |
| JP2010134578A (en) * | 2008-12-03 | 2010-06-17 | Fujitsu Microelectronics Ltd | Information processing apparatus and content protection method |
| US20110113360A1 (en) * | 2009-11-12 | 2011-05-12 | Bank Of America Corporation | Facility monitoring and control system interface |
| US20130007217A1 (en) * | 2011-06-28 | 2013-01-03 | General Electric Company | Systems, methods, and apparatus for coordinating utility meter program files |
| US20130046866A1 (en) * | 2011-08-16 | 2013-02-21 | General Electric Company | Meter access management system |
| US8490054B2 (en) * | 2011-09-23 | 2013-07-16 | The United States Of America As Represented By The Secretary Of The Army | Software and related software tracking during software modification |
| TWI432962B (en) * | 2011-10-06 | 2014-04-01 | Mstar Semiconductor Inc | Electronic system and memory managing method thereof |
| FR2989857B1 (en) * | 2012-04-23 | 2014-12-26 | Electricite De France | METHOD FOR ACCESSING A LOCAL SERVICE OF A COMMUNICATOR DEVICE THROUGH A TERMINAL. |
| US9081964B2 (en) * | 2012-12-27 | 2015-07-14 | General Electric Company | Firmware upgrade error detection and automatic rollback |
-
2013
- 2013-05-20 US US13/898,290 patent/US20140344796A1/en not_active Abandoned
-
2014
- 2014-05-08 JP JP2014096423A patent/JP2014229309A/en active Pending
- 2014-05-08 CA CA2851003A patent/CA2851003A1/en not_active Abandoned
- 2014-05-13 AU AU2014202571A patent/AU2014202571B2/en active Active
- 2014-05-14 EP EP14168347.4A patent/EP2806250A1/en not_active Withdrawn
Also Published As
| Publication number | Publication date |
|---|---|
| AU2014202571A1 (en) | 2014-12-04 |
| AU2014202571B2 (en) | 2017-11-30 |
| EP2806250A1 (en) | 2014-11-26 |
| JP2014229309A (en) | 2014-12-08 |
| US20140344796A1 (en) | 2014-11-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6745138B2 (en) | Intelligent electronic device with assured data storage on powerdown | |
| US6813571B2 (en) | Apparatus and method for seamlessly upgrading the firmware of an intelligent electronic device | |
| US7191076B2 (en) | Expandable intelligent electronic device | |
| US9606595B2 (en) | Microprocessor-assisted auto-calibration of voltage regulators | |
| CN109683696A (en) | Fault of server power supply detection system, method, apparatus, equipment and medium | |
| CN103413070B (en) | A kind of method and device of local clock calibration | |
| US8943251B2 (en) | System and method for processing device with differentiated execution mode | |
| Poess et al. | Analysis of tpcx-iot: The first industry standard benchmark for iot gateway systems | |
| AU2014202571B2 (en) | Utility meter with utility configurable sealed data | |
| RU2008133310A (en) | DEGREGED PROTECTED runtime | |
| US9338057B2 (en) | Techniques for searching data associated with devices in a heterogeneous data center | |
| CN103488937B (en) | Measuring method, electronic equipment and measuring system | |
| CN104185827B (en) | Power consumption in control multi-core environment | |
| US9348618B2 (en) | Systems and methods for enhancing firmware | |
| CN108427634A (en) | Electronic device, the method for test and computer readable storage medium | |
| AU2012207000B2 (en) | Utility meters configured to execute multiple collection agents | |
| CN110162433A (en) | Method for analyzing chip failure, device, equipment and storage medium | |
| WO2016041398A1 (en) | Method for storing battery level information of mobile terminal and mobile terminal | |
| CN109375871A (en) | A kind of log processing method, system and electronic equipment and storage medium | |
| CA2783290C (en) | Systems and methods for table definition language generation | |
| CN115298652A (en) | System and method for storage medium health assessment | |
| CN103869275A (en) | Measuring accuracy calibration method of intelligent single-phase watt-hour meter | |
| CN105335660A (en) | Method for realizing MCU circuit encryption on basis of non-volatile memory | |
| CN103294569B (en) | The COS edition correcting methods and calibration equipment of smart card | |
| KR20140005417A (en) | Power measuring apparatus and operating mthod thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FZDE | Discontinued |
Effective date: 20200831 |