848372 - [META] Cell Broadcast implementation for 1.1

Status: RESOLVED FIXED

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

Description

[David Palomino [:dpalomino]]

As a user I want to be notified about incoming Cell Broacast messages. A notification should be shown in the utility tray (similar to SMS) and CB messages should be listed in the messaging application (e.g. In a unique thread for all that kind of messages). 

This is a critical requirement for many carriers, as it is a service used by Governments to warn about natural disasters (e.g. Earthquakes).

Comment 1

[Wilfred Mathanaraj [:WDM]]

This is a tracker bug for a complete cell broadcast implementation. 

Mobile operators use Cell Broadcast for communicating various items: e.g.
* area code of the antenna cell to the mobile user (via channel 050)
* nationwide or citywide emergency alerting, 
* weather reports, 
* mass messaging, 
* location based news

Cell Broadcast is a mobile technology that allows messages (up to 15 pages of up to 93 characters) to be broadcast to all mobile handsets and similar devices within a designated geographical area.

Different operators in different countries have different channels that are required for support.

Cell Broadcast support 4 different classes of messages (Class 0 to Class 3); all of which must be supported.

Please refer to the specification for Cell Broadcast to understand finer details of implementation requirements: 

3GPP: 44.012, 23.041

Comment 2

[Julien Wajsberg [:julienw]]

Should this be done for v1.1, or is it due for v1.2 ?

Comment 3

[Dietrich Ayala (:dietrich)]

Needed as a late 1.1 feature, as I understand. Still figuring out scope, and schedule.

Comment 4

[Rob MacDonald [:robmac]]

Attachment: Cell Broadcast UI Spec - v0.2

Initial spec attached. I look forward to your feedback and questions.

This spec and related content is also stored on Mozilla's box.com site. Go to https://mozilla.box.com/system and click on the Cell Broadcast folder.

Comment 5

[Wilfred Mathanaraj [:WDM]]

Open question you raised regarding class 1: If Class 1 is being handled in the messaging app there is no need for a UI. It should be treated as a "normal" message.

Class 0 message handling meets what we need from an operator perspective.

once we confirm if class 2 and 3 are handled by the modem we can close those two out of this discussion.

Comment 6

[Andreas Gal :gal]

How should class 1 be handled in the message app? We can treat those as SMS but who is the sender? Some magic number?

Comment 7

[Wilfred Mathanaraj [:WDM]]

i will check with partner as to what they use as sender (name or number) and if this remains consistent across any message that is received as class 0 CBS Message.

Comment 8

[Andreas Gal :gal]

We potentially want a patch in Gecko to automatically transform class 1 messages into SMS (or we do it in Gaia).

Comment 9

[Daniel Coloma:dcoloma]

(In reply to Andreas Gal :gal from comment #6)
> How should class 1 be handled in the message app? We can treat those as SMS
> but who is the sender? Some magic number?

In some implementations there is a thread in SMS applications called "Broadcast Messages" where these messages are listed. 

Some further comments:

Bear in mind that we already support class 0 SMS and that CB class 0 messages should be handled exactly in the same way.

Please also take into account that Cell Broadcast regulation changes *a lot* from country to country as the purpose in multiple countries is very different (tsunami warnings, inter-state roaming warning, child abduction emergency bulletins...) and the UX requirements are very different too. So if you are planning to meet a specific target with this lightweight implementation, I suggest you consider this.

Lastly: we already support CB as required by ANATEL (Brazil regulator) we need to ensure any change in CB does not break current implementation for Brazil.

Comment 10

[Andreas Gal :gal]

Feedback from our chipset partner is that we can handle class 0 and class 1 the same. We only use one notification mechanism. We will get a video of what Android does (which we know to pass IOT). Notifications might be sufficient, we don't need a fully modal dialog (potentially).

Comment 11

[Andreas Gal :gal]

comment 9: ideally we can close this bug and map the 1.1/leo requirements onto that so the existing channel changes are sufficient.

Comment 12

[Michael Schwartz [:m4]]

Where are these classes coming from?  You mention Class 0-3 but I don't see any mention of that in the CBS spec 3GPP TS 23.041 - I know they are relevant for SMS but not here.  There are parameters for CBS regarding whether a popup should be displayed or whether the message is emergency; are we talking about that?  If there is something I'm missing, please provide a spec ref.

Comment 13

[Andreas Gal :gal]

Daniel, it seems that we display CB for ANATEL in the lockscreen only. Is that correct?

Comment 14

[Andreas Gal :gal]

m4, can you please post the video we talked about? We are trying to imitate that behavior.

Comment 15

[Michael Schwartz [:m4]]

Attachment: Android CBS dialog

Checking the code and running some tests show the message ID value is ignored by Android and therefore we should be ok to do the same.

Comment 16

[Dietrich Ayala (:dietrich)]

All dependent bugs are now closed.

Comment 17

[Julien Wajsberg [:julienw]]

So, is there anything left to do in gaia then ?