987043 - [NFC-Payment-RIL-Vendor-Support ] BIP support for the remote management of secure element applets

Status: RESOLVED FIXED

(Firefox OS Graveyard :: NFC, defect)

Description

[Ming Yin]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0 (Beta/Release)
Build ID: 20140314220517

Comment 1

[Ming Yin]

This feature is required by the user story - Enable management of NFC services with the Mobile Wallet UI app (Bug 979158)

The detailed description of this feature requirement from the view point of a carrier's mobile wallet product.

1) The mobile device SHALL support BIP in UICC client mode for UDP.

2) The mobile device SHALL support two concurrent channels, BIP in UICC client mode.

3) The mobile device SHALL support the SMS push (per ETSI TS 102.226) to establish an open BIP channel as per ETSI TS 102.223 Open Channel Command.

4) The mobile device SHALL support Binary SMS bearer.

5) For mobile devices supporting multiple APNs, the device SHALL be able to set-up a SIM OTA channel using the APN information this is provided in the OPEN CHANNEL command. For devices which are configured as "Always-ON" and only support a single APN, the APN information provided in the OPEN CHANNEL command SHALL be ignored by the device and the default APN SHALL be used.

6) The mobile device SHALL support the following proactive commands:
- CAT class E (OPEN Channel, CLOSE CHANNEL, RECEIVE DATA, SEND DATA, GET CHANNEL STATUS)
- CAT Class L (ACTIVATE)

7) The mobile device SHALL support the following events:
-CAT class E/Event download (DATA AVAILABLE, CHANNEL STATUS)


Some external depedency to make this feature happen.
1) RIL vendor support for modifying the basedband processor, so that the above requirements 6) & 7) can be handled correctly!
2) carrier's test SIM card 
3) carrier's OTA backend support for the E2E OTA/BIP testing

Comment 2

[Ken Chang[:kenkai]]

For 1 to 4,
I wonder if this implementation should be done by modem. Could you please talk with your OEM partner to know the details? Thanks.
For 5, does any carrier assign a special APN only for this purpose.

By the way, do you have any example of this wallet ui app? I wonder if this wallet ui app only need to show the result, but don't involve in this transction procedure handled by STK.

Comment 3

[Ming Yin]

The OTA provision process of SIM applets(javacard application) is transparent for the wallet user. What the user from the wallet UI can see is a retrieved list of installed SIM applets. 

I will send you some walet UI snapshots per mail.

Comment 4

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

Heard this is no longer a blocking issue because it was solved?
Could you put some comments and let's close this bug?

Comment 5

[Ming Yin]

Attachment: Flame_BIP_CAT_TP_Test_Logs.txt

BIP Test using Flame device and carrier's OTA Server

Comment 6

[Ming Yin]

(In reply to Wesley Huang [:wesley_huang] from comment #4)
> Heard this is no longer a blocking issue because it was solved?
> Could you put some comments and let's close this bug?

I attached a BIP tests log file, which had been done using Flame and carrier's OTA server.
It shows that the required BIP featue has been supported on Flame. 
You can close this bug.