Definition
AMI (Advanced Metering Infrastructure) is an advanced metering infrastructure that enables remote meter reading, prepayment, and tiered pricing for water, electricity, gas, and heat meters via NB-IoT/4G modules, replacing manual in-home meter reading.
System architecture
AMI consists of smart meters, communication networks, meter reading platforms, and data analysis systems. Smart meters have built-in NB-IoT or LTE Cat.1 modules that report usage data at set intervals or triggered by events; the platform processes the data for billing, tiered pricing, overdue alerts, and remote valve control. Electricity meters use the DL/T 645 protocol, water and gas meters use the CJ/T 188 protocol, and heat meters follow relevant industry standards. The module is responsible for packaging the protocol data and uploading it via the cellular network.
Communication Standard Selection
NB-IoT is suitable for low-frequency meter reading scenarios such as water and gas meters due to low power consumption, deep coverage, and cost-effectiveness; LTE Cat.1 is suitable for electricity and heat meters requiring higher frequency or real-time control. Meters are often installed in hallways, basements, and other weak signal environments, so modules must have strong coverage and low power capabilities; prepayment scenarios also require support for downstream remote valve control, with certain latency requirements.
Value of Smart Metering
AMI implements automated meter reading, reducing labor costs and minimizing household disturbances; it supports detailed billing such as tiered pricing and peak-valley electricity prices; prepaid billing and remote valve control reduce the risk of arrears; usage data analysis can detect anomalies and assist in energy saving. With the advancement of smart cities, AMI has become standard in the water, electricity, gas, and heating industries, and communication modules are a key component.
Engineering Practice Supplement
For cross-team collaboration regarding "AMI": hardware provides impedance and power budget, RF provides spurious and sensitivity margin, embedded specifies thread models and storage lifespan, and cloud specifies SLA and rate limiting. For scenarios like NB-IoT, the business model needs to match wake-up cycles, packet length, and downlink capacity; for vehicular and mobile scenarios, session persistence during handover and roaming must be considered. At project closure, perform a "red team" style review: ensure there are defined behaviors for weak network, power loss, certificate expiration, clock jumps, and full storage.
The time gap between a meter read and a valve command
AMI means using communications to join meters, collection, and billing into a metering system that can act remotely. It is more than “the meter is online.” Usage can be gathered hourly or even daily. Closing a valve for arrears, opening it, and setting the clock are downlink commands, and they must land while the meter is awake. Three conditions therefore have to be true together: the battery can support one full attach and transmission, the network can deliver the command in an acceptable time, and the meter address on the platform matches the address inside the meter.
If a water or gas meter sleeps for a long time, a valve command sent during sleep piles up or times out. The design should state the worst-case arrival time, and the meter should ask, in an agreed window, whether a command is waiting. Do not assume the network can wake the meter at any moment. When an electricity meter needs a denser load profile or remote connect and disconnect, evaluate a higher-rate radio then, rather than putting every meter on the same cycle.
A duplicated meter address produces a wrong read
When several meters hang off one concentrator, an address clash writes usage onto another meter. The platform curve still looks continuous, so “data is present” does not reveal it. The installation list, the address inside the meter, and the platform record must be checkable against each other, and the old address must be retired as soon as a meter is replaced. If broadcast time sync has no collision avoidance, many meters answer at once and block the bus. The cellular side then only sees a concentrator timeout.
Where basement and riser coverage is poor, the module searches repeatedly and the battery curve falls after only a few reads. Improve the antenna position or the concentrator relay before making reports more frequent. Sleep settings have to be counted together with the paging window of eDRX. Pulse current goes back to battery chemistry: open-circuit voltage can look fine while the transmit instant resets the device.
A continuous curve that does not match the register
A reading every day does not prove it came from that meter. If the address is off by one digit, the curve still rises smoothly until it fails to match a manual register reading. Acceptance should sample a few meters and compare the cumulative value on the display with the last platform frame, including decimal places and units. Valve acceptance cannot stop at a button changing state on the platform. Confirm the valve at the meter, and see in a later usage frame that flow has actually stopped. Comparing only successful communication counts lets a wrong read into settlement. Compare the frozen read time as well, so the platform is not showing the previous cycle’s register.