Re: TODO: Network updating the emergency number list
Hi Petteri, On 12/21/2010 10:21 AM, Tikander Petteri wrote: Hi Rajesh and Denis, If we are in area with multiple networks (so multiple MCCs), lets pass only received emergency-list from the servicing network, where ME is registered to, and discard possible notifications from other network's emergency-number notifications: For sure we should not update the ECC list with numbers from outside the current MCC. However, it is less clear whether we can simply discard the ECCs from other MCCs or still cache this information in some fashion. I suspect discarding them as a first implementation is enough... Either way, the core has to make the final decision, no filtering should be done by the driver. TS 22101, ch. 10.1 The UE shall regard these emergency numbers as valid in that country only (as identified by the MCC) and shall discard them when a new country is entered. One think in one of those emails focusing on this discussion (Waldo's comment) was: The modem will typically already analyze the new emergency-numbers, filter out the ones that are not applicable and merge the numbers from the various sources in the right priority My idea first in analyzing was to compare new emergency numbers with already sent emergency numbers (default-list/SIM EFecc-list), and send those up, if new emergency numbers compared to the old already sent ones were received. OK, probably in many cases modems will do this analyze itself, and send only new ones to the oFono. I don't know if it's actually dangerous, if oFono passes all network emergency numbers received from the modem (filtered or not by the modem). OK, then it's possible that some ECCs are reported twice. On the other hand, network ECCs (if MCC matches) should always be valid ones, suitable numbers, in spite of, where mobile is located. So it should be valid to acknowledge those new numbers always to UI in spite of, what numbers are sent to UI in initialization phase. 22.101 exists for a reason. Same with the 27.007 standard. We should implement the standard to the letter here. Perhaps then the only thing to be analyzed could be that country-code item. Network downloaded emergency number-list can also contain emergency call type in the category-field (for instance Police, Ambulance...). This kind of information is not included for example in SIM EFecc-file, so Emergency-number property returns in this moment just the ECC-number without the category. What do you think, should this also be included in the Emergency-property? I believe the EFecc described in 31.102 also contains the category information. So we can certainly change the API to provide this information or an empty string if unknown. However, since the category information is a bitmap, mapping this to an API in a nice manner can be quite challenging. Feel free to propose something. Regards, -Denis ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
RE: TODO: Network updating the emergency number list
Hi Denis / Petteri, Network downloaded emergency number-list can also contain emergency call type in the category-field (for instance Police, Ambulance...). This kind of information is not included for example in SIM EFecc-file, so Emergency-number property returns in this moment just the ECC-number without the category. What do you think, should this also be included in the Emergency-property? I believe the EFecc described in 31.102 also contains the category information. So we can certainly change the API to provide this information or an empty string if unknown. However, since the category information is a bitmap, mapping this to an API in a nice manner can be quite challenging. Feel free to propose something. Is the emergency number category really used on the AP SW side ? All we do is to check the number against the ECC list to see its going to use the dedicated emergency services channel in the radio interface for that call or not, irrespective of the category type. If we are going to have an UI thats going to list ECC numbers and its corresponding category, then this information is useful, but I have never seen such UI in other platforms as well. BR, Rajesh ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: TODO: Network updating the emergency number list
Hi Rajesh, On 12/21/2010 04:14 PM, rajesh.naga...@elektrobit.com wrote: Hi Denis / Petteri, Network downloaded emergency number-list can also contain emergency call type in the category-field (for instance Police, Ambulance...). This kind of information is not included for example in SIM EFecc-file, so Emergency-number property returns in this moment just the ECC-number without the category. What do you think, should this also be included in the Emergency-property? I believe the EFecc described in 31.102 also contains the category information. So we can certainly change the API to provide this information or an empty string if unknown. However, since the category information is a bitmap, mapping this to an API in a nice manner can be quite challenging. Feel free to propose something. Is the emergency number category really used on the AP SW side ? All we do is to check the number against the ECC list to see its going to use the dedicated emergency services channel in the radio interface for that call or not, irrespective of the category type. If we are going to have an UI thats going to list ECC numbers and its corresponding category, then this information is useful, but I have never seen such UI in other platforms as well. 22.101 hints that such UI is a possibility. However, I tend to agree that this information isn't terribly useful otherwise. The other stumbling block is that EFecc in 51.011 and 11.11 never contained the information about the emergency number category in the EFecc fields... Regards, -Denis ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: TODO: Network updating the emergency number list
Hi Petteri, On 12/17/2010 03:10 AM, Tikander Petteri wrote: Hi, I have investigated a little bit dynamic updating of emergency numbers by network. So I suggest, I'll register new notification-handler for '+CEN'-report in voicecall-driver. And naturally give those new emergency-numbers for voicecall-atom to be analyzed. First version of network-ECC handling will enable +CEN-reporting statically in driver-probing. Then it listens '+CEN'-reports and after receiving new numbers compares those numbers with already stored numbers (SIM/default ECC's) and sends property-changed signal for same old good EmergencyNumbers-property, if new emergency numbers have been received from the network. Sounds good to me. According to TS.27007 network emergency numbers are not necessarily received from the same operator as currently registered, so this should probably also be considered in the future. Can you do me a favor and investigate what oFono's behavior should be if we receive emergency numbers that are not relevant to the currently registered PLMN? We should also update the task description with the above. My test-modem doesn't actually support '+CEN'-reports, but I can update a little bit Phonesim for simulating of testing the unsolicited network emergency-numbers. Sounds good. Regards, -Denis ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
RE: TODO: Network updating the emergency number list
Hi, I have investigated a little bit dynamic updating of emergency numbers by network. So I suggest, I'll register new notification-handler for '+CEN'-report in voicecall-driver. And naturally give those new emergency-numbers for voicecall-atom to be analyzed. The modem will typically already analyze the new emergency-numbers, filter out the ones that are not applicable and merge the numbers from the various sources in the right priority. Some modems are able to communicate the resulting effective list of emergency-numbers, in which case the voicecall-atom should just use the list of emergency numbers reported by the modem without doing any additional merging/analyzing. This also eliminates room for error if the algorithm that the ofono voicecall atom uses differs for some reason from the algorithm used by the modem. For modems that aren't able to communicate their effective list of emergency numbers ofono would still need to create such list by itself as it does now. Cheers, Waldo ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
RE: TODO: Network updating the emergency number list
Hi Denis, Hi Petteri, On 12/17/2010 03:10 AM, Tikander Petteri wrote: Hi, According to TS.27007 network emergency numbers are not necessarily received from the same operator as currently registered, so this should probably also be considered in the future. Can you do me a favor and investigate what oFono's behavior should be if we receive emergency numbers that are not relevant to the currently registered PLMN? We should also update the task description with the above. The ECC list downloaded from the network are country specific ones, so this ECC list usually can be notified by any available network not necessarily by the serving network. The ECC list thats downloaded from the serving network has to be reset when the phone registers in another network with a different MCC ( not MNC ), as this ECC list is country specific not operator specific. BR, Rajesh ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
Re: TODO: Network updating the emergency number list
Hi Rajesh, Can you do me a favor and investigate what oFono's behavior should be if we receive emergency numbers that are not relevant to the currently registered PLMN? We should also update the task description with the above. The ECC list downloaded from the network are country specific ones, so this ECC list usually can be notified by any available network not necessarily by the serving network. The ECC list thats downloaded from the serving network has to be reset when the phone registers in another network with a different MCC ( not MNC ), as this ECC list is country specific not operator specific. Sounds reasonable. Is this relevant only when the ME is registered with the IMSI known or also when the SIM is not present / PIN not entered? For these cases, what happens when we're in an area with multiple networks with multiple MCCs. Final question, is there a spec that describes this behavior? Regards, -Denis ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
RE: TODO: Network updating the emergency number list
Hi Denis, Hi Rajesh, Can you do me a favor and investigate what oFono's behavior should be if we receive emergency numbers that are not relevant to the currently registered PLMN? We should also update the task description with the above. The ECC list downloaded from the network are country specific ones, so this ECC list usually can be notified by any available network not necessarily by the serving network. The ECC list thats downloaded from the serving network has to be reset when the phone registers in another network with a different MCC ( not MNC ), as this ECC list is country specific not operator specific. Sounds reasonable. Is this relevant only when the ME is registered with the IMSI known or also when the SIM is not present / PIN not entered? Only when the SIM/USIM is present. For these cases, what happens when we're in an area with multiple networks with multiple MCCs. Good question :) Final question, is there a spec that describes this behavior? 3GPP TS 22.101 Section 10 BR, Rajesh ___ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
