Closed Bug 979888 Opened 6 years ago Closed 6 years ago
B2G NFC: support UICC-based card-emulation as per Mifare
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0 (Beta/Release) Build ID: 20140212131424
For NFC couponing and ticketing user story(ucid:NFC13, ucid:NFC14), the NFC Controller SHALL be configured to support UICC-based Card-Emulation as per Mifare (1K). Additionally,following requirements need to be fulfilled too. 1) Card Emulation mode SHALL be enabled as soon as the NFC hardware is turned on; 2) The default routing for the card emulation mode SHALL be via the UICC; 3) UICC SHALL be configured as default secure element; 3) Automatic and continuous switch between card emulation and reader mode, based on optimized power consumption.
Summary: B2G NFCd: support UICC-based card-emulation as per Mifare → B2G NFC: support UICC-based card-emulation as per Mifare
The NFC card emulation shall be also possible under following "abnormal" cases. 1) screen-off 2) screen-locked 3) battery-low(phone switched off) 4) battery-off(phone switched off, NFC/SIM powered by the field of external reader.) 5) flight-mode
Hi Ming, Thanks for this information. I wonder if you could provide a user scenario for this user story or some user flows for us. It would be more clear for what this user story is.
The user scenarios which will be based on this feature are 979154 and 979157. Please let me know, in case the description of 979154 and 979157 is not sufficient for you. The communicate flow looks normally like follows. (Precondication: the NFCd has configured the NFCC to support Mifare-based Card Emulation, similiar to the case with ISO14443) Reader application -> NFCC -> SIM-based Mifare Application -> NFCC -> Reader application
Currently all NFC payment user stories are covered under: Bug 979152, Bug 979154, Bug 979157, Bug 979158, 884478. All the dependencies for those should be marked in those meta bugs.
Hi Ming, Based on test results in TMobile Poland, Is this feature already supported now ?
(In reply to Dimi Lee[:dimi][:dlee] from comment #6) > Hi Ming, > Based on test results in TMobile Poland, Is this feature already supported > now ? I would say yes for Flame. :-) Before we change the bug status to "resolved", I would want to ask for some more friendly user tests, so that we are 100% sure about it.
In my testing nfcd now we can receive HCI_EVENT_TRANSACTION. But the correct data format should be: |'81'|AID Length|AID|'82'|Parameters| But in flame we received |'81'|AID Length|AID|'81'|AID Length|AID|'82'|Parameters| Now we are checking the behavior of Nexus5
(In reply to Dimi Lee[:dimi][:dlee] from comment #8) > In my testing nfcd now we can receive HCI_EVENT_TRANSACTION. > But the correct data format should be: > |'81'|AID Length|AID|'82'|Parameters| > > But in flame we received > |'81'|AID Length|AID|'81'|AID Length|AID|'82'|Parameters| > > Now we are checking the behavior of Nexus5 sorry this comment should belong to bug 979891, please ignore this
Hi Ming, can we close this bug?
Blocking user story. Moving from backlog to feature list.
blocking-b2g: backlog → ---
feature-b2g: --- → 2.1
yes, we can.
Thanks for your confirmation. Let's mark this as resolved fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.