Confirmed users
978
edits
WebAPI/WebTelephony/Multi-SIM: Difference between revisions
Jump to navigation
Jump to search
→Proposal for Multi-SIMs
m (→Incoming Call) |
|||
| Line 115: | Line 115: | ||
=== Proposal for Multi-SIMs === | === Proposal for Multi-SIMs === | ||
With various hardware design, there might be multiple ril-daemon (rild), one rild taking care of one SIM, while it is also possible that there is a single rild manipulating all the SIMs'. To make our architecture flexible enought, we are planning to have 'rilproxy' in charge of sending RIL parcels to the correct rild, no matter how many there are. Moreover, in consideration of code clarity, we introduce multiple instances to achieve one-instance-one-SIM mapping. | |||
Here is a proposal for multi-SIMs. | Here is a proposal for multi-SIMs. | ||
[[File:B2GArch-multisim.png|388x300px|Proposal: B2G Architecture for Multi-SIMs]] | [[File:B2GArch-multisim.png|388x300px|Proposal: B2G Architecture for Multi-SIMs]] | ||
==== Internal API: nsIRILContentHelper.idl ==== | |||
We might need to add 『index』, used for connecting a telephony object (phoneIndex) and a specific 『sim slot』. | |||
*Examples of modifiying the internal API: | *Examples of modifiying the internal API: | ||
| Line 127: | Line 130: | ||
readonly attribute jsval voicemailNumber; /* {index, number} */ | readonly attribute jsval voicemailNumber; /* {index, number} */ | ||
==== Potential Issues (Bugs we might need to file) ==== | |||
*Array-ize RadioInterfaceLayer: one instance for one sim slot | |||
*Send parcel to the correct rild: might need to modify ril_worker.js and rilproxy | |||
*Get the number of sim slots | |||
== Discussion == | == Discussion == | ||