Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC IEC 29341-6-14 — UPnP Low Power — Part 6-14: Energy Monitoring Service
Real-Time Power Measurement, Data Aggregation, and Reporting in UPnP Networks
The ISO/IEC 29341-6-14 standard specifies the Energy Monitoring Service for UPnP Low Power devices. This service enables real-time tracking of electrical energy consumption, generation, and grid interaction parameters. It is a cornerstone service for smart-home energy management systems, demand-response programs, and sustainability analytics.
The Energy Monitoring Service can measure both consumed and generated energy. For solar-equipped homes, configure separate service instances for grid import and PV export to obtain net-zero accounting automatically.
Metering State Variables and Data Model
The service maintains a comprehensive set of state variables that capture instantaneous and cumulative energy data. The data model follows the IEC 62053 metrology framework for compatibility with utility-grade meters.
| State Variable | Type & Unit | Description |
|---|---|---|
| InstantaneousPower | i4 (W) | Real power draw (positive) or generation (negative) in watts |
| EnergyConsumed | ui4 (Wh) | Cumulative energy consumed since last reset |
| EnergyGenerated | ui4 (Wh) | Cumulative energy generated (solar/wind) since last reset |
| Voltage | ui2 (V × 10) | RMS voltage measurement (e.g., 2300 = 230.0 V) |
| Current | ui2 (A × 100) | RMS current measurement (e.g., 500 = 5.00 A) |
| PowerFactor | i2 (× 0.001) | Power factor, range −1000 to 1000 (e.g., 950 = 0.95) |
| MeterReadingPeriod | ui4 (s) | Interval between meter data updates (typical 1–60 s) |
Using the Energy Monitoring Service, a household can achieve 15–25% energy savings through real-time consumption feedback alone — without any behavioral coaching or automated load shedding.
Reporting Actions and Eventing
The service exposes several actions for querying meter data and configuring reporting behavior:
- GetEnergyConsumption() — Returns InstantaneousPower and cumulative EnergyConsumed. This is the primary query for dashboard applications.
- GetEnergyGeneration() — Returns cumulative generated energy and instantaneous generation power. Returns zeros if the device does not support generation metering.
- GetMeterData() — Returns the full set of metrology variables (voltage, current, power factor, frequency) for detailed power-quality analysis.
- ResetCumulativeValues(NewResetType) — Resets either “consumed”, “generated”, or “all” cumulative counters. Typically used after meter installation or calibration.
- SetMeterReadingPeriod(NewMeterReadingPeriod) — Configures the update interval for the metering data cache. Shorter periods provide better resolution at the cost of increased processing overhead.
The service also supports evented state variables. Control points can subscribe to EnergyConsumed change notifications, receiving push updates when consumption crosses configurable thresholds. This is far more efficient than polling for demand-response scenarios.
When subscribing to EnergyConsumed change events, set a reasonable threshold delta (e.g., ≥10 Wh) rather than monitoring for every watt-hour change. High-resolution eventing at sub-watt levels can overwhelm UPnP control points with thousands of events per hour.
Engineering Design Considerations
Calibration and Accuracy. The Energy Monitoring Service does not mandate a specific accuracy class. For utility-billing applications, pair the UPnP service with an ANSI C12.20 / IEC 62053-22 Class 0.5 meter and expose the calibrated readings through the service interface. For non-billing applications (home energy displays), lower-cost Hall-effect sensors with ±5% accuracy are adequate.
Never expose the ResetCumulativeValues action to unauthenticated users or public networks. A malicious reset of cumulative energy data could invalidate feed-in tariff claims or create disputes with utility providers.
Data Aggregation Strategy. In a multi-device deployment (e.g., 20 smart plugs plus a whole-home meter), designate the whole-home meter as the primary time-source and synchronize all plug readings to its clock. This eliminates timing skew when aggregating data for grid-interactive applications. The standard supports this through the MeterReadingPeriod variable, which acts as a synchronization beacon.
Frequently Asked Questions
Q: Can the Energy Monitoring Service report negative energy values for net metering?
A: Yes. InstantaneousPower uses a signed integer where negative values indicate net generation. Cumulative EnergyConsumed and EnergyGenerated are separate unsigned counters, allowing simultaneous tracking of both directions.
A: Yes. InstantaneousPower uses a signed integer where negative values indicate net generation. Cumulative EnergyConsumed and EnergyGenerated are separate unsigned counters, allowing simultaneous tracking of both directions.
Q: How often should a control point poll GetEnergyConsumption()?
A: For real-time display, once every 2–5 seconds is sufficient. For historical logging, once per minute provides adequate resolution while minimizing network traffic.
A: For real-time display, once every 2–5 seconds is sufficient. For historical logging, once per minute provides adequate resolution while minimizing network traffic.
Q: Does the service support three-phase power monitoring?
A: The base standard defines single-phase variables. For three-phase applications, deploy three separate service instances (one per phase) or use a vendor extension that aggregates phase data into a single instance.
A: The base standard defines single-phase variables. For three-phase applications, deploy three separate service instances (one per phase) or use a vendor extension that aggregates phase data into a single instance.
Q: What is the maximum value of EnergyConsumed before rollover?
A: EnergyConsumed is a ui4 (32-bit unsigned) stored in watt-hours. Its maximum value is 4,294,967,295 Wh (~4,295 MWh). For a typical home consuming 500 kWh/month, rollover occurs after approximately 715 years — effectively never in practice.
A: EnergyConsumed is a ui4 (32-bit unsigned) stored in watt-hours. Its maximum value is 4,294,967,295 Wh (~4,295 MWh). For a typical home consuming 500 kWh/month, rollover occurs after approximately 715 years — effectively never in practice.
