What this page solves

This page is a starting point for planning revenue-grade single- and three-phase smart meters for residential, commercial and small industrial users. It focuses on how the internal blocks of one meter fit together: delta-sigma metering SoC, analog front-end, RTC, secure element, communication modules, relay or shunt switch, and AC-DC power with surge protection.

The content is written for projects that must meet Class 0.2 or Class 0.5 accuracy, withstand formal billing audits and deliver robust anti-tamper behavior over many years in the field. The goal is to highlight the main architectural choices inside the meter and the IC functions that typically support those requirements.

Concentrators, head-end systems, PLC coupling networks and substation-level cybersecurity are treated on separate pages in this Smart Grid cluster. This page focuses only on the internal architecture and IC building blocks of an individual smart meter.

System overview: single-phase vs three-phase smart meter

Single-phase smart meters usually target residential users and very small shops, where current and power levels are modest and cost per meter is critical. Three-phase meters are more common for small factories, building incomers, EV charging clusters and larger commercial users, where higher currents, phase imbalance, power factor and demand tariffs must be monitored.

Both meter types share the same main building blocks: voltage dividers and current sensors feeding an analog front-end, a delta-sigma metering SoC, RTC and backup supply, a secure element, one or more communication modules (PLC, cellular or LoRa), relay or shunt switch drivers and an AC-DC supply with surge protection. The three-phase variant mainly scales the number of voltage and current channels and adds monitoring for phase sequence, imbalance and reverse power flow.

This overview focuses on how these blocks connect at system level inside a single meter. Detailed metrology algorithms, PLC protocol stacks and advanced protection schemes are covered in later sections or on dedicated pages in the Smart Grid cluster.

ΔΣ metering SoC & analog front-end

The delta-sigma metering SoC and its analog front-end define the achievable accuracy, stability and anti-tamper visibility of a smart meter. Multiple delta-sigma ADC channels with integrated PGAs, reference sources and temperature sensing must track each other closely so that voltage and current vectors remain aligned over temperature and time. For single-phase designs the SoC may only need one or two current channels, while three-phase meters demand a full set of voltage and current inputs with tight channel-to-channel matching.

Inside the metering SoC, the ADC outputs feed a dedicated metrology core or an integrated MCU that accumulates active, reactive and apparent energy, calculates demand and supports basic harmonic and imbalance metrics. Some architectures treat the metering SoC as a stand-alone engine and keep the billing logic on a separate MCU, while others combine the metering and application control in one device. This choice affects firmware complexity, security review scope and how easily the platform can evolve over time.

The analog front-end translates line-level signals into ranges suitable for the metering SoC. On the current side, shunt-based inputs offer low cost and linearity at the expense of power dissipation, while current transformers or Rogowski coils bring isolation and high current capability with more emphasis on burden, phase error and bandwidth. On the voltage side, high-value divider networks, basic filtering and surge-aware protection components scale mains voltage into the SoC input window without compromising regulatory requirements.

Detailed power quality analysis and synchrophasor measurement are reserved for dedicated analyzers and PMU devices elsewhere in the Smart Grid cluster. Isolation components and high-voltage safety considerations are covered on the HV isolation and sensing page; this section stays focused on how the analog front-end and delta-sigma metering SoC work together inside a single meter.

Time base & RTC: billing, TOU and outage behavior

A smart meter needs a stable time base because billing schemes increasingly rely on time-of-use tariffs, demand windows and prepayment logic. Tariff periods, peak and off-peak bands and maximum demand intervals are tied to precise timestamps rather than only to accumulated kWh. If the internal clock drifts or jumps, energy charges can be misaligned with contracted periods, creating disputes between utilities and end users and undermining regulatory compliance.

Most metering platforms implement a 32.768 kHz crystal-based RTC either inside the metering SoC or in a companion RTC device. The crystal frequency, load capacitance and temperature behavior set the long-term accuracy of this clock. Backup power using a coin cell or supercapacitor keeps the RTC running when mains power is lost, so that outages do not break the billing time axis. The choice between a battery and supercapacitor depends on expected outage duration, maintenance strategy and environmental constraints.

Outage behavior goes beyond simply keeping the RTC alive. When the mains fails, the metering SoC stops accumulating energy but the RTC and a small portion of the logic continue under backup power. When power returns, the meter must correlate the outage interval with tariff schedules, record the event with start and end timestamps and resume time-of-use and demand calculations without gaps or overlaps. These events later support billing reconciliation and regulatory audits.

Time adjustment is treated as a controlled operation. RTC updates are normally allowed only through authenticated commands or maintenance procedures, and every significant time change is logged with previous and new values. The secure element can be used to sign or protect these records so that audit trails remain trustworthy. Station-level time distribution, PTP/NTP profiles and GNSS-based references are handled on the substation time synchronisation page; this section focuses on how the meter consumes that upstream time to maintain a reliable billing clock.

Anti-tamper & security: from bypass detection to secure element

Anti-tamper functions protect revenue by detecting attempts to bypass or disturb the metering chain. Typical physical attacks include reversing line and load connections, installing partial bypass links, applying strong magnetic fields, lifting the neutral conductor or forcing only one phase to carry the majority of current. The metering SoC and analog front-end correlate voltage and current vectors, power direction and phase imbalance to recognise patterns that do not match normal load behaviour. Enclosure open switches, tilt and vibration sensors add another layer that indicates direct access to the meter housing.

A secure element complements physical anti-tamper by protecting the digital assets of the meter. Cryptographic keys, certificates, tariff tables, prepaid balances and critical configuration parameters are stored in tamper-resistant non-volatile memory. Hardware-accelerated AES and ECC engines, true random number generators and monotonic counters support message authentication, encryption and replay protection for commands such as tariff updates, firmware downloads and remote connect or disconnect. The secure element typically connects to the metering SoC or external MCU over I²C or SPI and can participate in a secure boot chain to prevent unauthorised firmware from altering billing or tamper logic.

Every suspicious condition or configuration change should generate a structured event containing a timestamp, event type and a small set of contextual data. High-value events, such as time adjustments, tariff changes or repeated bypass patterns, are candidates for signing or hashing through the secure element so that later audits can trust the records. Uplinks to concentrators or head-end systems may use a mix of immediate and periodic reporting, depending on bandwidth and latency constraints. Wider grid security topics such as key lifecycle management, VPNs and TLS offload are addressed on the grid cybersecurity module page; this section concentrates on the anti-tamper and security mechanisms inside a single smart meter.

Communications: PLC, cellular and LoRa options

Smart meters provide the last-mile connection between end users and the utility back-end. The meter must deliver metering and event data reliably while accepting configuration, time synchronisation and control commands. Power-line communication, cellular and LoRa/sub-GHz links each address different deployment patterns and regulatory environments, and the IC-level design focuses on how the meter integrates the chosen modem or radio rather than how the entire advanced metering infrastructure is planned.

PLC solutions such as G3-PLC and PRIME are suited to dense neighbourhoods and multi-dwelling buildings, where low-voltage feeders reach many meters from a shared concentrator. The design can use an internal PLC engine within the metering SoC or an external PLC modem with a dedicated PLC front-end that drives the coupling network. External modems typically interface over UART, SPI or Ethernet MAC and rely on careful analog design around line coupling, impedance matching and surge protection, topics that are expanded on the PLC front-end page.

Cellular modems are preferred where meters are geographically dispersed or where building structures make PLC or local radio coverage difficult. 2G, LTE, NB-IoT and LTE-M modules provide wide-area connectivity and may embed TCP/IP and TLS stacks, shifting protocol complexity away from the metering SoC. The hardware design must allow for high peak transmit currents, robust RF grounding and low idle power, and usually integrates SIM or eSIM management and secure element hooks for end-to-end authentication. LoRa and other sub-GHz radios fit clustered rural or campus deployments, where gateways aggregate traffic from many meters. Here the emphasis is on ultra-low-power MCU integration, RF matching networks and compliance with regional spectrum limits.

At the IC level, PLC implies a PLC modem with line AFE, cellular implies a modem module with well managed power rails and serial control, and LoRa implies a sub-GHz transceiver, matching network and antenna. Network-wide topology, routing strategies, firmware-over-the-air campaigns and VPN designs are handled by concentrators, gateways and grid cybersecurity modules elsewhere in this Smart Grid cluster. This section focuses on how the communication blocks attach to the meter core in a way that respects EMC, power budget and long-term maintainability.

Relay drive & remote connect/disconnect inside the meter

The internal disconnect device in a smart meter implements remote connect and disconnect, overload protection and power-limiting functions. Depending on utility policy, the same device may support prepaid disconnection, reconnection after payment, safety-related shutdown and staged power restoration after faults. The metering platform must therefore treat the relay or solid-state switch as a controlled actuator that is tightly linked to billing logic, overload thresholds and regulatory requirements, not as a simple on/off contact.

Several device types are used for this role. Mechanical relays remain common because they provide clear galvanic isolation and low conduction losses, but they introduce limited electrical and mechanical lifetime and require careful control of inrush and arcing. Bidirectional solid-state relays and MOSFET based shunt switches can switch more frequently and integrate zero-cross detection or current limiting, while adding continuous conduction loss and leakage that must be managed thermally. Each topology must be evaluated against the meter's maximum current, load profile, required number of operations and local standards.

The drive path typically runs from the metering SoC or application MCU through a low-voltage driver stage into the relay coil, solid-state relay input or MOSFET gate. Zero-cross decisions are based on measured mains voltage and current to avoid switching at peaks and to limit inrush. Feedback from the metering channels is then used to detect welded contacts or incomplete disconnection: when a disconnect command has been issued but significant load current remains, firmware can flag a welded contact event, lock further reconnect attempts and raise a maintenance alarm. Local temperature sensors around the switching device enable derating and thermal shutdown behaviour that coordinates with overload and billing logic.

Remote connect and disconnect states are closely coupled to tariff and balance information, overload thresholds and safety rules. Prepaid meters may disconnect when remaining credit falls below a defined limit, while postpaid meters may restrict reconnect after repeated overload events until a safe inspection has been performed. This section describes requirements and interfaces from the smart meter perspective; broader device families and detailed switch IC mapping are covered on the meter relay and shunt switch pages in the same Smart Grid cluster.

Power supply, surge and backup inside a smart meter

The internal power architecture of a smart meter must convert wide-range mains voltage into multiple low-voltage rails while surviving surge events and maintaining critical functions during outages. Typical designs start from 110/230 Vac input, implement an AC-DC stage and then generate dedicated supplies for the metering SoC and analog front-end, communication modules and relay or solid-state switch drivers. Layout, grounding and filtering are arranged so that noisy domains do not compromise measurement accuracy or communication reliability.

Surge and EMC protection components surround the power path and interfaces. MOVs and gas discharge tubes near the line terminals absorb high-energy surges, while TVS diodes and RC or LC networks close to sensitive circuits clamp residual voltages and shape transient currents. The AC-DC stage and PLC coupling network must be coordinated with these protectors to satisfy standards such as IEC 61000-4-5 without overstressing semiconductor devices. Communication ports and auxiliary I/Os receive their own protection and filtering so that external disturbances do not propagate into metering or control logic.

Backup energy maintains the real-time clock and, in some designs, a minimal security and logging domain during outages. A supercapacitor or small battery, combined with diode or ideal-diode OR-ing, powers the RTC and secure element when mains power disappears. This arrangement allows the meter to preserve time, final billing registers and high-value events even when the main AC-DC converter is offline. Three-phase meters may derive power from multiple phases or implement rectifier arrangements that keep the logic running under single-phase loss or phase reversal, enabling continued measurement and event reporting under degraded conditions.

At the IC level, the design must map surge withstand, backup duration, power budget and redundancy requirements into specific PMICs, AC-DC controllers, protection components and supervisory devices. This section focuses on how these elements are arranged inside the meter. System-level surge coordination across panels and substations, along with detailed lightning protection schemes, is handled on the EMI, surge and lightning protection pages elsewhere in the Smart Grid and power distribution hierarchy.

Design checklist & IC mapping

This section compiles the main design decisions for single- and three-phase smart meters. The checklist groups metrology, sensing, time base, anti-tamper, communications, power supply and disconnect devices so that the IC set and bill of materials can be reviewed before design freeze.

1. Metrology accuracy & ΔΣ SoC selection

• Target accuracy class (for example Class 0.2 / 0.5 / 1.0) is defined and the ΔΣ metering SoC error budget, temperature drift and linearity leave sufficient margin across the operating range.
• Number of voltage and current channels covers the required single- or three-phase configuration, including any neutral current or spare channels reserved for future features.
• On-chip processing performance, memory and peripheral interfaces are adequate for metrology, anti-tamper logic, local control and communication stacks defined in this project.

2. Current & voltage sensing front-end

• Chosen current sensing approach (CT, shunt or Rogowski with AFE) matches expected continuous and short-circuit currents, conductor layout and thermal limits in the meter enclosure.
• Current range, overload capability and bandwidth are compatible with the metering SoC input range and the required accuracy over the full operating conditions.
• Voltage divider network power rating, accuracy and long term stability are sized correctly and coordinated with TVS and surge components protecting the analog front-end.

3. Time base, RTC & outage behaviour

• RTC accuracy over temperature and lifetime supports tariff and audit requirements for time-of-use, demand billing and prepayment.
• Backup energy (supercapacitor or battery) allows the RTC to maintain time across expected outage durations with margin for ageing and worst case conditions.
• Time synchronisation sources from concentrator, network time or GNSS are defined and time adjustments are restricted to authenticated commands with events logged for every change.
• Outage and restoration behaviour for billing is validated: registers, events and tariff state are stored safely before loss of mains and restored correctly after power returns.

4. Anti-tamper sensors & security domain

• Detection mechanisms are in place for typical tamper scenarios such as reverse wiring, bypass links, missing neutral, abnormal phase imbalance and strong external magnetic fields.
• Enclosure open, tilt and vibration sensors are connected, exercised and monitored with defined thresholds, debounce rules and periodic self-test.
• Secure element capabilities meet regulatory requirements: supported AES/ECC algorithms and key lengths, certificate formats, secure counters and protected storage capacity.
• Anti-tamper events are recorded with timestamp, type and minimal context and can be authenticated or signed through the secure element for later analysis by head-end systems.

5. Communications strategy: PLC, cellular and LoRa

• Primary communication path is selected for the target deployment: PLC, cellular, LoRa/sub-GHz or a defined combination.
• Backup communication path and failover policy are defined, including PCB area and connectors reserved for optional modems and antennas where required.
• PLC modem and analog front-end, cellular module interface and LoRa SoC all have reserved UART/SPI, GPIO and power rails on the metering platform.
• EMI/ESD and surge protection for each interface is consistent with the power, surge and lightning assumptions used in the Smart Grid cluster.

6. Relay / SSR / shunt switch drive

• Disconnect device type (mechanical relay, solid-state relay or shunt switch) matches rated current, short-circuit capability, mechanical and electrical lifetime and safety requirements.
• Zero-cross detection and inrush control strategy are implemented in hardware and/or firmware, considering typical load types attached to the meter.
• Welded-contact detection uses metering current measurements and command feedback to flag devices that do not open or close as requested and to block unsafe reconnection.
• Temperature sensors near the switching path provide thermal protection and derating rules linked to overload limits and reconnect policies.

7. Power supply, surge & backup strategy

• AC-DC conversion and downstream DC rails are partitioned so that precision metering, communication and relay drive domains have appropriate noise and current capability.
• Mains surge and EMC front-end (MOV, GDT, TVS and filters) is dimensioned to satisfy target standards and to protect both the AC-DC stage and PLC coupling network.
• Backup energy design aligns with RTC and secure element requirements and is checked against actual outage profiles and maintenance intervals.
• Single- and three-phase supply arrangements provide adequate resilience under phase loss or phase reversal so that essential measurement and event reporting remain available.

IC mapping by function block

The table below groups IC roles inside a smart meter. Each function is linked to its main responsibilities, key selection notes and the section or sibling page where the topic is developed in more detail. Specific vendors and part numbers are defined later in dedicated vendor-mapping pages and planning cards.

FAQs on smart meter architecture and IC choices

These twelve questions summarise common design decisions for single- and three-phase smart meters. Each answer focuses on practical trade offs across metrology, sensing, time base, anti tamper, communications, power supply and remote disconnect so that project teams can validate assumptions before committing to a hardware platform.