LFTUC is a high-speed, raw file transfer protocol designed specifically for trusted local area networks (LANs). By bypassing unnecessary end-to-end encryption and transit security overhead meant for public networks, LFTUC achieves maximum possible transfer speeds across local devices.
⚠️ IMPORTANT BRANCH NOTICE This specific branch contains the module with path URIs that correspond exclusively to the Android File System. Do NOT use this branch or its path URIs in a Windows implementation of the LFTUC Protocol.
LFTUC utilizes a lightweight multicast echo system for device discovery on the local network. Below is the strict payload structure required for broadcasting and parsing server visibility echoes.
Each payload is constructed as a delimited string using the * character as a separator.
| Field | Size Limit | Description & Examples |
|---|---|---|
| Address Code | 1 byte | Dictates the address type being broadcast.1 = IPv6 Address use case2 = MAC Address use case |
| Separator | 1 byte | Always * |
| Device/Server Name | 20 bytes (max) | The identifying name of the host device. Example: Desktop_LCFERT or Android-GPVE |
| Separator | 1 byte | Always * |
| Destination Address | 18 - 27 bytes | The actual network address of the host. Example (IPv6): fe80::8e13:9bba:740b:4792%3Example (MAC): 00-E0-2D-1D-D6-DC |
| Separator | 1 byte | Always * |
| Server Port | 5 bytes (max) | The port the LFTUC server is listening on. Can be null if not applicable (e.g., pure MAC broadcasts).Example: 65000, 8080, or null |
| Separator | 1 byte | Always * |
| Online Status | 1 byte | Boolean integer representing server availability.1 = Online0 = Offline |
Based on the architecture above, a complete payload broadcast from an online server should be constructed exactly like these examples:
Example 1: IPv6 Address Use Case (Address Code 1)
1*Desktop_LCFERT*fe80::8e13:9bba:740b:4792%3*8080*1
2*Android-GPVE*00-E0-2D-1D-D6-DC*null*1
This is the Payload Structure for multicast echoes:
