03-27-2012 12:41 PM
1/ Is it possible to access a secure element (from an external reader) as if it was a Mifare card? Actually, Is it possible that the secure element behaves like a Mifare card and not a Java Card?
2/ Supposing that I have done everything right with RIM or a carrier and that I have an cardlet located in a secure element (whatever UICC or eSe ), is it possible to access the cardlet (from an external reader) even if the phone (Bold 9900) is powerred off?
03-28-2012 03:57 AM
Mifare is a brand rather than a specific card so it's worth being as specific as you can. Mifare Ultralight is quite different to Mifare Classic for example.
Technically, you *may* be able to emulate a Mifare classic in either the embedded SE or the UICC SE. You'd need approval from RIM in the first instance or the carrier in the second.
Yes, it's technically possible that the secure element will still function when the device is powered off.
03-28-2012 05:15 AM
Thanks M Woolley
And Sorry to have been approximative about the Mifare cards but I thought about the classic 4K one
I have a BB9900, an external card reader (ACR122U) and I would like to develop a basic application to access the UICC SE or embedded SE (emulating a Mifare classic or a JavaCard) even if the phone is off. How can I test this development case before asking approval? Is it possible ?
And what are the procedures to follow to have approval from RIM or from a carrier (I guess it s depend on the carrier)??
03-28-2012 05:46 AM
03-29-2012 09:11 AM
Yes your help is very useful !!
I am indeed not sure whether to work with UICC or RIM's eSE.
If I want to work with RIM's eSE, I still have some questions:
Supposing that my cardlet is installed of 1000 of your RIM's eSE and that I have an update to do, how the update is done for all devices in one time? And who deal with it?
Supposing that one of your phone (having my NFC service on your RIM's eSE) is changing of end user, how and who updates the peronnal information of the end user of the cardlet?
More Generally how and who will deal with the life cycle of my NFC service?
03-29-2012 12:11 PM
Good questions and potentially long answer :-)
But the short version is that there's a role called TSM (Trusted Services Manager) which forms part of the NFC "eco system" and the TSM is key to these issues being dealt with.
You can search on line for more information on what a TSM is.
03-30-2012 05:58 AM - edited 03-30-2012 06:03 AM
Yes I know...TSM is a looong story
I have read some GlobalPlatform specs about TSM and differents actors roles but I think I don't need all these actors for my project.
As I explained you in previous messages, here are my main constraints:
- To have a dedicated secured memory zone (not dedicated to the payment) in each of your RIM's eSE.
- To have a BB application which is the only one to can access this dedicated secured memory zone and to store data in it.
- That this dedicated secured memory zone could be accessible (in a secured way) with external NFC reader even if the phone is powerred off.
I think they are feasible without TSM or MNO (mobile network operators). Please tell me what do you think?
03-30-2012 06:15 AM
Hi, yes I think I agree. I only mentioned TSM because of your questions about getting the application/applet onto the SE in the first place and of course handling upgrades.
I suspect your requirements can be met but this would need to be looked to more closely and before that can happen you need to apply for access so that your business case and technical requirements can be assessed.
04-02-2012 04:31 AM - edited 04-02-2012 04:32 AM
We'll have a proper form available for this kind of thing soon I hope but in the meantime just send me a private message using the forum facilities right here and I'll pass the request on. The details we need are as follows:
Description of Application(s) Being Developed:
Technology Type (e.g. ISO 14443 A/B, ISO 15693, ISO 18092, MiFare Classic, MiFare Plus, MiFare DESFire, iClass, Calypso, FeliCa)
Secure Element Access Required (Yes/No, UICC or embedded secure element):
Business/ Distribution Model:
Geographic Region Targeted:
Are you currently working with any Carriers/Operators? If so, which one(s)?