eNodeB Wrap-around Tester

Emulates LTE UE and EPC to test the eNB
eNodeB
EPC
UE
4G Conformance
eNodeB Wrap-around Tester

Emulates LTE UE and EPC to test the eNB

Overview

Valid8's LTE eNodeB Wrap-around Tester is a hardware-based solution that emulates LTE UE over Uu, plus optionally an additional eNodeB over X2, and the EPC to test the eNodeB.

What It Can Do For You

Cost effective solution to turn up eNBs and verify S1 conformance.

Why It’s Different

  • Software based solution can be run on M3 hardware with radio HW.
  • Web-based Graphical User Interface provides customer with intuitive, easy access via browser 
  • API’s used (REST, HTTP) enable automated testing using test tools. 
  • Emulated nodes behave exactly as true real nodes, due to Finite State Machine architecture 
  • Testing is scalable across multiple cores and multiple systems

Features

  • Emulates the UE OTA over Uu
  • Emulates the eNodeB over X2
  • Emulates some or all of core network, exposing all internal interfaces. 
  • Conformance tests available for S1 and X2.
  • True stateful simulation 
  • Handover support on X2 and S1 
  • Signaling request/response messages for call handling, mobility management, authentication, QoS 
  • Report on media received, call connect time, call duration, jitter, packet loss 
  • Generate valid and invalid/negative messages and call-scenarios (fully editable scenarios) 
  • Supports sending invalid messages including malformed, dropped, and misordered packets 
  • Check parameters in messages from SUT and flag errors 3GPP-compliant interfaces 
  • Core network 5G ready

Subsystems

KPIs
  • S1 Attach Requests/Successes/Fails 
  • S1 Detach Requests/Successes/Fails 
  • S1 Dedicated Bearer Requests/Successes/Fails 
  • Current Active Sessions/ Bearers 
  • Number of Sessions/ Bearers Created 
  • S1 Attach Request Response Time 
  • S1 Dedicated Bearer Setup Request Response Time 
  • S1 Detach Request Response Time S1 Authentication Request Response Time 
  • S6a Authentication Request Response Time 
  • S1 Tracking Area Update Request Response Time
Configurable Parameters
  • Frequency Band
  • EARFN
  • Channel Bandwidth 1.4, 3, 5, 10, 15, 20
  • Includes CBRS band
  • PLMN Mobile Country Code (MCC), Mobile Network Code (MNC)
  • eNodeB Type IP Address S1 Interface 
  • IP Address eNodeB 
  • Primary DNS Address 
  • Secondary DNS Adress 
  • MAC Address Public Gateway 
  • GTP Tunnel IP Address and Port 
  • GTP Tunnel eNodeB IP Address 
  • Integrity Algorithm 
  • IP Address to assign UEs on LAN

Automation API

User commands can be fully automated using REST API. This includes performing all test control functions as well as collecting results and metrics.

Scripting

The application’s subsystems can be edited directly in the browser using Javascript or by using the graphical tools seen below. The Message Workshop allows for creating of test scenarios directly from the hex stream of a remote capture, while the Graphical Editor allows for creating customized call scenarios by dragging and dropping the call flow to meet your test needs.

This is some text inside of a div block.

Use Cases

eNodeB Under Test

In the scenario where the eNodeB is to be tested, it can be tested by the Valid8 4G Network Emulator emulating the core network. Additionally, load and conformance tests are available for interfaces S1-MME and S1-U. In the case where the eNodeB needs to be tested on the RF side, it can be tested by the Valid8 4G UE Emulator.

Supported Scenarios:
  • ‍Power on / Start up
  • 4 Attach
  • 4 TAU
  • 4 Attach
  • 4 eRAB Setup
  • 4 Detach
  • UE Under 
  • Emulates MME (for S1-MME) and SGW (for S1-U) along with all other needed core network elements, exposing all internal interfaces
  • Conformance tests available for S1-MME, S1-U, and X2
eNodeB Wrap-around Tester
eNodeB Wrap-around Tester

Summary of Specifications

Specifications

Conformance tests:

  • S1 SETUP
  • S1 Setup between MME and eNodeB in a single PLMN configuration
  • Successful S1 Setup
  • Unsuccessful S1 Setup
  • S1 Setup between MME and eNodeB in a multiple PLMN configuration (MOCN configuration)
  • Successful S1 Setup
  • Unsuccessful S1 Setup
  • S1 Configuration Update (MME Initiated)
  • Successful S1 MME Configuration Update
  • Unsuccessful S1 MME Configuration Update
  • S1 Configuration Update (eNodeB Initiated)
  • Successful S1 Configuration Update (eNodeB Initiated)
  • Unsuccessful S1 Configuration Update (eNodeB Initiated)
  • S1 Reset Procedures
  • S1 Reset initiated by eNodeB
  • S1 Reset initiated by MME
  • S1 Recovery after nodes failure
  • S1 Recovery after eNodeB restart
  • S1 Recovery after MME restart
  • S1 Recovery after SGW restart
  • S1 Recovery from S1 failure due to physical connections lost
  • TRACE
  • Trace Procedures
  • Trace Start
  • Trace Start supporting S1 interface
  • Trace Start supporting X2 interface
  • Deactivate Trace
  • Location Reporting Procedures
  • Successful location reporting for a direct report of the UE location
  • Successful location reporting for serving cell change
  • Successful cancellation of location reporting for serving cell change
  • ATTACH/DETACH
  • Successful EPS Attach with UE unknown in MME and no Ciphering
  • Successful EPS Attach with UE unknown in MME and Ciphering
  • Successful EPS Attach procedure with UE known in MME and no Ciphering
  • Successful EPS Attach procedure with UE known in MME with Ciphering
  • Successful EPS Attach procedure with IMSI
  • Unsuccessful EPS Attach due to IMSI unknown on HSS
  • Successful EPS Detach initiated by UE
  • Successful EPS Detach initiated by UE due to switch off
  • Successful EPS Detach initiated by MME
  • ERAB PROTOCOL PROCEDURES
  • ERAB Setup
  • Successful E-RAB establishment for
  • Successful E-RAB establishment for– UE Aggregate Maximum Bit Rate IE is included
  • Successful E-RAB establishment for multiple E-RABs
  • E-RAB Modify
  • Successful E-RAB modification
  • Successful E-RAB modification for multiple E-RABs
  • Successful and Unsuccessful E-RAB modification for multiple E-RABs
  • E-RAB Release
  • E-RAB Release initiated by MME
  • E-RAB Release initiated by eNodeB
  • EPC BEARERS FUNCTIONAL PROCEDURES
  • Dedicated bearer Activation
  • Successful Dedicated Bearer Activation initiated by the network
  • Successful Dedicated Bearer Activation initiated by the UE
  • Successful Dedicated Bearer Activation during attach
  • Bearer Modification
  • Bearer Modification initiated by the EPC
  • PDN GW initiated bearer modification with QoS Update
  • HSS initiated Subscriber QoS Modification
  • Network Initiated Bearer modification without Bearer QoS Update
  • Bearer Modification initiated by the UE
  • UE Requested Bearer Modification accepted by the network
  • UE Requested Bearer Modification without QoS update accepted by the network
  • Dedicated Bearer deactivation
  • PDN GW initiated Dedicated Bearer Deactivation
  • MME initiated Dedicated Bearer Deactivation
  • UE initiated Dedicated Bearer Deactivation
  • IDLE MODE AND CONTEXT MANAGEMENT PROCEDURES
  • Active to Idle mode Transition (Context Release)
  • UE/eNodeB Context Release due to User Inactivity with a single bearer established
  • UE/eNodeB Context Release due to User Inactivity with multiple bearers established
  • UE Context Release due to radio connection with UE lost
  • Tracking Area Update procedures
  • Normal Tracking area Update
  • Normal Tracking area Update with bearer establishment requested
  • Combined Tracking and Location Area Update
  • Combined Tracking and Location Area Update with IMSI attach
  • Combined Tracking and Location Area Update with bearer establishment requested
  • Periodic Tracking area Update
  • Tracking Area Update rejected due to “No EPS Bearer context activated”
  • Tracking Area Update rejected due to “implicitly detached”
  • Paging
  • Paging with Paging DRX IE
  • Paging without Paging DRX IE
  • Idle to Active Mode (Service Request)
  • Successful Service Request invoked when the UE receives a paging request with CN domain indicator set to “PS” from the network in ECM-Idle mode (Single bearer)
  • Successful Service Request invoked when the UE receives a paging request with CN domain indicator set to “PS” from the network in ECM-Idle mode (Multiple bearers)
  • Successful Service Request invoked when the UE has pending user data to be sent in ECM-Idle mode (Single Bearer)
  • Successful Service Request invoked when the UE has pending user data to be sent in ECM-Idle mode (Multiple Bearers)
  • Successful Service Request invoked when the UE has uplink signaling pending in ECM-Idle mode
  • Successful Service Request invoked by 1xCS fallback when the UE is in Idle mode and has a mobile originating 1xCS fallback request
  • Successful Service Request invoked by 1xCS fallback when the UE is in Active mode and has a mobile originating 1xCS fallback request
  • Successful Initial UE message with Emergency Flag enabled
  • USER PLANE PROTOCOL AND DATA TRANSFER TEST CASES
  • User Plane Control Test Cases
  • GTP-U echo mechanism
  • GTP-U message “End of Marker”
  • Graceful Error Indication handling by eNodeB
  • Graceful Error Indication handling by S-GW
  • Data Transfer on Default Bearer
  • Data Transfer on Dedicated Bearer Test Cases
  • Successful Data Transfer with non-GBR Service and AM Mode
  • Successful Data Transfer with non-GBR Service and UM Mode
  • Successful Data Transfer with GBR Service and AM Mode
  • Successful Data Transfer with GBR Service and UM Mode
  • MOBILITY TEST CASES
  • Intra-System Handover
  • X2 Based Handover
  • Successful HO with single E-RAB via X2 interface
  • Successful HO with single E-RAB via X2 interface with Ciphering
  • Successful HO with multiple E-RABs via X2 interface
  • Partially Successful HO with multiple E-RABs via X2 interface
  • Unsuccessful HO via X2 interface due to EPC Failure
  • S1 Based Handover
  • Successful S1 HO with single E-RAB
  • Successful S1 HO with multiple E-RABs
  • Partially Successful S1 HO with multiple E-RABs
  • Unsuccessful S1 based HO due to fail on MME-target eNodeB connectivity
  • Unsuccessful S1 based HO due to not common ciphering algorithm
  • Unsuccessful S1 based HO due to no resources available at target eNodeB
  • Inter-System Handover
  • LTE to UTRAN Inter RAT Handover
  • Successful LTE to UTRAN HO for a single E-RAB
  • Successful LTE to UTRAN HO for multiple E-RABs
  • LTE to UTRAN HO failure due to connectivity issues
  • LTE to UTRAN HO failure due to not resources at NodeB
  • LTE to UTRAN CS-Fallback: Inter RAT Handover triggered by Mobile Originated Call, UE in Idle Mode
  • LTE to UTRAN CS-Fallback: Inter RAT HO triggered by mobile Terminated Call, UE in Idle mode
  • LTE to UTRAN CS-Fallback: Inter RAT HO triggered by mobile Originated Call, UE in Active Mode
  • LTE to UTRAN CS-Fallback: Inter RAT HO triggered by mobile Terminated Call, UE in Active Mode
  • LTE to UTRAN SRVCC: Inter RAT Handover for VoIP Call
  • LTE to UTRAN SRVCC: Inter RAT Handover for Data Transfer and VoIP Call
  • UTRAN to LTE Inter RAT Handover
  • Successful UTRAN to LTE Inter RAT Handover for a single RAB
  • Successful UTRAN to LTE Inter RAT Handover for multiple RABs
  • UTRAN to LTE Inter RAT Handover failure due to no resources at the eNodeB

Product Details

Emulates LTE eNodeB and EPC to test the UE

All Solutions

Valid8 exports its products strictly in accordance with all US Export Control laws and regulations which shall apply to any purchase or order. Specifications are subject to change without notice.

500 West Cummings Park, Suite 6550 Woburn, MA 01801
p: +1-855-482-5438
f: +1-781-996-3708
welcome@valid8.com
VALID8.COM

Ordering Information

Product Name: LTE Core Network Emulator

Product Code: lte-core-network-emulator

Datasheet Page

Related Video

Related Solutions

5G Network Emulator
  • Product Name: 5G Network Emulator 
  • Product Code: 5g-network-emulator
Datasheet Page
4G UE Emulator
  • Product Name: 4G UE Emulator 
  • Product Code: 4g-ue-emulator
Datasheet Page
MCPTT Load Tester

Product Name: MCPTT Load Tester 

Product Code: mcptt-load-tester

Datasheet Page
LTE EPC Emulator

Product Name: LTE Core Network Emulator 

Product Code: lte-core-network-emulator

Datasheet Page
Conformance
  • Product Name: SIP Conformance
  • Product Code: sip-conformance-base-suite
Datasheet Page