GROUP 7 (SHIELD)

Project Workflow: 5G-Enabled Traffic Light Control System

 Problem Statement:
Urban traffic congestion at four-way intersections is a growing problem, leading to increased travel
times, fuel consumption, and air pollution. Conventional traffic light systems operate on fixed timers,
which are inefficient as they don't adapt to real-time, fluctuating traffic loads. This static approach
results in unnecessary waiting times on empty roads while other, heavily congested roads are stuck
at a red light.

Centralized, wired control systems can be expensive to implement and maintain, and may still suffer
from latency. There is a need for a more flexible, responsive, and cost-effective solution for real-time
traffic management.

 Objective:
This project aims to demonstrate the feasibility of using emerging 5G technology and IoT hardware
(ESP32, pressure sensors) & CPE to create a prototype for a Traffic Management Using Smart 5G-
Enabled Traffic Lights system eliminating wired infrastructure that can be managed remotely,
instantly, and efficiently.

 Phase 1: Planning, Research, and System Design 📝

This initial phase focuses on defining the project scope, architecture, and required components.

1. Define Requirements & Scope:

o The system must control a full traffic light sequence (Red, Yellow, Green) for a four-way
intersection using LEDs.
o It must detect the presence of vehicles on each of the approaches using pressure
sensors.
o An ESP32 will serve as the core controller, processing sensor data and managing the
traffic light logic.
o The system's primary logic will be automated based on sensor input (e.g., the presence
of a car triggers a request for a green light).
o A control application will serve as a monitoring dashboard and an interface for manual
override commands.
o Communication will occur over a Wi-Fi network created by a CPE, ensuring low-latency
data transmission.

2. Component Selection:

o Microcontroller: ESP32 DevKit (e.g., ESP32-WROOM-32).

o Sensors: pressure sensors.

o Display: 2-digit common cathode seven-segment display.

o Network Device: Any 5G-capable handset with hotspot functionality.

o Prototyping: Breadboard, jumper wires, and current-limiting resistors (e.g., 220Ω).

 Phase 2: Hardware Assembly and Wiring

This phase involves building the physical circuit and a model of the intersection for the prototype.

 Model Construction: Build a scaled-down model of a intersection.

 Sensor Installation: Securely place pressure sensors on the surface of each road approach
before the stop line.

 Circuit Assembly: Connect all components to the ESP32.

o Connect the output of each pressure sensor to a separate analog or digital input pin
on the ESP32.

o Connect the LED clusters (Red, Yellow, Green for each road) to the ESP32's GPIO pins,
using resistors to limit the current.

 Phase 3: Software Development 💻

This phase involves writing the code for the ESP32 controller and the control application for
monitoring and control.

1. ESP32 Firmware Development:

 Wi-Fi Connection & Web Server: Write code to connect the ESP32 to the 5G CPE Network
and implement a web server. Define endpoints for status checks and manual overrides (e.g.,
/status, /forceGreenNorth).

 Sensor Reading Logic: Develop functions to continuously read data from the four pressure
sensors. Implement a threshold-based logic to determine if a vehicle is present.

 Dynamic Traffic Light Logic: Create the main control loop. This algorithm will check the
sensor states to make intelligent decisions. For example:

o If a vehicle is detected on a red light, and the cross-traffic's green light has been
active for a minimum duration, initiate a safe light-change sequence.

o Prioritize the direction with the highest traffic count (advanced implementation).

o If no traffic is detected anywhere, default to a primary road green or a flashing

red/yellow state.

2. Control Application Development:

 UI Design: Create an interface with:

o A status display area to show real-time data from the sensors (e.g., "Vehicles
Detected: North, West").

o Emergency override buttons (e.g., "Force Green North," "Force Green East").

o A text input for the ESP32's IP address.

 Backend Logic: Use the "Web" component to send HTTP GET requests to the ESP32's web
server when an override button is pressed. Set up a timer to periodically poll the
/status endpoint and update the UI.
 Phase 4: Integration and Testing ⚙️

This phase combines the hardware and software to test the complete system.

1. Upload Firmware: Compile and upload the Arduino code to the ESP32.

2. Get IP Address: Open the Arduino IDE's Serial Monitor to view the IP address assigned to the
ESP32 by the 5G hotspot upon successful connection.

3. Install App: Build the controls applications and install in on the device to be used.

 System Test Scenarios:

o Power on the ESP32 circuit and confirm its CPE connection.

o Single Vehicle Test: Place an object on a pressure sensor for a road with a red light.
Verify that the system registers the vehicle and correctly cycles the lights to give that
road a green light.

o Priority Test: Simultaneously apply pressure to sensors on two competing roads. Verify
the system follows its programmed priority logic.

o Override Test: From the mobile app, press an override button and confirm that the
traffic lights respond immediately, overriding the automated logic.

o Status Test: Verify that the control application status display accurately reflects the real-
time state of the sensors.

Foundation & Core Software Development Full System Testing &

Development & Integration Finalization

Planning & ESP32 Network Full Logic

Sourcing & Server Coding Integration
Hardware Control Debugging &
Assembly Application Refinement
Sensor Development Scenario Testing
Installation Initial Final
Standalone Integration Test Documentaion &
Testing Deployment