vSIM Administration

The table below describes the fields used in the of the vSIM Administration window.

Landslide TAS & Test Cases act as Client and communicate with Implementa SimArrayllx through the proprietary interface(Extended SIMCP over TCP/IP) defined by Implementa. https://www.implementa.com/products/sim-array.
The TAS retrieves the information(such as IMSI) of SIM Cards inserted in Implementa SimArrayllx and manages the resources for each test-run. The Test Case such as AMF Nodal or MME Nodal communicates with Implementa SimArrayllx during the test-run to get the 3gpp authentication result from SIM card in Implementa SimArrayllx.

Add SIM Array via Admin -> vSIM Administration

The Basic SIM Server system consists of three main components: SIM Array(s) and SIM Client(s) and SIM Emulators. SIM Array is a hardware unit that holds up to 13 hot-pluggable SIM Boards. Each SIM Board has a capacity of 32 SIM cards. Virtually any number of SIM Arrays can be combined to build huge “SIM farms”.

SIM Client is a software component that acts as a gateway between SIM Emulators and SIM Arrays. Each mobile device is equipped with a SIM Emulator inserted into its SIM Holder thereby replacing the physical SIM card. Different versions of SIM Emulators are available. Each mobile device connected to the system by means of a SIM Adapter is represented by a Channel entity in the application software and APIs.

SIM Arrays are typically placed in one or more central locations, while SIM Clients and Emulators are located remotely along with distributed mobile devices (e.g. GSM/UMTS terminals).

SIMC Client Tab becomes available for input when Use SIM Server is enabled in the supported test cases.

Add vSIM

NOTEs:

Select Add on the left side of screen to add a vSIM. Select Delete to delete a vSIM.
A single TAS can support up to 64 SIM servers connected to it thus the maximum SIM Cards supported is 64x412 = 26,368.
Retrieval of slot data queries to the SIM Server will be limited to once per 30 second window (if successful). We do not expect updates on the SIM Server that often and will keep the number of connections and request to a minimum. To protect the TAS from issues related to out of reach or mis-configured SIM Servers, if additional requests to the same SIM Array are within that 30 second window, all subsequent requests will return the latest cached slot information. If there are two consecutive failures, then the delay window will double to 60 seconds and continue to double after each consecutive failure until the delay window reaches a maximum of 15 minutes (6 or more consecutive failures). Once a successful query occurs the delay window will be reset to 30 seconds.

Here is example of the Real-Time logs you will see upon failures. Clearly identifying the next time a full query will be attempted:

Field	Description
Add vSIM	Click the Add button to a new vSIM Array. SIM Array is a hardware unit that holds up to 13 hot-pluggable SIM Boards. Each SIM Board has a capacity of 32 SIM cards. Virtually any number of SIM Arrays can be combined to build huge “SIM farms”. Enter SIM Array Name, IP Address and Port of SIM.
IP Address	This is the IP address of the SIM Array.
Port	This is the port of the SIM Array.
Slot Data	The Slot, IMSI, MCC, MNC, iccid and rid.
Slot	SIM Slot number.
IMSI	The International Mobile Subscriber Number (IMSI) of the SIM.
MCC	The Mobile Country Code (MCC) of the SIM.
MNC	The Mobile Network Code (MCC) of the SIM.
iccid	Each SIM is internationally identified by its integrated circuit card identifier (iccid).
rid	Test RUN ID. If it is being used by an active running test, it will be non-zero. The ID of the active test.
Has SUPI	Identifies whether a SIM card can be used for 5G core network testing. A new attribute “hasSupi” added to REST API response for “./api/simArrays/[#]. The new boolean attribute Has SUPI is only retrievable with new version of SIM Server via command reportsims. Older versions of SIM Server will continue to retrieve slot data via command listsims (in this scenario – Has SUPI will be false) - Using the RESTFul API contains reference information about the Landslide RESTFul API system. Refer to Swagger UI on Landslide Home Page, it contains the latest most accurate information for anything it covers.