forked from Mobiperf/MobiPerf
/
README
261 lines (214 loc) · 9.08 KB
/
README
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
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
This is a project to develop a mobile app and service for collecting
mobile network measurements. This is intended for experimental use
only.
Home page:
https://github.com/Mobiperf/Mobiperf
This code is released under the Apache 2.0 License (see LICENSE for
details).
How to Contribute to this Codebase
----------------------------------
This code can be found here:
https://github.com/Mobiperf/Mobiperf
If you wish to contribute, please read the instructions in
docs/code-review.txt
Note that simply issuing pull requests to the Mobiperf repository
on github will not suffice.
Overview of this code
---------------------
Mobiperf consists of an Android app that collects mobile network
measurements, and a data collection server, which runs on AppEngine.
The Android app periodically checks in with the measurement server,
which sends it a list of measurement tasks to perform. Measurement tasks
include ping, traceroute, HTTP GET, DNS lookup, and TCP Throughput. Each
task has an associated set of measurement parameters (e.g., which host
to ping), and a schedule (periodicity at which to take the measurement).
The device runs the measurements in the background, and uploads the
measurement results on its next checkin cycle. By default, devices
check in with the server every hour. In order to avoid draining the
battery, the app will not take any measurements if the battery is
below a given threshold (80% by default).
The protocol spoken between the app and the server is a simple JSON
REST API, documented below.
The server is implemented using Google AppEngine. It is responsible
for managing device checkins, handing out measurement tasks, and
collecting results. It has a simple Web dashboard for presenting
measurement results to the user. There is also a mechanism for
querying measurement results.
Protocol Description
--------------------
The Mobiperf app communicates with the Mobiperf service using
the following protocol, using JSON-encoded payloads over HTTP POST
methods.
All strings representing dates and times are represented in ISO8601
format with a trailing Zindicating UTC, e.g.,
2011-06-22T10:27:24.204589Z
/checkin - Used by devices to periodically check in with the service.
Input:
{
"id": "device ID",
/* Note that the user field is implied */
"manufacturer": "device manufacturer",
"model": "device model",
"os": "device OS",
"properties": {
"timestamp": "timestamp in ISO8601 format",
"os_version": "device OS version",
"location": {
"latitude": latitude value as floating point decimal degrees,
"longitude": longitude value as floating point decimal degrees
}
"location_type": "location type string",
"network_type": "network type string",
"carrier": "carrier identifier string",
}
}
Output: A list of JSON objects representing task descriptors for the
measurements that the device should perform. This schedule overwrites
any existing schedule on the device. Ongoing measurement tasks not
included in the new schedule are terminated immediately. If the
schedule is empty, the device will stop performing measurements.
[
{ "key": "optional task key",
"type": "measurement type",
"parameters": [
{ "paramName1": "paramValue1" },
{ "paramName2": "paramValue2" },
...
]
"start_time": "task start time in ISO8601 format",
"end_time": "task end time in ISO8601 format",
"interval_sec": interval as an integer,
"count": count as an integer,
"priority": priority as an integer
},
{ /* Additional Task... */ },
{ /* Additional Task... */ }
]
/postmeasurement - Used by the device to post a set of measurement
results to the service.
Input: JSON representation of a list of Measurement objects, with
embedded DeviceProperties.
[ { "device_id": "device ID",
"properties": {
"timestamp": "timestamp in ISO8601 format",
"os_version": "device OS version",
"location": {
"latitude": latitude value as floating point decimal degrees,
"longitude": longitude value as floating point decimal degrees
}
"location_type": "location type string",
"network_type": "network type string",
"carrier": "carrier identifier string",
}
"type": "measurement type",
"timestamp": "measurement timestamp in ISO8601 format",
"success": true or false,
"task_key": "task key associated with this measurement, if any",
"parameters": [
{ "paramName1": "paramValue1" },
{ "paramName2": "paramValue2" },
...
],
"values": [
{ "valueName1": "valueValue1" },
{ "valueName2": "valueValue2" },
...
],
},
{ /* Additional Measurement... */ },
{ /* Additional Measurement... */ },
]
Output: A JSON-encoded representation of whether the post was
successful:
{ "success": true or false }
The measurement type may be "ping", "traceroute", "dns", or "http".
The parameters and measurement values for each measurement type are
given below. All parameters and values are strings (since this is how
they are represented in the JSON protocol described above).
Ping parameters
(required) target - the host name or IP address of the server to ping
(optional) packet_size_byte - the packet per ICMP ping in the unit of
bytes. Default to 56.
(optional) ping_timeout_sec - the number of seconds we wait for a ping
response. Default to 0.5.
Ping values
(required) target_ip - the IP address of the target we ping against
(required) ping_method - the actual ping method this result represents.
(ping_cmd, java_ping, http).
(required) mean_rtt_ms - Mean RTT in milliseconds (e.g.,
"20.485" for 20.485 ms)
(required) min_rtt_ms - Min RTT in milliseconds
(required) max_rtt_ms - Max RTT in milliseconds
(required) stddev_rtt_ms - Standard deviation of RTT in milliseconds
(optional) filtered_mean_rrt_ms - Mean RRT with outlier values filtered
out. Unit is in milliseconds
(optional) packet_loss - Fraction of lost packets (e.g., "0.5" for 50% loss)
Traceroute parameters
(required) target - the hostname or IP address to use as the target of
the traceroute.
(required) packet_size_byte - the packet per ICMP ping in the unit of
bytes. Default to 56.
(optional) ping_timeout_sec - the number of seconds we wait for a ping
response. Default to 2.
optinal ping_interval_sec - the interval between successive pings in
seconds. Default to 0.5.
optinal pings_per_hop - the number of pings we use for each ttl value.
Default to 3.
(optional) max_hop_count - the total number of hops we ping before we
declare the traceroute fails. Default to 10.
Traceroute results
(required) num_hops - Number of observed hops in the traceroute
(required) hop_N_addr_i - The ith IP address of the Nth hop along the
observed route, where N ranges from 0 to num_hops-1.
(required) hop_N_rtt_ms - Observed RTT in milliseconds to this hop.
DNS lookup parameters
(required) target - Hostname of the target to resolve
(optional) server - IP address of a DNS server to use as the resolver.
If not present, the device's default resolver is used.
DNS lookup values
(required) address - IPv4 address of the target as returned by an A
record
(required) real_hostname - True FQDN of the host that has been resolved
(required) time_ms - Time taken to perform the DNS lookup
HTTP parameters
(required) url - URL to request
(optional) method - HTTP method to use. Defaults to "GET"
(optional) headers - String (possibly containing newlines) with
additional headers to send with the request. Each header and value
pair is in the form of "headerParam:value", with different
pairs separated by "\r\n".
(optional) body - String with the request body to send (if method is
"POST")
HTTP values
(required) time_ms - Time in milliseconds to perform the complete
request
(required) code - Response code (e.g., "200")
(optional) headers_len - Size in bytes of the original response headers
(optional) body_len - Size in bytes of the original response body
(optional) headers - Response headers - may be compressed, truncated, or
elided in the case of a large response
(optional) body - Response body - may be compressed, truncated, or
elided in the case of a large response. It is a JSON encoded byte
array.
TCP Throughput parameters
(required) dir_up - Uplink or Downlink measurement (boolean)
(required) target - hostname for servers. Use m-lab for now. (string)
(optional) data_limit_mb_up - Uplink cellular network data
limit (double)
(optional) data_limit_mb_down - Downlink cellular network data
limit (double)
(optional) duration_period_sec - Downlink maximum experiment
duration period (double)
(optional) pkt_size_up_bytes - The size each packet in the uplink (int)
(optional) sample_period_sec - The small interval to calculate current
throughput result (double)
(optional) slow_start_period_sec - Waiting period to avoid TCP slow
start (double)
(optional) tcp_timeout_sec - TCP connection timeout (double)
TCP Throughput value
(required) tcp_speed_results - A list of throughput sampling results
in kbps (list of double)
(required) data_limit_exceeded - A flag indicating transmitted data
exceeding limit (boolean)
(required) duration - Time to finish the task (double)
(required) server_version - M-Lab server side code version (string)