112 Systems

Leave a comment Posted on 112 Systems, APCO, EENA, Government Public Safety, NENA, NG911 Solutions, Non Government Organizations (NGOs), PSAP 9-1-1, PSAP NG911, Public Safety E911, Public Safety E911, 112 Systems

FIXED: Cellular E911 Location

The two biggest issues with cellular emergency services:
Text to 911 and Cellular Location Accuracy

But the question is, how can this be so in today’s ultra-modern broadband connected world?

The answer, it turns out, is simple. The Emergency services network no matter where you are located is, for the most part, an analog-based legacy infrastructure with only the ability to convey VOICE calls and no data services. Because of this simple fact, we have pigeonholed ourselves into a quagmire of isolation from the modern communications capabilities that have become commonplace and inherent in the devices nearly all of us seem to be carrying.

How do we extract ourselves from this destitute pit of captivity? The answer is quite simple. We need a rope, and it just so happens that Google has decided to provide that lifeline, with of course a brand-new acronym; AML for Advanced Mobile Location.

Currently, on the network side AML is  only deployed in Estonia and in the United Kingdon however, the functionality (which has been code-named ‘Thunderbird’) is actually embedded in every current  Android device with operating systems from Gingerbread forward. To discuss the history of Thunderbird, and how it came to be, I sat down for a Podcast with European Emergency Number Association Executive Director, and colleague of many years, Gary Machado.

Listen to the Podcast here:

Fletch:
The big story in the news is location and emergencies in cellular phones, and you guys have really come up with something that’s pretty interesting over in Europe. Tell us about AML?

Gary:
Thank you, Fletch. Yes, we came up with AML, which stands for Advanced Mobile Location, a few years ago. Actually, the idea is not ours. The Advanced Mobile Location was created in the UK in 2014 by a guy named John Medland, who works for BT 999/112 emergency services.

He basically lost faith in the EU’s ability to regulate of the sector and to contribute to the improvement of caller location in Europe, so he decided to start talking with the handset manufacturers and the mobile operators here in Europe, what in the US you call I think carriers, and he came up with a simple idea: how can we find an easy way to retrieve the location data that is in the phone that we all use everyday to order pizza, to order Uber, et cetera, and how can we take this data and deliver it to the PSAPs as easily as possible?

That’s how the project started. John led the whole project in the UK. It started slowly in 2014 with AGC, the handset manufacturer, and one mobile operator named EE, and since then, AML has been very successful. We have about 85% of locations that are below 50 meters, within 50 meters, and AML has been extended to other handset manufacturers, namely Alcatel, Sony Mobile, Samsung devices, and extended also to other mobile operators in the UK.

Fletch:
I think the big thing was when Google jumped onboard. Google saw what John had proposed doing, and basically in a nutshell, the way I explain it to people is, when the carrier, when the mobile operator looks from the network towards the handset, it’s one view, but when the handset looks out towards the world, they can see much more. It’s like looking through a peephole on a hotel room door the wrong way, right?

From the carrier side, you get a very myopic view of where that device is, but the device can take advantage of cellular, it can take advantage of GPS, it can take advantage of WiFi signals that [can be seen], not necessarily connected to, but just seen, and then all of that information together [delivers] a much more accurate resolution. One number that I saw published was 4,000 times more accurate?

Gary:
Yes. Fletch, I want to say I love the way you describe it, which is exactly correct. What happens, we actually happened to meet Google at the right time, were starting to look into the project, they were wondering on how to get this information delivered to the PSAPs, and so we actually bridged between BT in the UK, Google and ourselves and we started to have about a conference call per week, basically, and we started to progress, let’s say, the Google way, which is very fast. Yes, as you said, Google wanted to benefit from the use of their Google fused location provider and have this accurate location information we use everyday installed on all Android devices in the world. That was what they were trying to achieve. Since they saw the success of the project in the UK, which was running on Android devices already, on Android-based smartphone manufacturers, they decided to work with us and

Since they saw the success of the project in the UK, which was running on Android devices already, on Android-based smartphone manufacturers, they decided to work with us and BT to, let’s say, upgrade all the devices in the world with this accurate location. Now, where are we right now? All Android devices in the world back to Gingerbread have been upgraded with Advanced Mobile Location, so it’s in every Android phone in the world, besides a few phones that haven’t been updated because they haven’t been charged or connected to the WiFi and didn’t get the update, of course, but otherwise it’s already

Now, where are we right now? All Android devices in the world back to Gingerbread have been upgraded with Advanced Mobile Location, so it’s in every Android phone in the world, besides a few phones that haven’t been updated because they haven’t been charged or connected to the WiFi and didn’t get the update, of course, but otherwise it’s already in your phone. If you have an Android phone, AML is there. You just have to check your phone, look for the Google Play Services, and if you have a version of Google Play Services which is something like 9.0+, then you have AML in your phone. AML

You just have to check your phone, look for the Google Play Services, and if you have a version of Google Play Services which is something like 9.0+, then you have AML in your phone. AML is deployed in two countries in Europe. It is fully deployed in the UK and Estonia.

That means that everyday, UK and Estonian emergency services receive extremely accurate location information, again, 85% at below 50 meters using GPS or WiFi location, and yes, when we look at the figure, it’s about 3,000 to 4,000 times more accurate than what we get in Europe currently, which is only the primarily cell ID.

Fletch:
Before everyone runs out and turns on AML and expects this incredible accuracy to be there, there is the other side of this, and that’s the 911 center, the emergency center, the PSAP has to be able to, or the network I should say, has to be able to receive this data. One of the pieces of AML is a destination for this information to be sent, so that’s got to be in place, too. Now that’s the carrier responsibility.

Gary:
Yes. I would say the beauty of this project is its simplicity. When you dial an emergency number, 112, 911, it will trigger AML in your phone if you’re in a country where the service has been activated; in other words, where PSAPs are able to receive the information. Once you dial this number, it triggers the AML for 20 seconds, collects the location information and sends it over to the PSAPs over a mobile network.

Now there are two ways of doing that. The first way is using SMS. There are two kinds of SMSs that are used. I will not get into the specificity of those, but these two SMSs are working. One of these two can be implemented in any country. Either the message can be sent to an SMS endpoint, which is what both BT, our organization, EENA, and Google recommends, because it works in most cases, SMS, and it’s actually extremely reliable. So it can be sent to an SMS endpoint or it can be sent over HTTPS to the emergency services. Emergency services are free to choose.

In Europe, we work at the country level. [Governments] are free to choose whether they want SMS or if they want HTTPS. For now, in Europe, we have SMS installations, but other countries are deploying an HTTPS endpoint to be able to receive the AML data.

Fletch:
I’m going to assume that when you bring your handset online and you get your configuration from the carrier that this AML destination would be part of that provisioning.

Gary:
Yes. Actually, it’s managed by Google. Google defines the emergency numbers that should activate the service in a country. If a country has several emergency numbers, those numbers will trigger the AML service, which will turn on for 20 seconds and collect the location data, and then send it over to this endpoint selected by a country or a region or a county. Basically, what’s to be done by the PSAPs, the authorities and/or the mobile operator or carrier in the US, it’s very simple. Google needs to know the endpoint to be able to deliver that message. They need to be provided by an endpoint. The carrier needs to, for instance, in case of an SMS, allow it to be free of charge, and that’s what we have in most countries in Europe already with SMS for the deaf and hard of hearing, and/or they need to provide for an HTTPS endpoint to be set up, which often in the US I believe has been at the carriers rather than in the PSAPs. In Europe, we have a different setup for these things.

Fletch:
The very first thing people are going to complain about it is, “Hey, wait a second, Gary, if this thing gets turned on, Google’s going to start tracking my location. It’s bad enough that they know every website I go to and they’re putting cookies all over my phone, now they’re going to be tracking my specific locations and what I’m doing. I’ve already got the NSA in the US doing that. I don’t need Google on top of that doing the same thing.” Is there going to be pushback?

Gary:
As you can guess, we get it over here in Europe even more than in North America. People are very, very concerned about it here. I can say I have myself a certain interest for these issues. I actually help some of the privacy activist organizations here in Brussels on my private time, let’s say, and I never switch on my location on my own, for instance, but in case of emergency service, I want to have my location turned on. The beauty of this project and working with Google for more than a year, they have been extremely cautious with that. The location just turns on for the time of triggering the AML and turns off after 20 seconds. Google does not store that location. Google doesn’t want to see that location. That location is retrieved and is sent over to the PSAPs in an SMS or HTTPS, and that’s it. Google doesn’t want to see that location. I think, honestly, no one is [inaudible 00:11:05]. Google has plenty of locations everyday. I don’t think they are looking for more of that project. That’s not what they are looking for.

The location just turns on for the time of triggering the AML and turns off after 20 seconds. Google does not store that location. Google doesn’t want to see that location. That location is retrieved and is sent over to the PSAPs in an SMS or HTTPS, and that’s it. Google doesn’t want to see that location. I think, honestly, no one is [inaudible 00:11:05]. Google has plenty of locations everyday. I don’t think they are looking for more of that project. That’s not what they are looking for.

Fletch:
So they never even get the data to be able to store it. It goes directly into the public safety networks.

Gary:
Exactly.

Fletch:
Let’s face it, if you’re having an emergency, your location is something that you probably want to share. 

Gary:
Yes, exactly. That’s the case, and I’m sure it’s the same in the US, but in Europe, we have the proper legislation for that, that in case of emergency call, caller location is authorized. Yes, that’s one of the very few times where you actually need and you want your location to be used.

Fletch:
I’ve got to tell you, when I first saw this back in 2014 over in Europe, I was a little hesitant. I was a little hesitant because it was operating system-specific. At that time it was carrier-specific and even handset-specific, and [I thought], interesting idea, but it’s going to be the adoption that really makes this happen, and although it’s taken a couple of years, it is actually a great idea. It’s very simple in its form, it’s very basic. It doesn’t require a big uplift in the network. It doesn’t require huge upgrades in the PSAPs. It’s just a simple activation of information that’s already there, and it’s information that most devices already have anyway. Again, like you said before, if I want to order a pizza or if I want to order an Uber, they know exactly where I am with incredible accuracy, so it’s just activating that function that’s already there and creating the mechanism to transport that over to the PSAP, the people that actually need to use that. Really kind of a brilliant idea and John, John’s a great guy and I’ve known John for many years over at BT. It really took a lot of stamina just to keep pounding his foot down and saying, “This will work,” and getting Google in there is a big deal. Obviously the big question, what about iOS and Apple and Microsoft? What’s happening with those guys? Have they mentioned anything about this?

It’s very simple in its form, it’s very basic. It doesn’t require a big uplift in the network. It doesn’t require huge upgrades in the PSAPs. It’s just a simple activation of information that’s already there, and it’s information that most devices already have anyway. Again, like you said before, if I want to order a pizza or if I want to order an Uber, they know exactly where I am with incredible accuracy, so it’s just activating that function that’s already there and creating the mechanism to transport that over to the PSAP, the people that actually need to use that. Really kind of a brilliant idea and John, John’s a great guy and I’ve known John for many years over at BT. It really took a lot of stamina just to keep pounding his foot down and saying, “This will work,” and getting Google in there is a big deal. Obviously the big question, what about iOS and Apple and Microsoft? What’s happening with those guys? Have they mentioned anything about this?

Really kind of a brilliant idea and John is a great guy.  I’ve known him for many years over at BT. It really took a lot of pounding his foot down and saying, “This will work,” and getting Google in there is a big deal. Obviously the big question, what about iOS and Apple and Microsoft? What’s happening with those guys? Have they mentioned anything about this?

Gary:
First, I want to join you here in saying I really admire what John has done. He’s taken this idea, he’s been fighting for it. He’s been going step by step. He’s very cautious. He wanted to validate every step of the project. We owe John a lot, as all in the public safety community, I believe. I also want to thank the guys at Google, of course, and also congrats to the Estonians. The Estonians implemented AML in less than six months with Google and they are one of the countries that are fully enabled right now. About Apple and Microsoft, we are in contact with Microsoft, trying to get some information, some progress on this. At this stage, we do not see a lot, but we are hopeful that it will progress. We are also trying to get in touch with Apple. We’ve informed Apple via many emails, conference calls and so on. We haven’t seen a lot back from Apple, though we actually discovered just by Googling one day that Apple has published a patent on the location topic, which seems to be rather an idea pretty similar to what we’ve just talked about during this podcast. Very interesting. Very interesting. We’re hopeful that Apple will join the project. We also started to see the first articles, one article in Estonia last week, clearly explain that they believe that Apple will start joining the

We haven’t seen a lot back from Apple, though we actually discovered just by Googling one day that Apple has published a patent on the location topic, which seems to be rather an idea pretty similar to what we’ve just talked about during this podcast. Very interesting. Very interesting. We’re hopeful that Apple will join the project. We also started to see the first articles, one article in Estonia last week, clearly explain that they believe that Apple will start joining the project, because people will think of Google’s Android phone as the safe phones. That was an opinion written in an Estonian article, which is in English.

Fletch:
I have to agree with that. If somebody’s going to make a telephone purchase and this one has got safety features that this one does not, that’s going to become a decision. If I’m going to buy a phone for my daughter who’s going off to college now, I’m going to make sure she’s got a phone that’s going to provide her with as much safety as possible. That’s going to bring the financial model into play and it’s not going to be long before somebody over in Cupertino says, “Hey, wait a second, sales are going down. We need to turn this on,” and Microsoft’s going to do the same.

Gary:
Let’s hope so. Apple Keynote is coming out soon, so, let’s wait.

Fletch:
Listen, Gary, it’s always a pleasure to talk to you. It’s been a while since we’ve chatted. I really appreciate you taking the time to talk about this. Tremendous progress on this. Congratulations to everybody over at EENA who drove this, and of course to John Medland over at BT, who had the brainchild and the fortitude to get this program moving.

Gary:
Thanks, Fletch. Bye-bye.

Leave a comment Posted on 112 Systems, EENA, Government Public Safety, Non Government Organizations (NGOs), Public Safety E911, 112 Systems

999 – The history of the ‘Hooter’

For and AUDIO version of my Blog – Check it out here on SoundCloud:

While the digits 9-1-1 win the popularity contest for the most popular emergency service globally, the very first emergency number ever to be put into circulation was ‘across the pond’ in London on June 30, 1937, by British Telecom.

As is typically the case it, the need for the service was inspired by a disaster involving to tragic loss of several lives. In November of 1935, five women died during a fire on Wimpole Street. As the story goes, neighbors who saw the fire, tried desparately to report it by dialing zero and asking the operator for the fire services. This method for summoning the fire department had been the long standard practice since 1927. Unfortunately, on this particular occasion, the telephone operator switchboard had been particularly jammed with non-emergency calls; therefore the emergency callers were unable to get through to report the emergency.

General-post-office-logoThe General Post Office, who at the time ran the telephone network in London, decided that a new, easy to remember three-digit number was needed, allowing citizens to reach emergency services quickly. Ensuring calls received the appropriate level of priority by BT operators; an alert signal would be triggered indicating the emergency call. Using the latest technology available in the late 1930’s, a flashing light accompanied by an audio device -dubbed as a “Hooter”.

I’ll give you all a moment to recover from your snickering – All done? Great, then let’s continue with today’s history lesson.

The trigger for the lights and their accompanying Hooter was the number 9-9-9. If you are a tech history geek like myself and are interested in the full story behind choosing 999 as the number, Gary Holland from the BBC wrote an interesting article on this very topic telling the entire story.

Logo_112_20100929Currently, across the European Union member states, 112 is recognized as the official emergency number, and along with 911 are recommended by the IETF as the preferred primary emergency numbers. Despite 112 being in place, in most places, the historical and legacy numbers continue to operate. According to EENA the European Emergency Number Association, technology is not always the primary concern. The most troubling hindrance is the lack of knowledge by citizens. Even though 112 has been the EU-wide emergency number for some time, according to recent surveys, only single-digit percentage growths have been seen over the past several years with three out of four European citizens still not aware that they can dial 112 all over Europe.

PBX or MLTS administrators, when addressing their emergency call dialing, should examine their user base and understand the need to support additional emergency numbers. 911 and 9-911 are distinct entries in your emergency dialing tables, but if you find that you have a large employee base that includes folks from Europe, it would be wise or to provision 112 and 9-112 or 999 and 9-999 as valid dialing patterns in the PBX as well. Just make sure that you translate anything that is not 911 to the digits 911 as today’s landline carrier networks are likely not provisioned to recognize emergency numbers beyond 911.

Oddly enough, this isn’t the case on most cellular networks today. In fact, not only does my iPhone understand 911 is an emergency number, others such as 112, 999, 000, 114 and 118, and likely several others, are treated the same. Dialing any of these will put the device into “emergency mode”, invoking functionality or disabling others as defined by the carrier profile. The phone never actually ‘dials’ anything, it merely indicates to the network that the user is making an emergency call. This mechanism is how multiple numbers are all supported and translated to the proper emergency service in the country where you are located.

In turn, the network then connects me as if I had dialed 911, or the appropriate local emergency number, directly.

DISCLAIMER: 
PLEASE TAKE MY WORD ON THIS, AND TRUST ME THAT THIS WORKS.
DO NOT TRY TO TEST THIS YOURSELF. YOU’LL SIMPLY TIE UP EMERGENCY LINES WITH NON-EMERGENCY TRAFFIC, PUTTING LIVES AT RISK. THE 9-1-1 OPERATOR WILL NOT SEE ANYTHING DIFFERENT THAN IF YOU DIAL 9-1-1, THE NORMAL EMERGENCY NUMBER, OR EVEN KNOW THAT YOU HAVE DIALED ANYTHING DIFFERENTLY.

As we move forward with new communication technologies and modalities, SIP will be the primary protocol used for transport. Based on this, phone numbers will become less and less relevant, and an endpoint or destination name will replace it. My identity, and how to reach me will shift from 908-848-2602 to something more like my email address FletcherM@Avaya.com. Which is another reason why routing emergency calls based on telephone numbers is an archaic construct that does not fit the next generation 911 model, and we must STOP relying on phone numbers as a location cross-reference.

While the people that manage those databases have the financial incentive to keep customers locked into this irrelevant technology, maintaining phone number to location correlation, there’s far too much automation, complexity, and expense associated with that to remain as the right way forward.

Emergency services need to be able to migrate to simply “SOS” as an emergency destination address, and location information needs to be conveyed in the PIDF-LO location object in the SIP header. If the financial model has to change for some providers, then so be it; these folks must learn to adapt, or cease their operations. We are talking about life safety services, and profits need to be put on the back burner. While there is nothing wrong with cost recovery of sensible technology, 9-1-1 is not a license to steal.

1 Comment Posted on 112 Systems, APCO, NG911 Solutions, Non Government Organizations (NGOs), PSAP 9-1-1, PSAP NG911, Public Safety E911, Public Safety E911, 112 Systems

Predictive Assistance via Caller Context

A concern that can exist in nearly any city, county, state, or even country, is that once an easy to remember emergency number, such as 911 in the US, 112 across the European Union, and the 999 available in the UK, has been deployed, massive misuse of the system by non-emergency calls starts to put strain on the network; equipment and even staff must now cope with the increase of non-emergency citizen outreach beyond the purpose of the service. Because there isn’t a catchall category of call types, there often isn’t a single, all-encompassing solution to the problem. Technology can help and when properly deployed, is capable of providing support for dealing with many of the strains that are put on Emergency Networks and Systems.

The Architecture Problem:

 

BLOG-PO-Pic1

Fig. 1 Silos of Call Types for Public Safety and Citizen Services

 

In the past, when we built and designed Public Safety networks, the solutions were siloed, purpose built creating disparate, disconnected islands of connectivity. An agency decided what their inbound traffic would be for that particular service, and then engineer the incoming trunks for a P.01 grade of service, meaning that 1 out of every 100 calls could be blocked during the busy hour. This is a standard level that is accepted by the Public Safety industry for Public Safety Answer Points.

But this creates a problem when a service (9-1-1 for example) receives more calls than expected. Typically, they would track analytics and call volume reports that displayed trend information. These reports guided them on the increase of the number of positions and trunks to handle the new projected call loads. You would think that expansion should not be a problem for agencies, as they are tasked with providing service to a geographic area, and when the population increases, call volumes increase and budgets should naturally increase.

Unfortunately, however, quite often population increases along with call volume, but agencies are always being asked (read demanded) to do more with less.

BLOG-PO-Pic2

Fig. 2 Interagency trunking disrupts traffic engineering formulas

While other organizations may be able to aide with the call volume, the problem of citizens dialing 9-1-1 for everything and anything still exists. Because the network was built as independent islands of service, virtual inter-agency barriers naturally evolved. In specific cases, inter-departmental trunking can be created that allows adjacent agencies to transfer calls over those facilities directly. Now the caller is communicating with the right resource that can assist them, and we have freed up the original 9-1-1 resource to allow them to take another call, but we create another problem on the back end.

 

BLOG-PO-Pic3

Fig. 3 – Emergency Services IP Network (ESInet)

Although the issue of routing is solved, the problem still exists where the limited trunking that connects the 9-1-1 center to the PSTN remains an issue and another blockage point. This blockage is easily corrected. By removing these trunks from the equation, and replacing or augmenting them with an IP pipe that is dynamically expanded and contracted as needed, based on the application of rules logic that takes into consideration the number of available 9-1-1 call takers that are currently available and ready to take calls.

 

While I realize that every Public Safety person who is reading this just got a chill up their spine, and muttered, “Your CRAZY Fletch”, this is what needs to happen to solve the problem, and is not new bleeding edge technology. in fact, local carriers have been offering SIP-based trunking to the commercial market for years. The technology has been refined and the largest contact centers in the world use this architecture to bring calls into their network, where they decide the best resource to apply to the inbound call.

BLOG-PO-Pic4With the right tools on the right network, solving these type of problems becomes simpler and a routine process in the contact center, and there is no reason why this technology and thought process cannot be applied to Public Safety Answer Points to assist in improving efficiency and reliability during large-scale national disasters. At the same time, this can also radically improve service to callers. For example, meet Ava. Ava requires 911 services on a regular basis. She is considered to be, what Public Safety has nicknamed, a ‘Frequent Flyer.’
This term is not meant to be derogatory, in fact, Ava has a medical condition that requires Emergency Transportation much more often that the average citizen, but her condition is not life-threatening.

When Ava calls 9-1-1 for medical transport, most of the time, resources are available and dispatched immediately. But on occasion, Ava’s request arrives in the middle of complete chaos. Because the 9-1-1 network is unable to differentiate Ava’s call from any other call being processed by the system, all calls are treated with the same priority level, despite the vast prior history and information that may be available. By collecting and examining this information in a context store, and associating it with a particular call event can dynamically apply specialized call handling. Simply by knowing that Ava is a frequent flyer caller, and her condition is not life-threatening, her call is answered by a Speech Recognition enabled IVR that collects the relevant information giving Ava the opportunity to escalate the call to a call taker.

N11 – More than just Emergencies

9-1-1 has been called the most widely recognized ‘brand element’ in the world. Nearly everyone is aware of the number, and despite the attempt to increase awareness of other avenues of access, 9-1-1 remains to be the winner. Unbeknownst to many in the US, several other N-1-1 services are available to citizens. In most of the cases, these are geographically routed the same way 9-1-1 emergency calls are routed to centers that are close to the caller. Following the N-1-1 format, these easy to remember numbers are as follows:

2-1-1  Reserved for the World Health Organization and Red Cross
3-1-1  Reserved for local government non-emergency services
4-1-1  Not officially reserved, but often used for local Telco information
5-1-1  Reserved for Highway and Traffic information systems
6-1-1  Not officially reserved, but often used for local Telco repair
7-1-1  TDD Relay services for Deaf, Hard of Hearing or Disability
8-1-1  Reserved for the Call before You Dig utility mark-out hotline

While these services can often provide valuable information to citizens, they are often under-publicized, and under-utilized. By consolidating connectivity in the cloud, we gain flexibility in dynamically adjusting the trunking required, and calls destined for other agency remediation. This can effectively eliminate the public education and awareness problem. While the dialed number can be an indicator of the nature of the request, calls can still be handled efficiently, and resources are no longer limited and blocked.

Proactive Citizen Outreach

When a known issue exists, reaching out to the public in an affected area can be an efficient and dynamic countermeasure that can significantly reduce the number of inquiries for more information while reassuring concerned citizens that an issue is being addressed. In addition to providing information, a query can be made to ensure no other problems exist. If the citizen does have an additional concern, the system is already ‘context aware’ of the identity of the citizen, and they can be queued up against the appropriate resource. Upon connection to the person or agency that can provide the additional information they need, information about the previous interaction can be displayed to the call taker, facilitating quicker response and better service levels.

Follow me on Twitter @Fletch911
Read my other AVAYA CONNECTED Blogs

 

Mark J. Fletcher, ENP is the Chief Architect for Worldwide Public Safety Solutions at Avaya. As a seasoned professional with nearly 30 years of service, he directs the strategic roadmap for Next Generation Emergency Services in both the Enterprise and Government portfolios at Avaya. In 2014, Fletcher was made a member of the NENA Institute Board in the US, in 2014 – 2015 he served as co-chair of the EENA NG112 Committee in the European Union, providing valuable insight to State and Federal legislators globally driving forward both innovation and compliance.

Leave a comment Posted on 112 Systems, Government Public Safety, GUEST BLOGS, NG911 Solutions, Public Safety E911, Public Safety E911, 112 Systems

Breaker 911: 50-Year Old Technology Saves Lives

You can never know where technology will rear its head. Most of the time it is based on the future, but many times it can be based on our past. This week, I proudly turn my blog over to Professor Ima Pharceur, PhD. Professor Pharceur is the noted Chief Research Scientist at the world-class Social Media Communications and Information Sharing Institute of Technology (SMCISIT for short) in Brussels, Belgium.

 

Next Generation Citizen Band Emergency Services

There is no doubt that Social Media is deeply embedded in our daily lives today, however, it’s roots can be traced back to a Social Media craze that was popular 4 decades ago in the mid-70’s. Millions of people all over the country, and the world installed small, low powered two-way radio transmitters in their cars to talk to each other, converse with over the road truckers, and report emergencies to teams of dedicated people and police agencies monitoring CB Channel ‘9’, the official Emergency Hailing Frequency for the Citizen Band Radio Communications and Information Radio Relay System, or CBRCIRRS for short.

The Federal Communications Commission established Citizen Band Radios as a core system of low powered short-distance radio communications between endpoints on the same channel within the possible 40 channels that all exist in the 27 MHz (11 m) band.

This frequency range is distinct and separate from the existing Family Radio System (FRS), General Mobile Radio System (GMRS), Multi Use Radio System (MURS), and Amateur Radio Service commonly known as “ham” radio systems.

Unlike it’s more powerful cousins the Ham Radio, operation often does not require a license, and it may be used for both business or personal communications, and refrigeration is not required as with most Ham products. Since the frequencies, better known as channels, are open in nature, any user can share the channel in a simplex type of operation. This means that while one station transmits; other stations listen and wait for the channel to be available.

Initially, 23 channels were assigned by the FCC, however due to popularity in the late 70’s and 80’s, a massive increase in use was seen, and the FCC allocated and additional 17 frequencies, bringing the total to 40. To remain backward compatible with radios already in place, Channel ‘9’ remained as the designated emergency channel.

Today, with Next Generation Emergency Services on the cusp of deployment across the US, and with 3.5 Million professional truckers on the road in the US, that is potentially 14 Million individual eyes or ears that are keeping watch over every quarter square mile if distributed evenly.

CB-911-CircuitWith most radios in use today being digital in nature, the addition of a new additional channel, specifically designed for NG911 usage is a simple low-cost addition to nearly any radio transmitter. In an effort not to ‘step on’ existing communities and their usage of the existing public airways, this new technology, patented by the SMC Institute, uses a new Bi-Polar Wave Guide Induction Ionosphere Relay Circuit or B-PWIIRC for short, to create a new dynamic frequency waveguide that is capable of transmitting information at speeds equaling 100 Gbs, which is perfect for voice, video, text, email, IM, Internet Relay Chat, TTY-TDD, and Morse Code, making it 100% backwards compatible with technology.

200px-CrazyeddieThis very well may be the thing that brings corporations like RadioShack and Syosset, NY-based Lafayette Electronics back into business, and there are rumors that the estate of ‘Crazy’ Eddie Antar is interested in setting up mobile sales venues in Truck Stops and Shopping Malls across the northeast.

Next Generation Emergency Services expert Mark J. Fletcher, ENP from Avaya was quoted as saying, “I’ve run the numbers myself, and what they are claiming seems to work out, mathematically speaking. Obviously, rigorous interoperability testing will be required.” Fletcher added that he see’s several uses for the product, like summoning local drones and passing truckers to emergent events, because they “usually carry band-aids, and many times are armed.”

The system is only compatible with 911 solutions today, but being digitally based, there are already models on the drawing board for 112 and 999 solutions in the UK and Europe. With the 3D printing capabilities that exist now, anything that is on the drawing board is a real possibility.

 

Thanks to Doctor Pharceur for his tireless work on this topic, and I hope that he keeps the hammer down, and things are clean and green as he brings this technology to fruition. Happy April 1st everyone!

Follow me on Twitter @Fletch911
Read my other AVAYA CONNECTED Blogs

Mark J. Fletcher, ENP is the Chief Architect for Worldwide Public Safety Solutions at Avaya. As a seasoned professional with nearly 30 years of service, he directs the strategic roadmap for Next Generation Emergency Services in both the Enterprise and Government portfolios at Avaya. In 2014, Fletcher was made a member of the NENA Institute Board in the US, in 2014 – 2015 he served as co-chair of the EENA NG112 Committee in the European Union, providing valuable insight to State and Federal legislators globally driving forward both innovation and compliance.

Leave a comment Posted on 112 Systems, APCO, EENA, Government Public Safety, NENA, NG911 Solutions, PSAP NG911, Public Safety E911, Public Safety E911, 112 Systems

Solution? Or Knee-Jerk Reaction?

FOR THE PODCAST AUDIO OF THIS BLOG: Get it on SoundCloud:

Emergency services in India have evolved over the years. But instead of consolidating access numbers, the decision was made to implement different numbers for everything. At the 9-1-1 Goes to Washington event in March of 2014, FCC Commissioner Ajit Pai  referred to this problem during his address to the Public Safety community.

“We in the United States often take our 911 system for granted. But my recent trip to India reminded me how fortunate we are. In India, there isn’t a single number that people can call for help. There’s one number to reach the police, another for the fire department, and yet another if you need an ambulance. There are even different numbers for senior citizens, women, and children to use. I learned that many Indian households have a long list of numbers stuck on their walls and refrigerator doors to remind them which number to call for which emergency. All of this leads to needless confusion and delayed response times.”

FCC Commissioner Ajit Pai

In an effort to solve this problem of confusion, a recent initiative has been initiated by India’s Women & Child Development Minister, Maneka Gandhi. After much discussion about how to solve the issues, the idea of ‘pressing and holding the 9 button’ on cell phones was given the go ahead in a recent meeting of representatives from the various service providers as well as mobile phone manufacturers. Apps were discussed, but dismissed, based on the same reasons they have not been effective elsewhere in the world.

[I]t does raise a few concerns . . .

For an App to be useful, it has to be used, the device must have it installed, and it has to be current and active. Unfortunately, we do not have the luxury of  this level of planning, before we have an emergency. Additionally, pressing ‘9’ on an older analog cellular phone could effectively be implemented at the carrier level, and not exclude these devices, which are prominent in many parts of the India suburban areas.

While I have to commend the essential simplicity of this action, it does raise a few concerns that may not have been completely vetted, and may actually have some unintended negative impact. Unfortunately, the source article did not contain enough information detailing how long the ‘long press’ needed to be to activate the function.  This leads to several questions, including:

  • How exactly long is a long press?
  • Can it be canceled?
  • What will multiple rapid presses do?
  • Pocket Dialing is a huge problem. How many misdial events will this potentially generate having a negative impact on public safety resources that are already running paper thin on staff and budget?

Without a study being done on the misdial call load on PSAPs alone (something that can be tracked measured) it appears this solution may be a ‘knee-jerk’ reaction to a problem, and has the possibility of making the situation worse by impacting public safety.

“Any Device, Any Time, Any Where . . .

Another point to consider is the potential confusion that this may cause to citizens. Clearly, 911, 112, and 999 are well-known emergency access numbers globally. They all have been promoting the concept of  “Anywhere, Anytime, and on Any device” for more than a decade.

While this addresses mobile phones, it is likely the ‘long press’ of 9 on telephone devices that are NOT cell phones could be difficult, if not impossible to reproduce or replicate. This would then eliminate the universality of access to emergency services we currently enjoy today.

The IETF states that the numbers for emergency services globally should be 911, and 112.

After 2 years of fighting the policy battle in the US, we are just beginning to win the “No 9 Needed” battle with MLTS PBX systems. This initiative, know best under the name ‘Kari’s Law’,  requires MLTS Systems to recognize just the digits 911, 112 and 999 as emergency numbers; effectively eliminating the “9” normally needed to get an outside line. The popular tagline for Kari’s law is “No 9 Needed”, but now we need to modify this message to be “Except in India where you just press 9”? Hank Hunt may have a comment or 2 on that.

The IETF states that the numbers for emergency services globally should be 911, and 112. In the UK, 999 has been locally engrained, and although attempts and suggestions have been made over the years to change it, history will live on, and the best that we will see is support for 911 and 112 in the local PSTN, and 999 will continue to live on in perpetuity.

Clearly the problem will continue, but it is good that people are looking to solve the issues. I would highly recommend to the Ministers of India take into consideration the expertise contained in organizations like NENA, EENA, and APCO International are consulted before potentially life-changing decisions like this are made under a great emotional influence, and without completely vetting the technical and social impact of the decision.

Follow me on Twitter @Fletch911

Read my other AVAYA CONNECTED Blogs

Mark J. Fletcher, ENP is the Chief Architect for Worldwide Public Safety Solutions at Avaya. As a seasoned professional with nearly 30 years of service, he provides the strategic roadmap and direction of Next Generation Emergency Services in both the Enterprise and Government portfolios at Avaya. In 2014, Fletcher was made a member of the NENA Institute Board in the US, and is an active participant in EENA where he provides insight to State and Federal legislators globally driving forward best practices in both innovation and compliance.

Leave a comment Posted on 112 Systems, Enterprise 9-1-1, Public Safety E911

HELP! Operator! Gimme the number for 911!

Homer-911

True, it’s funny when Homer says it, but in many places around the world that actually may be a valid question. We talk about the first 911 call in the United States taking place on February 16, 1969 in Haleyville Alabama. But we need to look back even further to find the very first emergency call ever made, with the exception of Alexander Graham Bell calling for Watson when he spills battery acid on himself, as the story goes.

As typically the case, it was a disaster when lives were lost; 1935 five women died during the fire in Wimpole Street in London. Apparently neighbors, who had to dial zero and ask the operator for police fire or ambulance, found that the telephone operator switchboard had been jammed with calls, and weren’t able to get through.

The General Post Office, which ran the telephone network in London, decided that a new three digit number could be used to reach emergency services. Additionally, it would be able to trigger specialized alerting that would indicate to the operators the presence of an emergency call. The alerting was accomplished by flashing lights and an audio device called a “Hooter”. I’ll give you all a second to finish your childish snickering. All done? Great. The number chosen was 999, and if you want the reasoning behind that there is a great article by the BBC that tells the entire story.

Currently, across the European Union member states, 112 is typically recognized as the official emergency number. Although in most places the legacy numbers are also recognized. One of the problems Europeans experience, according to the European Emergency Number Association (EENA), is the lack of knowledge of 112 as the EU wide emergency number according to recent surveys. Only single-digit percentage growths have been seen over the past five years with three out of four European citizens still not aware that they can dial 112 all over Europe.

This past month at an International Telecommunications Union (ITU) conference on UN telecommunications regulations in Dubai, 193 nations committed to decide between either 911 or 112 as a standard global emergency number for new generations of mobile phones and other devices. If you’re going to go that far, and actually state one or the other, then, in my opinion, it only makes sense to support both.

Let’s face it, we’ve invested so much in our 911 education in North America, that it would just be counterproductive to “change” the designated emergency number. The same holds true in the European Union where 112 has been highlighted. Even adding in 999, popular in London and the United Kingdom, would limit the list to three, something certainly manageable at most levels.

PBX or MLTS administrators, in addition to remediating their 911 dialing, should examine their user base and understand the need to support additional emergency numbers. 911 and 9-911 are obvious entries in your emergency dialing tables, but if you find that you have a large employee base that includes folks from Europe, it would be wise or to provision 112 and 9-112 or 999 and 9-999 as valid dialing patterns in the PBX. Just make sure that you translate anything that is not 911 to the digits 911 as today’s carrier networks are probably not provisioned to recognize 112 or 999 as emergency numbers.

Oddly enough, this isn’t the case on most cellular networks today. In fact, not only does my iPhone recognize 112 as an emergency number, putting the device in “emergency mode”, it translates the 112 numbers to 911, where the network then connects me as if I had dialed 911 myself.

DISCLAIMER: PLEASE TAKE MY WORD ON THIS, AND DO NOT TRY THIS AS A TEST. YOU’LL SIMPLY TIE UP EMERGENCY LINES WITH NONEMERGENCY TRAFFIC, PUTTING ADDITIONAL LIVES AT RISK.

As we move forward with new communication technologies and modalities, SIP will be the primary protocol used for transport. Based on this, phone numbers will become less and less relevant, and an endpoint or destination name will replace it. My identity, and how to reach me will shift from 908-848-2602 to something more like my email address FletcherM@Avaya.com. Which is another reason why routing emergency calls based on telephone numbers is an archaic architecture that does not fit the next generation 911 model, and we have to STOP relying on phone numbers as location references. In order to maintain phone number to location correlation, there’s far too much automation, complexity, and expense associated with that. Moving forward, based on this thinking, emergency services will be able to migrate to simply “SOS” as an emergency destination address, and location information will be conveyed in the PIDF-LO location object in the SIP header.

Once that problem is solved, Homer can start working on a real problem:

I like to take this opportunity to wish all of you a safe, happy and healthy holiday of your choice. I greatly appreciate your support, and interest in fixing the emergency number problems in your MLTS/PBX systems, as well as those of you in the 911 industry itself, I would like to thank you for all that you do. Although I’m not a 911 “frequent-flier”, I’ve had enough incidents over the past couple years to personally appreciate the personal sacrifices you make and the dedication you give to your jobs.

Next week I’ll be taking off for the holidays, but, I’ll go through the 120 podcast and special reports, and post the most popular episode over the past two years.

We’ll see you back live on Friday, December 28 where will do a 2012 year-end wrap-up. Until then, take care, enjoy your families, and once again have a safe and happy holiday.

Follow me on Twitter @Fletch911

Read my other AVAYA CONNECTED Blogs

Mark J. Fletcher, ENP is the Chief Architect for Worldwide Public Safety Solutions at Avaya. As a seasoned professional with nearly 30 years of service, he provides the strategic roadmap and direction of Next Generation Emergency Services in both the Enterprise and Government portfolios at Avaya. In 2014, Fletcher was made a member of the NENA Institute Board in the US, and co-chair of the EENA NG112 Committee in the EU, where he provides insight to State and Federal legislators globally driving forward both innovation and compliance.