874801 - [CBS] [User Story] Handle remaining Cell Broadcast Message Classes

Status: RESOLVED INVALID

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

Description

[Wilfred Mathanaraj [:WDM]]

As an operator and as a user I expect the different class of cell Broadcast messages to be handled according to specification.

Class 0: to be displayed immediately (even on a locked screen) , user must have option to dismiss, save or delete the message; user must be able to scroll through long messages and user must be notified with an audible alert when the message arrives on the device.

Class 1:  to be handled the same way as class 1 SMS message - and should be displayed to the user and user must have option to delete or save the message

Class2: are directed at USIM applications and should not be displayed to the user

Class3: are directed to the terminal equipment attached to the mobile device and not displayed to the user.

Comment 1

[Dale Harvey (:daleharvey)]

hey Dylan, is there any UX that has already been done for this?

Comment 2

[Dylan Oliver [:doliver]]

Not yet -- the UX team is working on this right now under bug 874793 and bug 874796.

Comment 3

[Stephany Wilkes]

What Dylan said - thank you, Dylan, for referencing those bugs. Rob Macdonald is doing the UX for CBS this week.

Comment 4

[Andreas Gal :gal]

Dale, we have some preliminary UI for this posted in the parent bug.

Comment 5

[Andreas Gal :gal]

We should split this bug. It sounds like we only care about class 0 and class 1 for IOT.

Comment 6

[Wilfred Mathanaraj [:WDM]]

we do need to find a way to gracefully handle the other messages - if this means we confirm that modem receives it and ignores it.
Once we confirm this then we can split and ignore the class 2 and class 3

Comment 7

[Wilfred Mathanaraj [:WDM]]

for clarity: class 2 and class 3 would be just test cases at this point

Comment 8

[Michael Schwartz [:m4]]

Android handles all classes equally so we should be able to as well.