{"id":576,"date":"2025-12-15T10:17:56","date_gmt":"2025-12-15T03:17:56","guid":{"rendered":"https:\/\/blog.datacore.vn\/?p=576"},"modified":"2026-01-07T17:25:14","modified_gmt":"2026-01-07T10:25:14","slug":"digital-levees-episode-2-decentralize-infrastructure-designing-an-unbreakable-survival-network","status":"publish","type":"post","link":"https:\/\/blog.datacore.vn\/en\/digital-levees-episode-2-decentralize-infrastructure-designing-an-unbreakable-survival-network\/","title":{"rendered":"DIGITAL LEVEES &#8211; EPISODE 2: Decentralize Infrastructure \u2013 Designing An &#8220;UNBREAKABLE&#8221; Survival Network"},"content":{"rendered":"\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">TL;DR (Too Long; Didn&#8217;t Read)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>The Problem:<\/strong> As analyzed in Episode 1, the centralized <strong>Hub-and-Spoke<\/strong> telecommunications model is fundamentally flawed for disaster scenarios due to the <strong>Single Point of Failure (SPOF)<\/strong> at Base Transceiver Stations (BTS).<\/li>\n\n\n\n<li><strong>The Architectural Solution:<\/strong> We must shift to a <strong>Mesh Topology<\/strong> where network resilience is achieved through <strong>Self-healing<\/strong> and <strong>Multi-hop routing<\/strong>, eliminating reliance on a central coordinator.<\/li>\n\n\n\n<li><strong>The Implementation:<\/strong> We propose <strong>V-FloodNet<\/strong>, a Hybrid Architecture:\n<ul class=\"wp-block-list\">\n<li><strong>Urban Layer:<\/strong> High-density <strong>Smartphone Mesh<\/strong> (BLE\/Wi-Fi Aware).<\/li>\n\n\n\n<li><strong>Rural Layer:<\/strong> Long-range <strong>LoRaWAN Mesh<\/strong> for lifeline connectivity in remote areas.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Protocol Optimization:<\/strong> Transition from heavy HTTP\/TCP to lightweight <strong>MQTT-SN\/UDP<\/strong> and implement <strong>Store-and-Forward<\/strong> mechanisms to handle intermittent connectivity.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">1. Introduction: Beyond the &#8220;Offline Shock&#8221;<\/h3>\n\n\n\n<p>In <a href=\"https:\/\/blog.datacore.vn\/digital-levees-episode-1-system-failure-analysis-why-does-multi-billion-dollar-infrastructure-still-go-dark-in-the-eye-of-the-storm\/\" data-type=\"post\" data-id=\"535\"><strong>Episode 1: System Failure Analysis<\/strong>,<\/a> we conducted a &#8220;post-mortem&#8221; on the information infrastructure during the 2024-2025 disaster seasons. The conclusion was painful but necessary: We gambled our critical lifeline communications on antenna towers\u2014the infrastructure most vulnerable to Category 4+ typhoons. When the BTS towers snapped or power grids failed, millions of modern smartphones became isolated silicon bricks.<\/p>\n\n\n\n<p>Episode 2 tackles the most challenging engineering problem at the <strong>Physical Layer<\/strong>: <strong>How do we maintain digital connectivity when the national power grid and Internet backbone suffer a total blackout?<\/strong><\/p>\n\n\n\n<p>The answer does not lie in building stronger concrete towers (economically unfeasible), but in a fundamental <strong>Architectural Paradigm Shift<\/strong>: Moving from dependence on a central &#8220;Hub&#8221; to leveraging the collective power of &#8220;Edge&#8221; devices.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. The Paradigm Shift: From Star to Mesh Topology<\/h3>\n\n\n\n<p>To build a <strong>Resilient System<\/strong>, we must ruthlessly eliminate Single Points of Failure (SPOF).<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">2.1. Technical Analysis of Topologies<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Current Model: Star Topology (Hub-and-Spoke)Every client device connects directly to a central Router\/BTS.\n<ul class=\"wp-block-list\">\n<li><em>Pros:<\/em> Centralized management, high throughput in ideal conditions, low latency.<\/li>\n\n\n\n<li><em>Fatal Flaw:<\/em> If the Central Node fails, the entire network collapses. There is no redundancy path.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Proposed Model: Mesh TopologyIn a Mesh network, the distinction between Client and Router blurs. Every device (Node) acts as a receiver, sender, and relay.\n<ul class=\"wp-block-list\">\n<li><em>Mechanism:<\/em> Data travels via <strong>Multi-hop Routing<\/strong>. If Node A wants to message Node Z but is out of range, the packet hops A <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/blog.datacore.vn\/wp-content\/ql-cache\/quicklatex.com-76319e471bb0c08bfa33603fd4f71eb2_l3.png\" class=\"ql-img-inline-formula quicklatex-auto-format\" alt=\"&#92;&#114;&#105;&#103;&#104;&#116;&#97;&#114;&#114;&#111;&#119;\" title=\"Rendered by QuickLaTeX.com\" height=\"10\" width=\"17\" style=\"vertical-align: -1px;\"\/> B <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/blog.datacore.vn\/wp-content\/ql-cache\/quicklatex.com-76319e471bb0c08bfa33603fd4f71eb2_l3.png\" class=\"ql-img-inline-formula quicklatex-auto-format\" alt=\"&#92;&#114;&#105;&#103;&#104;&#116;&#97;&#114;&#114;&#111;&#119;\" title=\"Rendered by QuickLaTeX.com\" height=\"10\" width=\"17\" style=\"vertical-align: -1px;\"\/> C <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/blog.datacore.vn\/wp-content\/ql-cache\/quicklatex.com-76319e471bb0c08bfa33603fd4f71eb2_l3.png\" class=\"ql-img-inline-formula quicklatex-auto-format\" alt=\"&#92;&#114;&#105;&#103;&#104;&#116;&#97;&#114;&#114;&#111;&#119;\" title=\"Rendered by QuickLaTeX.com\" height=\"10\" width=\"17\" style=\"vertical-align: -1px;\"\/> &#8230; <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/blog.datacore.vn\/wp-content\/ql-cache\/quicklatex.com-76319e471bb0c08bfa33603fd4f71eb2_l3.png\" class=\"ql-img-inline-formula quicklatex-auto-format\" alt=\"&#92;&#114;&#105;&#103;&#104;&#116;&#97;&#114;&#114;&#111;&#119;\" title=\"Rendered by QuickLaTeX.com\" height=\"10\" width=\"17\" style=\"vertical-align: -1px;\"\/> Z.<\/li>\n\n\n\n<li><em>Self-healing Capability:<\/em> Routing protocols (like AODV, OLSR, or proprietary LoRa Mesh algorithms) continuously update the routing table. If Node B runs out of battery or is destroyed, the network automatically recalculates a new path via Node D or E.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Engineering Insight:<\/strong> <em>&#8220;In a disaster context, network redundancy is not waste; it is the core requirement for survival.&#8221;<\/em><\/p>\n<\/blockquote>\n\n\n\n<p>Below is a visual comparison of how these topologies behave under stress:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"559\" src=\"https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/Datacore_blog_digital-levee_ep2_mesh-vs-central-1024x559.jpg\" alt=\"Datacore Digital Levee: Mesh and Cetranlize\" class=\"wp-image-578\" srcset=\"https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/Datacore_blog_digital-levee_ep2_mesh-vs-central-1024x559.jpg 1024w, https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/Datacore_blog_digital-levee_ep2_mesh-vs-central-300x164.jpg 300w, https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/Datacore_blog_digital-levee_ep2_mesh-vs-central-768x419.jpg 768w, https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/Datacore_blog_digital-levee_ep2_mesh-vs-central-1536x838.jpg 1536w, https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/Datacore_blog_digital-levee_ep2_mesh-vs-central-2048x1117.jpg 2048w, https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/Datacore_blog_digital-levee_ep2_mesh-vs-central-1320x720.jpg 1320w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\">Datacore Digital Levee: Mesh and Cetranlize<\/figcaption><\/figure>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">3. Proposed Architecture: V-FloodNet (Hybrid Mesh Layer)<\/h3>\n\n\n\n<p>Vietnam&#8217;s topography is complex, ranging from dense urban centers (Hanoi, Ho Chi Minh City) to fragmented mountainous regions and vast river deltas. No single Mesh technology is a &#8220;silver bullet.&#8221;<\/p>\n\n\n\n<p>Datacore proposes <strong>V-FloodNet<\/strong>\u2014a <strong>Hybrid Two-Tier Architecture<\/strong> optimized for specific contexts:<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"559\" src=\"https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_featurepic-1.jpg\" alt=\"Datacore Digital Levees VfloodNet\" class=\"wp-image-579\" srcset=\"https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_featurepic-1.jpg 1024w, https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_featurepic-1-300x164.jpg 300w, https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_featurepic-1-768x419.jpg 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\">Datacore Digital Levees Vflood-net<\/figcaption><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\">Tier 1: Urban High-Density Mesh<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Context:<\/strong> Urban flooding scenarios where population density is high, and inter-device distance is short (&lt;100m).<\/li>\n\n\n\n<li><strong>Core Technology:<\/strong> Leveraging citizen smartphones as network nodes via <strong>Bluetooth Low Energy (BLE)<\/strong> or <strong>Wi-Fi Aware (NAN)<\/strong>.<\/li>\n\n\n\n<li><strong>Principle:<\/strong> Turning every citizen into a &#8220;mobile base station.&#8221; When thousands of people enable this mode, they create a massive connectivity cloud. An SOS message from a user trapped in a deep alley can &#8220;hop&#8221; through neighbors&#8217; phones, to a rescue boat&#8217;s tablet, eventually reaching a device with an Internet uplink (e.g., a Starlink terminal).<\/li>\n\n\n\n<li><strong>Technical Challenges:<\/strong> OS Fragmentation (iOS and Android handle background Bluetooth advertising very differently) and battery drain.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Tier 2: Rural Long-Range Mesh<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Context:<\/strong> Mountainous regions or flash flood zones where population is sparse. Distances between clusters range from 2km to 10km. Bluetooth is useless here.<\/li>\n\n\n\n<li><strong>Core Technology:<\/strong> <strong>LoRaWAN (Long Range Wide Area Network)<\/strong> operating on unlicensed bands (e.g., 433MHz or 923MHz in Vietnam).<\/li>\n\n\n\n<li><strong>Deployment:<\/strong> Equipping village heads, forest rangers, and rescue teams with low-cost, battery-powered LoRa Mesh nodes.<\/li>\n\n\n\n<li><strong>LoRa Technical Advantages:<\/strong>\n<ul class=\"wp-block-list\">\n<li><strong>High Link Budget (up to 168dB):<\/strong> Allows signals to penetrate obstacles and reach 10-15km in rural Line-of-Sight conditions.<\/li>\n\n\n\n<li><strong>Low Power Consumption:<\/strong> A node can operate for weeks on a single 18650 battery using Deep Sleep cycles.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4. Deep Dive: Protocol Optimization for Low Bandwidth<\/h3>\n\n\n\n<p>System engineers must be realistic: Mesh Networks, especially LoRa, have extremely low <strong>Throughput<\/strong> (ranging from a few hundred bps to a few kbps).<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Warning:<\/strong> <em>&#8220;Do not design for video streaming or high-res photos on a rescue Mesh. This is a Lifeline connection, reserved for the most essential bytes of data.&#8221;<\/em><\/p>\n<\/blockquote>\n\n\n\n<p>To ensure the network doesn&#8217;t collapse under the load of thousands of SOS beacons, we must optimize at the <strong>Protocol Layer<\/strong>:<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">4.1. Replacing HTTP\/TCP with MQTT-SN\/UDP<\/h4>\n\n\n\n<p>Standard HTTP over TCP is too &#8220;heavy&#8221; (high overhead) due to the 3-way handshake and verbose headers.<\/p>\n\n\n\n<p><strong>Solution:<\/strong> Implement <strong>MQTT-SN (MQTT for Sensor Networks)<\/strong> over <strong>UDP<\/strong>. MQTT-SN is specifically designed for unstable, low-bandwidth environments, minimizing header size and connection establishment costs.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">4.2. Extreme Data Compression<\/h4>\n\n\n\n<p>Avoid JSON text formats like <code>{\"lat\": 21.0285, \"long\": 105.8542}<\/code>. Instead, utilize <strong>Bit-packing<\/strong> or Binary Serialization standards like <strong>Protobuf<\/strong> or <strong>FlatBuffers<\/strong>.<\/p>\n\n\n\n<p>A standard SOS packet should be compressed to under <strong>50 bytes<\/strong>, containing:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>Device_ID<\/code> (4 bytes)<\/li>\n\n\n\n<li><code>Timestamp<\/code> (4 bytes)<\/li>\n\n\n\n<li><code>GPS_Lat_Long<\/code> (Compressed to 8 bytes)<\/li>\n\n\n\n<li><code>Status_Code<\/code> (1 byte &#8211; e.g., 1=Medical, 2=Food, 3=Critical Water Level)<\/li>\n\n\n\n<li><code>Short_Message<\/code> (Max 30 char text)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">4.3. Store-and-Forward Mechanism<\/h4>\n\n\n\n<p>In storm conditions, Mesh connectivity is <strong>Intermittent<\/strong>. The system must adopt <strong>Delay-Tolerant Networking (DTN)<\/strong> principles.<\/p>\n\n\n\n<p>If a Node receives a message but cannot find a path to the next hop, it must <strong>Store<\/strong> the packet in its local buffer and continuously <strong>Retry<\/strong> until a connection is restored or a new path is discovered (<strong>Forward<\/strong>). This guarantees that no cry for help is lost, even if delivery is delayed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5. Real-World Benchmark: Lessons from Project Owl<\/h3>\n\n\n\n<p>This is not just theoretical engineering. After Hurricane Maria devastated Puerto Rico in 2017, leaving the island without power or comms for months, <strong>Project Owl<\/strong> (IBM Call for Code Winner) successfully deployed this exact model.<\/p>\n\n\n\n<p>They utilized small, floating IoT devices called &#8220;DuckLinks&#8221; powered by solar panels. These DuckLinks automatically formed a Mesh, creating a &#8220;Captive Portal&#8221; for civilians to connect via Wi-Fi and send basic text SOS messages. These messages hopped through the DuckLink network until they reached a &#8220;MamaDuck&#8221; hub equipped with a satellite uplink.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Lesson:<\/strong> A simple, low-cost, <strong>Rapid Deployment<\/strong> Mesh network provides significantly higher practical value than expensive systems that rely on the survival of the national power grid.<\/p>\n<\/blockquote>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"800\" height=\"420\" src=\"https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_project-owl-1.webp\" alt=\"Project Owl\" class=\"wp-image-577\" srcset=\"https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_project-owl-1.webp 800w, https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_project-owl-1-300x158.webp 300w, https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_project-owl-1-768x403.webp 768w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" \/><figcaption class=\"wp-element-caption\">Project Owl<\/figcaption><\/figure>\n\n\n\n<p>Description: Small yellow &#8220;DuckLink&#8221; boxes floating in floodwaters among submerged houses, emitting signal waves. A person on a roof connects via phone. On a distant, dry hill, a larger &#8220;MamaDuck&#8221; unit with a satellite dish receives the aggregated data and pushes it to the cloud.<\/p>\n<\/blockquote>\n\n\n\n<p>Reference source: Project Owl &#8211; ClusterDuck. Link: https:\/\/contest.techbriefs.com\/2019\/entries\/electronics-sensors-iot\/9982-0701-215912-project-owl-clusterduck<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6. Conclusion &amp; Bridge to Episode 3<\/h3>\n\n\n\n<p>In Episode 2, we have solved the problem of &#8220;Building the Pipes.&#8221; We have defined a decentralized infrastructure architecture capable of self-sustaining connectivity in worst-case scenarios.<\/p>\n\n\n\n<p>However, restoring connectivity is only half the battle. When thousands of people simultaneously send SOS messages via the Mesh, command centers will face a new disaster: <strong>A DDoS attack of&#8230; rescue data.<\/strong><\/p>\n\n\n\n<p>How do we distinguish between a &#8220;Water is in my yard&#8221; message (Low Urgency) and a &#8220;Heart attack patient, water at chest level&#8221; message (Critical Urgency) amidst a sea of chaotic, unstructured, and noisy data?<\/p>\n\n\n\n<p>The physical infrastructure needs a &#8220;Brain&#8221; to process this flow. This is where <strong>Big Data and Artificial Intelligence<\/strong> enter the equation.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p>COMING UP IN EPISODE 3: DATA &amp; AI \u2013 TURNING CHAOS INTO SIGNAL.<\/p>\n\n\n\n<p>We will deep dive into NLP models (like PhoBERT) for spam filtering, Computer Vision for water level measurement, and Data Fusion strategies to merge fragmented information sources.<\/p>\n\n\n\n<p><strong>MISSED THE PREVIOUS EPISODE?<\/strong> To fully understand the context of the &#8220;Offline Shock&#8221; and why centralized architecture fails, catch up here: <a href=\"https:\/\/blog.datacore.vn\/digital-levees-episode-1-system-failure-analysis-why-does-multi-billion-dollar-infrastructure-still-go-dark-in-the-eye-of-the-storm\/\" data-type=\"post\" data-id=\"535\">DIGITAL LEVEES \u2013 EPISODE 1: System failure analysis \u2013 Why does multi-billion dollar infrastructure still &#8220;GO DARK&#8221; in the eye of the storm?<\/a><\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>TL;DR (Too Long; Didn&#8217;t Read) 1. Introduction: Beyond the &#8220;Offline Shock&#8221; In Episode 1: System Failure Analysis, we conducted a &#8220;post-mortem&#8221; on the information infrastructure during the 2024-2025 disaster seasons. The conclusion was painful but necessary: We gambled our critical lifeline communications on antenna towers\u2014the infrastructure most vulnerable to Category 4+ typhoons. When the BTS [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":571,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","_swt_meta_header_display":false,"_swt_meta_footer_display":false,"_swt_meta_site_title_display":false,"_swt_meta_sticky_header":false,"_swt_meta_transparent_header":false,"footnotes":""},"categories":[6,59],"tags":[],"class_list":["post-576","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-xa-hoi"],"uagb_featured_image_src":{"full":["https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_featurepic.jpg",1024,559,false],"thumbnail":["https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_featurepic-150x150.jpg",150,150,true],"medium":["https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_featurepic-300x164.jpg",300,164,true],"medium_large":["https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_featurepic-768x419.jpg",768,419,true],"large":["https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_featurepic.jpg",1024,559,false],"1536x1536":["https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_featurepic.jpg",1024,559,false],"2048x2048":["https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_featurepic.jpg",1024,559,false],"trp-custom-language-flag":["https:\/\/blog.datacore.vn\/wp-content\/uploads\/2025\/12\/datacore_blog_dedieuso_ky2_featurepic.jpg",18,10,false]},"uagb_author_info":{"display_name":"Kien Vu","author_link":"https:\/\/blog.datacore.vn\/en\/author\/kienvq\/"},"uagb_comment_info":1,"uagb_excerpt":"TL;DR (Too Long; Didn&#8217;t Read) 1. Introduction: Beyond the &#8220;Offline Shock&#8221; In Episode 1: System Failure Analysis, we conducted a &#8220;post-mortem&#8221; on the information infrastructure during the 2024-2025 disaster seasons. The conclusion was painful but necessary: We gambled our critical lifeline communications on antenna towers\u2014the infrastructure most vulnerable to Category 4+ typhoons. When the BTS&hellip;","_links":{"self":[{"href":"https:\/\/blog.datacore.vn\/en\/wp-json\/wp\/v2\/posts\/576","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.datacore.vn\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.datacore.vn\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.datacore.vn\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.datacore.vn\/en\/wp-json\/wp\/v2\/comments?post=576"}],"version-history":[{"count":2,"href":"https:\/\/blog.datacore.vn\/en\/wp-json\/wp\/v2\/posts\/576\/revisions"}],"predecessor-version":[{"id":600,"href":"https:\/\/blog.datacore.vn\/en\/wp-json\/wp\/v2\/posts\/576\/revisions\/600"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.datacore.vn\/en\/wp-json\/wp\/v2\/media\/571"}],"wp:attachment":[{"href":"https:\/\/blog.datacore.vn\/en\/wp-json\/wp\/v2\/media?parent=576"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.datacore.vn\/en\/wp-json\/wp\/v2\/categories?post=576"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.datacore.vn\/en\/wp-json\/wp\/v2\/tags?post=576"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}