Closed Bug 898994 Opened 7 years ago Closed 7 years ago

[OMA CP][User Story] OMA CP protocol support

Categories

(Firefox OS Graveyard :: RIL, defect)

x86
macOS
defect
Not set

Tracking

(blocking-b2g:koi+, firefox26 fixed)

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

People

(Reporter: bhuang, Assigned: chucklee)

References

()

Details

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

Attachments

(2 files)

User Story:
As an operator, I want to be able to remotely customize system settings using OMA CP.

The goal of this story is so that gecko side is able to receive the provisioning requests and notify gaia accordingly.  It is not tied to a specific setting or operator.
blocking-b2g: --- → koi+
Flags: in-moztrap?(echu)
QA Contact: echu
Introduction of WAP Push structure of Firefox OS
Whiteboard: [ucid:OMA CP1] → [ucid:OMA CP1], [FT:RIL]
Hi Bruce,

As we discussed with Dev today, currently we don't have dedicate carrier with clear CP scope to implement on Gaia part, so I will test this user story with test app first, and therefore there is no test case for it. Please let me know if you have any question about it.

Thanks.
Flags: in-moztrap?(echu) → in-moztrap-
Whiteboard: [ucid:OMA CP1], [FT:RIL] → [ucid:OMA CP1, FT:RIL, KOI:P1]
Flags: in-moztrap- → in-moztrap+
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.
Operators 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
Verified with Unagi master build 20130816122903.
Status: RESOLVED → VERIFIED
Component: General → RIL
You need to log in before you can comment on or make changes to this bug.