SIM applet
Budget: ₹1,000,000 – ₹2,500,000 INR
We are building a BYOD SIM product which can fire up a popup or URL of choice when the SIM is entered into the mobile device. We have inbound demand from Telcos for this product.
1. Java applet
a. InMobi to provide text & basic layout
b. InMobi to provide logo & location
c. A single button that says ‘continue’
d. InMobi to provide the web url to be invoked
2. Invoke this only if a certain App is not found on the phone
a. That is, if our App is already installed then don’t show this
3. Test on SIM versions
a. 2.1.1
b. 2.2.1
c. 3.0.1
d. 3.0.4
e. Check with vendor which other versions are popular
4. Exploratory
a. Test Telco command to invoke this without SIM insertion or phone restart. Understand limitation if this is not possible.
b. If SIM already has some other invocations on it, then understand how these are sequenced, and related constraints
5. Vendor to provide
a. Time & cost of PoC – i.e. one round of all above
b. Time & cost of each subsequent iteration
c. Note: We don’t expect to test on Telco’s SIM. We should be able to send them our verified applet, and they should be able to test it themselves.
Technical feasibility to be confirmed by Agency
1. SIM triggering a Web page-based portal or a system popup (see attached options in Exhibit 1 we have discussed with some Telcos)
2. Is SIM able to receive additional signals from Telcos for re-nudging users in a few days to remind them to complete the setup/downloads etc if they have not done so first time?
3. FOTA support on SIM
4. Share details on what a typical Gemalto like Sim STK toolkit capabilities do for our scenarios.
5. SIM can be programmed in such a manner that whenever the data plan is active Telco can send a signal (SMS/Http) which will trigger the same experience
Some indicative Telco SIM specs
• JavaCard version: 3.0.1 should be the minimum for this to work. Cards with 3.0.4 are also slowly becoming available so better, but for actual rollout check the necessary features, algorithms and maybe try to aim for 2.2.2-compatible code. Keep in mind that API compatibility does not relate to algorithm availability!
• GlobalPlatform version: 2.1.1 and 2.2.1 are common. This relates to loading your application to the card (for which 2.1.1 is sufficient) but 2.2 adds SCP03 support, which uses AES instead of 3DES. In addition to version and SCP algorithm, make sure that the card supports necessary features like RMAC or security domains or delegated management.
• EEPROM size: 64K, 72K, 128K, 144K and bigger sizes are Good. This is a small code 100 lines or less so 64k-72K will be enough but Bigger is better
• SIM cards: many if not all SIM (UICC) cards are JavaCard. Mapping guidelines exist, but SIM related functionality is usually independent of the programmable JavaCard part. USAT and similar packages must be available on the SIM.
• Majorly its Gemalto 64k SIM with Javacard version 3.0.1 or above. Gemalto also provides a rich Sim STK (toolkit) that carriers use to build VAS services on the SIM.
1. Java applet
a. InMobi to provide text & basic layout
b. InMobi to provide logo & location
c. A single button that says ‘continue’
d. InMobi to provide the web url to be invoked
2. Invoke this only if a certain App is not found on the phone
a. That is, if our App is already installed then don’t show this
3. Test on SIM versions
a. 2.1.1
b. 2.2.1
c. 3.0.1
d. 3.0.4
e. Check with vendor which other versions are popular
4. Exploratory
a. Test Telco command to invoke this without SIM insertion or phone restart. Understand limitation if this is not possible.
b. If SIM already has some other invocations on it, then understand how these are sequenced, and related constraints
5. Vendor to provide
a. Time & cost of PoC – i.e. one round of all above
b. Time & cost of each subsequent iteration
c. Note: We don’t expect to test on Telco’s SIM. We should be able to send them our verified applet, and they should be able to test it themselves.
Technical feasibility to be confirmed by Agency
1. SIM triggering a Web page-based portal or a system popup (see attached options in Exhibit 1 we have discussed with some Telcos)
2. Is SIM able to receive additional signals from Telcos for re-nudging users in a few days to remind them to complete the setup/downloads etc if they have not done so first time?
3. FOTA support on SIM
4. Share details on what a typical Gemalto like Sim STK toolkit capabilities do for our scenarios.
5. SIM can be programmed in such a manner that whenever the data plan is active Telco can send a signal (SMS/Http) which will trigger the same experience
Some indicative Telco SIM specs
• JavaCard version: 3.0.1 should be the minimum for this to work. Cards with 3.0.4 are also slowly becoming available so better, but for actual rollout check the necessary features, algorithms and maybe try to aim for 2.2.2-compatible code. Keep in mind that API compatibility does not relate to algorithm availability!
• GlobalPlatform version: 2.1.1 and 2.2.1 are common. This relates to loading your application to the card (for which 2.1.1 is sufficient) but 2.2 adds SCP03 support, which uses AES instead of 3DES. In addition to version and SCP algorithm, make sure that the card supports necessary features like RMAC or security domains or delegated management.
• EEPROM size: 64K, 72K, 128K, 144K and bigger sizes are Good. This is a small code 100 lines or less so 64k-72K will be enough but Bigger is better
• SIM cards: many if not all SIM (UICC) cards are JavaCard. Mapping guidelines exist, but SIM related functionality is usually independent of the programmable JavaCard part. USAT and similar packages must be available on the SIM.
• Majorly its Gemalto 64k SIM with Javacard version 3.0.1 or above. Gemalto also provides a rich Sim STK (toolkit) that carriers use to build VAS services on the SIM.
Related categories:
Business, Accounting, Human Resources & Legal