989939 - [B2G][MMS][DSDS] Enhancement of Sending/Retrieving MMS for non Active SIM in DSDS device.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: RIL, defect)

Description

[Bevis Tseng[:bevis][:btseng](Exited)]

Fire this bug to follow up the discussion of sending/retrieving MMS in DSDS device in bug 983315.

[major issues regarding sending/retrieving MMS under DSDS device]:
1. What's the priority and policy of other ongoing operations compared to MMS transaction?
   - Including Voice Call, Default Internet Data Connection, SUPPL, DUN, etc.
2. How to inform user and get user's confirmation if the selected service Id is not active.
3. How to make the transaction to be done smoothly and provide feedback accordingly 
   when switching active SIM is needed.
4. Shall we restore the active SIM after transaction is done no matter it's success or not?

[Proposal from Gaia]
1. 1 additional parameter |forceSwitch| is introduced in sendMMS/retrieveMMS WebAPI.
2. when |forceSwitch| was not specified, gecko returns a specific error for gaia
   to handle the issue#2.
3. Then, gaia can call either send/retrieve again with |forceSwitch| set to |true| for
   gecko to handle the switching and then the transaction accordingly.

[Proposal from Gecko]
1. Bug 985945 has to be introduced to provide a general solution for
   apps to define their-own UX behaviors.
2. For the implementation of sendMMS/retrieveMMS API, to make sure that it matches 
   the semantic meaning of these APIs:
   a. Gecko has to accomplish the MMS transaction to the specified serviceId including
      switching the active SIM when needed during the transaction for DSDS.
   b. For sendMMS, if there is no serviceId specified, 
      default serviceId in the settings will be used.
   c. In DSDS, the switching is triggered on the fly per sending/retriving request.
      Hence, there shall be no change to both |dom.mms.defaultServiceId| and 
      |ril.data.defaultServiceId| during the transaction.
   D. If issue#4 is needed, the switching has to be restored after request is completed.

Comment 1

[Ken Chang[:kenkai]]

Put this bug into backlog.

Comment 2

[Bevis Tseng[:bevis][:btseng](Exited)]

no longer following up this bug.

Comment 3

[BMO Automation]

Firefox OS is not being worked on