MAPS™ 5G-ORAN E1AP Interface Emulator
Emulates the E1 reference point between gNB-CU-CP (Control Plane) and gNB-CU-UP (User Plane), supporting bearer context management, control-user plane separation, and related signaling procedures as defined by 3GPP standards.
Request a Demo / QuoteOverview
GL’s MAPS™ (Message Automation & Protocol Simulation) 5G-ORAN E1AP Interface Emulator is a powerful and flexible test solution designed to simplify validation of the E1 reference point in 5G networks. It emulates both gNB-CU-CP (Control Plane) and gNB-CU-UP (User Plane) network elements, enabling engineers to test real-world signaling scenarios across the E1 interface with ease. Compliant with 3GPP TS 38.463, it supports critical procedures such as E1 Setup, Bearer Context Management, Reset, and Configuration Update—ensuring that control and user plane separation in CU architectures is robust and standards-compliant from the outset.
With its built-in flexibility, GL’s MAPS™ platform accelerates development and reduces deployment risks for vendors and operators adopting ORAN and 5G CU-split architectures. It enables detailed verification, troubleshooting, and optimization of E1 interactions in a controlled lab environment—leading to better performance, faster rollouts, and improved reliability.
Key Features
- E1 Interface Emulation: Fully emulates gNB-CU-CP and gNB-CU-UP network elements for comprehensive E1 interface validation
- Dynamic Call Flows: Easily create, modify, and execute custom call flows using the built-in Script and Message Editor
- Fault Injection & Negative Testing: Insert malformed messages, delays, or resets to verify robustness under failure conditions
- High-Scale Simulation: Emulates multiple CUs and large bearer contexts to perform load and stress testing of control plane interactions
- Automated Test Execution: Schedule and run unattended tests with automation tools and remote access for continuous integration workflows
- Ready-to-Use Test Scripts: Includes pre-built scripts for common E1 procedures to accelerate setup and reduce testing time
- Interoperability Validation: Helps verify CU split architectures across different vendor implementations in a controlled lab environment
Applications
- Validate E1AP Procedures: Perform compliance testing for E1AP messages and procedures as defined in 3GPP standards
- Simulate Control and User Plane Split: Test interactions between gNB-CU-CP and gNB-CU-UP in multi-vendor deployments
- Stress and Load Testing: Evaluate system behavior under high bearer loads and signaling volumes to ensure performance stability
- Fault Tolerance Testing: Introduce errors, resets, or malformed signaling to assess recovery and resilience mechanisms
- Optimize CU Deployments: Troubleshoot and fine-tune CU split configurations before live network integration
- Regression Testing: Ensure stability and backward compatibility after software upgrades or configuration changes
- Automate Test Cycles: Enable repeatable, automated testing for faster development and reduced deployment risks
- Monitor and Analyze Performance: Access detailed statistics, traces, and event logs for in-depth debugging and optimization
Frequently Asked Questions
- What is the primary purpose of the 5G E1AP Interface Emulator?
- It emulates the E1 reference point between gNB-CU-CP and gNB-CU-UP, enabling validation of control–user plane separation and associated signaling. It supports bearer context management, configuration updates, and other key E1AP procedures defined in 3GPP TS 38.463, ensuring robust CU-split operation.
- Which E1AP procedures and protocols does the emulator support?
- It supports core E1AP procedures including E1 Setup, Bearer Context Setup/Modification/Release, Reset, Configuration Update, and related signaling interactions required for E1 interface initialization and control-plane/user-plane coordination.
- Can the emulator simulate multiple CUs and bearer contexts simultaneously?
- Yes, it supports high-scale simulation, allowing emulation of multiple CU elements, large numbers of bearer contexts, and extensive signaling loads—ideal for stress, load, and performance testing.
- Does it support testing in multi-vendor or heterogeneous network environments?
- Yes. The emulator is designed for interoperability validation, enabling testing of CU-CP and CU-UP interactions across different vendor implementations in multi-vendor ORAN and heterogeneous 5G deployments.
- What customization options are available for test scenarios?
- Users can customize:
- Call flows using the Script Editor
- Message templates using the Message Editor
- E1AP parameters and bearer attributes through editable profiles
- Is there support for automation and remote testing?
- Yes. It supports automated test execution, remote access, unattended scheduling, and integration into continuous testing workflows—enabling 24/7 regression and functional testing.
- What hardware or software requirements are recommended?
- The system requires PCs with Intel or AMD processors and GL hardware/software for compliance. The software license is available as MAPS™ 5G-E1AP (PKS513).
- How does this emulator assist in real-world 5G CU deployments?
- It helps validate and optimize control–user plane split architectures before field deployment. By emulating real-world signaling, performing fault injection, and testing at scale, it reduces deployment risks, accelerates rollout, and ensures stable CU behavior in live networks.
- Is the E1AP emulator compliant with the latest 3GPP specifications?
- Yes. It is fully compliant with 3GPP TS 38.463 and implements standards-based E1AP messages, procedures, and formatting. Continuous updates ensure alignment with the latest 3GPP releases, enabling accurate protocol validation and interoperability testing.
Supported Protocols Standards
| Supported Protocols | Standard / Specification Used |
E1AP Interface |
TS38.463 |
SCTP |
RFC 4960 |
- SCTP for the control plane (SCTP): This transport layer protocol guarantees delivery of signaling messages between gNB CU CP and gNB CU UP (E1AP). SCTP is defined in RFC 4960
Use Cases
5G E1AP Interface Procedure
In 5G E1AP interface, MAPS™ acts as either gNB CU CP to test gNB CU UP or gNB CU UP to test gNB CU CP emulating the following call control procedure.
The below figures depict the Call Generation and Reception of 5G E1AP interface between gNB CU CP and gNB CU UP.
Resources
Note: PCs which include GL hardware/software require Intel or AMD processors for compliance.
| Item | Description |
| PKS513 | MAPS™ 5G E1AP Interface Emulator |
| Related Software | |
|---|---|
| PKS512 | MAPS™ 5G F1AP Interface Emulator |
| PKS500 | MAPS™ 5G N1N2 Interface Emulator |
| PKS501 | MAPS™ 5G N4 Interface Emulator |
| PKS502 | MAPS™ 5G N17 Interface Emulation |
| PKS503 | MAPS™ 5G N8 Interface Emulation (Requires PKS502) |
| PKS504 | MAPS™ 5G N10 Interface Emulation (Requires PKS502) |
| PKS505 | MAPS™ 5G N11 Interface Emulation (Requires PKS502) |
| PKS506 | MAPS™ 5G N12 Interface Emulation (Requires PKS502) |
| PKS507 | MAPS™ 5G N13 Interface Emulation (Requires PKS502) |
| PKS508 | MAPS™ 5G N20 Interface Emulation (Requires PKS502) |
| PKS509 | MAPS™ 5G N21 Interface Emulation (Requires PKS502) |
| PKS510 | MAPS™ 5G N22 Interface Emulation (Requires PKS502) |
| PKS511 | MAPS™ 5G N29 Interface Emulation (Requires PKS502) |
| PKS511 | MAPS™ 5G N51 Interface Emulation (Requires PKS502) |





