Overview
eSIM Tracer introduces a novel method for visualizing communication between a cellular module and a soldered eSIM or integrated SIM (iSIM) when direct physical access to the UICC is no longer possible. By interfacing with a common interface to device- or module-specific data sources, it enables real-time monitoring of Application Protocol Data Unit (APDU) traffic. At present, eSIM Tracer is designed to work with devices using Qualcomm chipsets, however, support for other chipsets is expected in the future.
eSIM Tracer records, decodes, translates, and analyzes APDU commands, displaying the communication in an ordered APDU list view with details such as time, command type, state, command, and response. Additional context, descriptions, and translations are available for selected commands. The recorded data can be stored in a dedicated format and reloaded for further analysis.
Who benefits from eSIM Tracer?
Would you like to discuss live tracing of eSIM communication in light of your specific context or would you like to see the tool in action? Let's get in touch!
Data recording
eSIM Tracer allows live monitoring of communication between a cellular module and a soldered eSIM or iSIM, even without direct physical access to the SIM interface. Logging data is displayed in a clear UI and the visualization includes information on timing, translated command name, status information, as well as command and response data.
Monitoring of ISO application layer
Displays real-time monitoring of ISO Application Layer communications (ISO/IEC 7816 protocols; T=0). The configurable spreadsheet allows users to select which columns to display, offering detailed views of APDU commands. A translation of commands and elementary files (EFs) is offered for selected entries, e.g. for READ/UPDATE commands.
eSIM Tracer setup
Data and data format are different between different chipset/module/mobile equipment manufactures. The service providing the device/module vendor-specific data (eSIM Tracer adapter) utilizes a Rest API (OpenAPI 3.0) defined by COMPRION, which can be implemented by either the vendor or COMPRION.
If you cannot find what you are looking for, leave us a note and we will get back to you as soon as possible.