Closed Bug 1000623 Opened 11 years ago Closed 10 years ago

API to retrieve EF_SPN to distinguish MVNO from an MNO

Categories

(Firefox OS Graveyard :: RIL, defect)

Product:
Firefox OS Graveyard
Component:
RIL
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1027430

People

(Reporter: dbialer, Assigned: wmathanaraj)

References

Details

(Whiteboard: [dependency: marketplace])

MVNO's seem to use the same mcc and mnc as the MNO they are on. For example both Telekom/T-mobile and Congstar have the same mcc and mnc and there is no way to distinguish which network the user is on so that Marketplace can display the proper operator shelf and payment processor. I am told that the way to distinguish it is by the string used to display the network or EF_SPN. We need a way to access this so that we can display the proper operator shelf and payment processor. I am not sure if I am filing this bug in the right place.
Component: DOM: Device Interfaces → RIL
Product: Core → Firefox OS
Icc API provides EF_SPN already; however, the API is for certified Apps only. Currently Marketplace could access only "lastKnownNetwork" and "lastKnownHomeNetwork" which are composed of mcc and mnc strings. Maybe we should start to think about a privileged API for Marketplace.
Whiteboard: [depency Marketplace] → [depedency marketplace]
Yes - it would be good to consider this as a privileged API - or at least get this field (or any other field to differentiate the MVNO from the MNO).
This is needed in Firefox OS 2.1
Assignee: nobody → wmathanaraj
Whiteboard: [depedency marketplace] → [dependency: marketplace]
See Also: → 1027430
Depends on: 1027430
this is a duplicate of 1027430
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Blocks: 1049054
You need to log in before you can comment on or make changes to this bug.