TEAM DETAILS:
TEAM NAME:- PROTECTWAVE (RESCUENET)
TEAM LEADER:-
PROBLEM STATEMENT:- IN DISASTER SCENARIOS (FLOODS, EARTHQUAKES, CYCLONES), INTERNET AND
CELLULAR NETWORKS OFTEN [Link] CANNOT RELY ON MOBILE DATA OR TRADITIONAL
MESSAGING APPS TO CALL FOR HELP. RESCUE TEAMS NEED A ROBUST, OFFLINE COMMUNICATION
SYSTEM THAT CAN TRANSMIT SOS ALERTS WITHOUT INTERNET CONNECTIVITY.
SOLUTION OVERVIEW
•Offline Emergency Communication: Enables victims to send SOS alerts using local TCP/IP or
Bluetooth/Wi-Fi Direct mesh networking, even when there is no internet or cellular network.
•Accurate Distance Calculation: Uses the Haversine formula to calculate the real-world distance
between the rescue station and the victim’s location.
•Real-Time Rescue Dashboard: Displays incoming SOS alerts on a Python Tkinter GUI for quick
monitoring and response by rescue operators.
•Smart Navigation Support: Generates a Google Maps route link for rescue teams when internet
connectivity is available at the rescue station.
•Disaster-Ready & Reliable: Designed to function during network blackouts, making it ideal for
natural disasters, emote areas, and emergency situations.
OPPORTUNITIES & STANDOUT POINTS
Opportunities
Growing Need for Offline Safety Tech: Increased awareness of network failures in disasters and
remote areas creates demand for robust offline SOS systems.
Rural & Disaster-Prone Region Use Cases: Huge applicability in areas with frequent network
blackouts where traditional emergency services fail.
Integration with IoT & Smart Devices: Can be extended to wearables, sensors, and drones for
automated and scalable rescue ecosystems.
Partnerships with Governments & NGOs: Opportunity for public safety programs, disaster
management agencies, and community health initiatives.
Commercialization Potential: Safety features such as offline SOS could be licensed into consumer
apps, insurance services, and hardware vendors.
Standout Points
Location-Aware Rescue Support: Combines offline alerting with distance calculations (Haversine),
improving rescue prioritization.
Scalable & Extensible Architecture: Can evolve into broader emergency networks with mesh
upgrades, IoT sensors, and voice alerts.
Low Cost & Easy Deployment: Built on common technologies (Python, Bluetooth,Wi-Fi Direct),
reducing barriers to adoption.
LIST OF FEATURES OFFERED BY THE
SOLUTION (OFFLINE SOS NETWORK)
No Internet Required: SOS alerts are transmitted via local
TCP/IP, Bluetooth, or Wi-Fi Direct.
Resilient Communication: Works even when mobile towers and
internet fail.
Multi-threaded Server: Handles multiple SOS alerts
simultaneously.
Real-time Dashboard: Immediate visualization of alerts.
Distance Calculation: Helps prioritize nearest victims.
Google Maps Integration: Provides navigation when internet is
restored at the rescue station.
•Data Preparation
•Exported SOS alerts into a CSV file with fields: ID, Latitude, Longitude, Distance, Timestamp.
•Cleaned data so Distance was numeric and Timestamp was Date/Time.
•Connecting to Looker Studio
•Uploaded the CSV as a data source.
•Defined field types (Latitude/Longitude as numbers, Timestamp as Date/Time).
•Created calculated fields like Distance_Range for grouping.
•Building Visualizations
•Bar Chart → Grouped SOS alerts by distance ranges.
•Box Plot → Showed spread, median, and outliers in distances.
•Heatmap → Highlighted peak times of SOS alerts.
•Geo Map → Plotted SOS coordinates on a map for spatial analysis.
•Scorecards/KPIs → Displayed total SOS, max distance, average distance, and median distance.
•Google Looker Link: [Link]
WHAT GOOGLE TECHNOLOGY USED? GOOGLE LOOKER STUDIO
PROCESS FLOW DIAGRAM & USE-CASE DIAGRAM
Use Case Scenarios
Natural Disasters: Enables victims to send SOS
alerts even when internet and mobile networks fail.
Remote & Rural Areas: Provides emergency
communication in locations with no cellular
coverage.
Military / Security Zones: Allows troops to
transmit offline distress signals in blackout or
restricted areas.
Hackathons & Academia: Demonstrates
resilient, offline communication for educational and
prototype showcases.
WIREFRAMES/MOCK DIAGRAMS OF THE PROPOSED SOLUTION
ARCHITECTURE DIAGRAM OF THE
PROPOSED SOLUTION
SNAPSHOTS OF MVP
ADDITIONAL DETAILS/ FUTURE DEVELOPMENT
Future Enhancements
Mesh Networking: Devices relay SOS messages
across nearby phones.
Priority Alerts: Classify SOS as critical, moderate, or
minor.
Offline Maps: Cache maps for navigation without
internet.
Database Logging: Store SOS history using
SQLite/PostgreSQL.
Victim Identification: Include name, device ID, or
SOS code.
Auto GPS Capture: Automatically send location
coordinates.
Alert Notifications: Sound alarms or visual alerts on
dashboard.
Multi-Station Support: Share SOS alerts across
multiple rescue stations.
EXTERNAL RESOURCES & REFERENCE LINKS
GitHub:- [Link]
Demo Video Link: 1. how the rescue station works when it receives sos from the nearby phone:
[Link]
2. SOS networking simulation:
[Link]
[Link]
[Link]
THANK YOU