aboutsummaryrefslogtreecommitdiffstats
path: root/src/main/proto/messages/VehiclePrecisionLocation.proto
blob: 7e132ecee7d6901906696be59b1e3d000d80bbd5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
syntax = "proto3"; /**
* <h1>Precise Vehicle Location</h1>
*<p>This set of messages define how to acquire vehicle location, either on demand or by interval and events.</p>
*<h2>Message Orchestration</h2>
*<p><img src="doc/images/mqttLocation.png" alt="HeaderMessage.puml"></p>
*<h2>MQTT Topic Design</h2>
*<table>
*  <thead>
*    <tr>
*      <th>Direction</th>
*      <th>Subscribe Topic</th>
*      <th>Publish Topic</th>
*    </tr>
*  </thead>
*  <tbody>
*    <tr>
*      <td>Vehicle to Cloud</td>
*      <td>vloc/"*"</td>
*      <td>vloc/&lt;device_id&gt;</td>
*    </tr>
*    <tr>
*      <td>Cloud to Vehicle</td>
*      <td>&lt;device_id&gt;/vloc</td>
*      <td>&lt;device_id&gt;/vloc</td>
*    </tr>
*  </tbody>
* </table>
*/

package messages;
import "messages/VehicleMessageHeader.proto";
message RequestCurrentVehicleLocationTest
/// Requests vehicle location on demand
{ 
  string vehicle_identity = 1; /// At most this identity should be all that is required to trigger the request for location and should contain a salted hash
  
}

message ResponseCurrentVehicleLocation 
/// Response to vehicle location request
{
  VehicleMessageHeading vehicleMessageHeading =1;
  VehicleCurrentLocation vehicleCurrentLocation =2;
  ResponseStatusEnum responseStatus = 3; 
}

enum ResponseStatusEnum { 
  SUCCESS = 0; /// A good GPS Location response was possible and GPS data is being returned in the payload
  FAIL_NO_RESPONSE = 1; /// No GPS information was able to be retrieved
  FAIL_DEGRADED_RESPONSE = 2; // GPS location available but degraded accuracy
}

message PublishCurrentVehicleLocation /// This is the event based version, proactively publishing location data without a cloud side request
{
  VehicleMessageHeading vehicleMessageHeading =1;
  VehicleCurrentLocation vehicleCurrentLocation =2;
}

message VehicleCurrentLocation {
  string Timestamp = 1;
  double Latitude = 2;
  double Longitude = 3;
  double Heading = 4;
  double HorizontalAccuracy = 5;
  double Altitude = 6;
  double VerticalAccuracy = 7; 

  VehicleCurrentLocationGNSSReceiver GNSSReceiver = 8;
}

message VehicleCurrentLocationGNSSReceiver {
  string FixType = 1;
  VehicleCurrentLocationGNSSReceiverMountingPosition MountingPosition = 2;
}

message VehicleCurrentLocationGNSSReceiverMountingPosition {
  int32 X = 1;
  int32 Y = 2;
  int32 Z = 3;
}