MILESGO
Request a Quote

Smart City & MunicipalS59

City IoT Edge Gateway

The problem

Each city department buys its own sensors and cloud, so the same street carries several networks and data cannot be shared between services.

Solution overview

MILESGO gateways collect data from LoRaWAN wireless sensors, environmental stations (PM2.5, PM10, noise, weather), street light controllers, level sensors, bin fill-level sensors over LoRaWAN / Modbus RTU / Modbus TCP, and deliver it to the city IoT platform, a cloud platform (MQTT), third-party platforms (HTTP API) as MQTT / OPC UA / BACnet/IP. Field equipment keeps its own protocol and control logic; integration is done by configuration and point mapping, not custom code.

Typical scope

  • LoRaWAN wireless sensors
  • environmental stations (PM2.5, PM10, noise, weather)
  • street light controllers
  • level sensors
  • bin fill-level sensors

Protocol path

LoRaWAN / Modbus RTU / Modbus TCP → MQTT / OPC UA / BACnet/IP

Implementation checklist for the project manager

  • Run a LoRaWAN coverage survey and pick the regional band (EU868 / US915 / AU915 / AS923 / KR920 / CN470) before ordering.
  • Keep OT networks segregated and use VPN for remote access instead of opening ports to the internet.
  • Fix a site / asset naming convention before the first site so data from all sites can be compared.
  • Standardise one configuration template per equipment type so further sites are copied, not rebuilt.
  • Outdoor sites need a weatherproof, ventilated enclosure with surge protection; the gateways are panel-mount devices (working range -20 °C to +70 °C).
  • Where equipment only offers a vendor API or cloud, confirm access rights, data rate and costs with the vendor before design.

Project deliverables

  • Signed point table and protocol mapping
  • Gateway configuration files and backups
  • IP address plan and network drawing
  • FAT and SAT test records
  • As-built documentation and operator training

System architecture

Field layer: LoRaWAN wireless sensors, environmental stations (PM2.5, PM10, noise, weather), street light controllers, level sensors, bin fill-level sensors, connected over LoRaWAN / Modbus RTU / Modbus TCP. Edge and integration layer: MILESGO protocol gateways and edge controllers, mounted on DIN rail in existing panels, polling each device, time-stamping values and buffering them locally. Upper layer: the city IoT platform, a cloud platform (MQTT), third-party platforms (HTTP API), which receives the data as MQTT / OPC UA / BACnet/IP. Remote access for maintenance runs over VPN rather than open internet ports.

System composition

Field devices
LoRaWAN wireless sensors, environmental stations (PM2.5, PM10, noise, weather), street light controllers, level sensors, bin fill-level sensors
Edge / integration
MILESGO protocol gateways and edge controllers
Upper systems
the city IoT platform, a cloud platform (MQTT), third-party platforms (HTTP API) (MQTT / OPC UA / BACnet/IP)
Tools and commissioning
Web-based configuration, point table import/export (Excel), off-site simulation and on-site diagnostic tools

Software and AI capabilities

  • Anomaly detection on trend dataRoadmap
  • Natural language questions over site dataRoadmap

Delivery steps

  1. 1

    Site survey and point list

    Inventory devices, protocols, register maps, panel space, power and network paths.

  2. 2

    Design and point table sign-off

    Map every point to the target protocol and system; agree it with the client and the upper-system contractor.

  3. 3

    Configuration and FAT

    Build the gateway configuration off site, simulate it and test against the signed point table.

  4. 4

    Installation and wiring

    Mount gateways on DIN rail, wire RS-485 / I/O / Ethernet, apply the IP plan.

  5. 5

    SAT and alarm tests

    Verify values against local readings, test every alarm and command end to end.

  6. 6

    Handover and support

    Hand over configuration backups, point table and as-built documents; train operators.

Customer value

  • Open interfaces (BACnet, Modbus, OPC UA, MQTT, HTTP) avoid lock-in to one vendor
  • Data ready for cloud platforms and analytics
  • Configuration templates reused across sites
  • One view of all subsystems instead of separate vendor consoles

More solutions in Smart City & Municipal

Tell us about your project

Send the protocols, point count and target system. A sales and engineering pair reviews every submission.

Discuss Your Project