Esim Card Reader
Karleen Chura
lpac supports pcsc-lite to access smart card readers, so it should work right away when you use the smart card (not the SIM!) slot of a Librem5. For making it work in the SIM slot, the modem would have to support something like AT+CSIM (APDU tunneling over AT commands) and that would have to be glued as transport into lpac.
Note that using lpac or any other 3rd party LPA with esim me is a violation of their terms of service, so be careful about this specific product. However, there are other suppliers of eUICC In plastic card form-factor.
After further searching on the Internet, I came across the desktop software Truphone/LPAdesktop, whose manual mentions that it can configure these eSIM cards through a PC/SC smart card reader. And the current smart card readers on the market generally only cost around 30-50 yuan, which is much more affordable than buying an LTE module.
If you have a relatively new, rooted Android device around, you can also try using PeterCxy/OpenEUICC software to configure it directly on your phone. Someone has already made a magisk module for it: -org/magisk-module-openeuicc
National security has a requirement to read IMSI numbers from mobile phones and other small electronic devices used by members of staff. Current practice usually involves removing the physical SIM card from the device and placing it into a reader that interrogates the card and displays its IMSI number.
Commercial software solutions are available that read eSIMs, but they also collect collateral data such as contact lists and SMS messages in addition to IMSI numbers. This is unacceptable in this situation as it contravenes data handling regulations. There is currently, therefore, no acceptable means to read and record IMSI numbers from the emerging generation of eSIM enabled mobile phones and devices.
There are six desirable functions for solutions put forward. They must be able to read and display IMSI numbers from a wide range of unlocked mobile phones that use eSIMs; and where more than one eSIM is active within a given mobile device, the solutions must be capable of reading and displaying the IMSI number for each SIM.
Outcomes must not pose a risk of damaging or corrupting the device being read or its associated eSIM; and the solutions should be intuitive to use so that non-technical people can read and record IMSI numbers effectively, with little or no training.
There is interest in developing innovative technology to approximately TRL 5 or 6, but we are not looking for horizon scanning, technology mapping or low TRL developments. We are not prescriptive on the format of the concept demonstrator, but it must comply with data protection and GDPR, and data aggregation must be considered and handled securely.
This challenge is open to sole innovators as well as industry, academic and research organisations of all types and sizes. There is no requirement for security clearances. Solution providers or collaborators from countries listed by the UK Government under trade sanctions and/or arms embargoes, are not eligible to take part.
Clarifying questions or general requests for assistance can be submitted directly to cocre...@hmgcc.gov.uk prior to the cut-off date. These clarifying questions may be technical, procedural, or commercial in subject, or anything else where assistance is required. Please note that answered questions will be published to allow a fair and open competition.
HMGCC Co-Creation is a partnership between HMGCC and DSTL (Defence Science and Technology Laboratory), created to deliver a new, bold and innovative way of working with the wider UK science and technology community. It brings together the best in class across industry, academia, and Government, to work collaboratively on national security engineering challenges and accelerate innovation.
Devices with embedded UICCs can be provisioned or configured over a cellular network connection using a network simulator or an IP connection. Not soldered (e)UICCs can be easily accessed with a card reader.
For M2M eUICCs that are already soldered into a device, a connection via a simulated (or real) cellular network needs to be established. Network simulators of different manufacturers can also be applied. This setup fits for Remote File and Application Management.
For consumer devices eUICCs that are already soldered into a device, an IP connection via a Wifi network or via a simulated (or real) mobile network needs to be established. A Wifi router or network simulator can be applied.
Remote SIM Provisioning in M2M environment
eUICC Profile Manager's Loader M2M component supports of Remote SIM Provisioning functionality according to GSMA SGP.02 v3.2 and v4.2.
Easily download, enable, disable and delete profile defined according to Trusted Connectivity Alliance eUICC Profile Package: Interoperable Format Technical Specification, Version 2.x and 3.x.
eUICC Profile Manager supports the Remote SIM Provisioning functionality according to GSMA SGP.22 v2 and SGP.22 v3 (via a PC/SC card reader). The configuration of the SM-DP+ simulation allows the operation of different test eUICCs and prepares a profile defined according to Trusted Connectivity Alliance eUICC Profile Package: Interoperable Format Technical Specification, version 2.x and 3.x defined profile for download.
eUICC Profile Manager supports the Remote SIM Provisioning functionality according to GSMA SGP.32 v1.0. The configuration of the SM-DP+ simulation and eIM (eSIM IoT Remote Manager) allows the operation of different test eUICCs and prepares a profile defined according to Trusted Connectivity Alliance eUICC Profile Package: Interoperable Format Technical Specification, version 2.x and 3.x profile for download.
Scan templates allow you to detect all files located below the available applications (e.g. UICC, USIM, CSIM, ISIM and PKCS#15). The resulting file system view allows you to easily navigate between files and to update their contents remotely. Deleting existing files and creating new ones is also possible.
The compare function allows you to compare different scanned file systems and file systems defined in the interoperable Trusted Connectivity Alliance (TCA) profile package format or SIM Profile Markup Language (UXP). A report summarises the results.
The Explorer component allows over-the-air application management operations.Remote scanning for loaded/installed packages/applications with predefined GolbalPlatform defined
commands is an easy task as well as the loading of packages and installation of applications.
Want to create your own command sequence? The Command Sequencer is the right tool. It complements the remote access options and gives you complete freedom to define the commands to be sent to a target application on the (e)UICC.
Predefined templates consisting of Command APDUs (ETSI TS 102 221, ETSI TS 102 222, Global Platform Card Specification), Immediate Action TLVs, Error Action TLVs and Script Chaining TLVs support the definition of the command sequences.
If you want to test how the eUICC/UICC reacts to communication errors or unusual system behaviour, you can manipulate the default behaviour of the Remote SIM Provisioning or Remote Management procedures.
To test the behaviour of the eUICC or UICC, it is most useful to perform manipulations on the different layers of the ES5 interface (communication of SM-SR with the eUICC) or the ES6 interface (communication of Operator with eUICC/UICC).
If the Over-The-Air (OTA) communication of your SIMs is malfunctioning and is already in service, it is almost impossible to make changes.
Let me show you how you can verify in advance that OTA works on your standard UICCs.
Installing eSIM profiles is not possible with Retool Mobile. Retool Mobile is designed and intended for internal apps, not public distributed apps (although possible), so it would be very helpful if you can add a tad more context to what you're trying to achieve so that we can guide you in the right direction :-).
Just to clarify, Retool is a low-code tool, not a no-code tool, so if you have no prior coding experience, I'd recommend you getting familiar with basic Javascript to give yourself a better understanding of what's going on in your deployments :-).
Working with special sensitive hardware-interacting handlers such as Apple Wallet for payment cards, eSIMs etc generally requires a deep implementation, and Retool Mobile and similar tools will very rarely result in an acceptable solution for your end-users, the platform (i.e. Apple's App Store), or your business.
About what I want to achieve.
I have an idea to make an application "Esim Wallet". User can save all his eSIMs by scanning the QR-code, add the comment and additional data.
At the same time, Apple allows to install eSIM by click on the button with class from first message.
User can install eSIM native, or he can share esim by generated QR code
This my idea)
For iOS I'd also recommend you to check up if this is how Apple eSIMs work. I'm saying this, because as far as I'm aware the eSIMs are only able to be activated once, and if you remove an eSIM to activate another, you can't simply re-scan your QR code (or deploy the same eSIM ICCID). I'm saying this because my own carrier sent me two different QR codes in case the first one failed during deployment, as they could only be used once.
Or any other way to access the SIM's mobile data from the laptop, which does not support the insertion of a SIM to the laptop itself (without using the phone's hotspot, because that will drain phone's battery faster). Laptop doesn't support eSIM either.
The frequencies used by mobile networks are very different from those used by Wifi or Bluetooth, and the encoding of data and power levels used are also very different. None of the "normal" radios present in a PC can communicate with cellphone towers as they lack the radios and protocols necessary.
You can get LTE adapters (or laptops that already contain LTE modules) that contain all the radio electronics necessary to talk to a cellphone tower, but normally these also contain a SIM card slot so your SIM Card Reader is completely redundant and useless in this case.
c80f0f1006