Closed Bug 989889 Opened 10 years ago Closed 10 years ago

[B2G][NFC][User Story]: NFC Daemon modifications for supporting Tap2pay

Categories

(Firefox OS Graveyard :: NFC, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(feature-b2g:2.0, tracking-b2g:backlog)

RESOLVED FIXED
2.0 S4 (20june)
feature-b2g 2.0
tracking-b2g backlog

People

(Reporter: skamat, Assigned: dimi)

References

Details

(Keywords: feature, Whiteboard: [ucid:NFC17, 2.0, FT:RIL])

User Story

This is an enabler for NFC payment demo

The entails following:

1. NFC Daemon modifications for supporting Tap2pay (without application triggering and UI notification)
2. Modify NFC daemon with sample codes for chip vendor as shown in architecture
(See Attachment: Same as what Dimi presented for NFCD during first NFC workweek)
3. No modification in Gecko and Gaia necessary at this time.

Acceptance Criteria

AC1: If the settings has NFC turned on with appropriate secure elements (payments data), the user makes payment simply by tapping at an enabled point of sale.

AC2: The POS payment terminal shows the user whether the transaction succeeded or failed.

Attachments

(2 files)

This is an enabler for NFC payment demo.

NFC Daemon modifications for supporting Tap2pay (without application triggering and UI notification)
User Story: (updated)
No longer depends on: 979868
This bug should have dependency on the 979868!
Depends on: 979868
I wonder if this bug depends on bug 979868.
Dimi, according to what you explained last week, this user story should have been supported.
Flags: needinfo?(dlee)
(In reply to Ken Chang[:ken] from comment #2)
> I wonder if this bug depends on bug 979868.
> Dimi, according to what you explained last week, this user story should have
> been supported.

Currently nfcd source code support this user story is in my personal repository and not yet integrate to mozilla nfcd branch. I will do more test to make sure that CE mode will not affect original tag discover and p2p function then i will merge it to mozilla nfcd branch.
Flags: needinfo?(dlee)
Thanks, this bug is yours.
Assignee: nobody → dlee
Acceptance Criteria:

AC1: If the settings has NFC turned on with appropriate secure elements (payments data), the user makes payment simply by tapping at an enabled point of sale.

AC2: The POS payment terminal shows the user whether the transaction succeeded or failed.
AC updated
User Story: (updated)
Whiteboard: [ucid: , FT:RIL] → [ucid:NFC17, 2.0, FT:RIL]
blocking-b2g: --- → backlog
Depends on: 1006460
feature-b2g: --- → 2.0
Depends on: 1010123
Flags: in-moztrap-
Status: NEW → ASSIGNED
For flame, this feature will only work after using T2M libnfc-nci
Depends on: 1008809
Has T2M already been informed about it? If yes, when would T2M libnfc-nci be available?
I believe libnfc-nci is available and what we need to do is to sync.
So now tap2pay demo works ok on Nexus5 but on Flame we need bug 1008809.
Target Milestone: --- → 2.0 S4 (20june)
Feature can be tested on Nexus5 + partner's simulator, which is planned scope.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: