next generation Telecommunication Technology Testing Tools
NG40 for Cloud Service Testing

Virtual SIM Platform Test Environment

Cloud Service Testing
Background: From Single SIM to Virtual SIM

In traditional mobile networks the user identity was strictly linked to the SIM card. The possession of a SIM card was precondition for mobile connectivity and - from mobile operator perspective - for correct charging. The relationship was simple:

1x SIM card = 1x mobile user = 1x IMSI = 1x MSISDN number

With the launch of DUAL SIM card phones in 2000 it was possible to use two independent services without the need to carry two phones.

The deployment of 3G communication protocols like HSDPA and HSUPA fosters the shift from voice to data services. Mobile users require mobile connectivity not just for smartphones but also for laptops and tablets. Mobile Operators started to respond with Multi SIM services. Operators like T-Mobile bundle three SIM cards into one contract.

Virtual SIM goes further this path. Virtual SIM is also a paradigm change, because it abolishes the strict relationship between SIM card and user identity. With Virtual SIM it is now possible to assign several mobile numbers to one and the same physical device. Virtual SIM functionality enables solution providers to develop sophisticated communication applications.

Virtual SIM Platform

-

How to test?

After sending a Supplementary Service Request: The mobile user gets a new MSISDN number within seconds, delivered directly from the operator to the phone. This sounds simple and convenient. Nevertheless, the protocol machine in the network supporting these scenarios is complex. It has to withstand heavy load conditions and attacks from fraudulent subscribers.

The Virtual SIM server has to interact with several network nodes: MSC, HLR, VLR, Short Message Center, Pre-Paid Subscriber as well as Called Party. Consequently, it has to support the relevant protocols. To name the most important: ISUP, MAP, Supplementary Service and Short Message Service.

The protocol state machine defines all permitted protocol messages, its elements and parameters. The state machine has somethimes also to support country-specific and/or vendor specific variants.

There is no guarantee that all subscribers follow the rules. Some subscribers may - intended or unintended - send other messages. Is the state machine prepared for that? Functional Test with Error Injection facilitates the design process of complex state machines. Memory leaks are a nightmare for every solution provider. Load and Capacity Tests offer an efficient protection against such and other design flaws.

NG40 Key Features
  • Functional, Load and Capacity Tests
  • Mobile Node Emulation (MSC, EPC, HLR, SMS Center)
  • Support of external mobile phones via A-Interface and NANO BTS
  • Customized SIM cards
  • Internal simulation of mobile subscriber behavior
  • Wide range of 2G / 3G / 4G protocols
  • Protocol customization (support of national and vendor-specific variants)
  • Error Injection
  • Graphical User Interface for test case execution
  • Statistics and counters
  • PCAP generation ( Wireshark support )
  • Off-the-shelve-hardware (Quad Core Engine)

ng4T offers these and other advanced solutions for cloud service testing.

Don't hesitate to contact us if you have any specific request!

ng4T - Telecommunication Technology Testing Tools

2009-2013 ng4T GmbH - All rights reserved    |     www.ng4t.com                     Impressum  (German)                     Legal Notice  (English)