Add fields to heartbeat and mobile_reward_share files to help underst…

…and how rewards are calculated

src/service/poc_mobile.proto

@@ -213,6 +213,7 @@ message heartbeat {
   // applicable to cell heartbeats only
   string cbsd_id = 1;
   bytes pub_key = 2;
+  // this value is the heartbeat_multiplier * location_trust_score_multiplier
   float reward_multiplier = 3;
   uint64 timestamp = 4;
   cell_type cell_type = 5;
@@ -227,6 +228,10 @@ message heartbeat {
   // Distance in meters to the asserted location of the gateway_reward
   // at the time of heartbeat verification
   uint64 distance_to_asserted = 11;
+  // based on cell_type of radio
+  float heartbeat_multiplier = 12;
+  // only used for wifi indoor radios, all others should have a value of 1.0
+  float location_trust_score_multiplier = 13;
 }
 
 enum heartbeat_validity {
@@ -321,13 +326,23 @@ message radio_reward {
   uint64 seniority_timestamp = 6;
   // UUID of the coverage object used to reward this radio
   bytes coverage_object = 7;
+  // based on number of heartbeats received and cell_type
+  float heartbeat_multiplier = 8;
+  // only used for wifi indoor radios, all others should have a value of 1.0
+  float location_trust_score_multiplier = 9;
+  // based on speedtest averages of speedtests during 48 hour period from end of rewardable period
+  float speedtest_multiplier = 10;
 }
 
 message gateway_reward {
   /// Public key of the hotspot
   bytes hotspot_key = 1;
   /// Amount awarded for dc transfer
   uint64 dc_transfer_reward = 2;
+  /// count of rewardable bytes transfered 
+  uint64 rewardable_bytes = 3;
+  /// Price of MOBILE used when calculating rewards
+  uint64 price = 4;
 }
 
 message subscriber_reward {