massage

[jack157770]

version
required
string

The version number of the Network Survey Messaging API that this message is based off of.
messageType
required
string

The type of message, must be GsmRecord.
required
object

The payload of this message that contains all the message data.
deviceSerialNumber
required
string

The unique identifier for the device that captured this record. This should be consistent and should never change.
deviceName
required
string

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.
deviceTime
required
string
format: date-time

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'.
latitude
number
format: double

The latitude representing where this survey record was recorded.
longitude
number
format: double

The longitude representing where this survey record was recorded.
altitude
number
format: float

The altitude in meters above MSL representing where this survey record was recorded.
speed
number
format: float>= 0

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.
missionId
required
string

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.
recordNumber
required
integer
format: int32>= 1

Starts at 1 and each subsequent record should have its number incremented by 1.
groupNumber
required
integer
format: int32>= 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.
accuracy
integer
format: int32>= 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.
locationAge
integer
format: int32>= 0

The age of the location fix in milliseconds. This field is optional and if it is not present that is an indication that the age of the location fix is unknown. Added in version 1.7.0.
heading
number
format: float[ -180 .. 180 ]

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
number
format: float[ -180 .. 180 ]

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
number
format: float[ -180 .. 180 ]

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.
fieldOfView
number
format: float[ 0 .. 360 ]

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.
receiverSensitivity
number
format: float>= 0

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.
mcc
integer
format: int32>= 0

Mobile Country Code, 3 digits.
mnc
integer
format: int32>= 0

Mobile Network Code, used in conjunction with MCC (PLMN) to identify a carrier, 2 to 3 digits.
lac
integer
format: int32[ 0 .. 65535 ]

Location Area Code, location code inside a PLMN, valid range 0-65535.
ci
integer
format: int32[ 0 .. 65535 ]

Cell Identity of the measured cell, valid range 0-65535.
arfcn
required
integer
format: int32>= 0

Absolute Radio Frequency Channel Number, valid values defined in 3GPP TS 45.005 Release 10 Section 2.
bsic
required
integer
format: int32[ 0 .. 63 ]

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.
signalStrength
required
number
format: float[ -200 .. 200 ]

The signal strength of the received signal in dBm.
ta
integer
format: int32[ 0 .. 63 ]

Timing Advance, corresponding to the timing offset a mobile phone needs to use when transmitting a signal to the tower.
servingCell
boolean

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.
provider
string

The company providing the cellular service.
slot
integer

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.

[christianrowlands]

I don't see a question or discussion topic in here. If you have a question please ask it. Closing.