Closed Bug 898997 Opened 7 years ago Closed 7 years ago

[OMA CP][User Story] OMA CP settings provisioning

Categories

(Firefox OS Graveyard :: RIL, defect)

x86
Gonk (Firefox OS)
defect
Not set

Tracking

(blocking-b2g:koi+, firefox26 fixed)

RESOLVED FIXED
blocking-b2g koi+
Tracking Status
firefox26 --- fixed

People

(Reporter: bhuang, Assigned: chucklee)

References

Details

(Whiteboard: [ucid:OMA CP2, FT:RIL, KOI:P1])

Attachments

(2 files)

User Story:

As an OEM, I want to be able to customize which settings are configurable depending on operator requests.

Considering each OEM/Operator may want to configure different settings, from a platform perspective we will want OEMs to customize this mechanism according to who they are shipping to.
blocking-b2g: --- → koi+
Flags: in-moztrap?(echu)
QA Contact: echu
Introduction of WAP Push structure of Firefox OS
Whiteboard: [ucid:OMA CP2] → [ucid:OMA CP2], [FT:RIL]
Hi Bruce and Kevin,

Based on the requirement, it's provide a method for OEM to customize the settings they want to configure. There is no UI/APP for end user at this point, so I will not create test case for it. Let me know if you have any question for it.
Flags: in-moztrap?(echu) → in-moztrap-
Whiteboard: [ucid:OMA CP2], [FT:RIL] → [ucid:OMA CP2, FT:RIL, KOI:P1]
WAP Push test app[1] can be used as an example of WAP Push receiving.

[1] https://github.com/mozilla-b2g/gaia/tree/master/test_apps/test-wappush
WAP Push test app in Gaia which receives all WAP Push messages and show its content.
This can be used an example of how to receive and handle WAP Push messages.
OEMs can customize WAP Push app based on information provided in attachments.
The user story is resolved.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Assignee: nobody → chulee
Component: General → RIL
You need to log in before you can comment on or make changes to this bug.