Closed Bug 1024776 Opened 6 years ago Closed 6 years ago

[B2G] [User Story] Support for EU Internet APN (regulatory requirement)

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect)

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(feature-b2g:2.1)

VERIFIED FIXED
2.1 S3 (29aug)
feature-b2g 2.1

People

(Reporter: skamat, Assigned: arthurcc)

References

Details

(Whiteboard: [ucid: , FT:RIL][2.1-feature-qa+])

User Story

ROAMING REGULATION (EU) NO 531/2012

Per the EU Internet APN regulation, As a user when I roam into a foreign country (within EU) I should have an option to use a specific roaming APN for all data traffic. The roaming APN terminating in the GGSN of the roaming network and not in the home network. As a user I should be able to manually set/edit this EU internet APN, based on my contracts with specific network (or for similar other reasons).

Acceptance:
 - When user roams in a EU network with a EU sim, prompt the user if they want to use the breakout APN
 - In data settings, a new EU APN should appear that is editable by user.
 - Exact EU network mcc/mnc or APN settings should be customizable.

Attachments

(1 file)

Add support for EU Internet APN for devices for below regulation.

EU regulation within body of EU regulators for Electronics Communications BEREC, from 1 July 2014

"The roaming regulation provides a right to all end-users to choose (from 1 July 2014) a provider of international roaming services different from the provider of domestic services choice, ARP (Alternative Roaming Provider).

Furthermore, it also gives the end user the right to make a local deal with a service provider in the roaming country for using internet data without the knowledge from home operator LBO (LocalBreakOut).

The process is known as decoupling or separate sale of roaming services. This requirement mandates that the end user should be able to manually set the roaming operator as well as use an alternative APN while roaming."
No longer depends on: 985945, 999310
User Story: (updated)
feature-b2g: --- → 2.1
Currently, RIL get APN setting from Gaia. That means this user story should be owned by Gaia developer. Change the component and ni? Howie to get his opinions.
Component: RIL → Gaia::Settings
Flags: needinfo?(hochang)
Summary: [B2G] [RIL] [User Story] Support for EU Internet APN (regulatory requirement) → [B2G] [User Story] Support for EU Internet APN (regulatory requirement)
Gaia will investigate this. To summarize the requirement: 1.This feature only gets enabled for devices sold in EU that are roaming within EU networks 2.Add additional APN type "EU Roaming APN 3.Add setting that asks user if they want to use their original roaming settings or use the new EU breakout APN. If user chooses the EU APN then use the "EU Roaming APN" for roaming.
Flags: needinfo?(hochang)
Bruce - Per email discussion, Can you pls move this to settings user story?
Flags: needinfo?(bhuang)
Yes we're tracking in System Platform
Flags: needinfo?(bhuang)
User Story: (updated)
See Also: → 1032631
Hi all, please see attached for latest APN setting spec. Thanks!
Depends on: 1032631
QA Whiteboard: [COM=SystemPlatform]
QA Whiteboard: [COM=SystemPlatform] → [COM=SystemPlatform][2.1-feature-qa+]
Assignee: nobody → arthur.chen
Flags: in-moztrap?(gchang)
QA Contact: gchang
QA Whiteboard: [COM=SystemPlatform][2.1-feature-qa+] → [COM=SystemPlatform]
Whiteboard: [ucid: , FT:RIL] → [ucid: , FT:RIL][2.1-feature-qa+]
Target Milestone: --- → 2.1 S3 (29aug)
User Story: (updated)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
We are unable to verify this issue since we have no way of roaming inside a EU network using an EU SIM.
QA Whiteboard: [COM=SystemPlatform] → [COM=SystemPlatform][QAnalyst-verify-]
Add the test cases.
https://moztrap.mozilla.org/manage/cases/?filter-suite=756
Flags: in-moztrap?(gchang) → in-moztrap+
Verified @
Gaia      95e9b099aa89ded133e44014dd40b19dc0193c01
Gecko     https://hg.mozilla.org/releases/mozilla-aurora/rev/757931d0149e
BuildID   20140904000203
Version   34.0a2
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.