HALP: The Solution

What is HALP and how does it help?

To improve the resilience of our networks, we need to allow people to connect with each other using existing and future mobile handsets.

Helpful Alternative Link Protocol is a cellular network protocol that would enable communications between phones where primary carrier connections are not possible, or where they are used to extend that bubble of connectivity. As depicted below, using this new protocol could empower emergency communications for those in need.

Using this protocol users can:

  1. Connect with those immediately around them and receive emergency alerts

  2. Send out an emergency alert beacon with location information

  3. Request for help

  4. Offer help

  5. Voluntarily enroll their phones to act as a relay to forward communications messages with others.

Other features could be added using this new protocol, including using cell phones as "walkie talkies" in completely disconnected areas.

The Helpful Alternative Link Protocol should be the accepted standard that all device manufacturers use to enable offline communications. It should operate as a built-in emergency radio that can also send data such as map location, text messages, and alerts.

What technical changes are needed to make HALP happen?

The HALP protocol needs to be developed in conjunction with major mobile device manufacturers and the telecommunications companies, with oversight by the Federal Communications Commission. Today, there is no incentive to allow peer-to-peer emergency mesh communications over these frequencies; the carrier's primary incentive is to provide paid-for services. As spectrum is auctioned off, a portion of that spectrum should be reserved for emergency communications. During emergencies, this spectrum can be used to power long-range mesh emergency communications.

To make the Helpful Alternative Link Protocol happen:

  1. The FCC needs to allow currency that is normally allocated to cellular spectrum allocated for emergency communications purposes.

  2. Baseband radio systems need to support this protocol at a firmware level.

  3. Smartphone manufacturers (Apple, Google etc) need to support some basic level of functionality within the operating system.

What other development considerations are needed?

  1. Security: First and foremost, HALP should not cause any harm. The development of this protocol should come with rigorous and regular testing. It should also be developed in a way that supports modular updating through regularly deployed security patches. See our section on security for more information.

  2. Scalability: HALP should be developed and tested using real world conditions to ensure that it can properly scale to (potentially) millions of handsets in close proximity. Proper sharing of the limited frequencies must be considered.

  3. Noncompete: The development of this protocol is not intended to compete with cellular service providers’ ability to operate in the open market. The intent of HALP is to augment a carrier's ability to continue providing some level of service during emergency outages, but is not intended to replace them.

  4. Cellular spectrum stewardship: The carriers should participate in the development of the protocol. The way in which radio frequencies are allocated and are used is complicated. Radio frequencies are selected and used in overlapping sectors to ensure that the frequencies in use don't step on each other and cause what essentially would become the equivalent of a shouting match over radio frequencies. With carrier input, an appropriate approach to sharing existing spectrum could developed.

  5. User research: Before any significant development of any system is done, extensive user research needs to be conducted to ensure the protocol meets the needs of users that may be disconnected while experiencing an emergency.