<aside> 💡

The Helium Improvement Proposal (HIP) 98 outlines quality-of-service (QoS) requirements for the Mobile SubDAO to ensure robust, reliable, and measurable contributions to the Helium 5G network. The proposal introduces key metrics and mechanisms to assess and validate radio performance, focusing on signal coverage, uptime, and backhaul quality.

Highlights:

  1. Performance Metrics:

• Defines clear metrics for coverage and service reliability.

• Incorporates modeled coverage data to evaluate signal strength and propagation, as outlined in HIP 74, instead of relying solely on physical radio locations.

  1. Reward System:

• Introduces a reward system based on coverage points calculated using signal strength, hex coverage (res12), and compliance with uptime/backhaul requirements.

• Rewards are tiered based on estimated signal levels: high, medium, low, and none.

  1. Validation and Compliance:

• Utilizes a reward oracle and obstruction data to validate network contributions.

• Incentivizes consistent performance by penalizing downtime or unreliable backhaul connectivity.

  1. Support for Diverse Deployments:

• Addresses different setups (indoor vs. outdoor radios) and adapts validation criteria accordingly, promoting equitable rewards across deployment types.

HIP 98 aims to ensure the Mobile SubDAO fosters a reliable and scalable network while fairly compensating participants based on measurable contributions.

</aside>

HIP/0098-mobile-subdao-quality-of-service-requirements.md at main · helium/HIP

Related Prior HIPs:

HIP 53 - Established the concept of the MOBILE SubDAO

HIP 74 - Established modeled proof of coverage, and modeled coverage points.

HIP 85 - Established limits to how many radios are rewarded proof of coverage rewards per res12 hex based on overlapping coverage.

HIP 93 - Established Wi-Fi Access Points to be onboarded and rewarded to the Helium 5G network.

Summary

This Helium Improvement Proposal (HIP) sets quality of service (QOS) requirements that were noted within this blog post.

Motivation

Previous QOS requirements were implemented for the MOBILE network without community input and vote. As these requirements were previously implemented without a HIP, a HIP is being created to memorialize these QOS requirements.

Stakeholders

MOBILE Deployers - MOBILE Deployers will be affected, as they will have to continue to meet speedtest and heartbeat requirements in order to earn rewards for Proof of Coverage (PoC).