AUSTIN, Texas, Sept. 16, 2020 /PRNewswire/ -- RapidDeploy, the industry's only truly open and integrated emergency response platform, announced today that the company will directly integrate supplemental emergency data from some of the largest and most influential...

By Brian Crawford, FirstNet Authority Board Member
As our country faces challenges during the COVID-19 pandemic, first responders continue to answer the call to protect our communities while experiencing a unique set of challenges of their own. I am a 30-year fire service veteran and the former City Manager of Shreveport, LA. I know that in times of need, we rely on readily available technologies that give us what we need, when we need it. For the first time in the history of this country, first responders have access to a network designed specifically to keep them connected as they serve and protect communities. And that connection is now, more than ever, critical. READ MORE

About 4.9-GHz Spectrum
The 4.9-GHz band is 50 MHz of spectrum that was allocated to public safety in 2002 on the heels of the 9/11 attacks. This spectrum was set aside by the FCC Commissioners at the time to improve public-safety communications and address one of the major issues described in the 9/11 Commission Report. More than a year later, vendors were able to build WiFi-like equipment capable of operating in this band. 
Starting in 2018, the FCC issued a series of Notices of Proposed Rulemaking (NPRM) claiming this spectrum was underutilized and announcing its intention to license other types of users in the same spectrum. The public-safety community responded to each and every subsequent NPRM by asserting that preserving the 4.9-GHz spectrum for public-safety-use-only is still the highest and best use of the spectrum. 
After the FCC issued a sixth NPRM without taking any action, the public-safety community once again responded with its comments, again affirming that public safety needs the spectrum for its communications requirements and still the FCC did not take action. 
Why Is There a Rush Now? 
A few months ago, a number of public-safety professionals, most of whom were directly involved in the creation of the Nationwide Public Safety Broadband Network (NPSBN) known as FirstNet, formed the Public Safety Spectrum Alliance (thepssa.org). They immediately began working with public-safety organizations and the FCC in an effort to convince the FCC Commissioners that, once again, the highest and best use for this 50 MHz of spectrum is for it to remain with the public-safety community. 
Soon after the PSSA was founded and began its campaign, the FCC Chairman stated in a blog that he would introduce a rulemaking at the FCC’s open Commission meeting at the end of September (this month). This rulemaking, which is now public and has been reviewed by many, does not include anything taken from the multitude of comments the FCC received during the first six notices of proposed rulemaking. In a total departure, the Chairman is now proposing that the Commission vote on a rulemaking that would assign this spectrum to each state and allow each state to lease the spectrum to a master lease-holder. This lease-holder would then control how the spectrum will be used moving forward.
This new rulemaking does not provide for any new public-safety use of 4.9-GHz spectrum and it leaves use decisions up to each master spectrum lease-holder in each state. While some states might recognize the importance of this spectrum for public safety, others might see this as a revenue opportunity, lease the spectrum, and not worry about who will use it for what purposes.  
Why Now?
I have to wonder what the FCC is trying to do at this month’s FCC open meeting. At this time, the public-safety community is heavily engaged in protecting us on many different fronts including the Covid-19 pandemic, horrendous wildfires, an abnormal number of hurricanes, and civil unrest with rioting and looting. Yet this month, the FCC intends to make matters even more difficult for public safety by taking away roughly 50 MHz of spectrum it has been using since 2002. What is the rush to take back spectrum that is needed today and, more importantly, that will be needed to accommodate wireless technology advances tomorrow? Why now when so many issues threaten to overwhelm the first-responder community? Why now when public safety is facing difficult challenges on multiple fronts? #Whatstherush? 
Wireless technology is advancing quickly and radio spectrum is tough to come by. Public safety cannot afford to lose any of its spectrum. When it needed new spectrum for a nationwide public-safety broadband network, it took almost ten years of working with Congress, the FCC, and the Executive Branch to finally acquire spectrum for FirstNet, today’s broadband network dedicated to first responders. The outlook for adding more spectrum is poor, even as the public-safety need for expanded communications continues to grow. 
Public safety is already being pushed to its limits. Why did today’s FCC decide to take spectrum away from the community charged with protecting life and property during the many crises we are facing? The FCC will vote on the 4.9-GHz take-back and reallocation on September 30, 2020. Why now? Why can’t this wait? What is the sudden urgency?
Public safety needs your support today! Let the FCC Commissioners know this matter does not have to be decided today and if they proceed, their action will greatly diminish our ability to provide our public-safety professionals with the best possible communications capabilities now and into the future. 
Andrew M. Seybold©2020, Andrew Seybold, Inc.

A number of committees are working toward solving both the Land Mobile Radio (LMR)/LTE Push-To-Talk (PTT) interoperability issues and LTE/LTE PTT interoperability issues. Meanwhile, the 3GPP standards body is crafting 3GPP TS 23.283, Mission-Critical Communication Interworking with Land Mobile Radio Systems, or the Interworking Function (IWF). The IWF is to be the interface that will provide solid interoperability between Mission-Critical Push-To-Talk (MCPTT) and LMR networks.
IWF specifications are intended to support a broad range of LMR technologies, effectively allowing MCPTT to interoperate with most of today’s LMR systems. Sounds good, however, in practice it will be an extremely complex implementation, beyond that of any interoperable systems in use today. There are no IWF implementations in existence at this time, which makes sense since there are no fully-compliant MCPTT systems in existence. Some Over-The-Top (OTT) broadband push-to-talk systems including Motorola and ESChat are successfully deploying P25 interoperability via Inter-RF Subsystem Interface (ISSI). Motorola has also introduced Critical Connect, a subscription-based (SaaS) interoperability hub that will connect Motorola’s LMR and LTE PTT solutions.
Implementing the IWF will be a massive task, which we assume will be offered in an SaaS model as well, similar to Motorola’s offering. The IWF will be managed by the wireless carrier, which also represents numerous risks. This is foreign ground for any wireless carrier, and one must question whether they really want to be (or should be) in this position. Fulfilling the IWF will be a task larger than implementing MCPTT itself. 
Even though IWF specifications have been released, so far, no company I know of has deployed the IWF interface. It also appears that while designed to solve MCPTT to P25 and Tetra interface issues, IWF does not address other issues, and addresses still others with limited functionality. This includes the large number of analog FM LMR systems still in use in the United States and it is not clear if IWF requires ISSI as a P25 interface, which can cost an agency anywhere from $40K to more than $500K depending on the vendor. I am hearing that several vendors either have contracts to start implementing IWF or have actually begun an implementation. I, for one, don’t know if IWF, if it existed today, would truly resolve the interoperability issues that are before us.
Remember, the goal, at least as I see it, is to enable LMR and FirstNet/LTE networks to pass push-to-talk traffic between an LMR network and the FirstNet/LTE network. This is a very important goal and one that, as far as I am concerned, is taking far too long to accomplish. We should already be in a position to connect every public-safety LMR network to FirstNet in both directions. However, this is only one part of the equation and it is needed now, not years into the future. In an ideal world, all of the different PTT vendors’ offerings that are available on FirstNet should be able to interoperate with all the others. 
Some technologists say once Mission-Critical Push-To-Talk becomes the standard of the land, other PTT venders will simply fold their tents and go away. This is not realistic. Today, existing FirstNet-approved PTT vendors already have a huge share of the available market and I, as well as others, don’t see every agency on FirstNet simply moving over to a different PTT platform. Further, until 100-percent of the public-safety agencies are using FirstNet (a goal that may never be fully realized), MCPTT will not handle cross-network communications. However, several vendors with over-the-top PTT products do. PTT works well on FirstNet and all of the vendors that have FirstNet-approved products provide very fast and functional PTT services. Some interoperate with several of the others, and every vendor, so far, has been able to provide cross-LMR/FirstNet connectivity in one form or another. 
Where We Are Today
IWF is not a reality but it is being developed. Once it is available, it will still have to pass muster to determine whether it actually meets the needs of the public-safety community. 
FirstNet has announced Mission-Critical PTT and it is becoming available. I consider today’s version to be the foundation of what MCPTT can become over time once it can compete with PTT applications already in the market and when it is capable of interoperating with LMR PTT systems. 
There are seven certified PTT platforms currently running on FirstNet; three are fully interoperable and others could be interoperable if there was a desire by the vendor to make that happen.
Some technologists and pundits are still trying to push public safety to a FirstNet-only environment (please note that even FirstNet (Built with AT&T) is not among them). However, they continue to miss the fact that LMR supports off-network communications and while MCPTT does provide support, it is not in a way that would be of any use to the public-safety community.
Still other technologies and pundits are fond of saying we will reach full PTT interoperability in the future. Perhaps this is true, but I have to ask, “Why do we have to wait for the future?”
We have the brightest and best wireless engineers anywhere in the world, vendors that can build devices purposefully for public safety that are also attractive to the general public, and vendors busy building FirstNet and LMR into one device. What we don’t have is a standard, and some people say we should wait for one. I like to reference Scott McNealy, one of the founders of Sun Microsystems (now owned by Oracle). Scott and his folks built great machines and a great operating system. Oftentimes, he was called out for not building to “standards,” and his comeback was, “A standard is ONLY a standard when people use it!” 
Where We Need to Be
Things are moving fast in the world of technology. It took more than ten long, hard years for what is now known as FirstNet to be passed into law, another five years before a contract was awarded to build and operate the FirstNet network, and today, three years later, we still have not solved the most critical interoperability issue facing public safety. Push-to-talk is and will remain the most important method of communications used by public safety. Data, video, text, and other forms of transmissions that are enabled by FirstNet add to the total scope of communications for public safety, but at the end of the day, PTT over LMR and over FirstNet is the fastest and most important method of communications in the field. 
I have been participating in two committees from two different organizations. Both of these fully understand the importance of communications for the first-responder community, but the work drags on and on. Once a report is completed, it will have to be turned over to a standards body to wrestle into a standard or it will have to be embraced by The FirstNet Authority and the Public-Safety Advisory Committee (PSAC), then moved forward. Perhaps I am being too impatient, but I wonder why we have not yet addressed this issue and fixed it when it is clear that voice in the form of push-to-talk is the most important feature of public-safety communications and agencies using different flavors of PTT cannot communicate with each other.
Why do we have to wait for a “standard” passed by a body made up of mostly commercial broadband providers (networks and vendors) and a few public-safety types? When a standard was passed, why wasn’t work begun? Several vendors will follow a standard and most likely add some “neat” features, but will they really fix the LMR-to-FirstNet/LTE and FirstNet-to-FirstNet interoperability issues? If IWF won’t truly meet the needs of the public-safety community, where will we go from there and how much longer will it take? Or if one flavor of IWF meets the needs of the public-safety community but it has been implemented in several different ways, how do we identify the best way to provide true interoperability?
The good news is that I recently learned about several organizations (companies) that are working on different approaches to solve these interoperability issues. One thing they have in common is that they are not looking for only MCPTT-compliant (on-network) solutions. The are looking for approaches that take into consideration that there are and will continue to be several types of PTT on an agency’s premises, on-network, and in the cloud, as they work on ways to once and for all solve the interoperability issues and deliver a solution that works but is not years away.
As FirstNet (both The Authority and the network) moves forward, it is completely dedicated to the public-safety community as are vendors, various organizations, and most standards bodies that serve public safety. Everyone involved is dedicated to providing the public-safety community with what it wants and needs in the way of communications. Other issues that need to be addressed include Next-Generation 9-1-1 (NG911) funding, reversal of the T-Band giveback, ensuring that 4.9 GHz remains in the hands of public safety, and other concerns of equal importance. However, in my estimation, push-to-talk full interoperability in the field must be given the highest priority. We could see a solution not in five years but in one or two, certainly sooner than if we simply wait while the standards wheels keep grinding away.
Winding Down
What Is the FCC Thinking Now?
The FCC is apparently moving on the 4.9-GHz issue. As you may remember, the Public Safety Spectrum Alliance (PSSA, thepssa.org) is committed to retaining the 50 MHz of 4.9-GHz currently in the hands of the public-safety community by asking the FCC to license this spectrum to The FirstNet Authority. Instead, the FCC has frozen the 4.9-GHz spectrum from accepting new public-safety licenses, and according to the Chairman at the September 30, 2020, FCC open meeting, the FCC intends to propose issuing licenses for the 4.9-GHz spectrum to each state. This is a disaster waiting to happen and perhaps the worst decision to come out of the FCC in a very long time. 
Radio waves don’t stop at state borders, the plan is extremely premature, and I don’t believe what the FCC is doing will work anyway. Even though a follow-on notice states public safety will be protected, the “frequency coordinator” will be the major spectrum holder in each state. In other words, the company with the greatest incentive in each state will be responsible for coordinating who will make use of the spectrum for what purpose, and then working with surrounding states. Just think about the issues that will arise state-to-state and the differences state-to-state in what the spectrum will be used for, then trying to protect existing public-safety users! I do not understand how the FCC Commissioners can even consider this to be a viable option.
Radio Club of America
The Radio Club of America, a well-known and highly-respected organization, has been in continuous operation since 1909 and its members are from all communications disciplines. I have been a member of the RCA for many years and have had the good fortune to know Fred Link (the father of two-way radio). Fred was a long-term member and supporter of the Radio Club, and he proposed that I join the organization. It was the right move. I have met many of the folks who are and had been driving various communications segments including broadcast, commercial, public safety, amateur radio, and many other disciplines.  
Over the years, I have served on the board of directors, was elevated to Fellow in 1997, and was awarded the Club’s Sarnoff Citation in 2010. Every year, the Club holds elections and this year, Don Root, who has been exceedingly active in public-safety communications, is running for a position on the board. Don recently retired from many, many years at the County of San Diego working in the area of radio communications. He has also been deeply involved with the National Public Safety Telecommunications Council (NPSTC) and he spearheaded the committee that came up with the official names for the public-safety interoperability channels. I plan to vote for Don and if you are a member of RCA, I hope you will as well. 
If you are not a member and would like to learn more, I encourage you to visit the RCA website. I believe you will find it worthwhile to support the RCA. I especially appreciate that the Club spends a great deal of time supporting schools and other youth organizations in its efforts to turn the younger generation on to radio communications—an area that is imperative to the future of wireless communications.
Until next week…
Andrew M. Seybold©2020, Andrew Seybold, Inc.