Model for Non-IP Prototyping Over Radio: Architecture, Components, and Use Cases
Model for Non-IP Prototyping Over Radio
As 5G develops and we start looking ahead to 6G, it’s clear that traditional IP-based communication just doesn’t cut it for every situation. There are some emerging applications — think ultra-low latency in industrial automation, real-time control systems, and autonomous networks — that really need communication methods that completely skip the IP layer.
The Non-IP Prototyping over Radio model shown above illustrates how devices can connect via radio links using a non-IP data delivery system, allowing apps to interact directly over the radio without relying on TCP/IP.
What is Non-IP Prototyping Over Radio?
Non-IP Prototyping is about creating and testing communication systems that don’t depend on Internet Protocol (IP) for sending data. Instead, these systems utilize custom protocol handlers to manage data directly through the radio interface.
This approach is particularly useful in:
Industrial IoT (IIoT)
Mission-critical communications
Tactile Internet
5G URLLC (Ultra-Reliable Low-Latency Communication)
Future 6G AI-driven networks
By sidestepping IP overhead, Non-IP systems can achieve:
Lower latency
Higher reliability
Better determinism
Reduced processing needs
Understanding the Architecture
The diagram shows the Non-IP Prototyping model, which has two main parts:
User Equipment (UE) — This is the device that sends or receives data, like sensors or robots.
Server Host — This is where the data gets processed or received.
These two components talk to each other over a radio network, kept safe from outside electromagnetic interference by being placed in a Faraday cage, which is crucial for controlled testing.
Core Components of the Architecture
- Application Layer
At the top, both the User Equipment (UE) and the Server Host have application modules that generate and process user data. For example:
UE application: collecting sensor data, sending control signals to robots.
Server application: analyzing data, running machine learning tasks, or dispatching commands remotely.
These applications connect to the Application Client, which takes care of data exchange with the lower layers.
- Baseband Layer
The Baseband layer is responsible for radio signal modulation, demodulation, and physical layer control. It’s here that the digital signal gets transformed for radio transmission or brought back to a usable format.
Key tasks include:
Frequency allocation
Modulation (like QAM or OFDM)
Channel coding and decoding
Timing and synchronization for the radio
This layer makes sure that non-IP data packets are formatted correctly and sent through the air interface.
Operating System (OS)
Within the OS, you’ll find three important components:
Kernel Space (KS)
User Space (US)
Protocol Handler Library (PH)
These manage protocol logic, buffer handling, and communication between layers.
Here’s a quick rundown of what they do:
Kernel Space (KS): Operates at the base level of the OS. It connects directly with hardware, managing real-time scheduling and protocol stack integration.
User Space (US): This part runs higher-level protocols and applications, giving room for debugging and testing.
Protocol Handler Library (PH): This connects user and kernel spaces, defining how data gets formatted, parsed, and sent, essentially taking the place of the conventional IP/TCP stack.
Application Client
The Application Client acts as a bridge between the application and radio communication layers. It manages:
Session control
Data encapsulation
Picking the protocol (whether custom or standard non-IP)
Timing and synchronization for sending data
Both the UE and Server Host have their own application clients to make sure the communication is quick and smooth.
Radio Network Interface
The radio network, shown by the dashed red line, connects the UE and server host. Notable features include:
Non-IP data exchange over radio
Support for 5G NR physical layer
Controlled test environments (like inside a Faraday cage)
The Faraday cage (marked with the outer blue boundary) keeps the system shielded from outside radio interference — a typical setup in telecom labs for prototyping.
How Non-IP Communication Works
Here’s a simplified breakdown of the communication process in this model:
Application Data Generation: The UE’s application creates data packets (like sensor readings).
Protocol Encapsulation: The Protocol Handler Library (PH) formats the data according to non-IP standards, bypassing TCP/IP.
Baseband Transmission: The baseband layer modulates the data and sends it over the radio interface.
Reception and Decoding: The server host’s baseband takes the received signal and demodulates it.
Data Interpretation: The PH and Application Client on the server decode the data for the final application.
Use Cases of Non-IP Prototyping
Non-IP prototyping isn’t just theory — it’s a key player in future communication tech. Here are some major applications:
Industrial Automation: Direct link between machines in a factory setting.
5G URLLC Research: Testing ultra-reliable low-latency links without IP.
Autonomous Systems: Communication between drones or vehicles that require instant reactions.
Defense and Tactical Systems: Quick, secure communication in challenging environments.
Edge Computing: Sending data straight to local servers without the routing overhead.
Challenges in Non-IP Prototyping
Despite the advantages, there are some challenges:
Interoperability: Non-IP systems may struggle to integrate with existing IP networks.
Security: New security measures need to be developed since IP encryption isn’t applicable here.
Standardization: Organizations like 3GPP and ETSI are still working on standard definitions for non-IP transport in future updates.
Scalability: Handling multiple devices and sessions needs efficient addressing techniques.
Future Outlook: Non-IP in 6G Networks
As the telecom industry moves toward 6G, the focus on deterministic, AI-driven, low-latency communication will become even more critical. Non-IP networking is likely to support:
Network slicing for specialized applications
AI-driven control methods
Holographic and tactile Internet technologies
Non-terrestrial networks (like satellites and drones)
The Non-IP Prototyping model is set to be a testbed for validating these next-gen technologies before they launch.
Conclusion
The Model for Non-IP Prototyping over Radio marks a big leap in telecom innovation. By getting rid of IP dependency, it opens the door to ultra-efficient, low-latency, and deterministic communication systems—essential for Industry 4.0 and future 6G connectivity.
With the integration of Protocol Handler Libraries, Kernel/User Space management, and radio-based communication, researchers now have the opportunity to explore faster, leaner, and more intelligent communication solutions.
As the telecom landscape pushes into a hyperconnected, intelligent, and autonomous future, Non-IP communication is more than just a concept — it's shaping the future of seamless connectivity.