Part XVIII: Integration Architecture
Connecting the mathematical models to live simulation — TraCI binary protocol, four bridge architectures with latency benchmarks, Protocol Buffer schemas, and complete orchestration of the multi-physics urban simulation engine.
Part Overview
Covers the TraCI binary protocol and TCP message format for SUMO communication, then benchmarks four bridge architectures: REST/FastAPI, ZeroMQ, gRPC with Protocol Buffers, and direct shared-memory. Designs the protobuf schema for physics engine dispatch and analyzes the complete latency budget for real-time multi-physics orchestration.
Key Topics
- • TraCI binary protocol
- • TCP message format
- • REST/FastAPI architecture
- • ZeroMQ bridge
- • gRPC + protobuf
- • Protocol Buffer schema
- • Physics engine dispatch
- • Latency budget analysis
3 chapters | From protocol to orchestration | Wiring the simulation engine
Chapters
Chapter 1: TraCI Protocol
The TraCI (Traffic Control Interface) binary protocol for commanding and querying SUMO at runtime. Dissects the TCP message format, command/response lifecycle, and subscription mechanism for efficient per-step data retrieval.
Chapter 2: Bridge Architectures
Benchmarks four bridge architectures for connecting physics engines to SUMO: REST/FastAPI for rapid prototyping, ZeroMQ for low-latency pub-sub, gRPC for typed contracts, and shared-memory for minimal overhead. Latency and throughput comparisons guide architecture selection.
Chapter 3: Protobuf Integration
Designs the Protocol Buffer schema for physics engine dispatch — message types for traffic state, emission vectors, canyon concentrations, and routing updates. Completes the orchestration layer with latency budget analysis for real-time multi-physics simulation.