PhD in Engineering with 5+ years of experience in research (IoT security). Published & presented papers, found a few bugs here and there.
Tech I've Worked With:
- Languages: Python, C, Rust-curious. Experience across the stack, from firmware to full applications.
- Wireless & Networking: Signal processing, low-level protocols, network engineering, with a focus on connectivity (5G, BLE, WiFi).
- Tools: Wireshark, git, CI/CD, Docker. Focused on whatever gets the job done.
Although my academic background is in IoT security, I'm not seeking a security role. I excel when solving challenges that blend multiple disciplines, such as UX. If you're working on something innovative and need a versatile engineer with a hacker’s mindset, let's connect.
Is "Non-IP Data Delivery" (basically SMS but for raw data packets, bound to a pre-defined application server) already a thing in practice?
In theory, you get all the power saving that the cellular network stack has to offer without having to maintain a connection. While on protocol layer NIDD is almost handled like an SMS (paging, connectionless), it is not routed through a telephony core (and hence sloooow). The base station / core will directly forward it to your predefined application server.
It has been heavily advertised, but its support is inconsistent. If you are deploying devices across multiple regions, you likely want them to function the same way everywhere.
Tech I've Worked With:
- Languages: Python, C, Rust-curious. Experience across the stack, from firmware to full applications.
- Wireless & Networking: Signal processing, low-level protocols, network engineering, with a focus on connectivity (5G, BLE, WiFi).
- Tools: Wireshark, git, CI/CD, Docker. Focused on whatever gets the job done.
Although my academic background is in IoT security, I'm not seeking a security role. I excel when solving challenges that blend multiple disciplines, such as UX. If you're working on something innovative and need a versatile engineer with a hacker’s mindset, let's connect.