Definition
SOC (State of Charge), indicating the percentage of remaining battery capacity, BMS core monitoring parameter, reported by charging stations and vehicles for charging management and range display.
Estimation Methods
SOC cannot be measured directly and needs to be estimated through parameters such as voltage, current, and temperature. Common methods include: Open Circuit Voltage method (OCV-SOC lookup table), Ah Counting method (Coulomb Counting), Kalman Filter, Neural Networks, etc. The BMS integrates various methods for fused estimation to improve accuracy. SOC estimation errors affect the accuracy of range display and overcharge/overdischarge protection, making it one of the core algorithms of the BMS.
Application in Communication Modules Scenario
Devices such as electric vehicles, electric two-wheelers, energy storage systems, and charging stations report SOC to the cloud platform via 4G/LTE Cat.1 modules. Charging stations adjust charging strategies based on vehicle SOC; battery swap cabinets arrange battery swaps and maintenance according to SOC; fleet management plans charging and scheduling based on SOC. The module is responsible for packaging and uploading SOC data provided by the BMS or main controller, supporting real-time monitoring and historical analysis.
Relationship with SOH
SOC represents the current state of charge, and SOH (State of Health) represents the battery's health and remaining lifespan. Both are key parameters of the BMS and are often reported together. SOH affects the reference capacity used for SOC estimation; as a battery ages, its actual usable capacity decreases, so SOC display and range prediction need to be corrected based on SOH.
Engineering Practice Supplement
Regarding 'SOC,' it is recommended to differentiate the real-time control link from the non-real-time telemetry link in the architecture: keep control and interlock loops local as much as possible, and use cellular for monitoring, configuration, and OTA. On the cloud platform side, use observability metrics (connection duration, message latency distribution, error codes, and reconnection reasons) to drive optimization, rather than just checking 'connectivity.' Document deliverables should include interface descriptions, error code tables, extreme working conditions, and known limitations; test deliverables should include cases, data, and conclusions to facilitate third-party retesting or auditing.
The following are additional tips related to cellular IoT project delivery: it is recommended to keep screen recordings of typical scenarios, screenshots of key indicators, and summaries of masked packet captures during the acceptance phase; in the mass production phase, change records should be kept for software and hardware versions, calibration parameters, and key component batches to facilitate problem attribution, customer audits, and long-term maintenance. When payment or personal information is involved, also check whether log masking and key rotation strategies are executable.
When a State-of-Charge Estimate Can Drive Power Decisions
State of charge is an estimate of remaining charge relative to currently usable capacity. It is not another name for terminal voltage, and a communication module cannot measure it by itself. On a device that includes a module, the point is this: the BMS or the host hands the fused percentage to the module, the module reports it on a period or an event, and local thresholds decide whether transmission or a firmware upgrade is still allowed. Open-circuit voltage is steadier after a rest. Coulomb counting follows dynamic current, but the integral drifts. Both need temperature and SOH correction. After the cell ages, the same percentage corresponds to fewer usable ampere-hours.
The percentage may be used for decisions only after the estimator has initialized, the current-sense offset has been calibrated, and the battery is inside the chemistry and temperature range the algorithm declares. Cellular transmission is a short, high current. If sampling misses the pulse, coulomb counting drops charge and the display reads high. A report should carry time, temperature, and whether the estimate is trustworthy. If the cloud stores only a percentage, it cannot tell a full charge from voltage rebound after a pulse. When the level is low, reduce transmit power or postpone the upgrade before an undervoltage reset, rather than discovering that the data cannot go out.
Applying a rest-voltage table directly to a loaded condition treats the sag during a burst as a sudden loss of charge, and the rebound as charge that was put back in. Ignoring health and integrating against factory capacity makes an aged pack report empty too early, or discharge too far. Watching only the pack percentage hides the weak cell that has already hit its limit. If the module keeps caching an old value while offline and does not mark when it froze, the platform will schedule charging from a level that is hours old.
The interval after power-up, before the estimate has converged, should be marked invalid. Do not use it to trigger shutdown or to show remaining runtime to the user. After a cell change or a management-system reset, allow one full rest calibration instead of keeping the old integral residual. A message that includes percentage, voltage, current, and temperature is what later shows whether the estimate diverged or the sensing circuit failed.