Wireless 5G Core Network

IP Network Simulation

MAPS™ 5G-ORAN F1AP Interface Emulator

Emulates the F1 interface between gNB-CU and gNB-DU, managing UE contexts, transferring RRC messages, supporting bearer setup and management and all associated signaling procedures as defined in 3GPP standards.

  Request a Demo / Quote
MAPS™ 5G-ORAN F1AP Architecture

Overview

GL’s MAPS™ (Message Automation & Protocol Simulation) 5G-ORAN F1AP Interface Emulator is a powerful testing solution for validating the F1 interface between gNB Central Unit (CU) and gNB Distributed Unit (DU) as defined by 3GPP TS 38.473. It emulates both CU and DU network elements, enabling users to test real-world signaling scenarios across the F1-C (Control Plane) and F1-U (User Plane) with ease. Fully compliant with 3GPP standards, it supports key procedures such as UE context setup, bearer management, and RRC message forwarding, —ensuring reliable and standards-compliant midhaul operations.

With its flexible architecture, MAPS™ F1AP allows performance testing, fault insertion, and interoperability verification under varied network conditions without the need for live RAN equipment. Traffic emulation modules allow operators and vendors to troubleshoot, optimize, and validate 5G Open RAN (ORAN) deployments—accelerating time to market and reducing risk.

The product supports Mobile Traffic Core – GTP (ETH101) and Mobile Traffic Core – Gateway (ETH102) for user-plane traffic emulation between CU and DU.


Key Features

  • F1 Interface Emulation: Emulates both gNB-CU and gNB-DU nodes—either side can act as DUT for complete interface testing
  • Control- and User-Plane Support: Supports F1-C signaling procedures (UE Context Management, bearer setup, RRC forwarding) and F1-U traffic using GTP-U
  • Fault Insertion & Impairments: Simulates faulty network conditions by inserting impairments and malformed F1AP messages
  • Customizable Scenarios: Modify call flows and message templates easily using the built-in Script, Message, and Profile Editors
  • Ready-to-Use Scripts: Start testing immediately with pre-built, ready-to-use F1AP test scripts
  • Automated Call Handling: Supports scripted call generation and automated reception for repeatable and consistent test cycles
  • 24/7 Automation & Remote Access: Run unattended tests using automation tools, remote access, and scheduled execution


Applications

  • Validate F1AP Protocol Compliance: Perform comprehensive standards-based testing for F1 procedures
  • Simulate Large-Scale Networks: Emulate multiple CUs, DUs, and UEs using easy-to-configure subscriber profiles
  • Fault and Recovery Testing: Insert impairments to validate error handling, robustness, and recovery mechanisms
  • Interoperability Testing: Ensure seamless integration of multi-vendor ORAN components in 5G midhaul networks
  • Automate Call Workflows: Enable automated generation and reception of calls for efficient, repeatable test cycles
  • Support R&D and Training: Use in lab environments for protocol development, network optimization, and training
  • Support Continuous Testing: Use built-in automation and remote tools to execute tests 24/7


Frequently Asked Questions

What is the primary purpose of the 5G F1AP Interface Emulator?
It emulates the F1 reference point between gNB-CU and gNB-DU, enabling validation of 5G midhaul signaling. It supports UE context management, RRC message transfer, bearer setup, and other F1 procedures as defined in 3GPP TS 38.473, ensuring reliable CU–DU interaction.
Which F1-C and F1-U procedures and protocols are supported by the emulator?
It supports key F1-C procedures such as UE Context Setup/Release, bearer management, RRC message forwarding, and F1 interface initialization. On the user plane, it supports GTP-U tunneling using GL’s Mobile Traffic Core – GTP (ETH101) and Gateway (ETH102) modules for realistic F1-U traffic emulation.
Can the emulator simulate both gNB-CU and gNB-DU roles?
Yes, it can emulate both CU and DU nodes, allowing either side to act as the DUT. This enables full end-to-end testing of F1 signaling and traffic flows in flexible midhaul configurations.
Does it support performance testing, load testing, and fault insertion for midhaul networks?
Yes, the emulator supports performance testing, load generation, impairments, and fault insertion. It can introduce malformed messages, delays, and error conditions to evaluate robustness and midhaul performance under stress.
What customization options are available for call flows, messages, and profiles?
Users can customize:

  • Call flows through the Script Editor
  • Message templates using the Message Editor
  • Subscriber, UE, CU/DU profiles via the Profile Editor
These tools allow flexible modification of scenarios, parameters, and signaling flows.
Is there support for automation, remote testing, and scheduled execution?
Yes. MAPS™ F1AP supports scripted automation, remote access, automated call handling, and 24/7 scheduled execution for continuous, unattended testing.
What are the hardware and software requirements to deploy the emulator?
The system requires PCs with Intel or AMD processors and GL hardware/software for compliance. The software license is available as MAPS™ 5G-F1AP (PKS512).
How does this emulator ensure multi-vendor ORAN interoperability?
The emulator ensures interoperability by providing standards-compliant F1 procedures, realistic CU–DU behavior, and configurable profiles that allow testing with different vendor implementations—enabling validation of multi-vendor ORAN midhaul deployments.
How does the 5G F1AP emulator ensure compliance with 3GPP TS 38.473 standards?
Compliance is ensured through:

  • Full implementation of 3GPP TS 38.473-defined F1AP procedures
  • Accurate encoding/decoding of F1AP messages
  • Support for both control-plane and user-plane operations as per 3GPP specifications
This guarantees reliable, standards-aligned CU–DU interface testing.

Supported Protocols Standards

Control Plane for F1AP Interface

Control Plane for F1AP Interface

Supported Protocols Standard / Specification Used

F1AP Interface

TS38.473

SCTP

RFC 4960

Non-Access-Stratum (NAS)

3GPP TS 24.501

NR and NG-RAN

3GPP TS 38.300 V17


  • SCTP for the control plane (SCTP): This transport layer protocol guarantees delivery of signaling messages between gNB CU and gNB DU (E1AP). SCTP is defined in RFC 4960

Use Cases

MAPS™ F1AP configured as gNB DU to test gNB CU (DUT)

MAPS™ F1AP configured as gNB DU to test gNB CU (DUT)

MAPS™ F1AP configured as gNB CU to test gNB DU (DUT)

MAPS™ F1AP configured as gNB CU to test gNB DU (DUT)


5G F1AP Interface Procedure

In 5G F1AP interface, MAPS™ acts as either gNB CU to test gNB DU or gNB DU to test gNB CU emulating the following call control procedure.

5G F1AP call control procedure


The below figures depict the Call Generation and Reception of 5G E1AP interface between gNB CU and gNB DU.

5G F1AP interface Call Generation at gNB DU Node

5G F1AP interface Call Generation at gNB DU Node

5G F1AP interface Call Reception at gNB CU Node

5G F1AP interface Call Reception at gNB CU Node

Resources

Note: PCs which include GL hardware/software require Intel or AMD processors for compliance.

Item Description
PKS512 MAPS™ 5G F1AP Interface Emulator
  Related Software
PKS513 MAPS™ 5G E1AP 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)