MAPS™ 5G N51 interface can emulate Access and Mobility Management Function (AMF) and Network Exposure Function (NEF) via the service-based N51 interface. MAPS™ N51 Interface Emulator supports Namf_EventExposure service procedure.
GL has enhanced its MAPS™ protocol emulation tool to emulate multi-protocol and multi-interface offering a complete range of test solutions, covering the entire 5G, 4G, 3G, and 2G networks.
By mimicking real-world customer behavior in lab environments, our solutions allow mobile operators and equipment manufacturers to verify their 5G networks before deployment.
GL also provides a GUI based Multi-Protocol Analyzer for online capture and decode of the signaling in real-time both during tests and as a stand-alone tracer for live systems.
- Emulate AMF and NEF elements
- Supports Namf_EventExposure Service (Registration State Change Event, Connection State Change Event, Location Report Event, Presence In Area of Interest Event)
- Services use REST APIs based on HTTP and JSON data format
- Supports TLS and TCP transports
- Supports scripted call generation and automated call reception
- Supports customization of call flow and message templates using Script Editor
- Ready-to-use scripts for quick testing
- Provides Call Statistics and Events Status
- Automation, Remote access, and Schedulers to run tests 24/7
Supported Protocols Standards
N51 Interface (NEF - AMF)
IETF RFC 8259
IETF RFC 7540
IETF RFC 793
IETF RFC 791 
5G N51 Interface Procedures
In 5G N51 interface, MAPS™ acts as either NEF to test AMF or AMF to test NEF emulating the Namf_EventExposure Service Operations.
UE Subscription Notification of One Time Event Detection
Supports the following event functions
- Registration State Change Event
- Connection State Change Event
- Location Report Event
- Presence In Area of Interest Event
The below screenshots depict the Call Generation and Reception of 5G N51 interface between NEF and AMF.
Please Note: The XX in the Item No. refers to the hardware platform, listed at the bottom of the Buyer's Guide, which the software will be running on. Therefore, XX can either be ETA or EEA (Octal/Quad Boards), PTA or PEA (tProbe Units), UTA or UEA (USB Units), HUT or HUE (Universal Cards), and HDT or HDE (HD cards) depending upon the hardware.
|PKS511||MAPS™ 5G N51 Interface Emulator (Requires PKS502)|
|PKS305||MAPS™ 5G Multi-Interface Emulation|
|PKS500||MAPS™ 5G N1/N2 Interface Emulator|
|PKS501||MAPS™ 5G N4 Interface Emulator|
|PKS502||5G Service-based Emulation (Prerequisite base license for all service-based (Open API) interface emulations)|
|PKS502||MAPS™ 5G N17 Interface Emulator|
|PKS503||MAPS™ 5G N8 Interface Emulator (Requires PKS502)|
|PKS504||MAPS™ 5G N10 Interface Emulator (Requires PKS502)|
|PKS505||MAPS™ 5G N11 Interface Emulator (Requires PKS502)|
|PKS506||MAPS™ 5G N12 Interface Emulator (Requires PKS502)|
|PKS507||MAPS™ 5G N13 Interface Emulator (Requires PKS502)|
|PKS502||MAPS™ 5G N20 Interface Emulator (Requires PKS502)|
|PKS502||MAPS™ 5G N21 Interface Emulator (Requires PKS502)|
|PKS502||MAPS™ 5G N22 Interface Emulator (Requires PKS502)|
|PKS511||MAPS™ 5G N29 Interface Emulator (Requires PKS502)|