@Track Air Interface Protocol

GSM/GPRS/GPS Tracker GL300 @Track Air Interface Protocol Application Notes: TRACGL300AN001 Revision: 1.02 [email protected] GL300 @Tracker A...
34 downloads 1 Views 3MB Size
GSM/GPRS/GPS Tracker

GL300

@Track Air Interface Protocol Application Notes: TRACGL300AN001 Revision: 1.02

[email protected]

GL300 @Tracker Air Interface Protocol

Document Title

GL300 @Tracker Air Interface Protocol

Version

1.02

Date

2013-11-26

Status

Release

Document Control ID

TRACGL300AN001

k n i l l c a i e t u n Q fide n o C

General Notes Queclink offers this information as a service to its customers, to support application and engineering efforts that use the products designed by Queclink. The information provided is based upon requirements specifically provided to Queclink by the customers. Queclink has not undertaken any independent search for additional relevant information, including any information that may be in the customer’s possession. Furthermore, system validation of this product designed by Queclink within a larger electronic system remains the responsibility of the customer or the customer’s system integrator. All specifications supplied herein are subject to change.

Copyright This document contains proprietary technical information which is the property of Queclink Limited. The copying of this document, distribution to others, and communication of the contents thereof, are forbidden without express authority. Offenders are liable to the payment of damages. All rights are reserved in the event of a patent grant or the registration of a utility model or design. All specification supplied herein are subject to change without notice at any time. Copyright © Queclink Wireless Solutions Co., Ltd. 2011

TRACGL300AN001

-1-

GL300 @Tracker Air Interface Protocol

Contents Contents ............................................................................................................................................2 Table Index........................................................................................................................................4 Figure Index ......................................................................................................................................5 0. Revision history ............................................................................................................................6 1. Overview.......................................................................................................................................8 1.1. Scope ...................................................................................................................................8 1.2. Terms and Abbreviations.....................................................................................................8 2. System Architecture ......................................................................................................................9 3. Message Description ...................................................................................................................10 3.1. Message Format ................................................................................................................10 3.2. Command and Acknowledgement.....................................................................................12 3.2.1. Quick Start Setting...............................................................................................12 3.2.2. Bearer Setting Information ..................................................................................15 3.2.3. Backend Server Register Information..................................................................16 3.2.4. Global Configuration ...........................................................................................18 3.2.5. Non movement detection .....................................................................................21 3.2.6. Time Adjustment..................................................................................................23 3.2.7. Fixed Report Information ....................................................................................24 3.2.8. Geo-Fence Information........................................................................................27 3.2.9. Speed Alarm.........................................................................................................29 3.2.10. Function Key Setting ...........................................................................................30 3.2.11. Real Time Operation............................................................................................32 3.2.12. White Call List Configuration .............................................................................33 3.2.13. Google link SMS configuration ...........................................................................35 3.2.14. Auto unlock SIM-PIN..........................................................................................36 3.2.15. Digital Input Port Settings ...................................................................................37 3.2.16. Protocol watchdog ...............................................................................................38 3.2.17. Data transfer between UART and backend server ...............................................40 3.2.18. Network Select.....................................................................................................41 3.2.19. Outside Working Hours .......................................................................................42 3.2.20. Temperature Alarm ..............................................................................................43 3.2.21. Store Command String.........................................................................................45 3.2.22. User Defined Function.........................................................................................46 3.2.23. Update configuration over the air ........................................................................48 3.2.24. Jamming Detection ..............................................................................................49 3.3. Report................................................................................................................................52 3.3.1. Position Related Report .......................................................................................52 3.3.2. Device Information Report ..................................................................................56 3.3.3. Report for Querying.............................................................................................58 3.3.4. Event Report ........................................................................................................70 3.3.5. Buffer Report .......................................................................................................83

k n i l l c a i e t u n Q fide n o C

TRACGL300AN001

-2-

GL300 @Tracker Air Interface Protocol

3.3.6. Report Google Maps hyperlink............................................................................84 3.4. Heartbeat ...........................................................................................................................85 3.5. Sever Acknowledgement...................................................................................................85 Appendix: Message Index...............................................................................................................87

k n i l l c a i e t u n Q fide n o C TRACGL300AN001

-3-

GL300 @Tracker Air Interface Protocol

Table Index TABLE 1: TERMS AND ABBREVIATIONS .........................................................................................8

k n i l l c a i e t u n Q fide n o C TRACGL300AN001

-4-

GL300 @Tracker Air Interface Protocol

Figure Index FIGURE 1: SYSTEM ARCHITECTURE................................................................................................9 FIGURE 2: @TRACKER PROTOCOL MESSAGES FLOW...............................................................10

k n i l l c a i e t u n Q fide n o C TRACGL300AN001

-5-

GL300 @Tracker Air Interface Protocol

0. Revision history Revision

Date

Author

Description of change

0.02

2012-10-12

Evan.tu

Initial

1.00

2012-10-26

Evan.Tu

2012-11-12 2012-11-14

Evan.Tu Evan.Tu

1. Add a new parameter to control whether to drive the motor in the command “AT+GTFKS” 2. Add a new command “AT+GTMON” 3.Delete the command “AT+GTFFC” protocol 4.Modified the command “AT+GTRTO” protocol 5.Modified the command “AT+GTOWH” protocol 6.Delete the report massage “+RESP:GTANT” 7.Add the report massage “+RESP:GTALS” 8.Add 4 reserved parameter in the command “AT+GTOWH” 9.Modified the parameter is reserved in the commands “AT+GTQSS 、AT+GTBSI” 10.Modified the report massage “+RESP:GTDOG” 11.Modified the description of NOTE in the command “AT+GTFRI” 12.Add the report massage “+RESP:GTDAT” 13.Add a parameter in the command “AT+GTNTS” 14.Modified the report massage “+RESP:GTALL” 15.Modified the report massage “+RESP:GTDOG” 16.Modified the decription of the parameter in command “AT+GTFKS” 17.Add the report massage “+RESP:GTMON” 18.Add the temperature alarm report function AT+GTTEM and the alarm report massage +RESP:GTTEM 19.Add a parameter in the report massage +RESP:GTINF 20.Modified the report massage “+RESP:GTMON”

k n i l l c a i e t u n Q fide n o C 2012-11-16 2012-11-19 2012-11-20

Evan.Tu Evan.Tu Evan.Tu

2012-11-26 2012-11-28

Evan.Tu Evan.Tu Evan.Tu

1.01

1.02

2012-11-29

Evan.Tu Evan.Tu

2012-12-04

Evan.Tu

2012-12-15

Evan.Tu

2013-1-5

Evan.Tu

2013-1-9

Evan.Tu

2013-1-15

Evan.Tu

2013-07-24

Evan.Tu

1.Add two new commands “AT + GTCMD” and “AT + GTUDF” 2.Add two new parameters and in the command “AT+GTSRI”

2013-08-28

Evan.Tu

1.Add a new protocol command AT + GTUPC

2013-08-30

Evan.Tu

1.Delete a protocol command AT + GTMON

2013-10-17

Evan.Tu

1.Add the report mode 6 in the command AT+GTQSS

TRACGL300AN001

-6-

GL300 @Tracker Air Interface Protocol

2.Add the mode 6 in the command AT+GTFRI 2013-11-14

Evan.Tu

1.Add a new protocol command AT+GTJDC

k n i l l c a i e t u n Q fide n o C TRACGL300AN001

-7-

GL300 @Tracker Air Interface Protocol

1. Overview

1.1. Scope The @Track Air Interface Protocol is a digital communication interface based on printable ASCII characters over SMS or GPRS which is used for all communication between the backend server and the terminal. The backend server sends a command to the terminal and then the terminal confirms with an acknowledgement message. If necessary, the terminal also sends report messages to the backend server. The purpose of this document is to describe how to build up the backend server based on the @Track Air Interface Protocol.

k n i l l c a i e t u n Q fide n o C

1.2. Terms and Abbreviations

Table 1: Terms and abbreviations Abbreviation

Description

APN

Access Point Network

ASCII GPRS GSM HDOP ICCID IP SMS TCP UDP UTC

TRACGL300AN001

American National Standard Code for Information Interchange General Packet Radio Service

Global System for Mobile Communications Horizontal Dilution of Precision Integrated Circuit Card Identity Internet Protocol

Short Message Service

Transmission Control Protocol User Datagram Protocol

Coordinated Universal Time

-8-

GL300 @Tracker Air Interface Protocol

2. System Architecture

k n i l l c a i e t u n Q fide n o C Figure 1: System architecture

The backend server can be accessed by many terminals and should have the following abilities:  The backend server should be able to access the internet and listen to the connection originating from the terminal.  The backend server should be able to support a TCP or UDP connection with the terminal. It should be able to receive data from the terminal and send data to the terminal.  The backend server should be able to receive and send SMS.

TRACGL300AN001

-9-

GL300 @Tracker Air Interface Protocol

3. Message Description

3.1. Message Format All of the @Track Air Interface Protocol messages are composed of printable ASCII characters. Each message has the following format: Message format

Message type

AT+GTXXX=,,…$

Command

+ACK:GTXXX,,,…$

Acknowledgement

+RESP:GTXXX,,,…$

Report

k n i l l c a i e t u n Q fide n o C

The entire message string ends with character ‘$’. The characters ‘XXX’ identify the deferent message. The “,,…” carry the message’s parameters. The number of parameters is different in different messages. The ASCII character ‘,’ is used to separate the neighbouring parameter characters. The parameter string may contain the ASCII characters: ‘0’-‘9’, ’a’-‘z’, ’A’-‘Z’. Detailed descriptions of each message format are located in the specific message sections.

By sending Commands to the terminal, the backend server can either configure and query the parameters of the terminal or control the terminal to perform specific actions. When the terminal receives Commands over the air, it will reply with a corresponding Acknowledgement message. According to the configuration of the parameters, the terminal can send Report messages to the backend server. Please see the following figure:

Command

Acknowledgement

Terminal

Backend Server

Report Report Report

Figure 2: @Tracker protocol messages flow

TRACGL300AN001

- 10 -

GL300 @Tracker Air Interface Protocol

When the device receives commands over the air, it supports several commands in one SMS or GPRS packet without separate symbol between two close commands. But it is necessary to make sure the total size of the several commands is not longer than 160 if the commands are sent via SMS. Here is an example to send three commands in one SMS. AT+GTFRI=gl300,1,1,,,0000,2359,60,60,,,1F,0,,,,,,,,0007$AT+GTGEO=gl300,0,3,101.412248, 21.187891,1000,600,,,,,,,,,0008$AT+GTSPD=gl300,1,5,40,30,60,,,,,,,,,,,,,,,,0009$ It includes three commands (AT+GTFRI, AT+GTGEO and AT+GTSPD) in the above message. And the terminal will handle the three commands one by one after it received the message via SMS and it will report the following three acknowledgement message to the backend server one by one.

k n i l l c a i e t u n Q fide n o C

+ACK:GTFRI,1A0102,135790246811220,,0007,20100310172830,11F0$

+ACK:GTGEO,1A0102,135790246811220,,0,0008,20100310172900,11F1$ +ACK:GTSPD,1A0102,135790246811220,,0009,20100310172930,11F2$

TRACGL300AN001

- 11 -

GL300 @Tracker Air Interface Protocol

3.2. Command and Acknowledgement 3.2.1.

Quick Start Setting

The command AT+GTQSS is used to set the GPRS parameter and backend server information in one command if all these settings are within 160 bytes, otherwise use AT+GTBSI and AT+GTSRI in two steps.  AT+GTQSS= Example: AT+GTQSS=gl300,cmnet,,,4,,,116.226.44.17,9001,116.226.44.16,9002,+8613812341234,0,1, ,,0001$

k n i l l c a i e t u n Q fide n o C

Parameter

Length (byte)

Range/Format

Default

Password

4–6

‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’

gl300

0–6

0

0|1|2

1

0 – 65535

0

APN