Features
GSat Micro Protocol
GSE Open GPS Protocol is an open standard for GPS, M2M, or SCADA device manufacturers to utilize for ease of implementation and flexibility by using a common standard. This standard is open to additional message types as suggested by the community of manufacturers of telematics devices and sensor manufacturers. The protocol is designed to include multiple blocks of data in a single transmission and can be broken into multiple transmissions as seen fit based on the message size limitations of satellite, GSM, UDP, or the protocol of your choosing. The device in the field is typically microcontroller-based, and therefore, compiling messages sequentially in an integer-based binary format is preferred.[1]
This protocol format is a collaboration of multiple vendors to utilize a common protocol or messaging structure for low-bandwidth, messaging-style applications, where there is often a custom protocol definition for every hardware vendor in the IoT market. As there are large blocks of datasets left open for definitions and expansions as new technologies come to market, continually adding additional dataset definitions to this protocol will expand as the groups of vendors continue to innovate in these markets. Feel free to reach out to any of the groups of vendors contributing to this protocol for comments, questions, reviews, or additions.
Intended future uses include LoRA[3], 4G, NB-IOT, BLE 4, BLE 4.1, BLE 5, ANT+, and RFID.
Open License
Copyright (c) 2017 Global Satellite Engineering, Inc. Permission is hereby granted, free of charge, to any person to deal in the message format without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the message format, to send and receive messages formatted according to the message format, and to permit persons to whom the message format is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies of documentation describing the message format. THE MESSAGE FORMAT IS PROVIDED "AS IS," WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT, OR OTHERWISE, ARISING FROM, OUT OF, OR IN CONNECTION WITH THE MESSAGE FORMAT OR THE USE OR OTHER DEALINGS IN THE MESSAGE FORMAT.
Supported Products
- GSatMicro
- GSatMicro X
- GSatMicro OEM
- Iridium Products[4]
- Iridium Next Products
- Inmarsat Terminals[5]
Mobile Originated Packet Structure
All data blocks are big-endian (MSB) unless otherwise specified.
| Mobile Originated Packet Structure | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Octet | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | |
| 0 | Message Block Type | ||||||||
| 0: GPS Format Reserved 10 Byte | |||||||||
| 1: Text Message | |||||||||
| 2: Settings Update | |||||||||
| 3: Interface Version Response | |||||||||
| 4: 10 Byte GPS Location | |||||||||
| 5: 18 Byte GPS Location | |||||||||
| 6: MAC Address (BLE or WiFi) |
Mobile Terminated Packet Structure
Mobile-terminated blocks always include a message or block size in the message to help simple parsers (microcontrollers) to decode and process blocks with simple loops and integer indexing.
| Mobile Terminated Packet Structure | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Octet | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | |
| 0 | Packet Version | ||||||||
| 1 | Message Block Type | ||||||||
| 0: Command | |||||||||
| 1: Text Message | |||||||||
| 2: Setting(s) Update | |||||||||
| 3: Settings Request | |||||||||
| 4: Settings Interface Version | |||||||||
| 5: Request Data |
Future Expansion
| Definitions to be released |
|---|
| Advanced text message with status acknowledgement |
| Message is a reply to a specific message |
| Message has been viewed |
| Message has been deleted |
| Message has been replied |
| Message has been delivered |
| Message is being sent to a phone number (must start with a + sign and follow E.164 numbering standard) |
| Message is being sent to an email, must contain an @ sign |
| Message is being forwarded to another unit/user, must be a number |
| Message is being sent to the portal operator, destination field is set to "0" |
| Multi-packet block |
| Sequence field |
| Message # x of y |
| Mobile-terminated 9601/2/3 = (270 bytes - 4 byte header) * 256 = 68096 byte packet maximum |
| Mobile-originated 9601/2/3 = (340 bytes - 4 byte header) * 256 = 86016 byte packet maximum |
| Mobile-terminated 9522/3 = (1890 bytes - 4 byte header) * 256 = 482816 byte packet maximum |
| Mobile-originated 9601/2/3 = (1960 bytes - 4 byte header) * 256 = 500736 byte packet maximum |
| Configuration Update block |
References
External links
[1] Integrating Wireless Sensor Networks with the Web , Walter, Colitti 2011.
[2] IOT Agenda, internet of things IoT Rouse, Margaret 2019..
[4] Iridium Encyclopedia Astronautica. Retrieved 13 September 2016.
[5] Inmarsat-About Us.