Smart Meter Architecture and Key Design Requirements

Smart meters feature a core architecture built around a power system, a microcontroller, and a communication interface that automates two-way data exchange with utility providers.

Voltage and current sensing circuits collect electrical signals from the mains. These measurements are processed by the metering and control electronics to calculate parameters such as energy consumption, voltage, current, and power. The MCU manages calculations, local functions, data storage, timing, and communication.

A simplified data flow looks like this:

Voltage and Current Sensors → Metering Circuit → Nuvoton MCU → SIMCom Module → Cellular Network → Cloud or Utility Server

Depending on the application, the meter also includes local storage, a display, an RTC, tamper monitoring, relay control, and diagnostic functions.

Single-phase meters generally have a simpler sensing and processing architecture. Three-phase smart meters require additional measurement channels and more complex calculations because multiple voltage and current phases must be monitored.

In addition, accuracy and long-term reliability should be considered from the beginning. IEC standards for static electricity meters define requirements and test considerations for areas such as measurement accuracy, repeatability, timekeeping, and electromagnetic influences.

Selecting a Nuvoton MCU for Smart Meter Applications

The MCU acts as the operational hub of the smart meter hardware design. It processes measurement data while managing communication, timing, storage, diagnostics, and other peripheral functions.

Before selecting a Nuvoton MCU, engineers should evaluate:

• ADC resolution and available channels

• Flash and SRAM requirements

• UART, SPI and I²C interfaces

• GPIO and PWM availability

• RTC and watchdog functionality

• Low-power operation

• Operating temperature range

• Security and firmware protection

The ADC is important because voltage and current measurement require accurate data acquisition. However, the complete measurement accuracy depends on the entire sensing and metering architecture, including signal conditioning, reference stability, calibration, and firmware calculations, not the MCU alone.

Nuvoton's NuMicro portfolio provides options with combinations of ADCs, communication interfaces, RTCs, watchdog timers, and security features. For example, the NuMicro M251/M252 family includes UART-related interfaces, SPI, I²C, watchdog functionality, RTC support and multiple analog peripherals. It also includes memory-protection and code-protection features that can be relevant when protecting embedded firmware.

The best approach is to select the MCU based on the actual meter architecture instead of simply choosing the highest-performance device.

Integrating SIMCom Cellular Connectivity

Cellular communication enables a connected smart meter to send readings beyond the installation site. This is useful for remote monitoring, billing systems, alerts, diagnostics, and firmware management.

A common architecture connects the Nuvoton MCU and SIMCom module through UART. The MCU sends AT commands to configure the module, check network registration, monitor signal conditions, and initiate data communication.

The communication path can be summarized as:

Nuvoton MCU → UART → SIMCom Cellular Module → Mobile Network → Server or Cloud Platform

SIMCom offers cellular modules designed for IoT applications. For example, the A7672X series supports LTE connectivity and provides interfaces including UART, USB, I²C and GPIO, while SIMCom also provides technical resources for UART, TCP/IP, SSL and sleep-mode implementation across relevant module families.

The appropriate technology depends on the deployment. Conventional 4G LTE may suit applications requiring regular data exchange, while LTE-M or NB-IoT may be considered where network availability and lower-data IoT requirements make them suitable.

A reliable design should also account for SIM or eSIM selection, antenna placement, RF layout, and temporary network failures. The meter should not lose readings when connectivity drops. Instead, important data can be stored locally and transmitted once the connection is restored.

Power, Measurement, and Protection Design

The power supply is one of the most important parts of smart energy meter design because the electronics must operate continuously in a mains-connected environment.

The design requires AC-DC conversion followed by regulated low-voltage rails for the MCU, sensing circuits, display, and communication module. The power architecture should be planned around efficiency, isolation requirements, thermal performance, and protection.

The SIMCom module deserves special attention because cellular transmission can create short-duration current demands. If the supply cannot handle these peaks, the module or MCU may experience voltage drops and unexpected resets.

The measurement section should be carefully isolated from noise generated by switching power stages and cellular communication. PCB layout, grounding, filtering, component placement, and EMC planning can directly affect measurement stability.

Depending on the design requirements, protection of smart energy meter includes:

• Fuses and overcurrent protection

• Surge and transient protection

• Isolation barriers where required

• Reverse-polarity protection for backup supplies

• Thermal monitoring

Battery or backup power can also help preserve the RTC, important system information, or controlled operation during a mains interruption.

End-to-End Data Flow, Security, and Development

A smart meter becomes genuinely useful when its measurement data can be converted into secure, actionable information.

The end-to-end flow includes a chain of actions which include:

Sensors collect electrical data → MCU processes and stores readings → SIMCom module transmits data → Server analyses information → Utility or user receives monitoring data and alerts

The MCU can perform calculations locally before transmission, reducing unnecessary communication and supporting basic edge processing. The backend can then store readings, generate alerts, analyze consumption, and support remote diagnostics.

For interoperability, smart-meter ecosystems use established data-exchange frameworks such as DLMS/COSEM. This framework is designed for standardized data exchange between smart devices and head-end systems and can operate across different communication technologies.

Security should be built into the design rather than added later. Important measures include device authentication, encrypted communication, secure credential storage, firmware protection, error detection, and controlled firmware updates.

Before mass deployment, engineers should test the complete system for network loss, weak signal conditions, power interruptions, temperature variation, communication failures, and recovery behaviour. Long-term component availability also matters because smart meters are expected to remain operational for extended deployment cycles.

Reliable smart meter design requires the right balance of measurement, processing, connectivity, power, and protection. A Nuvoton MCU can handle core processing and control, while SIMCom modules enable remote communication. Campus Component provides these and other essential electronic components to help engineers build dependable, connected smart-meter solutions with fewer design challenges.

Planning a connected smart meter?Explore Nuvoton MCUs, SIMCom modules, power components, and other essential hardware at Campus Component to build a reliable, connected design.

FAQs:

1. What communication protocols can a smart meter use to send data to a utility server?

A smart meter can use cellular IoT connectivity to communicate with a remote server. Depending on the system architecture, protocols such as MQTT or HTTP/HTTPS can be used to transmit meter readings and other device data.

2. What happens if a smart meter temporarily loses cellular connectivity?

The meter can continue collecting readings and store them in internal or external memory. Once the network connection is restored, the stored data can be transmitted to the server, helping minimize data loss during temporary outages.

3. How can a smart meter identify unusual energy consumption?

The MCU can monitor parameters such as voltage, current, power, and energy consumption to identify readings that fall outside predefined conditions. When an unusual pattern is detected, the system can trigger an alert locally or send it to a remote server.

4. Why does a smart meter need a real-time clock (RTC)?

An RTC helps the meter attach accurate timestamps to energy readings and system events. This can be useful for time-based billing, consumption analysis, event logging, and retaining accurate records when network connectivity is temporarily unavailable.

5. What should be tested before deploying a cellular smart meter?

Testing should cover key areas such as measurement accuracy, power-supply stability, cellular connectivity, antenna performance, communication recovery, temperature operation, surge and transient protection, firmware reliability, data security, and long-term system performance.

Understanding Smart EV Charger Architecture

A smart EV charger, also called as Electric Vehicle Supply Equipment (EVSE), is an intelligent system that acts as a secure communication bridge between the electric grid, the charging network, and the vehicle. These smart charging systems utilize advanced hardware and software to optimize charging times, manage energy consumption, and process payment.

Core layers include:

• Hardware Layer: MCU, power modules, sensors, and LTE module

• Communication Layer: LTE, OCPP, MQTT, HTTP protocols

• Application Layer: Cloud backend, mobile apps, dashboards

• Control Layer: Charging logic, safety systems, load management

This layered structure ensures that EV chargers can operate independently while staying connected to cloud platforms for monitoring and control.

Role of MCU in Smart EV Chargers

Microcontroller units (MCUs) serve as the brain of smart EV chargers which are responsible for controlling power conversion, safety monitoring, communication, and user interaction. They are essential for managing the complex interaction between the electric grid and the EV battery, ensuring safe and efficient energy transfer.

Key functions of MCU include:

• Controls charging cycles and power flow

• Helps monitoring voltage, current, and temperature in real time

• Handles communication with LTE module and backend systems

• Executes safety checks and fault protection

• Supports firmware updates and system logic execution

Why MCU is essential:

MCUs ensure real-time decision-making, which is essential for safe EV charging operations.

Common MCU families used:

• ARM Cortex-M series

• STM32 microcontrollers

• NXP automotive MCUs

• Renesas embedded controllers

These MCUs are widely used in embedded EV charger firmware architecture for their reliability and low power consumption.

Why 4G LTE is Used in EV Charging Systems

4G LTE is primarily used in EV charging systems to ensure reliable, high-speed connectivity for remote monitoring, real-time payment processing, and secure over-the-air software updates. It offers superior reliability compared to Wi-Fi. Key reasons why 4G LTE is used include:

• Reliable Connectivity: 4G networks help charging stations stay connected and operational, even in public or remote locations where Wi-Fi coverage may be inconsistent.

• Real-Time Monitoring: Operators can track station usage, energy consumption, and overall performance instantly, making day-to-day management much easier.

• Remote Maintenance & Better Security: With 4G connectivity, many charger issues can be identified and resolved remotely, which helps reduce unnecessary on-site maintenance visits. It also supports secure and encrypted communication to help protect against cyber threats.

• Faster and Easier Installation: Cellular connectivity, especially with eSIM technology, removes the need for complex cabling, helping charging stations get installed more quickly and cost-effectively.

• Smarter Charging Experience: 4G supports features like real-time payment processing, user authentication, and smart load management for a smoother and more efficient charging experience.

Communication Flow Between EV Charger, Cloud, and User Applications

In 2026, EV chargers, cloud platforms, and mobile apps work together through a real-time communication system using OCPP 2.0.1 over WebSockets. This setup enables secure, seamless connectivity and ensures different charging hardware and software platforms can work together smoothly.

1. Charger-to-Cloud Communication

EV chargers connect to the internet through Ethernet, Wi-Fi, or cellular networks and communicate with the backend system using OCPP. While OCPP 1.6J is still common, the industry is rapidly moving toward OCPP 2.0.1 and 2.1 for stronger security and smarter charging features. Chargers continuously share data like charging status, energy usage, and authentication requests, while the backend can remotely control charging sessions, unlock connectors, or push firmware updates securely.

2. Backend System Operations

The backend platform acts as the central control system for the entire charging network. It manages charging sessions, balances energy loads, processes payments, verifies users, and supports roaming between different charging operators. It also connects with smart grids to optimize charging during peak electricity demand.

3. Mobile App Connectivity

The mobile app communicates with the backend through APIs, allowing users to start or stop charging sessions remotely, track charging progress in real time, and view details like energy usage and remaining time. Modern EV charging systems now include secure authentication features like OAuth and Plug & Charge, making the charging experience simpler and more convenient for users.

Communication Protocols used in Smart EV Chargers

Smart EV chargers rely on multiple communication protocols:

• OCPP (Open Charge Point Protocol): Standard protocol for EV charger-cloud communication

• MQTT: Lightweight protocol for IoT telemetry data

• HTTP/HTTPS: Used for APIs and backend communication

• Modbus: Used in industrial energy systems

• CAN Protocol: Used for internal vehicle and charger communication

• OCPP is especially important as it ensures interoperability between different charging networks.

LTE Module and MCU Integration Architecture

An LTE module connects to a microcontroller through a simple serial interface, where the MCU runs the device logic and the LTE module takes care of all cellular communication. This setup lets IoT and industrial devices get 4G connectivity for things like data transfer, remote control, and over-the-air updates.

Core Integration Architectures

• Host-based architecture (MCU + external LTE modem): An MCU controls a separate LTE module using AT commands over UART/USB. Best for applications needing higher local processing like displays or camera-based systems.

• Integrated SoC/module approach: MCU and LTE modem are combined into a single chip or module, ideal for compact, low-power devices like trackers and wearables.

• Key advantage of integration: Simpler design, lower power use, reduced size, and fewer components overall.

• MCU (host): Runs the main logic, reads sensors, and handles protocols like MQTT/HTTP (e.g., STM32, ESP32).

Hardware interface Components

• LTE module (modem): Manages cellular connectivity and SIM communication (e.g., Quectel BG96, u-blox SARA-R410M).

• Communication link: Usually UART, or USB/SPI for faster data exchange.

• Power system: Needs strong power support due to high current spikes during transmission.

• SIM setup: Uses either a physical SIM or eSIM for network access.

Software Architecture & Data Flow

• MCU software layer: The MCU uses a driver or AT command manager to control the LTE module.

• AT commands: Simple text commands are sent from the MCU to handle tasks like opening connections or sending data.

• Built-in networking: The LTE module already manages TCP/IP, so the MCU only focuses on the actual data, not networking details.

• Ready-made libraries: Vendor SDKs like Quectel or ST cellular stacks simplify integration with prebuilt APIs.

Security Architecture in Connected EV Chargers

Security in connected EV chargers is built in layers to protect the power grid, user information, and the vehicles themselves. The architecture include:

• Secure communication: Standards like ISO 15118 use digital certificates and encryption to ensure safe, verified communication between the vehicle and charger.

• OCPP security: Newer OCPP versions (2.0.1/2.1) add stronger protections like encrypted messaging, secure boot, and safe firmware updates.

• Access control: Different users and operators have defined permissions, ensuring only authorized actions are allowed through role-based access.

• Physical security: Chargers are built with anti-tamper hardware since they are often installed in open public spaces.

• Grid protection: Systems are designed to prevent unauthorized usage and protect the electrical grid from misuse or large-scale disruption.

Remote Monitoring and Diagnostics

Smart EV chargers support advanced remote monitoring features:

• Real-time telemetry data collection

• Fault detection and alerts

• Predictive maintenance using usage patterns

• Energy consumption tracking

Challenges in Smart EV Charger Communication Systems

Despite various advancements of EV charger communication systems, several challenges also exist, which include:

• Network latency in remote areas

• Signal instability in dense urban environments

• Cybersecurity risks in connected systems

• Scalability issues for large deployments

Addressing these challenges requires strong embedded design and reliable LTE integration.

Future of Connected EV Charging Infrastructure

The future of EV charging communication is evolving rapidly with the following trends:

• 5G integration: For faster and ultra-low latency communication

• AI-based charging management: For smart load balancing and prediction

• Smart grid connectivity: For dynamic energy distribution

• Vehicle-to-Grid (V2G): For two-way energy flow between EVs and grid

These technologies are expected to make EV charging more intelligent and energy-efficient.

The Bottom Line

A smart EV charger communication architecture built using MCU and 4G LTE enables reliable, scalable, and secure charging infrastructure. It connects hardware, cloud systems, and users in real time, ensuring better control, monitoring, and energy management. With the growing EV adoption, robust communication architecture is expected to become a key factor in building future-ready charging networks.

For companies developing EV infrastructure, investing in strong embedded systems and LTE-based connectivity is no longer optional, but essential.

Looking to develop scalable and secure smart EV charging systems? Connect with embedded and IoT engineering experts at Campus Component to build next-generation EV communication architectures.

FAQs:

1. What MCU is used in EV chargers?

Most EV chargers use ARM Cortex-M, STM32, NXP, or Renesas MCUs for real-time control and communication handling.

2. Why is 4G LTE used in EV charging stations?

4G LTE provides stable, wide-area connectivity, making it ideal for remote and public EV charging infrastructure.

3. What protocols are used in smart EV chargers?

Common protocols include OCPP, MQTT, HTTP/HTTPS, Modbus, and CAN for internal and external communication.

4. How does remote monitoring work in EV chargers?

EV chargers send real-time data to cloud servers via LTE, enabling monitoring, diagnostics, and control through dashboards or apps.

5. What is OCPP in EV charging?

OCPP (Open Charge Point Protocol) is a standard that allows EV chargers to communicate with backend management systems.

The SIM8918X Smart Module is a powerful embedded solution designed for smart mobility, ADAS, and IoT applications. Built on advanced processing and rich connectivity, it supports multimedia, AI, and Android-based systems. This blog explores its key features, applications, and benefits, helping developers and OEMs understand its role in modern intelligent device development.