Hi Sri A few comments <DL> in-line </DL>.
David From: Sri Gundavelli (sgundave) <[email protected]> Date: Wednesday, 29 March 2023 at 10:34 To: Lake, David (PG/R - Comp Sci & Elec Eng) <[email protected]>, [email protected] <[email protected]> Subject: Re: [DMM] Emergency 911 Services over Wi-Fi Hi David, Thanks a lot for the feedback. I agree with the two key problems you have identified. It is indeed about network selection; it is about temporary access and also about using emergency service configuration for use with the default dialer. * Network attachment. The solution with a roaming WiFi partner is good but we should also consider the ability to extend the concept of an ‘Emergency Attach’ to LTE/5GNR without the need for credentials (or with well-known credentials). This is made much more complex in the case of incoming roamers where 2G/3G has sunset – for example, if I visit the US now, I can be in a position where I get LTE/5G data service through a roaming partner but no IMS access. Many international carriers also limit ‘home’ ePDG (‘WiFi Calling’) access. There is support for emergency attach without expired SIM, or no SIM. Those mechanisms are supported. The focus of CSRIC 8 group is how to make that call work over Wi-Fi; this can be for Wi-Fi only capable device, or a dual radio capable device. For the latter case, the answer is always ePDG call, but that goes with the assumption the device is able to authenticate to the access network. We are solving that basic connectivity problem with OpenRoaming. A device with no access credentials, just with an emergency passpoint profile can perform an attach and make that emergency call. As you also say, what IMS configuration should the device use in such scenario where there is no mobile operator, is the other issue. <DL> Given the number of ‘2nd number’ applications out there (Swytch, Vyke, etc.) if you have a Wifi connection then you’ll have phone service; just not through the M(v)NO! My conclusion is that it is the 3GPP/IMS architecture that is wrong and needs to be simplified/changed to disassociate the application (voice/text) from the data pipe…. </DL> * No matter how I attach to an IP network, I should be able to access the upper-layer application (which is essentially a SIP dialler) and make a 911 call. I can’t because the dialler currently relies on IMS registration which then takes me straight back to the issues with IMS access, IMS-to-IMS roaming, non-availability of VoWiFi (via ePDG), etc. Location SHOULD be available via GPS from the end device or from the IP path of the packets (knowing the location of the attached AP/gNB). Yes, completely agree. The dialer should be access agnostic. That may be the case, but this needs to be qualified. Perhaps device vendors should do some testing and make sure the device can use the obtained emergency service configuration and make the call over the available access. <DL> See above! What has astonished me being here in Japan is that in common with other UK (and possibly European) carriers, Vodafone UK don’t allow me to use WiFi Calling at-all when roaming instead forcing me to use their very expensive (and poor quality) roaming interconnect. I’m even dropped to circuit-switched for voice calls despite having an LTE service. But my iMessage, WhatsApp, Signal and Swytch services work perfectly over LTE or WiFi. So the dialer today is absolutely NOT access-agnostic and I am told that is by-design in 3GPP as it is the fact that I am a) not on my home PLMN and b) not in the UK by IP address (and there is VPN detection as well) disables the WiFi Calling access on a per-carrier profile basis. The problem is made worse because there is no interworking between these disparate applications for calls and texts which means that I can end up with many separate dialers that can reach/are reachable by their own user groups. I think what we need to be doing is unifying the applications over a common protocol (which is IP) and then disaggregating the service to providing interoperability. That solves E911 and so much more and starts to move us away from the 3GPP architecture for all applications. SIP is exactly the thing to do that but not the combination of SIP+IMS. Obviously the issue then is that VoLTE/VoNR is able to manipulate the OTA to provide a better grade-of-service but we should be able to steer packets from any of the rich-media apps through a dedicated bearer if we can get the transport network to provide us with APIs to do so. In fact, there would be benefit in opening-up the transport APIs to enable ANY application to request a higher-grade of service determined by required QoE. </DL> Location is a complex topic. The device can always use GPS source, but in many indoor environments GPS signal may be blocked. Secondly, we need to prevent rogue calls with incorrect location. We solve the location issue using the OpenRoaming IDP-ANP signaling, and with the use of Secure Location Tag. <DL> Not my area of expertise at all so I gracefully step away 😊 </DL> Regards Sri From: dmm <[email protected]> on behalf of David Lake <[email protected]> Date: Sunday, March 26, 2023 at 7:06 PM To: "[email protected]" <[email protected]> Subject: [DMM] Emergency 911 Services over Wi-Fi Sri Thank you for the interesting presentation. I think we have two problems: 1. Network attachment 2. E911 calling via the inbuilt dialler Taking each of these in turn: 1. Network attachment. The solution with a roaming WiFi partner is good but we should also consider the ability to extend the concept of an ‘Emergency Attach’ to LTE/5GNR without the need for credentials (or with well-known credentials). This is made much more complex in the case of incoming roamers where 2G/3G has sunset – for example, if I visit the US now, I can be in a position where I get LTE/5G data service through a roaming partner but no IMS access. Many international carriers also limit ‘home’ ePDG (‘WiFi Calling’) access. 1. No matter how I attach to an IP network, I should be able to access the upper-layer application (which is essentially a SIP dialler) and make a 911 call. I can’t because the dialler currently relies on IMS registration which then takes me straight back to the issues with IMS access, IMS-to-IMS roaming, non-availability of VoWiFi (via ePDG), etc. Location SHOULD be available via GPS from the end device or from the IP path of the packets (knowing the location of the attached AP/gNB). I see 2) as the major issue to solve but I think this is a subset of the wider issue of relying on the 3GPP architecture for a voice applications. If I use a non-IMS voice application (e.g. WhatsApp, iMessage, second-number services such as Swytch, etc), then as long as I have IP connectivity, I have the ability to make an E911 call (or in fact any other call). So surely the answer is to decouple the application from the network in some manner such that it doesn’t have to make an IMS registration specifically for E911/112/999 calls but instead uses generic SIP (maybe with default/well-known credentials)? Best David Lake Tel: +44 (0)7711 736784 [Text Description automatically generated with low confidence] 5G & 6G Innovation Centres Institute for Communication Systems (ICS) University of Surrey Guildford GU2 7XH
_______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
