29 May 2011

Nexus S Secure Element, Google Wallet

Nexus S does NFC but has no µSD Slot
Google&Mastercard want to control your wallet.


But:

DIY NFC using the Nexus S

Here's what we did next: Download the source (actually from CyanogenMod 7 to have the full build environment for the new Nexus S), make the appropriate changes to the code, recompile everything and put it back into the phone and it works — Nexus S supports card emulation and SWP!
Then we developed an Android app which we call "The Secure Element Manager" that gives the user full control over the secure elements in the phone as well as the NFC chip.
We are now able to fully control the PN65N from an Android app. Very nice, but not enough; we need more: an API for accessing the UICC (secure element) from an Android API.
nearfieldcommunicationsworld...................................................................................................
Luckily Giesecke & Devrient already supports the development of a smartcard stack for Android, SEEK, the Secure Element Evaluation Kit. This one is available for Android 2.2 and requires some adaption to work in Gingerbread, but after these changes we have a fully featured NFC phone using the Nexus S Hardware. Nice, isn't it?
aaa

http://groups.googlecom/group/android-developers/browse_thread/thread/418c9b370f08a9f7

__________________________________________________
Nokia C7 comes with a PN544 from NXP. .. ready for Single Wire Protocol support in order to use the UICC as the secure element.

.. Nokia only needs to provide firmware .. likely use NXP's FRI (Forum Reference Implementation), which is also used in the Google phone...
aaa

The FRI a basic software stack for managing the NFC chip through HCI (Host Controller Interface) Android's core and Symbian^3 are both implemented in C, so the stack ..can be ported to both ..

P2P/LLCP and card emulation using SWP or an embedded secure element.

On top of the FRI, Nokia will provide JSR257 (Java layer) in order to manage reading/writing functionality or exchanging of NDEF data structures. Depending on the configuration of the FRI, the phone can support SWP to offer card emulation using a UICC.

Nokia's C7 already provides JSR177 for J2ME applications to communicate with the UICC...
.......................
The Nexus S comes with a PN65N from NXP. This chip is a combination of the PN544 NFC controller and an embedded SmartMX secure element.
__________________________________________________



1. Is this the birth of a new payments network, or an old network in mobile form?

.. Google will be partnering with MasterCard to bring mobile payments ... If that turns out to be true, it's a definite win for the old guard. The current payments infrastructure is built on principles that were defined in the 1970s when credit cards as we know them appeared on the market. It's ripe for disruption and Google has the perfect skillset for doing so. Both MasterCard and Visa have looked at risk of disintermediation.

"secure element" in the case of the Google Nexus S, .. a chip embedded in the mobile phone during manufacturing. (Nexus has NO slot)
With a microSD, it can be anyone. With an embedded secure element, it would usually be the manufacturer of the phone. This is expected to be the case with RIM's forthcoming Blackberry NFC phones and is almost certain to be the case with a future Apple iPhone.
..........
Will any business be able to get access to Google mobile wallets — even direct competitors like Microsoft and Apple — or will Google lock them out? How about the likes of Groupon, PayPal, Facebook and Visa? And who will these businesses go to instead to access the new generation of mobile wallet technology if they can't access a Google Wallet?
nearfieldcommunicationsworld
__________________________________________________


The NXP PN65 .. the NFC radio controller, the embedded secure element and NFC software ...
nxp

Google Wallet, Google Offers, Google Prepaid Card and SingleTap, .. in conjunction with MasterCard, Citi, First Data and Sprint.
. add funds.. from any credit card.
Payments processing ..through MasterCard's PayPass network.
First Data for trusted service manager (TSM) ..such as provisioning card ..
..
nearfieldcommunicationsworld
hypercom

The Google Wallet limited to Nexus S 4G phones Sprint, not the 3G version for T-Mobile or other Android phones...
..Steve Owen, vice p id NXP ..all Android .. could potentially support the wallet
Google could try to control embedded chips and APIs, in other NFC phones ... at odds with mobile operators that want to control the application-bearing chips ..

Isis AT&T, Verizon Wireless and T-Mobile wants to control the secure elements Sprint dropped out.
nfctimes
European.. business model for NFC is based on charging fees to banks and other service providers to put their NFC applications on SIM cards that the telcos issue.

But Google, in fact, is also seeking to recruit European banks ..the Nexus S also supports the single-wire protocol connection to the SIM card, it's possible that Google could block this.

PayPal accusing Google of stealing its trade secrets by recruiting Osama Bedier Google's head of payments. also names Tilenius, who worked at eBay.

__________________________________________________

the wallet will require an “app-specific PIN” to activate, and in the first release (sic), “all payment card credentials will be encrypted and stored on a chip.” (like, in later releases card credentials will be scattered about in clear?]

Update: It's possible Google could ... use Andorid API availability to prohibit other wallet service providers? ..
Google made a point of saying that the wallet would be open to other banks and service providers, along with other mobile carriers and handset makers. ..Google is likely to want to control which applications go into its wallet, ..APIs and master keys, managed by First Data.

__________________________________________________

2 comments:

  1. http://www.madlmayr.at/blog/?p=139
    seems to be close to the origin

    ReplyDelete
  2. /* what conceivable version of TDES could take Key 1C94D15B507F8C2C6DD3C3BEF2C8FA75
    data F1E3D1C7B1A3918F and give output of 35E431B4BE541C0A ?
    - I suppose one where the IV is neglected to mention...
    god bledd MWO for keping their documents secret...
    */

    ReplyDelete