The Network Survey Messaging API defines a set of messages that can be used to describe wireless survey related events. The messages range from cellular surveys such as GSM, CDMA, UMTS, LTE, and NR, to simple RF energy detection events.
NOTE: Despite the name "Network Survey Messaging API", this message specification is not exclusive to the Network Survey Android App. Instead, the Network Survey Android App is just one app that leverages Network Survey Messaging. Therefore, there are messages in this specification that do not apply to the Network Survey Android App (e.g. EnergyDetection).
While the most common use of these messages would be to send to an MQTT broker, this API specification simply defines the message schema. The transport or storage technology employed is purposefully left open to allow for these messages to flow over a variety of transports such as MQTT, gRPC, AMQP, etc. In addition, these messages can be written to disk by writing the JSON strings directly to a file to support unstructured data storage, or in a more structured approach such as a PostgreSQL or SQLite database.
Officially, the message schema support for the Network Survey Messaging API are the JSON defined messages from this document. However, protobuf definitions of these messages have been created as a convenience for a couple of reasons. First, it can make generating the JSON compliant messages easier and also converting the JSON messages to language specific objects. Secondly, it can allow for sending the messages in protocol buffer format instead of JSON if a compressed binary format is needed. It also has the side effect of supporting sending these messages over gRPC if Remote Procedure Call support is of interest. Check out the Network Survey Messaging Github README for more details.
The gsm_message topic/channel is where GSM survey records can be published. For MQTT, set the MQTT topic as "gsm_message" and then publish a JSON message representing a GSM survey record in the format defined below.
Accepts the following message:
Represents information recorded about a GSM tower at a particular time and geographic location.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be GsmRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. For simple frequency sweeps, all detections in the same sweep should have the same group number. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
Location Area Code, location code inside a PLMN, valid range 0-65535.
Cell Identity of the measured cell, valid range 0-65535.
Absolute Radio Frequency Channel Number, valid values defined in 3GPP TS 45.005 Release 10 Section 2.
Base Station Identity Code, consists of NCC and BCC, valid range 0-63 (in octal). For example, a BSIC of 38 maps to an NCC of 4 and BCC of 6.
The signal strength of the received signal in dBm.
Timing Advance, corresponding to the timing offset a mobile phone needs to use when transmitting a signal to the tower.
Boolean indicating if this record represents a serving cell record, or a neighbor cell record. If the field is unset then it is unknown if this record is for the serving cell or a neighbor cell. A value of true indicates that the record represents a serving cell, a value of false indicates a neighbor record.
The company providing the cellular service.
The slot number of the SIM card or radio slot that this record was captured from. This enables support for multiple SIM cards in a single device or multiple radios in a single device. Numbering does not start at 0 or 1, and can be any arbitrary number. Therefore, the number does not reveal anything about the number of SIM cards or radio slots in the device. This field is optional, and if it is not present that is an indication that the device only has a single SIM card or radio (but the presence of this field does not indicate multiple SIM cards or radios). Added in version 0.15.0.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "GsmRecord",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"recordNumber": 1,
"groupNumber": 1,
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"mcc": 310,
"mnc": 410,
"lac": 174,
"ci": 47241,
"arfcn": 557,
"bsic": 25,
"signalStrength": -73.1,
"ta": 4,
"servingCell": true,
"provider": "ATT",
"slot": 2
}
}
The cdma_message topic/channel is where CDMA survey records can be published. For MQTT, set the MQTT topic as "cdma_message" and then publish a JSON message representing a CDMA survey record in the format defined below.
Accepts the following message:
Represents information recorded about a CDMA tower at a particular time and geographic location.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be CdmaRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. For simple frequency sweeps, all detections in the same sweep should have the same group number. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
System Identification Number, 15 bit number that represents the service provider(s) a base station provides service to.
Network Identification Number, 16 bit number that represents the network within a SID.
A collection of one or more base stations treated as a unit when determining whether a mobile station should perform zone-based registration.
Base Station Identifier. Exclusively identifies a base station under a SID/NID.
Channel number that corresponds to a frequency.
Pseudo Random Noise, 0-511, used to differentiate sectors on base stations.
The signal strength of the received signal in dBm.
Measure of the quality / cleanliness of the signal from the tower to the modem (signal to noise). Energy per chip to Interference power ratio measured in dB.
Boolean indicating if this record represents a serving cell record, or a neighbor cell record. If the field is unset then it is unknown if this record is for the serving cell or a neighbor cell. A value of true indicates that the record represents a serving cell, a value of false indicates a neighbor record.
The company providing the cellular service.
The slot number of the SIM card or radio slot that this record was captured from. This enables support for multiple SIM cards in a single device or multiple radios in a single device. Numbering does not start at 0 or 1, and can be any arbitrary number. Therefore, the number does not reveal anything about the number of SIM cards or radio slots in the device. This field is optional, and if it is not present that is an indication that the device only has a single SIM card or radio (but the presence of this field does not indicate multiple SIM cards or radios). Added in version 0.15.0.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "CdmaRecord",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"recordNumber": 1,
"groupNumber": 1,
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"sid": 139,
"nid": 4,
"zone": 232,
"bsid": 12731,
"channel": 384,
"pnOffset": 136,
"signalStrength": -73.1,
"ecio": -11.4,
"servingCell": true,
"provider": "Verizon",
"slot": 2
}
}
The umts_message topic/channel is where UMTS survey records can be published. For MQTT, set the MQTT topic as "umts_message" and then publish a JSON message representing a UMTS survey record in the format defined below.
Accepts the following message:
Represents information recorded about a UMTS NodeB at a particular time and geographic location.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be UmtsRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. For simple frequency sweeps, all detections in the same sweep should have the same group number. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
Location Area Code, location code inside a PLMN, valid range 0-65535.
The Cell Identity of the measured cell, 28 bits, the RNC-ID is the first 12 bits, and the C-ID is the last 16 bits, valid range 0-268435455. Defined in 3GPP TS 25.331.
UTRA Absolute Radio Frequency Channel Number (Downlink), valid range 0-13096, defined in 3GPP TS 25.101 and 3GPP TS 25.102.
Primary Scrambling Code, valid range 0-511.
Reference Signal Code Power in dBm.
Received energy per chip divided by the power density in the band in dB. The value is negative as the RSCP is smaller than the total received power. Added in version 0.8.0.
The signal strength of the received signal in dBm.
Boolean indicating if this record represents a serving cell record, or a neighbor cell record. If the field is unset then it is unknown if this record is for the serving cell or a neighbor cell. A value of true indicates that the record represents a serving cell, a value of false indicates a neighbor record.
The company providing the cellular service.
The slot number of the SIM card or radio slot that this record was captured from. This enables support for multiple SIM cards in a single device or multiple radios in a single device. Numbering does not start at 0 or 1, and can be any arbitrary number. Therefore, the number does not reveal anything about the number of SIM cards or radio slots in the device. This field is optional, and if it is not present that is an indication that the device only has a single SIM card or radio (but the presence of this field does not indicate multiple SIM cards or radios). Added in version 0.15.0.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "UmtsRecord",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"recordNumber": 1,
"groupNumber": 1,
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"mcc": 310,
"mnc": 260,
"lac": 174,
"cid": 61381,
"uarfcn": 9800,
"psc": 141,
"rscp": -73,
"ecno": -11.4,
"signalStrength": -73.1,
"servingCell": true,
"provider": "T-Mobile",
"slot": 2
}
}
The lte_message topic/channel is where LTE survey records can be published. For MQTT, set the MQTT topic as "lte_message" and then publish a JSON message representing an LTE survey record in the format defined below.
Accepts the following message:
Represents information recorded about an LTE eNodeB at a particular time and geographic location.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be LteRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. For simple frequency sweeps, all detections in the same sweep should have the same group number. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
Tracking Area Code, location code inside a PLMN, valid range 0-65535.
ECI, the Cell Identity of the measured cell, 28 bits. The Macro eNB ID is the first 20 bits of the Cell Identity and the last 8 bits represent the sector. Valid range 0-268435455.
Downlink E-UTRA Absolute Radio Frequency Channel Number, valid range 0-262143, defined in 3GPP TS 36.331 version 14.2.2 Release 14 page 567.
Physical Cell Identity, valid range 0-503.
Reference Signal Received Power in dBm, valid range -44 to -140, corresponding to RSRP_97 to RSRP_00 respectively.
Reference Signal Received Quality in dB, valid range -3 to -19.5, corresponding to RSRQ_34 to RSRQ_00 respectively.
The Reference Signal Signal-to-Noise Ratio measured in dB. Range: -20 dB to +30 dB. Added in version 1.2.0.
LTE Timing Advance, corresponding to the timing offset a mobile phone needs to use when transmitting a signal to the tower. Valid range 0-1282.
The signal strength of the received signal in dBm.
Channel Quality Indicator, used by the UE to notify the serving cell (eNodeB) about the quality of the downlink channel, valid range 0-15. This field was added in version 0.14.0.
Boolean indicating if this record represents a serving cell record, or a neighbor cell record. If the field is unset then it is unknown if this record is for the serving cell or a neighbor cell. A value of true indicates that the record represents a serving cell, a value of false indicates a neighbor record.
The LTE downlink bandwidth in MHz (one of 1.4, 3, 5, 10, 15, 20).
The company providing the cellular service.
The slot number of the SIM card or radio slot that this record was captured from. This enables support for multiple SIM cards in a single device or multiple radios in a single device. Numbering does not start at 0 or 1, and can be any arbitrary number. Therefore, the number does not reveal anything about the number of SIM cards or radio slots in the device. This field is optional, and if it is not present that is an indication that the device only has a single SIM card or radio (but the presence of this field does not indicate multiple SIM cards or radios). Added in version 0.15.0.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "LteRecord",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"recordNumber": 1,
"groupNumber": 1,
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"mcc": 311,
"mnc": 480,
"tac": 52803,
"eci": 52824577,
"earfcn": 5230,
"pci": 234,
"rsrp": -107,
"rsrq": -11,
"snr": 19,
"ta": 27,
"signalStrength": -73.1,
"cqi": 7,
"servingCell": true,
"lteBandwidth": "MHZ_10",
"provider": "Verizon",
"slot": 2
}
}
The nr_message topic/channel is where 5G NR survey records can be published. For MQTT, set the MQTT topic as "nr_message" and then publish a JSON message representing a 5G NR survey record in the format defined below.
Accepts the following message:
Represents information recorded about a 5G NR gNodeB at a particular time and geographic location.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be NrRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. For simple frequency sweeps, all detections in the same sweep should have the same group number. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
NR Tracking Area Code, location code inside a PLMN, valid range 0 - 16,777,215 as defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 643.
NCI, the Cell Identity of the measured cell, 36 bits. The gNB ID is the first 22-32 bits of the NCI and the remaining bits represent the sector. Valid range 0 - 68,719,476,735 as defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 370.
Downlink NR Absolute Radio Frequency Channel Number, valid range 0 - 3,279,165, defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 784.
NR Physical Cell Identity, valid range 0-1007 as defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 503.
Secondary Synchronization signal Reference Signal Received Power in dBm, valid range -156 to -31, corresponding to RSRP_1 to RSRP_126 respectively as defined in 3GPP TS 38.133 version 16.5.0 Release 16 Table 10.1.6.1-1.
Secondary Synchronization signal Reference Signal Received Quality in dB, valid range -43 to 20, corresponding to SS-RSRQ_1 to SS-RSRQ_127 respectively (increments of 0.5) as defined in 3GPP TS 38.133 version 16.5.0 Release 16 Table 10.1.11.1-1.
Secondary Synchronization signal signal-to-noise and interference ratio in dB. The reporting range of SS-SINR is defined from -23 dB to 40 dB with 0.5 dB resolution, corresponding to SINR_1 to SINR_127 respectively as defined in 3GPP TS 38.133 version 16.5.0 Release 16 Table 10.1.16.1-1.
Channel State Information (CSI) Reference Signal Received Power in dBm, valid range -140 to -44, corresponding to RSRP_17 to RSRP_113 respectively as defined in 3GPP TS 38.133 version 16.5.0 Release 16 Table 10.1.6.1-1.
CSI Reference Signal Received Quality in dB.
CSI signal-to-noise and interference ratio in dB. The reporting range of CSI-SINR is defined from -23 dB to 40 dB with 0.5 dB resolution, corresponding to SINR_1 to SINR_127 respectively as defined in 3GPP TS 38.133 version 16.5.0 Release 16 Table 10.1.16.1-1.
NR Timing Advance, corresponding to the timing offset a mobile phone needs to use when transmitting a signal to the tower. Valid range 0-3846.
Boolean indicating if this record represents a serving cell record, or a neighbor cell record. If the field is unset then it is unknown if this record is for the serving cell or a neighbor cell. A value of true indicates that the record represents a serving cell, a value of false indicates a neighbor record.
The company providing the cellular service.
The slot number of the SIM card or radio slot that this record was captured from. This enables support for multiple SIM cards in a single device or multiple radios in a single device. Numbering does not start at 0 or 1, and can be any arbitrary number. Therefore, the number does not reveal anything about the number of SIM cards or radio slots in the device. This field is optional, and if it is not present that is an indication that the device only has a single SIM card or radio (but the presence of this field does not indicate multiple SIM cards or radios). Added in version 0.15.0.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "NrRecord",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"recordNumber": 1,
"groupNumber": 1,
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"mcc": 311,
"mnc": 480,
"tac": 52803,
"nci": "52824577",
"narfcn": 5230,
"pci": 234,
"ssRsrp": -107.1,
"ssRsrq": -11.5,
"ssSinr": 14.5,
"csiRsrp": -107.1,
"csiRsrq": -11.5,
"csiSinr": 14.5,
"ta": 14,
"servingCell": true,
"provider": "Verizon",
"slot": 2
}
}
The 80211_beacon_message topic/channel is where 802.11 beacon survey records can be published. For MQTT, set the MQTT topic as "80211_beacon_message" and then publish a JSON message representing an 802.11 Access Point survey record in the format defined below.
Accepts the following message:
Represents information recorded about an 802.11 Access Point at a particular time and geographic location. 802.11 Beacon frames are sent by Access Points to advertise their existence and to provide all the necessary connection information. This message represents a capture of a single 802.11 Beacon message.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be WifiBeaconRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Source MAC Address, the original source of the frame.
Destination MAC Address, the final destination of the frame.
Basic Service Set Identifier, the MAC Address of the Access Point.
Beacon Interval, in milliseconds. The rate at which beacon frames are sent from an Access Point advertising the existence of the AP.
The Service Set Type that this node belongs to.
The Service Set Identifier (aka the Wi-Fi network name), UTF-8 Encoded.
A list of data rates supported by this device separated by semicolons.
An extended list of data rates supported by this device separated by semicolons.
A list of the supported cipher suites. See IEEE Std 802.11-2012 Section 8.4.2.27.2 for more details on the 802.11 Cipher Suites.
A list of the supported Authentication and Key Management (AKM) suites. See IEEE Std 802.11-2012 Section 8.4.2.27.3 for more details on the 802.11 AKM Suites.
The encryption type used by the Access Point. This field should be kept in sync with the cipherSuites field as it is directly related.
Boolean indicating if this Access Point supports Wi-Fi Protected Setup as defined by the Wi-Fi Alliance.
Boolean indicating if this is a Passpoint Enabled Network Access Point. Passpoint is a standard defined by the Wi-Fi Alliance, not IEEE. This field was added in version 0.13.0.
The channel on which this 802.11 frame was recorded.
The frequency in MHz on which this 802.11 frame was recorded.
The Wi-Fi bandwidth in MHz (one of 20, 40, 80, 80 Plus, 160, 320).
The signal strength of the received signal in dBm.
The Signal to Noise Ratio of the received signal to the noise power measured in dB. A ratio higher than 1:1 (greater than 0 dB) indicates more signal than noise.
The type of station that sent this frame.
The 802.11 standard being employed by the device.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "WifiBeaconRecord",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"recordNumber": 1,
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"sourceAddress": "68:7F:74:B0:14:98",
"destinationAddress": "68:7F:74:B0:14:22",
"bssid": "68:7F:74:B0:14:98",
"beaconInterval": 100,
"serviceSetType": "BSS",
"ssid": "My Wi-Fi Network",
"supportedRates": "1; 2; 5.5; 11; 18; 24; 36; 54",
"extendedSupportedRates": "6; 9; 12; 48",
"cipherSuites": [
"TKIP",
"CCMP"
],
"akmSuites": [
"OPEN"
],
"encryptionType": "WPA_WPA2",
"wps": true,
"passpoint": true,
"channel": 6,
"frequencyMhz": 2417,
"bandwidth": "MHZ_40",
"signalStrength": -73.1,
"snr": 19.2,
"nodeType": "AP",
"standard": "IEEE80211AX"
}
}
The 80211_probe_request_message topic/channel is where 802.11 probe request survey records can be published. For MQTT, set the MQTT topic as "80211_probe_request_message" and then publish a JSON message representing an 802.11 Probe Request record in the format defined below. Added in 0.9.0
Accepts the following message:
Represents information recorded about an 802.11 Probe Request at a particular time and geographic location. 802.11 Probe Request frames are sent by clients looking to discover information about an Access Point with a specific SSID. This message represents a capture of a single 802.11 Probe Request message.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be WifiProbeRequestRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Source MAC Address, the original source of the frame.
Destination MAC Address, the final destination of the frame.
Basic Service Set Identifier, the MAC Address of the Access Point.
The Service Set Identifier (aka the Wi-Fi network name), UTF-8 Encoded.
The channel on which this 802.11 frame was recorded.
The frequency in MHz on which this 802.11 frame was recorded.
The signal strength of the received signal in dBm.
The Signal to Noise Ratio of the received signal to the noise power measured in dB. A ratio higher than 1:1 (greater than 0 dB) indicates more signal than noise.
The type of station that sent this frame.
The 802.11 standard being employed by the device.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "WifiProbeRequestRecord",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"recordNumber": 1,
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"sourceAddress": "68:7F:74:B0:14:98",
"destinationAddress": "68:7F:74:B0:14:22",
"bssid": "68:7F:74:B0:14:98",
"ssid": "My Wi-Fi Network",
"channel": 2,
"frequencyMhz": 2417,
"signalStrength": -73.1,
"snr": 19.2,
"nodeType": "AP",
"standard": "IEEE80211AX"
}
}
The 80211_deauthentication_message topic/channel is where 802.11 (Wi-Fi) Deauthentication Management Frames can be published. For MQTT, set the MQTT topic as "wifi_deauthentication_message". When a station wants to disassociate from another station, it invokes the deauthentication service. Deauthentication is a notification and cannot be refused. A station performs deauthentication by sending an authentication management frame (or group of frames to multiple stations) to advise of the termination of authentication.
Accepts the following message:
Represents an 802.11 deauthentication management frame. When a station wants to disassociate from another station, it invokes the deauthentication service. Deauthentication is a notification and cannot be refused. A station performs deauthentication by sending an authentication management frame (or group of frames to multiple stations) to advise of the termination of authentication.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be WifiDeauthenticationRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Source MAC Address, the original source of the frame.
Destination MAC Address, the final destination of the frame.
Basic Service Set Identifier, the MAC Address of the Access Point.
Clients may disassociate prior to powering off. APs may disassociate clients for various reasons including failure to properly authenticate, for load balancing or timeout reasons, entering a state of maintenance, etc. The 802.11-2016 standard includes a list of disassociation reasons.
The Service Set Identifier (aka the Wi-Fi network name), UTF-8 Encoded.
The channel on which this 802.11 frame was recorded.
The frequency in MHz on which this 802.11 frame was recorded.
The signal strength of the received signal in dBm.
The Signal to Noise Ratio of the received signal to the noise power measured in dB. A ratio higher than 1:1 (greater than 0 dB) indicates more signal than noise.
The type of station that sent this frame.
The 802.11 standard being employed by the device.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "WifiDeauthenticationRecord",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"recordNumber": 1,
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"sourceAddress": "68:7F:74:B0:14:98",
"destinationAddress": "68:7F:74:B0:14:22",
"bssid": "68:7F:74:B0:14:98",
"reason": 2,
"ssid": "My Wi-Fi Network",
"channel": 2,
"frequencyMhz": 2417,
"signalStrength": -73.1,
"snr": 19.2,
"nodeType": "AP",
"standard": "IEEE80211AX"
}
}
The 80211_ota_message topic/channel is where Over The Air (OTA) 802.11 (Wi-Fi) messages can be published. For MQTT, set the MQTT topic as "wifi_ota_message" and then publish a JSON message representing an OTA WiFi message.
Accepts the following message:
Represents information recorded about an 802.11 packet recorded at a particular time and geographic location. This message represents a capture of a 802.11 packet in PCAP format.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be WifiOtaRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The frame type of the 802.11 message. The frame type represents the type of 802.11 frame that the pcapRecord field contains. For example, a frame type of 0 represents a management frame, 1 represents a control frame, and 2 represents a data frame, and 3 represents an extension.
The subtype of the 802.11 message that corresponds to the frame type. The frame subtype represents the subtype of the 802.11 frame that the pcapRecord field contains. For example, if the frame type is 0 (aka Management) a frame subtype of 0 represents an association request, 1 represents an association response, 2 represents a reassociation request, etc.
The raw 802.11 frame bytes encoded in base64. The bytes in this field are the raw message bytes captured from the Over The Air (OTA) 802.11 radio frame with the appropriate PCAP headers as the prefix. In other words, the bytes are the same bytes that would show up in a pcap file for an 802.11 message. The general structure consists of a PCAP record header, PPI header, Radiotap header, followed by the 802.11 frame. Using this structure means that Wireshark, tshark or any other tool that can read 802.11 pcap records can easily parse out the contents of this message.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "WifiOtaRecord",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"recordNumber": 1,
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"frameType": 0,
"frameSubtype": 4,
"pcapRecord": "aVwDZYj5DgBJAAAASQAAAAAAMABvCABAOsN7FAAAAAASDGwJwACroAAAAAN/ABAAAAAAAAAAAAAAAAAAAAAAAFQAZABszdbclR85lO2uZIceAQAgCAk4KYc="
}
}
The bluetooth_message topic/channel is where Bluetooth survey records can be published. For MQTT, set the MQTT topic as "bluetooth_message" and then publish a JSON message representing a Bluetooth survey record in the format defined below.
Accepts the following message:
Represents information recorded about a Bluetooth device at a particular time and geographic location. This message represents a capture of a signal Bluetooth frame.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be BluetoothRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Source MAC Address, the original source of the frame.
Destination MAC Address, the final destination of the frame.
The signal strength of the received signal in dBm.
The power in dBm that the device used to transmit the signal.
The Bluetooth wireless technology system that is used in this frame. See the BLUETOOTH SPECIFICATION Version 5.0 | Vol 1, Part A Section 1 (page 166) for more details.
The Bluetooth wireless technology systems that are supported be the transmitting device. See the BLUETOOTH SPECIFICATION Version 5.0 | Vol 1, Part A Section 1 (page 166) for more details.
The Bluetooth device name is the user-friendly name that a Bluetooth device exposes to remote devices. See the BLUETOOTH SPECIFICATION Version 5.0 | Vol 3, Part C Section 3.2.2 (page 1988) for more details.
The channel on which this frame was recorded. See the BLUETOOTH SPECIFICATION Version 5.0 | Vol 2, Part A Section 2 (page 325) for more details.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "BluetoothRecord",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"recordNumber": 1,
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"sourceAddress": "68:7F:74:B0:14:98",
"destinationAddress": "68:7F:74:B0:14:22",
"signalStrength": -73.1,
"txPower": 8,
"technology": "LE",
"supportedTechnologies": "DUAL",
"otaDeviceName": "Apple Pencil",
"channel": 2
}
}
The gnss_message topic/channel is where GNSS positioning records can be published. For MQTT, set the MQTT topic as "gnss_message" and then publish a JSON message in the format defined below.
Accepts the following message:
Represents information recorded about a Global Navigation Satellite System (GNSS) at a particular time and geographic location. Each record represents a single navigation message from a single satellite. These individual records are tied together using the group number field.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be GnssRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. Records with the same group number indicate they were all seen in the same "scan" for GNSS space vehicles.
The model number of the device that this message originated from.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The satellite constellation associated with the record.
The identifier for the space vehicle (SV).
The carrier frequency utilized by the SV, in Hz.
The clock offset calculated by the receiver based on the space-vehicle time contained in a received navigation message, i.e. the time it took for a given navigation message to be sent from a space vehicle to the receiver's antenna, as calculated by the receiver itself.
Indicates whether this particular satellite data was used as part of the solution. A value of true indicates that the record was used in the solution, a value of false indicates that the record was not used in the solution.
The height in meters of the geoid at a given point, relative to a given reference ellipsoid, i.e. the difference in height between the 'real' surface (ignoring topographical features) and a 'modeled' surface given by a reference ellipsoid such as the one defined by WGS84. Valid range, -150.0 to 150.0.
The standard deviation of the latitude measurement in meters, where a higher value indicates a less precise position lock. For example, a 5m deviation indicates that, with 68% confidence, the latitude is within 5m of the reported position; with 95% confidence, the latitude is within 10m of the reported position, etc. This relates to the Horizontal Dilution of Precision (HDOP).
The standard deviation of the longitude measurement in meters, where a higher value indicates a less precise position lock. For example, a 5m deviation indicates that, with 68% confidence, the longitude is within 5m of the reported position; with 95% confidence, the longitude is within 10m of the reported position, etc. This relates to the Horizontal Dilution of Precision (HDOP).
The standard deviation of the altitude measurement in meters, where a higher value indicates a less precise position lock. For example, a 5m deviation indicates that, with 68% confidence, the altitude is within 5m of the reported position; with 95% confidence, the altitude is within 10m of the reported position, etc. This relates to the Vertical Dilution of Position (VDOP), and tends to be higher than the Lat/Lon standard deviations due to GNSS satellites being above GNSS receivers.
Automatic Gain Control, measured in dB. Valid range, -50.0 to 50.0
The Carrier-to-noise density in dB-Hz, which represents the measured C/N0 for the signal at the antenna inputCarrier to noise density ratio, measured in dB-Hz. Typical range: 10-50 dB-Hz. The range of possible C/N0 values is 0-63 dB-Hz to handle some edge cases.
Horizontal Dilution of Precision. Valid range, 0.0 to 50.0.
Vertical Dilution of Precision. Valid range, 0.0 to 50.0.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "GnssRecord",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"recordNumber": 1,
"groupNumber": 1,
"deviceModel": "Pixel 5",
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"constellation": "GALILEO",
"spaceVehicleId": 2345,
"carrierFreqHz": 120000000,
"clockOffset": 0.001,
"usedInSolution": true,
"undulationM": 125.1,
"latitudeStdDevM": 5.2,
"longitudeStdDevM": 4.1,
"altitudeStdDevM": -122.1,
"agcDb": -25.2,
"cn0DbHz": 1.1,
"hdop": 1.2,
"vdop": 1.3
}
}
The energy_detection_message topic/channel is where RF energy detection records can be published. For MQTT, set the MQTT topic as "energy_detection_message" and then publish a JSON message in the format defined below.
Accepts the following message:
Represents a General Purpose Radio (GPR) Energy Detection event. This survey record represents a general RF/PTT energy detection (i.e. RF energy was detected above a pre-defined threshold).
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be EnergyDetection.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. For simple frequency sweeps, all detections in the same sweep should have the same group number. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The frequency, in Hz, that the radio signal was received on.
The bandwidth, in Hz, of the received signal.
The signal strength of the received signal in dBm.
The Signal to Noise Ratio of the received signal to the noise power measured in dB. A ratio higher than 1:1 (greater than 0 dB) indicates more signal than noise.
The date & time the energy/signal was detected as active. This is formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The duration of time, in seconds, that the signal was detected as active.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "EnergyDetection",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"recordNumber": 1,
"groupNumber": 1,
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"frequencyHz": 162000000,
"bandwidthHz": 12500,
"signalStrength": -73.1,
"snr": 19.2,
"timeUp": "1996-12-20T00:39:57.000Z",
"durationSec": 4.2
}
}
The signal_detection_message topic/channel is where signal detection records can be published. For MQTT, set the MQTT topic as "signal_detection_message" and then publish a JSON message in the format defined below.
Accepts the following message:
Represents a General Purpose Radio (GPR) Signal Detection event. This survey record represents RF detections where the modulation and/or signal type could be determined. If both the modulation and signal type are unknown, then use the `energy_detection_message` instead.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be SignalDetection.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. For simple frequency sweeps, all detections in the same sweep should have the same group number. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The frequency, in Hz, that the radio signal was received on.
The bandwidth, in Hz, of the received signal.
The signal strength of the received signal in dBm.
The Signal to Noise Ratio of the received signal to the noise power measured in dB. A ratio higher than 1:1 (greater than 0 dB) indicates more signal than noise.
The date & time the energy/signal was detected as active. This is formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The duration of time, in seconds, that the signal was detected as active.
The modulation type found on the received signal. It is appropriate to leave this blank if the modulation of the signal is unknown, but either the modulation or signalName field should be filled out. If neither of them are known then the energyDetection message should be used instead.
The modulation type found on the received signal. It is appropriate to leave this blank if the modulation of the signal is unknown, but either the modulation or signalName field should be filled out. If neither of them are known then the energyDetection message should be used instead.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "SignalDetection",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"recordNumber": 1,
"groupNumber": 1,
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"frequencyHz": 162000000,
"bandwidthHz": 12500,
"signalStrength": -73.1,
"snr": 19.2,
"timeUp": "1996-12-20T00:39:57.000Z",
"durationSec": 4.2,
"modulation": "4FSK",
"signalName": "DMR"
}
}
The device_status_message topic/channel is where device status records can be published. This includes both DeviceStatus and PhoneState messages. For MQTT, set the MQTT topic as "device_status_message" and then publish a JSON message in one of the formats defined below.
Accepts one of the following messages:
Represents a status message sent from the device to report its current state or to act as a heartbeat. The interval of this message can vary depending on use case.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be DeviceStatus.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
The model number of the device that this message originated from.
The version of the software application that this message originated from (most likely the Network Survey Android app, but could be any other app). Added in version 1.3.0.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The percentage of battery remaining (if the device has a battery).
If present, represents that the device is in an error state.
A description of the error state that the device is in.
Additional properties are allowed.
Indicates if the device currently has the Mobile Device Management (MDM) Override option turned on. If true, the user has forced the MDM options off, if false, the user has left the MDM control in place. Added in version 0.9.0.
The latitude as obtained from the GNSS location provider. This is an additional value to the regular latitude and is only provided for comparison and analysis purposes.
The longitude as obtained from the GNSS location provider. This is an additional value to the regular longitude and is only provided for comparison and analysis purposes.
The altitude in meters above MSL as obtained from the GNSS location provider. This is an additional value to the regular altitude and is only provided for comparison and analysis purposes.
The estimated horizontal accuracy of the provided location in meters as obtained from the GNSS location provider. This is an additional value to the regular accuracy and is only provided for comparison and analysis purposes.
The latitude as obtained from the Network based location provider (e.g. Cellular and/or Wi-Fi). This is an additional value to the regular latitude and is only provided for comparison and analysis purposes.
The longitude as obtained from the Network based location provider (e.g. Cellular and/or Wi-Fi). This is an additional value to the regular longitude and is only provided for comparison and analysis purposes.
The altitude in meters above MSL as obtained from the Network based location provider (e.g. Cellular and/or Wi-Fi). This is an additional value to the regular altitude and is only provided for comparison and analysis purposes.
The estimated horizontal accuracy of the provided location in meters as obtained from the Network based location provider (e.g. Cellular and/or Wi-Fi). This is an additional value to the regular accuracy and is only provided for comparison and analysis purposes.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "DeviceStatus",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"deviceModel": "Pixel 5",
"appVersion": 1.28,
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"batteryLevelPercent": 86,
"error": {
"errorMessage": "The scan stopped unexpectedly"
},
"mdmOverride": true,
"gnssLatitude": 51.470334,
"gnssLongitude": -0.486594,
"gnssAltitude": 13.3,
"gnssAccuracy": 40,
"networkLatitude": 51.470334,
"networkLongitude": -0.486594,
"networkAltitude": 13.3,
"networkAccuracy": 40
}
}
Represents the current state of the phone to include information about the currently registered networks. The interval of this message can vary depending on use case, but is typically sent when a change in the phone's state occurs, such as registering to a new network or being rejected from a network.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be PhoneState.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The current state of the SIM card. The values are taken directly from android.telephony.TelephonyManager#SimState and should be kept in sync with those values. Even the order lines up exactly, which makes conversion easier.
The PLMN portion of the SIM's IMSI. This indicates the provider that issued the SIM card. The format is the MCC and MNC concatenated as one string. Can be 5 or 6 digits in length where the MCC is always 3 digits and the MNC is either 2 or 3.
The slot number of the SIM card or radio slot that this record was captured from. This enables support for multiple SIM cards in a single device or multiple radios in a single device. Numbering does not start at 0 or 1, and can be any arbitrary number. Therefore, the number does not reveal anything about the number of SIM cards or radio slots in the device. This field is optional, and if it is not present that is an indication that the device only has a single SIM card or radio (but the presence of this field does not indicate multiple SIM cards or radios). Added in version 0.15.0.
A network that this device is registered to, or tried to register to.
The type of network, either Packet Switched (PS) or Circuit Switched (CS).
The technology type for this network, for example, UMTS or LTE. These values mirror the Android TelephonyManager Network Type constants.
Boolean indicating if this device is roaming on this network.
If the UE tried to register with this network and was denied, this value indicates the rejection reason. The values are defined in 3GPP TS 24.008 version 16.7.0 page 536 (Reject cause), and 3GPP TS 24.301 version 16.8.0 page 418 (EMM cause).
The properties defining the cell. The properties are different for each technology so the object type will be different depending on the accessNetworkTechnology. The name of this field will be different for each object. For example, it will be cellIdentityLte for LTE and cellIdentityNr for NR.
Contains the information about a particular GSM cell.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
Location Area Code, location code inside a PLMN, valid range 0-65535.
Cell Identity of the measured cell, valid range 0-65535.
Absolute Radio Frequency Channel Number, valid values defined in 3GPP TS 45.005 Release 10 Section 2.
Base Station Identity Code, consists of NCC and BCC, valid range 0-63 (in octal). For example, a BSIC of 38 maps to an NCC of 4 and BCC of 6.
Additional properties are allowed.
Contains the information about a particular CDMA cell.
System Identification Number, 15 bit number that represents the service provider(s) a base station provides service to.
Network Identification Number, 16 bit number that represents the network within a SID.
Base Station Identifier. Exclusively identifies a base station under a SID/NID.
Additional properties are allowed.
Contains the information about a particular UMTS cell.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
Location Area Code, location code inside a PLMN, valid range 0-65535.
The Cell Identity of the measured cell, 28 bits, the RNC-ID is the first 12 bits, and the C-ID is the last 16 bits, valid range 0-268435455. Defined in 3GPP TS 25.331.
UTRA Absolute Radio Frequency Channel Number (Downlink), valid range 0-13096, defined in 3GPP TS 25.101 and 3GPP TS 25.102.
Primary Scrambling Code, valid range 0-511.
Additional properties are allowed.
Contains the information about a particular LTE cell.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
Tracking Area Code, location code inside a PLMN, valid range 0-65535.
ECI, the Cell Identity of the measured cell, 28 bits. The Macro eNB ID is the first 20 bits of the Cell Identity and the last 8 bits represent the sector. Valid range 0-268435455.
Downlink E-UTRA Absolute Radio Frequency Channel Number, valid range 0-262143, defined in 3GPP TS 36.331 version 14.2.2 Release 14 page 567.
Physical Cell Identity, valid range 0-503.
Additional properties are allowed.
Contains the information about a particular NR cell.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
NR Tracking Area Code, location code inside a PLMN, valid range 0 - 16,777,215 as defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 643.
NCI, the Cell Identity of the measured cell, 36 bits. The gNB ID is the first 22-32 bits of the NCI and the remaining bits represent the sector. Valid range 0 - 68,719,476,735 as defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 370.
Downlink NR Absolute Radio Frequency Channel Number, valid range 0 - 3,279,165, defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 784.
NR Physical Cell Identity, valid range 0-1007 as defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 503.
Additional properties are allowed.
Additional properties are allowed.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "PhoneState",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"recordNumber": 1,
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"simState": "READY",
"simOperator": "311480",
"slot": 2,
"networkRegistrationInfo": [
[
{
"domain": "CS",
"accessNetworkTechnology": "LTE",
"roaming": false,
"rejectCause": 0,
"cellIdentityLte": {
"mcc": 311,
"mnc": 480,
"tac": 52803,
"eci": 52824577,
"earfcn": 5230,
"pci": 234
}
},
{
"domain": "PS",
"accessNetworkTechnology": "LTE",
"roaming": false,
"rejectCause": 0,
"cellIdentityLte": {
"mcc": 311,
"mnc": 480,
"tac": 52803,
"eci": 52824577,
"earfcn": 5230,
"pci": 234
}
}
]
]
}
}
The cellular_ota_message topic/channel is where Over The Air (OTA) cellular (LTE, UMTS/WCDMA) messages can be published. For MQTT, set the MQTT topic as "cellular_ota_message" and then publish a JSON message representing an OTA Cellular message.
Accepts one of the following messages:
Represents a raw GSM RR Signaling message sent Over The Air (OTA) between a GSM BTS and a GSM ME.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be GsmSignaling.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The channel type that this message was sent on. The channel type represents the logical channel that the raw cellular message was sent over.
The raw cellular message bytes encoded in base64. The bytes in this field are the raw message bytes captured from the Over The Air (OTA) cellular radio frame with the appropriate PCAP headers as the prefix. In other words, the bytes are the same bytes that would show up in a pcap file for a cellular message. The general structure consists of a PCAP record header, PPI header, layer 3 header, layer 4 header, a GSMTAP header, followed by the cellular OTA message. Using this structure means that Wireshark, tshark or any other tool that can read GSMTAP pcap records can easily parse out the contents of this message. For more details see the Network Survey+ Android App Source Code.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "GsmSignaling",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"channelType": "BCCH",
"pcapRecord": "FA4wAO0BawMAAFk5BQAAAAAJAEABfGtfkSAAAA=="
}
}
Represents a raw UMTS NAS message sent Over The Air (OTA) between a UMTS NodeB and a UMTS UE.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be UmtsNas.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The raw cellular message bytes encoded in base64. The bytes in this field are the raw message bytes captured from the Over The Air (OTA) cellular radio frame with the appropriate PCAP headers as the prefix. In other words, the bytes are the same bytes that would show up in a pcap file for a cellular message. The general structure consists of a PCAP record header, PPI header, layer 3 header, layer 4 header, a GSMTAP header, followed by the cellular OTA message. Using this structure means that Wireshark, tshark or any other tool that can read GSMTAP pcap records can easily parse out the contents of this message. For more details see the Network Survey+ Android App Source Code.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "UmtsNas",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"pcapRecord": "FA4wAO0BawMAAFk5BQAAAAAJAEABfGtfkSAAAA=="
}
}
Represents a raw WCDMA RRC message sent Over The Air (OTA) between a UMTS NodeB and a UMTS UE.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be WcdmaRrc.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The channel type that this message was sent on. The channel type represents the logical channel that the raw cellular message was sent over.
The raw cellular message bytes encoded in base64. The bytes in this field are the raw message bytes captured from the Over The Air (OTA) cellular radio frame with the appropriate PCAP headers as the prefix. In other words, the bytes are the same bytes that would show up in a pcap file for a cellular message. The general structure consists of a PCAP record header, PPI header, layer 3 header, layer 4 header, a GSMTAP header, followed by the cellular OTA message. Using this structure means that Wireshark, tshark or any other tool that can read GSMTAP pcap records can easily parse out the contents of this message. For more details see the Network Survey+ Android App Source Code.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "WcdmaRrc",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"channelType": "BCCH_BCH",
"pcapRecord": "FA4wAO0BawMAAFk5BQAAAAAJAEABfGtfkSAAAA=="
}
}
Represents a raw LTE RRC message sent Over The Air (OTA) between an LTE eNodeB and an LTE UE.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be LteRrc.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The channel type that this message was sent on. The channel type represents the logical channel that the raw cellular message was sent over.
The raw cellular message bytes encoded in base64. The bytes in this field are the raw message bytes captured from the Over The Air (OTA) cellular radio frame with the appropriate PCAP headers as the prefix. In other words, the bytes are the same bytes that would show up in a pcap file for a cellular message. The general structure consists of a PCAP record header, PPI header, layer 3 header, layer 4 header, a GSMTAP header, followed by the cellular OTA message. Using this structure means that Wireshark, tshark or any other tool that can read GSMTAP pcap records can easily parse out the contents of this message. For more details see the Network Survey+ Android App Source Code.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "LteRrc",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"channelType": "BCCH_BCH",
"pcapRecord": "FA4wAO0BawMAAFk5BQAAAAAJAEABfGtfkSAAAA=="
}
}
Represents a raw LTE NAS message sent Over The Air (OTA) between an LTE eNodeB and an LTE UE.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be LteNas.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The channel type that this message was sent on. The channel type represents the logical channel that the raw cellular message was sent over.
The raw cellular message bytes encoded in base64. The bytes in this field are the raw message bytes captured from the Over The Air (OTA) cellular radio frame with the appropriate PCAP headers as the prefix. In other words, the bytes are the same bytes that would show up in a pcap file for a cellular message. The general structure consists of a PCAP record header, PPI header, layer 3 header, layer 4 header, a GSMTAP header, followed by the cellular OTA message. Using this structure means that Wireshark, tshark or any other tool that can read GSMTAP pcap records can easily parse out the contents of this message. For more details see the Network Survey+ Android App Source Code.
Additional properties are allowed.
Additional properties are allowed.
{
"version": "1.5.0",
"messageType": "LteNas",
"data": {
"deviceSerialNumber": "1234",
"deviceName": "Craxiom Pixel",
"deviceTime": "1996-12-19T16:39:57-08:00",
"latitude": 51.470334,
"longitude": -0.486594,
"altitude": 13.3,
"speed": 9.3,
"missionId": "Survey1 20200724-154325",
"accuracy": 40,
"heading": 32.7,
"pitch": -0.1,
"roll": 0.15,
"fieldOfView": 40,
"receiverSensitivity": -50,
"channelType": "PLAIN",
"pcapRecord": "FA4wAO0BawMAAFk5BQAAAAAJAEABfGtfkSAAAA=="
}
}
Represents information recorded about a GSM tower at a particular time and geographic location.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be GsmRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. For simple frequency sweeps, all detections in the same sweep should have the same group number. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
Location Area Code, location code inside a PLMN, valid range 0-65535.
Cell Identity of the measured cell, valid range 0-65535.
Absolute Radio Frequency Channel Number, valid values defined in 3GPP TS 45.005 Release 10 Section 2.
Base Station Identity Code, consists of NCC and BCC, valid range 0-63 (in octal). For example, a BSIC of 38 maps to an NCC of 4 and BCC of 6.
The signal strength of the received signal in dBm.
Timing Advance, corresponding to the timing offset a mobile phone needs to use when transmitting a signal to the tower.
Boolean indicating if this record represents a serving cell record, or a neighbor cell record. If the field is unset then it is unknown if this record is for the serving cell or a neighbor cell. A value of true indicates that the record represents a serving cell, a value of false indicates a neighbor record.
The company providing the cellular service.
The slot number of the SIM card or radio slot that this record was captured from. This enables support for multiple SIM cards in a single device or multiple radios in a single device. Numbering does not start at 0 or 1, and can be any arbitrary number. Therefore, the number does not reveal anything about the number of SIM cards or radio slots in the device. This field is optional, and if it is not present that is an indication that the device only has a single SIM card or radio (but the presence of this field does not indicate multiple SIM cards or radios). Added in version 0.15.0.
Additional properties are allowed.
Additional properties are allowed.
Represents information recorded about a CDMA tower at a particular time and geographic location.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be CdmaRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. For simple frequency sweeps, all detections in the same sweep should have the same group number. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
System Identification Number, 15 bit number that represents the service provider(s) a base station provides service to.
Network Identification Number, 16 bit number that represents the network within a SID.
A collection of one or more base stations treated as a unit when determining whether a mobile station should perform zone-based registration.
Base Station Identifier. Exclusively identifies a base station under a SID/NID.
Channel number that corresponds to a frequency.
Pseudo Random Noise, 0-511, used to differentiate sectors on base stations.
The signal strength of the received signal in dBm.
Measure of the quality / cleanliness of the signal from the tower to the modem (signal to noise). Energy per chip to Interference power ratio measured in dB.
Boolean indicating if this record represents a serving cell record, or a neighbor cell record. If the field is unset then it is unknown if this record is for the serving cell or a neighbor cell. A value of true indicates that the record represents a serving cell, a value of false indicates a neighbor record.
The company providing the cellular service.
The slot number of the SIM card or radio slot that this record was captured from. This enables support for multiple SIM cards in a single device or multiple radios in a single device. Numbering does not start at 0 or 1, and can be any arbitrary number. Therefore, the number does not reveal anything about the number of SIM cards or radio slots in the device. This field is optional, and if it is not present that is an indication that the device only has a single SIM card or radio (but the presence of this field does not indicate multiple SIM cards or radios). Added in version 0.15.0.
Additional properties are allowed.
Additional properties are allowed.
Represents information recorded about a UMTS NodeB at a particular time and geographic location.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be UmtsRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. For simple frequency sweeps, all detections in the same sweep should have the same group number. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
Location Area Code, location code inside a PLMN, valid range 0-65535.
The Cell Identity of the measured cell, 28 bits, the RNC-ID is the first 12 bits, and the C-ID is the last 16 bits, valid range 0-268435455. Defined in 3GPP TS 25.331.
UTRA Absolute Radio Frequency Channel Number (Downlink), valid range 0-13096, defined in 3GPP TS 25.101 and 3GPP TS 25.102.
Primary Scrambling Code, valid range 0-511.
Reference Signal Code Power in dBm.
Received energy per chip divided by the power density in the band in dB. The value is negative as the RSCP is smaller than the total received power. Added in version 0.8.0.
The signal strength of the received signal in dBm.
Boolean indicating if this record represents a serving cell record, or a neighbor cell record. If the field is unset then it is unknown if this record is for the serving cell or a neighbor cell. A value of true indicates that the record represents a serving cell, a value of false indicates a neighbor record.
The company providing the cellular service.
The slot number of the SIM card or radio slot that this record was captured from. This enables support for multiple SIM cards in a single device or multiple radios in a single device. Numbering does not start at 0 or 1, and can be any arbitrary number. Therefore, the number does not reveal anything about the number of SIM cards or radio slots in the device. This field is optional, and if it is not present that is an indication that the device only has a single SIM card or radio (but the presence of this field does not indicate multiple SIM cards or radios). Added in version 0.15.0.
Additional properties are allowed.
Additional properties are allowed.
Represents information recorded about an LTE eNodeB at a particular time and geographic location.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be LteRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. For simple frequency sweeps, all detections in the same sweep should have the same group number. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
Tracking Area Code, location code inside a PLMN, valid range 0-65535.
ECI, the Cell Identity of the measured cell, 28 bits. The Macro eNB ID is the first 20 bits of the Cell Identity and the last 8 bits represent the sector. Valid range 0-268435455.
Downlink E-UTRA Absolute Radio Frequency Channel Number, valid range 0-262143, defined in 3GPP TS 36.331 version 14.2.2 Release 14 page 567.
Physical Cell Identity, valid range 0-503.
Reference Signal Received Power in dBm, valid range -44 to -140, corresponding to RSRP_97 to RSRP_00 respectively.
Reference Signal Received Quality in dB, valid range -3 to -19.5, corresponding to RSRQ_34 to RSRQ_00 respectively.
The Reference Signal Signal-to-Noise Ratio measured in dB. Range: -20 dB to +30 dB. Added in version 1.2.0.
LTE Timing Advance, corresponding to the timing offset a mobile phone needs to use when transmitting a signal to the tower. Valid range 0-1282.
The signal strength of the received signal in dBm.
Channel Quality Indicator, used by the UE to notify the serving cell (eNodeB) about the quality of the downlink channel, valid range 0-15. This field was added in version 0.14.0.
Boolean indicating if this record represents a serving cell record, or a neighbor cell record. If the field is unset then it is unknown if this record is for the serving cell or a neighbor cell. A value of true indicates that the record represents a serving cell, a value of false indicates a neighbor record.
The LTE downlink bandwidth in MHz (one of 1.4, 3, 5, 10, 15, 20).
The company providing the cellular service.
The slot number of the SIM card or radio slot that this record was captured from. This enables support for multiple SIM cards in a single device or multiple radios in a single device. Numbering does not start at 0 or 1, and can be any arbitrary number. Therefore, the number does not reveal anything about the number of SIM cards or radio slots in the device. This field is optional, and if it is not present that is an indication that the device only has a single SIM card or radio (but the presence of this field does not indicate multiple SIM cards or radios). Added in version 0.15.0.
Additional properties are allowed.
Additional properties are allowed.
Represents information recorded about a 5G NR gNodeB at a particular time and geographic location.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be NrRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. For simple frequency sweeps, all detections in the same sweep should have the same group number. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
NR Tracking Area Code, location code inside a PLMN, valid range 0 - 16,777,215 as defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 643.
NCI, the Cell Identity of the measured cell, 36 bits. The gNB ID is the first 22-32 bits of the NCI and the remaining bits represent the sector. Valid range 0 - 68,719,476,735 as defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 370.
Downlink NR Absolute Radio Frequency Channel Number, valid range 0 - 3,279,165, defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 784.
NR Physical Cell Identity, valid range 0-1007 as defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 503.
Secondary Synchronization signal Reference Signal Received Power in dBm, valid range -156 to -31, corresponding to RSRP_1 to RSRP_126 respectively as defined in 3GPP TS 38.133 version 16.5.0 Release 16 Table 10.1.6.1-1.
Secondary Synchronization signal Reference Signal Received Quality in dB, valid range -43 to 20, corresponding to SS-RSRQ_1 to SS-RSRQ_127 respectively (increments of 0.5) as defined in 3GPP TS 38.133 version 16.5.0 Release 16 Table 10.1.11.1-1.
Secondary Synchronization signal signal-to-noise and interference ratio in dB. The reporting range of SS-SINR is defined from -23 dB to 40 dB with 0.5 dB resolution, corresponding to SINR_1 to SINR_127 respectively as defined in 3GPP TS 38.133 version 16.5.0 Release 16 Table 10.1.16.1-1.
Channel State Information (CSI) Reference Signal Received Power in dBm, valid range -140 to -44, corresponding to RSRP_17 to RSRP_113 respectively as defined in 3GPP TS 38.133 version 16.5.0 Release 16 Table 10.1.6.1-1.
CSI Reference Signal Received Quality in dB.
CSI signal-to-noise and interference ratio in dB. The reporting range of CSI-SINR is defined from -23 dB to 40 dB with 0.5 dB resolution, corresponding to SINR_1 to SINR_127 respectively as defined in 3GPP TS 38.133 version 16.5.0 Release 16 Table 10.1.16.1-1.
NR Timing Advance, corresponding to the timing offset a mobile phone needs to use when transmitting a signal to the tower. Valid range 0-3846.
Boolean indicating if this record represents a serving cell record, or a neighbor cell record. If the field is unset then it is unknown if this record is for the serving cell or a neighbor cell. A value of true indicates that the record represents a serving cell, a value of false indicates a neighbor record.
The company providing the cellular service.
The slot number of the SIM card or radio slot that this record was captured from. This enables support for multiple SIM cards in a single device or multiple radios in a single device. Numbering does not start at 0 or 1, and can be any arbitrary number. Therefore, the number does not reveal anything about the number of SIM cards or radio slots in the device. This field is optional, and if it is not present that is an indication that the device only has a single SIM card or radio (but the presence of this field does not indicate multiple SIM cards or radios). Added in version 0.15.0.
Additional properties are allowed.
Additional properties are allowed.
Represents information recorded about an 802.11 Access Point at a particular time and geographic location. 802.11 Beacon frames are sent by Access Points to advertise their existence and to provide all the necessary connection information. This message represents a capture of a single 802.11 Beacon message.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be WifiBeaconRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Source MAC Address, the original source of the frame.
Destination MAC Address, the final destination of the frame.
Basic Service Set Identifier, the MAC Address of the Access Point.
Beacon Interval, in milliseconds. The rate at which beacon frames are sent from an Access Point advertising the existence of the AP.
The Service Set Type that this node belongs to.
The Service Set Identifier (aka the Wi-Fi network name), UTF-8 Encoded.
A list of data rates supported by this device separated by semicolons.
An extended list of data rates supported by this device separated by semicolons.
A list of the supported cipher suites. See IEEE Std 802.11-2012 Section 8.4.2.27.2 for more details on the 802.11 Cipher Suites.
A list of the supported Authentication and Key Management (AKM) suites. See IEEE Std 802.11-2012 Section 8.4.2.27.3 for more details on the 802.11 AKM Suites.
The encryption type used by the Access Point. This field should be kept in sync with the cipherSuites field as it is directly related.
Boolean indicating if this Access Point supports Wi-Fi Protected Setup as defined by the Wi-Fi Alliance.
Boolean indicating if this is a Passpoint Enabled Network Access Point. Passpoint is a standard defined by the Wi-Fi Alliance, not IEEE. This field was added in version 0.13.0.
The channel on which this 802.11 frame was recorded.
The frequency in MHz on which this 802.11 frame was recorded.
The Wi-Fi bandwidth in MHz (one of 20, 40, 80, 80 Plus, 160, 320).
The signal strength of the received signal in dBm.
The Signal to Noise Ratio of the received signal to the noise power measured in dB. A ratio higher than 1:1 (greater than 0 dB) indicates more signal than noise.
The type of station that sent this frame.
The 802.11 standard being employed by the device.
Additional properties are allowed.
Additional properties are allowed.
Represents information recorded about an 802.11 Probe Request at a particular time and geographic location. 802.11 Probe Request frames are sent by clients looking to discover information about an Access Point with a specific SSID. This message represents a capture of a single 802.11 Probe Request message.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be WifiProbeRequestRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Source MAC Address, the original source of the frame.
Destination MAC Address, the final destination of the frame.
Basic Service Set Identifier, the MAC Address of the Access Point.
The Service Set Identifier (aka the Wi-Fi network name), UTF-8 Encoded.
The channel on which this 802.11 frame was recorded.
The frequency in MHz on which this 802.11 frame was recorded.
The signal strength of the received signal in dBm.
The Signal to Noise Ratio of the received signal to the noise power measured in dB. A ratio higher than 1:1 (greater than 0 dB) indicates more signal than noise.
The type of station that sent this frame.
The 802.11 standard being employed by the device.
Additional properties are allowed.
Additional properties are allowed.
Represents an 802.11 deauthentication management frame. When a station wants to disassociate from another station, it invokes the deauthentication service. Deauthentication is a notification and cannot be refused. A station performs deauthentication by sending an authentication management frame (or group of frames to multiple stations) to advise of the termination of authentication.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be WifiDeauthenticationRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Source MAC Address, the original source of the frame.
Destination MAC Address, the final destination of the frame.
Basic Service Set Identifier, the MAC Address of the Access Point.
Clients may disassociate prior to powering off. APs may disassociate clients for various reasons including failure to properly authenticate, for load balancing or timeout reasons, entering a state of maintenance, etc. The 802.11-2016 standard includes a list of disassociation reasons.
The Service Set Identifier (aka the Wi-Fi network name), UTF-8 Encoded.
The channel on which this 802.11 frame was recorded.
The frequency in MHz on which this 802.11 frame was recorded.
The signal strength of the received signal in dBm.
The Signal to Noise Ratio of the received signal to the noise power measured in dB. A ratio higher than 1:1 (greater than 0 dB) indicates more signal than noise.
The type of station that sent this frame.
The 802.11 standard being employed by the device.
Additional properties are allowed.
Additional properties are allowed.
Represents information recorded about an 802.11 packet recorded at a particular time and geographic location. This message represents a capture of a 802.11 packet in PCAP format.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be WifiOtaRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The frame type of the 802.11 message. The frame type represents the type of 802.11 frame that the pcapRecord field contains. For example, a frame type of 0 represents a management frame, 1 represents a control frame, and 2 represents a data frame, and 3 represents an extension.
The subtype of the 802.11 message that corresponds to the frame type. The frame subtype represents the subtype of the 802.11 frame that the pcapRecord field contains. For example, if the frame type is 0 (aka Management) a frame subtype of 0 represents an association request, 1 represents an association response, 2 represents a reassociation request, etc.
The raw 802.11 frame bytes encoded in base64. The bytes in this field are the raw message bytes captured from the Over The Air (OTA) 802.11 radio frame with the appropriate PCAP headers as the prefix. In other words, the bytes are the same bytes that would show up in a pcap file for an 802.11 message. The general structure consists of a PCAP record header, PPI header, Radiotap header, followed by the 802.11 frame. Using this structure means that Wireshark, tshark or any other tool that can read 802.11 pcap records can easily parse out the contents of this message.
Additional properties are allowed.
Additional properties are allowed.
Represents information recorded about a Bluetooth device at a particular time and geographic location. This message represents a capture of a signal Bluetooth frame.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be BluetoothRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
Source MAC Address, the original source of the frame.
Destination MAC Address, the final destination of the frame.
The signal strength of the received signal in dBm.
The power in dBm that the device used to transmit the signal.
The Bluetooth wireless technology system that is used in this frame. See the BLUETOOTH SPECIFICATION Version 5.0 | Vol 1, Part A Section 1 (page 166) for more details.
The Bluetooth wireless technology systems that are supported be the transmitting device. See the BLUETOOTH SPECIFICATION Version 5.0 | Vol 1, Part A Section 1 (page 166) for more details.
The Bluetooth device name is the user-friendly name that a Bluetooth device exposes to remote devices. See the BLUETOOTH SPECIFICATION Version 5.0 | Vol 3, Part C Section 3.2.2 (page 1988) for more details.
The channel on which this frame was recorded. See the BLUETOOTH SPECIFICATION Version 5.0 | Vol 2, Part A Section 2 (page 325) for more details.
Additional properties are allowed.
Additional properties are allowed.
Represents information recorded about a Global Navigation Satellite System (GNSS) at a particular time and geographic location. Each record represents a single navigation message from a single satellite. These individual records are tied together using the group number field.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be GnssRecord.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. Records with the same group number indicate they were all seen in the same "scan" for GNSS space vehicles.
The model number of the device that this message originated from.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The satellite constellation associated with the record.
The identifier for the space vehicle (SV).
The carrier frequency utilized by the SV, in Hz.
The clock offset calculated by the receiver based on the space-vehicle time contained in a received navigation message, i.e. the time it took for a given navigation message to be sent from a space vehicle to the receiver's antenna, as calculated by the receiver itself.
Indicates whether this particular satellite data was used as part of the solution. A value of true indicates that the record was used in the solution, a value of false indicates that the record was not used in the solution.
The height in meters of the geoid at a given point, relative to a given reference ellipsoid, i.e. the difference in height between the 'real' surface (ignoring topographical features) and a 'modeled' surface given by a reference ellipsoid such as the one defined by WGS84. Valid range, -150.0 to 150.0.
The standard deviation of the latitude measurement in meters, where a higher value indicates a less precise position lock. For example, a 5m deviation indicates that, with 68% confidence, the latitude is within 5m of the reported position; with 95% confidence, the latitude is within 10m of the reported position, etc. This relates to the Horizontal Dilution of Precision (HDOP).
The standard deviation of the longitude measurement in meters, where a higher value indicates a less precise position lock. For example, a 5m deviation indicates that, with 68% confidence, the longitude is within 5m of the reported position; with 95% confidence, the longitude is within 10m of the reported position, etc. This relates to the Horizontal Dilution of Precision (HDOP).
The standard deviation of the altitude measurement in meters, where a higher value indicates a less precise position lock. For example, a 5m deviation indicates that, with 68% confidence, the altitude is within 5m of the reported position; with 95% confidence, the altitude is within 10m of the reported position, etc. This relates to the Vertical Dilution of Position (VDOP), and tends to be higher than the Lat/Lon standard deviations due to GNSS satellites being above GNSS receivers.
Automatic Gain Control, measured in dB. Valid range, -50.0 to 50.0
The Carrier-to-noise density in dB-Hz, which represents the measured C/N0 for the signal at the antenna inputCarrier to noise density ratio, measured in dB-Hz. Typical range: 10-50 dB-Hz. The range of possible C/N0 values is 0-63 dB-Hz to handle some edge cases.
Horizontal Dilution of Precision. Valid range, 0.0 to 50.0.
Vertical Dilution of Precision. Valid range, 0.0 to 50.0.
Additional properties are allowed.
Additional properties are allowed.
Represents a General Purpose Radio (GPR) Energy Detection event. This survey record represents a general RF/PTT energy detection (i.e. RF energy was detected above a pre-defined threshold).
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be EnergyDetection.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. For simple frequency sweeps, all detections in the same sweep should have the same group number. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The frequency, in Hz, that the radio signal was received on.
The bandwidth, in Hz, of the received signal.
The signal strength of the received signal in dBm.
The Signal to Noise Ratio of the received signal to the noise power measured in dB. A ratio higher than 1:1 (greater than 0 dB) indicates more signal than noise.
The date & time the energy/signal was detected as active. This is formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The duration of time, in seconds, that the signal was detected as active.
Additional properties are allowed.
Additional properties are allowed.
Represents a General Purpose Radio (GPR) Signal Detection event. This survey record represents RF detections where the modulation and/or signal type could be determined. If both the modulation and signal type are unknown, then use the `energy_detection_message` instead.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be SignalDetection.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
Starts at 1 and each subsequent scan should have its number incremented by 1. For simple frequency sweeps, all detections in the same sweep should have the same group number. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The frequency, in Hz, that the radio signal was received on.
The bandwidth, in Hz, of the received signal.
The signal strength of the received signal in dBm.
The Signal to Noise Ratio of the received signal to the noise power measured in dB. A ratio higher than 1:1 (greater than 0 dB) indicates more signal than noise.
The date & time the energy/signal was detected as active. This is formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The duration of time, in seconds, that the signal was detected as active.
The modulation type found on the received signal. It is appropriate to leave this blank if the modulation of the signal is unknown, but either the modulation or signalName field should be filled out. If neither of them are known then the energyDetection message should be used instead.
The modulation type found on the received signal. It is appropriate to leave this blank if the modulation of the signal is unknown, but either the modulation or signalName field should be filled out. If neither of them are known then the energyDetection message should be used instead.
Additional properties are allowed.
Additional properties are allowed.
Represents a status message sent from the device to report its current state or to act as a heartbeat. The interval of this message can vary depending on use case.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be DeviceStatus.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
The model number of the device that this message originated from.
The version of the software application that this message originated from (most likely the Network Survey Android app, but could be any other app). Added in version 1.3.0.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The percentage of battery remaining (if the device has a battery).
If present, represents that the device is in an error state.
A description of the error state that the device is in.
Additional properties are allowed.
Indicates if the device currently has the Mobile Device Management (MDM) Override option turned on. If true, the user has forced the MDM options off, if false, the user has left the MDM control in place. Added in version 0.9.0.
The latitude as obtained from the GNSS location provider. This is an additional value to the regular latitude and is only provided for comparison and analysis purposes.
The longitude as obtained from the GNSS location provider. This is an additional value to the regular longitude and is only provided for comparison and analysis purposes.
The altitude in meters above MSL as obtained from the GNSS location provider. This is an additional value to the regular altitude and is only provided for comparison and analysis purposes.
The estimated horizontal accuracy of the provided location in meters as obtained from the GNSS location provider. This is an additional value to the regular accuracy and is only provided for comparison and analysis purposes.
The latitude as obtained from the Network based location provider (e.g. Cellular and/or Wi-Fi). This is an additional value to the regular latitude and is only provided for comparison and analysis purposes.
The longitude as obtained from the Network based location provider (e.g. Cellular and/or Wi-Fi). This is an additional value to the regular longitude and is only provided for comparison and analysis purposes.
The altitude in meters above MSL as obtained from the Network based location provider (e.g. Cellular and/or Wi-Fi). This is an additional value to the regular altitude and is only provided for comparison and analysis purposes.
The estimated horizontal accuracy of the provided location in meters as obtained from the Network based location provider (e.g. Cellular and/or Wi-Fi). This is an additional value to the regular accuracy and is only provided for comparison and analysis purposes.
Additional properties are allowed.
Additional properties are allowed.
Represents the current state of the phone to include information about the currently registered networks. The interval of this message can vary depending on use case, but is typically sent when a change in the phone's state occurs, such as registering to a new network or being rejected from a network.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be PhoneState.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
Starts at 1 and each subsequent record should have its number incremented by 1.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The current state of the SIM card. The values are taken directly from android.telephony.TelephonyManager#SimState and should be kept in sync with those values. Even the order lines up exactly, which makes conversion easier.
The PLMN portion of the SIM's IMSI. This indicates the provider that issued the SIM card. The format is the MCC and MNC concatenated as one string. Can be 5 or 6 digits in length where the MCC is always 3 digits and the MNC is either 2 or 3.
The slot number of the SIM card or radio slot that this record was captured from. This enables support for multiple SIM cards in a single device or multiple radios in a single device. Numbering does not start at 0 or 1, and can be any arbitrary number. Therefore, the number does not reveal anything about the number of SIM cards or radio slots in the device. This field is optional, and if it is not present that is an indication that the device only has a single SIM card or radio (but the presence of this field does not indicate multiple SIM cards or radios). Added in version 0.15.0.
A network that this device is registered to, or tried to register to.
The type of network, either Packet Switched (PS) or Circuit Switched (CS).
The technology type for this network, for example, UMTS or LTE. These values mirror the Android TelephonyManager Network Type constants.
Boolean indicating if this device is roaming on this network.
If the UE tried to register with this network and was denied, this value indicates the rejection reason. The values are defined in 3GPP TS 24.008 version 16.7.0 page 536 (Reject cause), and 3GPP TS 24.301 version 16.8.0 page 418 (EMM cause).
The properties defining the cell. The properties are different for each technology so the object type will be different depending on the accessNetworkTechnology. The name of this field will be different for each object. For example, it will be cellIdentityLte for LTE and cellIdentityNr for NR.
Contains the information about a particular GSM cell.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
Location Area Code, location code inside a PLMN, valid range 0-65535.
Cell Identity of the measured cell, valid range 0-65535.
Absolute Radio Frequency Channel Number, valid values defined in 3GPP TS 45.005 Release 10 Section 2.
Base Station Identity Code, consists of NCC and BCC, valid range 0-63 (in octal). For example, a BSIC of 38 maps to an NCC of 4 and BCC of 6.
Additional properties are allowed.
Contains the information about a particular CDMA cell.
System Identification Number, 15 bit number that represents the service provider(s) a base station provides service to.
Network Identification Number, 16 bit number that represents the network within a SID.
Base Station Identifier. Exclusively identifies a base station under a SID/NID.
Additional properties are allowed.
Contains the information about a particular UMTS cell.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
Location Area Code, location code inside a PLMN, valid range 0-65535.
The Cell Identity of the measured cell, 28 bits, the RNC-ID is the first 12 bits, and the C-ID is the last 16 bits, valid range 0-268435455. Defined in 3GPP TS 25.331.
UTRA Absolute Radio Frequency Channel Number (Downlink), valid range 0-13096, defined in 3GPP TS 25.101 and 3GPP TS 25.102.
Primary Scrambling Code, valid range 0-511.
Additional properties are allowed.
Contains the information about a particular LTE cell.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
Tracking Area Code, location code inside a PLMN, valid range 0-65535.
ECI, the Cell Identity of the measured cell, 28 bits. The Macro eNB ID is the first 20 bits of the Cell Identity and the last 8 bits represent the sector. Valid range 0-268435455.
Downlink E-UTRA Absolute Radio Frequency Channel Number, valid range 0-262143, defined in 3GPP TS 36.331 version 14.2.2 Release 14 page 567.
Physical Cell Identity, valid range 0-503.
Additional properties are allowed.
Contains the information about a particular NR cell.
Mobile Country Code, 3 digits.
Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
NR Tracking Area Code, location code inside a PLMN, valid range 0 - 16,777,215 as defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 643.
NCI, the Cell Identity of the measured cell, 36 bits. The gNB ID is the first 22-32 bits of the NCI and the remaining bits represent the sector. Valid range 0 - 68,719,476,735 as defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 370.
Downlink NR Absolute Radio Frequency Channel Number, valid range 0 - 3,279,165, defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 784.
NR Physical Cell Identity, valid range 0-1007 as defined in 3GPP TS 38.331 version 16.2.0 Release 16 page 503.
Additional properties are allowed.
Additional properties are allowed.
Additional properties are allowed.
Additional properties are allowed.
Represents a raw LTE RRC message sent Over The Air (OTA) between an LTE eNodeB and an LTE UE.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be LteRrc.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The channel type that this message was sent on. The channel type represents the logical channel that the raw cellular message was sent over.
The raw cellular message bytes encoded in base64. The bytes in this field are the raw message bytes captured from the Over The Air (OTA) cellular radio frame with the appropriate PCAP headers as the prefix. In other words, the bytes are the same bytes that would show up in a pcap file for a cellular message. The general structure consists of a PCAP record header, PPI header, layer 3 header, layer 4 header, a GSMTAP header, followed by the cellular OTA message. Using this structure means that Wireshark, tshark or any other tool that can read GSMTAP pcap records can easily parse out the contents of this message. For more details see the Network Survey+ Android App Source Code.
Additional properties are allowed.
Additional properties are allowed.
Represents a raw LTE NAS message sent Over The Air (OTA) between an LTE eNodeB and an LTE UE.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be LteNas.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.
A unique name for this particular run of a survey. The timestamp of when the survey was started is typically included, or the mission ID might contain a user entered value to enable them to uniquely identify the purpose of this survey.
The estimated horizontal accuracy of the provided location, radial, in meters. We define horizontal accuracy as the radius of 68% confidence. In other words, if you draw a circle centered at this location's latitude and longitude, and with a radius equal to the accuracy, then there is a 68% probability that the true location is inside the circle. A value of 0 indicates there was no available horizontal accuracy.
Heading of the sensor/antenna, in degrees from true north. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Pitch of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
Roll of the sensor/antenna, in degrees from the ground plane. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The horizontal field of view of the sensor/antenna in degrees. If absent, then this assumes that the sensor has a 360 degree field of view (i.e. omnidirectional antenna). One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldofView, receiverSensitivity) to form more accurate estimates of the transmitter's position.
The minimum signal strength that a receiver can detect, in units of dBm. One can use sensor orientation (heading, pitch, roll) and sensor characteristics (fieldOfView, receiverSensitivity) to form more accurate estimates of the transmitter's position or distance from the sensor.
The channel type that this message was sent on. The channel type represents the logical channel that the raw cellular message was sent over.
The raw cellular message bytes encoded in base64. The bytes in this field are the raw message bytes captured from the Over The Air (OTA) cellular radio frame with the appropriate PCAP headers as the prefix. In other words, the bytes are the same bytes that would show up in a pcap file for a cellular message. The general structure consists of a PCAP record header, PPI header, layer 3 header, layer 4 header, a GSMTAP header, followed by the cellular OTA message. Using this structure means that Wireshark, tshark or any other tool that can read GSMTAP pcap records can easily parse out the contents of this message. For more details see the Network Survey+ Android App Source Code.
Additional properties are allowed.
Additional properties are allowed.
Represents a raw UMTS NAS message sent Over The Air (OTA) between a UMTS NodeB and a UMTS UE.
The version number of the Network Survey Messaging API that this message is based off of.
The type of message, must be UmtsNas.
The payload of this message that contains all the message data.
The unique identifier for the device that captured this record. This should be consistent and should never change.
A human readable name assigned to the device that captured this record. This value can change and is typically used as a human friendly display name.
The timestamp of when this message was created in milliseconds formatted as an RFC3339 date-time. For example, '1996-12-19T16:39:57-08:00'.
The latitude representing where this survey record was recorded.
The longitude representing where this survey record was recorded.
The altitude in meters above MSL representing where this survey record was recorded.
The speed at the time of this record capture in meters per second. This field was added in version 0.11.0. From the Network Survey Android app, this field is only present if it is detected that the device is in motion.