Particularly in automotive emergency response systems, RSP M2M communication depends on the reliable behavior of eSIM, device, mobile network, and back end server. Thanks to COMPRION’s eUICC Profile Manager, direct testing of eSIM actions is already quite simple. However, testing the eSIM’s reaction to communication failures remains complicated, and it requires considerable effort to produce the necessary network behavior. This is a critical point as the eSIM must react in a predefined way: If, for example, enabling of a profile fails because of network problems, then the eSIM must automatically roll back to the previous profile. Otherwise, the communication of an emergency system could be blocked, and the vehicle must be brought to a workshop for repair or replacement. It certainly is a good idea to check proper functioning before soldering new eSIMs into devices, especially if they’re going to be used in automotive applications! Until now, trying to produce network errors for testing has been no fun for anybody. This has changed.
First, we check if profile enabling on our new eUICC works as intended without any manipulation of the back end:
Here, everything worked as expected: Profile 2 (green rectangle) is enabled and profile 1, directly above, is disabled (now appears dimmed). In the ‘Messages’ view, we can track the operation and see that the profile has been successfully enabled (see the final entry in red rectangle). Now, let’s be mean and disrupt this idyll by manipulating the back end …
We want to reverse step 1 by re-enabling profile 1. But before we start, we manipulate the operation with an error that blocks the reception of a confirmation SMS on the back end. Therefore, we implant a manipulation script:
This script prevents the back end from successfully receiving SMS messages. Select the script and start it with just one click:
With Manipulation being activated, we begin to enable profile 1:
Sabotaging the communication went well and now we have the following result: Profile 1 is still disabled, and a rollback was performed (see error message). Rollback means that profile 2 was first disabled but, when enabling of profile 1 failed due to the manipulated communication error, profile 2 was re-enabled. Consequently, the eSIM performed perfectly well by making sure that an active profile is available even if the back end messes things up. So, this eSIM has passed an important (possibly lifesaving) test.
Producing M2M network errors for eSIM testing made easy: That’s COMPRION’s new Manipulation feature available with eUICC Profile Manager. Just activate the appropriate script for your test objective, and you can check if the eSIM under test reacts as expected, always ready for help in an emergency. And there is no need to fiddle with network settings.
You would like to see more of our How Tos? Just click here and find a solution to your issue!
Do you encounter high deviations of contactless analog results for EMVCo testing with your current setup? Does it take ages to compare the delta...
Alien eUICC profiles are “invading” your test space constantly. They are sent to you from different partners (MNOs) and consequently have very...