Heh, feel honored if Google praises the quality of technical discussions. Some words about the NFC/SE controller line of NXP.. As correctly mentioned S2C is an invention of NXP, which was opened to the public by standardizing it. One needs to be aware though that there are slight differences in the timing of the protocol itself, e.g. a PN532 won't work with SE which supports NFC-WI, or the other way around, a PN544 won't work with older SE's supporting S2C.
Normally NFC-WI protocol is only interesting to the combo-chip (PN65) or handset manufacturer (in case they connect NFC controller to a SE). It's not visible to outside like SWP towards UICC. If one sends a message to from AP to the SE, on Nexus S it runs some internal protocol first to PN544 where it gets to NFC-WI for SE. As mentioned in previous posts the SE on Nexus S is not accessible to the Android developer. The keys needed to load applications onto the SE are not known and there is no mechanism (yet?) to transform a SE into development mode. But you have other possibilities, e.g. to switch to UICC with SWP and if next Google phone has an SD card slot also to uSD approach. To make use of SE, without knowing SE keys, would be to have the SE owner provide a "crypto" applet which provides some security services to Android app developers. For instance, it could contain certificates, key store, PIN management, authenticity, .. of course it would need to be governed in some fashion, but at least Android apps have a secure local entity they can trust even in off-line mode. On Jul 13, 5:57 am, Nick Pelly <npe...@google.com> wrote: > I just want to jump in and say, wow, the quality of > android-developers@googlegroups.com has really improved. Most informative > thread i've read in a while! > > (although strictly off-topic since android-developers is meant to be about > developing about the SDK, but I don't mind) > > Nick > > On Tue, Jul 12, 2011 at 10:35 AM, Michael Roland <mi.rol...@gmail.com>wrote: > > > > > > > > > Hallo, > > > > I was thinking S2C is an NXP implementation (e.g. the commercial name) > > > of the NFC-WI. Both,S2C and NFC-WI, looks pretty similar. So in fact, > > > even they using similar approach, we are talking about two different > > > technologies? > > > No, same technology. S2C was there *before* NFC-WI was standardized. So > > NFC-WI is "inspired" by S2C. I didn't find any difference between the > > two so far. > > > > So having the NFC controller, e.g. Samsung S3FHRN2 > > > (http://www.samsung.com/global/business/semiconductor/support/ > > > brochures/downloads/systemlsi/S3FHRN2.pdf), which declared the NFC-WI > > > support we are talking about 2 different, probably not compatible > > > solutions? So theoretical SD card supporting S2C might not be > > > compatible with ECMA NFC-WI standard and vice verse? > > > See above. Should be compatible. > > > > When talking about PN532 and its card emulation capabilities, are you > > > sure the controller emulates the smart card even without having > > > attached the SmartMX secure element? > > > I'm very sure that this NFC controller has card emulation capabilities > > even without a dedicate SE chip. Emulation of the low-level protocol (up > > to ISO 14443-4) is handled by the PN532 and the high-level APDU protocol > > (ISO 7816-4) is handled by the application processor. > > > > NXP delivers to Samsung, SonyEricssion, Nokia, etc. the S2C might be > > > pretty widespread, right? > > > At least everything that uses a SmartMX as secure element uses the > > S2C/NFC-WI. > > > > But since S2C is NXP proprietary do you know if other NFC IC > > > manufacturers are going to support NFC-WI? > > > No, I don't. > > > > "It can, for example, act as a router and its powerful command set > > > allows all elements of the chosen architecture to interact in a > > > controlled manner (SIM, SE, SD card, Application Processor and NFC > > > interfaces).This allows for implementation of various business models > > > by mobile operators and third parties.". > > > Do you know anything about that? > > > No. > > > br, > > Michael > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to android-developers@googlegroups.com > > To unsubscribe from this group, send email to > > android-developers+unsubscr...@googlegroups.com > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
