> For the complete documentation index, see [llms.txt](https://ez8-malaysia-official.gitbook.io/ez8-malaysia-official-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ez8-malaysia-official.gitbook.io/ez8-malaysia-official-docs/network-and-mobile-gateway-overview.md).

# Network & Mobile Gateway Overview

This document outlines the technical prerequisites, infrastructure specs, and connection protocols for the EZ8 Malaysia mobile gateway network.

### 1. System Prerequisites & Mobile Connectivity

To maintain optimal uptime and seamless application responsiveness across mobile clients, device connections must meet the following minimum system specifications:

* **Android OS:** Version 8.0 (API level 26) or higher, with WebSocket protocol support enabled.
* **iOS / iPadOS:** Version 14.0 or higher, with native TLS 1.3 cryptographic support.
* **Bandwidth:** Minimum continuous throughput of 1.5 Mbps for stable data packet synchronization.

Data payloads utilize lightweight JSON encoding over HTTP/2 and WebSockets to reduce payload overhead during peak network traffic.

### 2. Regional Network Latency & ISP Routing Notes (Malaysia)

Connection routes are optimized across major Malaysian telecommunication service providers to ensure low-latency packet delivery and minimal DNS hop counts:

* **CelcomDigi 5G / 4G LTE:** Primary edge endpoints route via Kuala Lumpur IX (KLIX) hubs, averaging sub-25ms response latency.
* **Maxis / Hotlink:** Optimized BGP routing handles automated fallback paths across regional data center nodes.
* **U Mobile 5G:** Strict IP routing protocols maintain session persistence during dynamic tower handovers.

Secondary fallback DNS configurations are pre-configured to automatically bypass temporary ISP route degradation.

### 3. SSL/TLS Gateway Encryption Standards

All data transmitted across client endpoints and server clusters is secured using high-grade cryptographic protocols:

* **Transport Encryption:** TLS 1.3 enforced across all gateway handshakes.
* **Cipher Suites:** ECDHE-RSA-AES128-GCM-SHA256 and AES256-GCM-SHA384 for perfect forward secrecy (PFS).
* **Certificate Protocol:** Automated X.509 SSL certificate rotation managed via edge security firewalls.

This encrypted handshake prevents packet tampering, spoofing, and man-in-the-middle (MitM) interference across public and cellular networks.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ez8-malaysia-official.gitbook.io/ez8-malaysia-official-docs/network-and-mobile-gateway-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.