title>Data transmission interface protocol of global navigation satellite system reference station - GB/T 39607-2020 - Chinese standardNet - bzxz.net
Home > GB > Data transmission interface protocol of global navigation satellite system reference station
Data transmission interface protocol of global navigation satellite system reference station

Basic Information

Standard ID: GB/T 39607-2020

Standard Name:Data transmission interface protocol of global navigation satellite system reference station

Chinese Name: 卫星导航定位基准站数据传输和接口协议

Standard category:National Standard (GB)

state:in force

Date of Release2020-12-14

Date of Implementation:2020-12-14

standard classification number

Standard ICS number:Mathematics, Natural Sciences >> 07.040 Astronomy, Geodesy, Geography

Standard Classification Number:Comprehensive>>Surveying and Mapping>>A75 Surveying and Mapping Comprehensive

associated standards

Publication information

publishing house:China Standards Press

Publication date:2020-12-01

other information

drafter:Wang Xiaohua, Huang Chen, Yin Xiaoqing, Deng Guoqing, Li Chenggang, Bao Zhixiong, Ouyang Zhongnan, Liu Ruochen, Xie Huazhong, Zhang Lichao, Zhai Qingbin, Xiao Ping, Wang Tiejun, Li Lin, Liu Zhenyu

Drafting unit:Institute of Surveying and Mapping Standardization of the Ministry of Natural Resources, Guangzhou Zhonghaida Satellite Navigation Technology Co., Ltd., Shanghai Huace Navigation Technology Co., Ltd., Henan Provincial Bureau of Surveying, Mapping and

Focal point unit:National Geographic Information Standardization Technical Committee (SAC/TC 230)

Proposing unit:Ministry of Natural Resources of the People's Republic of China

Publishing department:State Administration for Market Regulation National Standardization Administration

Introduction to standards:

GB/T 39607-2020.Data transmission interface protocol of global navigation satellite system reference station.
1 Scope
GB/T 39607 specifies the general requirements, transmission interface, transmission data type and transmission data structure for data transmission between satellite navigation and positioning reference stations and data centers.
GB/T 39607 is applicable to data transmission between satellite navigation and positioning reference stations and data centers.
2 Abbreviations
The following abbreviations apply to this document.
BDS: BeiDou Navigation Satellite System
CGCS2000 : China Geodetic Coordinate System 2000
DOP : Dilution of Precision
FTP: File Transfer Protocol
Galileo: Galileo Navigation Satellite System
GDOP: Geometric Dilution Precision
GLONASS: Global Navigation Satellite System
GNSS : Global Navigation Satellite System
GPS: Global Positioning System
HDOP : Horizontal Dilution of Precision
NAME0183:National Marine Electronics Association Standard Protocol
Ntrip:Networked Transport of RTCM via Internet Protocol
PDOP:Position Dilution of Precision
This standard specifies the general requirements, transmission interface, transmission data type and transmission data structure for data transmission between satellite navigation and positioning base stations and data centers. This standard applies to data transmission between satellite navigation and positioning base stations and data centers.


Some standard content:

ICS07.040
National Standard of the People's Republic of China
GB/T39607—2020
Satellite navigation positioning base station
Data transmission interface protocol of global navigation satellite systemreferencestation
Released on 2020-12-14
State Administration for Market Regulation
National Standardization Administration
Implementation on 2020-12-14
GB/T39607—2020
2 Abbreviations
General requirements
Data transmission interface
Transmission data type
-General requirements
GNSS observation data
Differential correction data
Sensor data
Base station information data
5.6 Equipment information data
Satellite status data
6 Transmission data structure
Appendix A (Informative Appendix)
Implementation example of telegram data
This standard was drafted in accordance with the rules given in GB/T1.1-2009. This standard was proposed by the Ministry of Natural Resources of the People's Republic of China. This standard is under the jurisdiction of the National Technical Committee for Geographic Information Standardization (SAC/TC230). GB/T39607—2020
The drafting units of this standard are: Institute of Surveying and Mapping Standardization of the Ministry of Natural Resources, Guangzhou Zhonghaida Satellite Navigation Technology Co., Ltd., Shanghai Huace Navigation Technology Co., Ltd., Henan Provincial Bureau of Surveying, Mapping and Geographic Information, National Photoelectric Rangefinder Testing Center of the Chinese Academy of Surveying and Mapping, Chongqing Institute of Surveying and Mapping of the Ministry of Natural Resources, Wuhan University, Jilin Provincial Bureau of Surveying, Mapping and Geographic Information. The main drafters of this standard are: Wang Xiaohua, Huang Chen, Yin Xiaoqing, Deng Guoqing, Li Chenggang, Bao Zhixiong, Ouyang Zhongnan, Liu Ruochen, Xie Huazhong, Zhang Lichao, Zhai Qingbin, Xiao Ping, Zhu Tiejun, Li Sen, and Liu Zhenyu. 1
1Scope
Satellite navigation and positioning base station
Data transmission and interface protocol
GB/T39607—2020
This standard specifies the general requirements, transmission interface, transmission data type and transmission data structure for data transmission between satellite navigation and positioning base stations and data centers.
This standard applies to data transmission between satellite navigation and positioning base stations and data centers. 2
Abbreviations
The following abbreviations apply to this document.
BDS: BeiDou Navigation Satellite SystemCGCS2000: China Geodetic Co0rdinate System 2000DOP: Dilution of PrecisionFTP: File Transfer ProtocolGalileo: Galileo Navigation Satellite SystemGDOP: Geometric Dilution PrecisionGLONASS: Global Navigation Satellite SystemGNSS: Global Navigation Satellite SystemGPS: Global Positioning SystemHDOP: Horizontal Dilution of PrecisionNAME183: National Maritime Electronics Association Standard Protocol rine Electronics Association)Ntrip:Networked Transport of RTCM via Internet Protocol(Networked Transport of RTCM via Internet Protocol)
PDOP:Position Dilution of Precision(Position Dilution of Precision)QZSS:Quasi-Zenith Satellite System(Quasi-Zenith Satellite System)RTCM:Radio Technical Commission for Maritime Services(Radio Technical Commission for Maritime Services)
SBAS:Satellite-Based Augmentation System(Satellite-Based Augmentation System)TDOP:Time Dilution of Precision(Time Dilution of Precision)UTC:Coordinated Universal Time(Coordinated Universal Time)VDOP:Vertical Dilution of Precision(Vertical Dilution of Precision)General Requirements
3.1The communication protocol for data transmission between satellite navigation and positioning base station and data center should adopt TCP/IP protocol. 3.2The communication mode between satellite navigation and positioning base station and data center can adopt C/S mode and B/S mode. 3.3 The data transmission between the satellite navigation positioning base station and the data center can adopt wired or wireless communication methods. 3.4 The encoding method of data transmission between the satellite navigation positioning base station and the data center should ensure the correctness of the transmitted data. GB/T39607—2020
Certain security measures should be taken for the communication between the satellite navigation positioning base station and the data center, and the communication technology means should meet the security requirements of controlled 3.5
management.
6 The bandwidth of the communication network should meet the requirements of data transmission 3.6
4 Data transmission interface
The interface relationship of data transmission is shown in Figure 1. The direction of the arrow in the figure is the data transmission direction. The communication mode between the satellite navigation and positioning base station and the data center in the figure can adopt C/S mode and B/S mode. Note: This standard interface refers to the interface for data transmission between the satellite navigation and positioning base station and the data center 4.2
The satellite navigation and positioning base station and the data center transmit data through the communication network. The transmitted data includes GNSS observation data, differential correction data, sensor data, base station information data, equipment information data, satellite status data and other data 4.3 GNSS observation data, differential correction data, and sensor data are transmitted in one direction and sent from the satellite navigation and positioning base station to the data center at a set frequency.
4 Base station information data, equipment information data, satellite status data and other data are transmitted in two directions. 4.4
Data center
C/S, B/S
Interface relationship diagram
5Transmission data type
5.1 General requirements
The data transmitted between the satellite navigation positioning base station and the data center includes GNSS observation data, differential correction data, sensor data, base station information data, equipment information data, satellite status data and other data, see Table 1. Table 1 Transmission data type
Data type
GNSS observation data
Differential correction data
Sensor data
Base station information data
Data content
Pseudorange, signal-to-noise ratio, carrier phase, Doppler, satellite broadcast ephemeris, etc. Pseudorange, carrier phase, Doppler, satellite information, etc. for position correction Temperature, humidity, air pressure, etc. of meteorological instruments
Base station coordinates, point name, etc.
Data type
Equipment information data
Satellite status data
Other data
Table 1 (continued)
Data content
GB/T39607—2020||t t||Firmware version information, receiver registration information, power status information, timer power on/off parameters, storage space information, receiver temperature, antenna information, meteorological instrument information, communication interface parameters, file storage parameters, etc. Satellite system UTC time, satellite week second, number of tracked satellites, basic satellite status, satellite system activation status, altitude cutoff angle, DOP data, etc.
Other special information
The frequency of data transmission between the satellite navigation positioning base station and the data center is determined according to different data types, see Table 2, Table 2 Data transmission frequency
Data type
GNSS observation data
Differential correction data
Sensor data
Base station information data||t t||Equipment information data
Satellite status data
Other data
It is recommended to use 1Hz, which can be set according to application requirements. It is recommended to use 1Hz, which can be set according to application requirements. It is recommended to transmit once every 60s, which can be set according to application requirements. Transmission when triggered
Transmission when triggered
Transmission when triggered
Transmission when triggered
Transmission frequency
The data format of data transmitted between the satellite navigation and positioning base station and the data center is determined according to different data types, see Table 3. Table 3 Transmission data format
Data type
GNSS observation data
Differential correction data
Sensor data
Base station information Data
Equipment information data
Satellite status data
Other data
Data format
It is advisable to use international standard formats, such as RTCM, NAME0183, or a custom format. It is advisable to use international standard formats, such as RTCM
It is advisable to be consistent with the original observation data
See the relevant provisions of 6.2
See the relevant provisions of 6.2
See the relevant provisions of 6.2
See the relevant provisions of 6.2
GNSS observation data
GNSS observation data format should adopt international standard formats, such as RTCM, NAMEO183, etc., or a manufacturer-defined data format can be used. The data transmission frequency should be 1Hz, which can also be set as needed, GB/T39607—2020
Note: GNSS observation data includes original observation data, satellite ephemeris data and navigation positioning data. 5.3
Differential correction data
The data format of differential correction data should adopt international standard format, such as RTCM, and the data transmission frequency should adopt 1Hz, which can also be set as needed.
Sensor data
The data format of sensor data should be consistent with the original observation data, and the data transmission should be transmitted every 605, which can also be set as needed. Reference station information data
The data content of reference station information data is shown in Table 4, the data frequency is transmitted when triggered, and the data format is shown in 6.2. Note: Reference station information data includes reference station information, reference station spatial rectangular coordinates, and reference station geodetic coordinates. Table 4 Base station information data content
Data type
Base station basic information
Base station spatial rectangular
Base station geodetic coordinates
Equipment information data
Site name, site code, site registration number and other information Main data content
X coordinate, Y coordinate, Z coordinate (CGCS2000 coordinate system) positioning status, geodetic longitude B, geodetic latitude L, geodetic height H The data content of the equipment information data is shown in Table 5. The data frequency is transmitted when triggered. The data format is shown in 6.2. Note: Device information data includes firmware version information, receiver registration information, power status information, timed power on/off parameters, storage space information, receiver temperature, antenna information, meteorological instrument information, observation data parameters, network parameters, audit parameters, file storage parameters, etc. Table 5 Device information data content
Data type
Firmware version information
Receiver registration information
Power status information
Timed power on/off parameters
Storage space information
Receiver temperature
Antenna information
Meteorological instrument information
Observation data parameters
Main data content
Firmware version, firmware version date, equipment failure, time log information, etc. Receiver registration code, whether registration has expired, registration validity date information, etc. Power supply mode, battery power, battery voltage, battery current, battery capacity, remaining battery time, battery temperature, etc. Timed power on/off switch, power on time, power off time, etc. Total internal storage capacity, remaining internal storage capacity, total U disk capacity, remaining U disk capacity, total SD card capacity, remaining SD card capacity, etc.
Receiver temperature
Antenna type, antenna height, antenna gain adjustment, etc. Instrument name, instrument number, baud rate, temperature sensor ID, humidity sensor ID, pressure sensor ID, etc. Data types (raw observation data, differential correction data, sensor data) and data frequency, etc.
Network parameters
Serial port parameters
File storage parameters
Satellite status data
Table 5 (continued)wwW.bzxz.Net
Main data content
GB/T39607-—2 020
Network connection status, network transmission ID number, server IP address version number, server IP address, server port number, server domain name, transmission protocol, Ntrip mount point, user name, password, etc. Serial port switch, serial port number, data type, etc. File name, start date switch, start time switch, start date, start time, recording duration, loop storage, storage method, recording method, data frequency, file format, FTP server name, etc. The data content of satellite status data is shown in Table 6. The data frequency is transmitted when triggered, and the data format is shown in 6.2. Note: Satellite status data includes satellite system UTC time, satellite week second, number of tracked satellites, satellite basic status information, satellite activation status information, altitude cutoff angle, DOP data, etc.
Satellite status data content
Data type
Satellite system UTC time
Satellite week seconds
Number of tracked satellites
Basic satellite status information
Satellite activation status information
Altitude cutoff angle
DOP data
Transmission data structure
Main data content
Satellite system UTC date, satellite system UTC time, etc.GPS satellite week seconds, BDS satellite week seconds, Galileo satellite The satellite numbers of BDS, GPS, GLONASS, Galileo, SBAS, QZSS and other satellite systems tracked by Zhou Miao, etc. Satellite number, satellite system number, altitude angle, azimuth angle, signal-to-noise ratio, etc. The activation status information of BDS, GPS, GLONASS, Galileo, SBAS, QZSS and other satellite systems Altitude cutoff angle
HDOP, VDOP, PDOP, TDOP, GDOP and other limit difference information The data format of original observation data, differential correction data, and sensor data is shown in Table 3. The base station information data, equipment information data, satellite status data and other data are transmitted by telegram, which is encoded in binary 6.2
system. The data structure of the telegram is shown in Figure 2.For implementation examples, see Appendix A. The specific requirements are as follows: Message header
Data segment
Data structure diagram
Message header: The message header should include but not be limited to the following contents: Start identifier: The start identifier of the message;
Check area
Message number: The unique identifier of the message, used to distinguish the basic information such as the type and function of the message, and should be numbered uniformly; 5
GB/T39607—2020
Data segment length: The length of the data segment.
Data segment: The content of the data segment of each message is different, see 5.5.5.6, 5.7. b)
Check area: The cyclic residual check code is used for verification, and the bit error rate should be guaranteed to meet the data transmission requirements. The verified data segment starts from the first byte after the start identifier and ends at the parameter segment. A.1
Basic provisions
Message structure
Appendix A
(Informative Appendix)
Implementation example of message data
GB/T39607—2020
This appendix is ​​an extension of 6.2 message structure, including start identifier, protocol version number, reserved field, message number, time tag, data segment length, data segment and checksum. The message structure is shown in Table A.1. Table A.1
Message structure
Start mark
Protocol version number
Message header
Data segment
Check area
Reserved field
Message number
Time label
Data segment length
Data segment
Check code
Data type
Number of bytes
Content description
Marks the beginning of a message, the content is $S (0x2424) the protocol version number followed by the message. The version number adopts the form of "major version number.minor version number", the first byte is the major version number, and the second byte is the minor version number. The protocol version number of this appendix is ​​1.0 (0x0100)
A user-defined field is reserved for users. When this field is empty, the value is 0 (0x0000) Unique identifier for each message
The time when the message is sent, synchronized with UTC. The same time tag when the same message is sent repeatedly Number of bytes in the data segment
The data segment consists of parameter items. Parameter items generally have a fixed length. For parameters with non-fixed lengths, the corresponding length parameter item is used to specify the specific length of the parameter. When a parameter is missing, the value of its length parameter item is 0 (0x0000).
The parameter items of each message are different according to the data content. The cyclic redundancy check code is used for verification. The verified data segment starts from the first byte after the start identifier and ends at the end of the parameter segment
The message is transmitted in bytes, using the data type specified in Table A.2. Table A.2
UShort
Number of bytes
Data type list
Signed character type, the value range is -2\~2—1Unsigned character type, the value range is 0~28Pointer type
Char type array, N is the array length
Signed short integer type, the value range is -215~215-1Unsigned short integer type The value range is 0~216-1GB/T39607—2020
Double
Write method
Number of bytes
Table A.2 ( (continued)
Signed integer, value range is 21~231-1Unsigned integer, value range is 0~22-1Signed single precision floating point type. Value range is -2127~2127-1Signed double precision floating point type, value range is -2102~21023-1The message is written in high-order first mode, that is, the high byte of the data is stored at the low address, and the low byte is stored at the high addressA.2
Message content
The message grouping of base station information data, equipment information data and satellite status data is shown in Table A3. Each message group consists of two or four messages. The setting message is completed by the data center to control the base station and set various parameters of the base station; the response message is completed by the base station to return the result status of the setting message; the acquisition message is completed by the data center to obtain various information and data of the base station; the reply message is completed by the base station to return the information required to obtain the message. Table A.3
Data type
Base station information data
Device information data
Message grouping
Message group list
Base station mode and coordinate setting Get the current positioning coordinates and positioning status of the base station in the telegram group Get the firmware version information of the telegram group Get the telegram group
Receiver registration
Receiver registration period information acquisition
Power status acquisition
Timed power on/off setting and acquisition
GNSS board reset
System restart
Restore factory settings
Storage space acquisition
Antenna information setting and acquisition
Meteorological instrument parameter setting and acquisition
Meteorological instrument data setting and acquisition Get
Set and obtain meteorological data fusion
Set and obtain observation data
Including setting, response, obtaining, replying to telegrams including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including setting, response, obtaining, replying to telegrams including setting, response to telegrams
Including setting, response to telegrams
Including setting, response to telegrams
Including setting, response to telegrams||t t||Including acquisition and reply message
Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message A.3
Data type
Equipment information data
Satellite status data
Message example
Table A.3 (continued)
Message grouping
Ephemeris data setting and acquisition
Difference Correction data setting and acquisition
GNSS receiver navigation positioning data setting and acquisition Mobile network dial-up connection
Mobile network dial-up status acquisition
Wired network data transmission setting and acquisition
Wired network connection status acquisition
Serial port parameter setting and acquisition
Serial port data transmission parameter setting and acquisition
File record
File deletion
FTP push setting
Data output off
Satellite system activation status Setting and obtaining
Satellite altitude cutoff angle setting and obtaining
Satellite system UTC time obtaining
Satellite status information obtaining
DOP value obtaining
Base station mode and coordinate setting and obtaining
The setting should meet the following requirements:
Function: Set the base station startup mode and coordinates; Message number: 0x020101;
Data segment: See Figure A.1, parameters see Table A.4; GB/T39607-—2020
Including setting , response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including getting, reply telegram
including setting, response, get, reply telegram including getting, reply telegram
including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response telegram
including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response telegram
including setting, response, get, reply telegram including setting, response telegram| |tt||Including setting, response, acquisition, reply messageIncluding setting, response, acquisition, reply messageIncluding acquisition, reply message
Including acquisition, reply message
Including acquisition, reply message
Message example: 0x2424010000000201015C107B9A001902C13A035AF8C6F7E84152F9FC113A3405414B72E450FEF5CF0CC745CB, message description see Table A.5. Base station startup mode
X coordinate
Y coordinate
Z coordinate
Base station mode and coordinate setting message parameter segment structure diagram7. b)
Check area: The cyclic residual check code is used for checking. The bit error rate should be guaranteed to meet the data transmission requirements. The check data segment starts from the first byte after the start mark and ends at the parameter segment. A.1
Basic provisions
Message structure
Appendix A
(Informative Appendix)
Implementation example of message data
GB/T39607—2020
This appendix is ​​expanded on the basis of 6.2 message structure, including the start mark, protocol version number, reserved field, message number, time tag, data segment length, data segment and check code. The message structure is shown in Table A.1. Table A.1
Message structure
Start mark
Protocol version number
Message header
Data segment
Check area
Reserved field
Message number
Time label
Data segment length
Data segment
Check code
Data type
Number of bytes
Content description
Marks the beginning of a message, the content is $S (0x2424) the protocol version number followed by the message. The version number adopts the form of "major version number.minor version number", the first byte is the major version number, and the second byte is the minor version number. The protocol version number of this appendix is ​​1.0 (0x0100)
A user-defined field is reserved for users. When this field is empty, the value is 0 (0x0000) Unique identifier for each message
The time when the message is sent, synchronized with UTC. The same time tag when the same message is sent repeatedly Number of bytes in the data segment
The data segment consists of parameter items. Parameter items generally have a fixed length. For parameters with non-fixed lengths, the corresponding length parameter item is used to specify the specific length of the parameter. When a parameter is missing, the value of its length parameter item is 0 (0x0000).
The parameter items of each message are different according to the data content. The cyclic redundancy check code is used for verification. The verified data segment starts from the first byte after the start identifier and ends at the end of the parameter segment
The message is transmitted in bytes, using the data type specified in Table A.2. Table A.2
UShort
Number of bytes
Data type list
Signed character type, the value range is -2\~2—1Unsigned character type, the value range is 0~28Pointer type
Char type array, N is the array length
Signed short integer type, the value range is -215~215-1Unsigned short integer type The value range is 0~216-1GB/T39607—2020
Double
Write method
Number of bytes
Table A.2 ( (continued)
Signed integer, value range is 21~231-1Unsigned integer, value range is 0~22-1Signed single precision floating point type. Value range is -2127~2127-1Signed double precision floating point type, value range is -2102~21023-1The message is written in high-order first mode, that is, the high byte of the data is stored at the low address, and the low byte is stored at the high addressA.2
Message content
The message grouping of base station information data, equipment information data and satellite status data is shown in Table A3. Each message group consists of two or four messages. The setting message is completed by the data center to control the base station and set various parameters of the base station; the response message is completed by the base station to return the result status of the setting message; the acquisition message is completed by the data center to obtain various information and data of the base station; the reply message is completed by the base station to return the information required to obtain the message. Table A.3
Data type
Base station information data
Device information data
Message grouping
Message group list
Base station mode and coordinate setting Get the current positioning coordinates and positioning status of the base station in the telegram group Get the firmware version information of the telegram group Get the telegram group
Receiver registration
Receiver registration period information acquisition
Power status acquisition
Timed power on/off setting and acquisition
GNSS board reset
System restart
Restore factory settings
Storage space acquisition
Antenna information setting and acquisition
Meteorological instrument parameter setting and acquisition
Meteorological instrument data setting and acquisition Get
Set and obtain meteorological data fusion
Set and obtain observation data
Including setting, response, obtaining, replying to telegrams including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including setting, response, obtaining, replying to telegrams including setting, response to telegrams
Including setting, response to telegrams
Including setting, response to telegrams
Including setting, response to telegrams||t t||Including acquisition and reply message
Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message A.3
Data type
Equipment information data
Satellite status data
Message example
Table A.3 (continued)
Message grouping
Ephemeris data setting and acquisition
Difference Correction data setting and acquisition
GNSS receiver navigation positioning data setting and acquisition Mobile network dial-up connection
Mobile network dial-up status acquisition
Wired network data transmission setting and acquisition
Wired network connection status acquisition
Serial port parameter setting and acquisition
Serial port data transmission parameter setting and acquisition
File record
File deletion
FTP push setting
Data output off
Satellite system activation status Setting and obtaining
Satellite altitude cutoff angle setting and obtaining
Satellite system UTC time obtaining
Satellite status information obtaining
DOP value obtaining
Base station mode and coordinate setting and obtaining
The setting should meet the following requirements:
Function: Set the base station startup mode and coordinates; Message number: 0x020101;
Data segment: See Figure A.1, parameters see Table A.4; GB/T39607-—2020
Including setting , response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including getting, reply telegram
including setting, response, get, reply telegram including getting, reply telegram
including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response telegram
including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response telegram
including setting, response, get, reply telegram including setting, response telegram| |tt||Including setting, response, acquisition, reply messageIncluding setting, response, acquisition, reply messageIncluding acquisition, reply message
Including acquisition, reply message
Including acquisition, reply message
Message example: 0x2424010000000201015C107B9A001902C13A035AF8C6F7E84152F9FC113A3405414B72E450FEF5CF0CC745CB, message description see Table A.5. Base station startup mode
X coordinate
Y coordinate
Z coordinate
Base station mode and coordinate setting message parameter segment structure diagram7. b)
Check area: The cyclic residual check code is used for checking. The bit error rate should be guaranteed to meet the data transmission requirements. The check data segment starts from the first byte after the start mark and ends at the parameter segment. A.1
Basic provisions
Message structure
Appendix A
(Informative Appendix)
Implementation example of message data
GB/T39607—2020
This appendix is ​​expanded on the basis of 6.2 message structure, including the start mark, protocol version number, reserved field, message number, time tag, data segment length, data segment and check code. The message structure is shown in Table A.1. Table A.1
Message structure
Start mark
Protocol version number
Message header
Data segment
Check area
Reserved field
Message number
Time label
Data segment length
Data segment
Check code
Data type
Number of bytes
Content description
Marks the beginning of a message, the content is $S (0x2424) the protocol version number followed by the message. The version number adopts the form of "major version number.minor version number", the first byte is the major version number, and the second byte is the minor version number. The protocol version number of this appendix is ​​1.0 (0x0100)
A user-defined field is reserved for users. When this field is empty, the value is 0 (0x0000) Unique identifier for each message
The time when the message is sent, synchronized with UTC. The same time tag when the same message is sent repeatedly Number of bytes in the data segment
The data segment consists of parameter items. Parameter items generally have a fixed length. For parameters with non-fixed lengths, the corresponding length parameter item is used to specify the specific length of the parameter. When a parameter is missing, the value of its length parameter item is 0 (0x0000).
The parameter items of each message are different according to the data content. The cyclic redundancy check code is used for verification. The verified data segment starts from the first byte after the start identifier and ends at the end of the parameter segment
The message is transmitted in bytes, using the data type specified in Table A.2. Table A.2
UShort
Number of bytes
Data type list
Signed character type, the value range is -2\~2—1Unsigned character type, the value range is 0~28Pointer type
Char type array, N is the array length
Signed short integer type, the value range is -215~215-1Unsigned short integer type The value range is 0~216-1GB/T39607—2020
Double
Write method
Number of bytes
Table A.2 ( (continued)
Signed integer, value range is 21~231-1Unsigned integer, value range is 0~22-1Signed single precision floating point type. Value range is -2127~2127-1Signed double precision floating point type, value range is -2102~21023-1The message is written in high-order first mode, that is, the high byte of the data is stored at the low address, and the low byte is stored at the high addressA.2
Message content
The message grouping of base station information data, equipment information data and satellite status data is shown in Table A3. Each message group consists of two or four messages. The setting message is completed by the data center to control the base station and set various parameters of the base station; the response message is completed by the base station to return the result status of the setting message; the acquisition message is completed by the data center to obtain various information and data of the base station; the reply message is completed by the base station to return the information required to obtain the message. Table A.3
Data type
Base station information data
Device information data
Message grouping
Message group list
Base station mode and coordinate setting Get the current positioning coordinates and positioning status of the base station in the telegram group Get the firmware version information of the telegram group Get the telegram group
Receiver registration
Receiver registration period information acquisition
Power status acquisition
Timed power on/off setting and acquisition
GNSS board reset
System restart
Restore factory settings
Storage space acquisition
Antenna information setting and acquisition
Meteorological instrument parameter setting and acquisition
Meteorological instrument data setting and acquisition Get
Set and obtain meteorological data fusion
Set and obtain observation data
Including setting, response, obtaining, replying to telegrams including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including setting, response, obtaining, replying to telegrams including setting, response to telegrams
Including setting, response to telegrams
Including setting, response to telegrams
Including setting, response to telegrams||t t||Including acquisition and reply message
Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message A.3
Data type
Equipment information data
Satellite status data
Message example
Table A.3 (continued)
Message grouping
Ephemeris data setting and acquisition
Difference Correction data setting and acquisition
GNSS receiver navigation positioning data setting and acquisition Mobile network dial-up connection
Mobile network dial-up status acquisition
Wired network data transmission setting and acquisition
Wired network connection status acquisition
Serial port parameter setting and acquisition
Serial port data transmission parameter setting and acquisition
File record
File deletion
FTP push setting
Data output off
Satellite system activation status Setting and obtaining
Satellite altitude cutoff angle setting and obtaining
Satellite system UTC time obtaining
Satellite status information obtaining
DOP value obtaining
Base station mode and coordinate setting and obtaining
The setting should meet the following requirements:
Function: Set the base station startup mode and coordinates; Message number: 0x020101;
Data segment: See Figure A.1, parameters see Table A.4; GB/T39607-—2020
Including setting , response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including getting, reply telegram
including setting, response, get, reply telegram including getting, reply telegram
including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response telegram
including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response telegram
including setting, response, get, reply telegram including setting, response telegram| |tt||Including setting, response, acquisition, reply messageIncluding setting, response, acquisition, reply messageIncluding acquisition, reply message
Including acquisition, reply message
Including acquisition, reply message
Message example: 0x2424010000000201015C107B9A001902C13A035AF8C6F7E84152F9FC113A3405414B72E450FEF5CF0CC745CB, message description see Table A.5. Base station startup mode
X coordinate
Y coordinate
Z coordinate
Base station mode and coordinate setting message parameter segment structure diagram1
Message structure
Start mark
Protocol version number
Message header
Data segment
Check area
Reserved field
Message number
Time label
Data segment length
Data segment
Check code
Data type
Number of bytes
Content description
Marks the beginning of a message, the content is $S (0x2424) the protocol version number followed by the message. The version number adopts the form of "major version number.minor version number", the first byte is the major version number, and the second byte is the minor version number. The protocol version number of this appendix is ​​1.0 (0x0100)
A user-defined field is reserved for users. When this field is empty, the value is 0 (0x0000) Unique identifier for each message
The time when the message is sent, synchronized with UTC. The same time tag when the same message is sent repeatedly Number of bytes in the data segment
The data segment consists of parameter items. Parameter items generally have a fixed length. For parameters with non-fixed lengths, the corresponding length parameter item is used to specify the specific length of the parameter. When a parameter is missing, the value of its length parameter item is 0 (0x0000).
The parameter items of each message are different according to the data content. The cyclic redundancy check code is used for verification. The verified data segment starts from the first byte after the start identifier and ends at the end of the parameter segment
The message is transmitted in bytes, using the data type specified in Table A.2. Table A.2
UShort
Number of bytes
Data type list
Signed character type, the value range is -2\~2—1Unsigned character type, the value range is 0~28Pointer type
Char type array, N is the array length
Signed short integer type, the value range is -215~215-1Unsigned short integer type The value range is 0~216-1GB/T39607—2020
Double
Write method
Number of bytes
Table A.2 ( (continued)
Signed integer, value range is 21~231-1Unsigned integer, value range is 0~22-1Signed single precision floating point type. Value range is -2127~2127-1Signed double precision floating point type, value range is -2102~21023-1The message is written in high-order first mode, that is, the high byte of the data is stored at the low address, and the low byte is stored at the high addressA.2
Message content
The message grouping of base station information data, equipment information data and satellite status data is shown in Table A3. Each message group consists of two or four messages. The setting message is completed by the data center to control the base station and set various parameters of the base station; the response message is completed by the base station to return the result status of the setting message; the acquisition message is completed by the data center to obtain various information and data of the base station; the reply message is completed by the base station to return the information required to obtain the message. Table A.3
Data type
Base station information data
Device information data
Message grouping
Message group list
Base station mode and coordinate setting Get the current positioning coordinates and positioning status of the base station in the telegram group Get the firmware version information of the telegram group Get the telegram group
Receiver registration
Receiver registration period information acquisition
Power status acquisition
Timed power on/off setting and acquisition
GNSS board reset
System restart
Restore factory settings
Storage space acquisition
Antenna information setting and acquisition
Meteorological instrument parameter setting and acquisition
Meteorological instrument data setting and acquisition Get
Set and obtain meteorological data fusion
Set and obtain observation data
Including setting, response, obtaining, replying to telegrams including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including setting, response, obtaining, replying to telegrams including setting, response to telegrams
Including setting, response to telegrams
Including setting, response to telegrams
Including setting, response to telegrams||t t||Including acquisition and reply message
Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message A.3
Data type
Equipment information data
Satellite status data
Message example
Table A.3 (continued)
Message grouping
Ephemeris data setting and acquisition
Difference Correction data setting and acquisition
GNSS receiver navigation positioning data setting and acquisition Mobile network dial-up connection
Mobile network dial-up status acquisition
Wired network data transmission setting and acquisition
Wired network connection status acquisition
Serial port parameter setting and acquisition
Serial port data transmission parameter setting and acquisition
File record
File deletion
FTP push setting
Data output off
Satellite system activation status Setting and obtaining
Satellite altitude cutoff angle setting and obtaining
Satellite system UTC time obtaining
Satellite status information obtaining
DOP value obtaining
Base station mode and coordinate setting and obtaining
The setting should meet the following requirements:
Function: Set the base station startup mode and coordinates; Message number: 0x020101;
Data segment: See Figure A.1, parameters see Table A.4; GB/T39607-—2020
Including setting , response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including getting, reply telegram
including setting, response, get, reply telegram including getting, reply telegram
including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response telegram
including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response telegram
including setting, response, get, reply telegram including setting, response telegram| |tt||Including setting, response, acquisition, reply messageIncluding setting, response, acquisition, reply messageIncluding acquisition, reply message
Including acquisition, reply message
Including acquisition, reply message
Message example: 0x2424010000000201015C107B9A001902C13A035AF8C6F7E84152F9FC113A3405414B72E450FEF5CF0CC745CB, message description see Table A.5. Base station startup mode
X coordinate
Y coordinate
Z coordinate
Base station mode and coordinate setting message parameter segment structure diagram1
Message structure
Start mark
Protocol version number
Message header
Data segment
Check area
Reserved field
Message number
Time label
Data segment length
Data segment
Check code
Data type
Number of bytes
Content description
Marks the beginning of a message, the content is $S (0x2424) the protocol version number followed by the message. The version number adopts the form of "major version number.minor version number", the first byte is the major version number, and the second byte is the minor version number. The protocol version number of this appendix is ​​1.0 (0x0100)
A user-defined field is reserved for users. When this field is empty, the value is 0 (0x0000) Unique identifier for each message
The time when the message is sent, synchronized with UTC. The same time tag when the same message is sent repeatedly Number of bytes in the data segment
The data segment consists of parameter items. Parameter items generally have a fixed length. For parameters with non-fixed lengths, the corresponding length parameter item is used to specify the specific length of the parameter. When a parameter is missing, the value of its length parameter item is 0 (0x0000).
The parameter items of each message are different according to the data content. The cyclic redundancy check code is used for verification. The verified data segment starts from the first byte after the start identifier and ends at the end of the parameter segment
The message is transmitted in bytes, using the data type specified in Table A.2. Table A.2
UShort
Number of bytes
Data type list
Signed character type, the value range is -2\~2—1Unsigned character type, the value range is 0~28Pointer type
Char type array, N is the array length
Signed short integer type, the value range is -215~215-1Unsigned short integer type The value range is 0~216-1GB/T39607—2020
Double
Write method
Number of bytes
Table A.2 ( (continued)
Signed integer, value range is 21~231-1Unsigned integer, value range is 0~22-1Signed single precision floating point type. Value range is -2127~2127-1Signed double precision floating point type, value range is -2102~21023-1The message is written in high-order first mode, that is, the high byte of the data is stored at the low address, and the low byte is stored at the high addressA.2
Message content
The message grouping of base station information data, equipment information data and satellite status data is shown in Table A3. Each message group consists of two or four messages. The setting message is completed by the data center to control the base station and set various parameters of the base station; the response message is completed by the base station to return the result status of the setting message; the acquisition message is completed by the data center to obtain various information and data of the base station; the reply message is completed by the base station to return the information required to obtain the message. Table A.3
Data type
Base station information data
Device information data
Message grouping
Message group list
Base station mode and coordinate setting Get the current positioning coordinates and positioning status of the base station in the telegram group Get the firmware version information of the telegram group Get the telegram group
Receiver registration
Receiver registration period information acquisition
Power status acquisition
Timed power on/off setting and acquisition
GNSS board reset
System restart
Restore factory settings
Storage space acquisition
Antenna information setting and acquisition
Meteorological instrument parameter setting and acquisition
Meteorological instrument data setting and acquisition Get
Set and obtain meteorological data fusion
Set and obtain observation data
Including setting, response, obtaining, replying to telegrams including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including setting, response, obtaining, replying to telegrams including setting, response to telegrams
Including setting, response to telegrams
Including setting, response to telegrams
Including setting, response to telegrams||t t||Including acquisition and reply message
Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message A.3
Data type
Equipment information data
Satellite status data
Message example
Table A.3 (continued)
Message grouping
Ephemeris data setting and acquisition
Difference Correction data setting and acquisition
GNSS receiver navigation positioning data setting and acquisition Mobile network dial-up connection
Mobile network dial-up status acquisition
Wired network data transmission setting and acquisition
Wired network connection status acquisition
Serial port parameter setting and acquisition
Serial port data transmission parameter setting and acquisition
File record
File deletion
FTP push setting
Data output off
Satellite system activation status Setting and obtaining
Satellite altitude cutoff angle setting and obtaining
Satellite system UTC time obtaining
Satellite status information obtaining
DOP value obtaining
Base station mode and coordinate setting and obtaining
The setting should meet the following requirements:
Function: Set the base station startup mode and coordinates; Message number: 0x020101;
Data segment: See Figure A.1, parameters see Table A.4; GB/T39607-—2020
Including setting , response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including getting, reply telegram
including setting, response, get, reply telegram including getting, reply telegram
including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response telegram
including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response telegram
including setting, response, get, reply telegram including setting, response telegram| |tt||Including setting, response, acquisition, reply messageIncluding setting, response, acquisition, reply messageIncluding acquisition, reply message
Including acquisition, reply message
Including acquisition, reply message
Message example: 0x2424010000000201015C107B9A001902C13A035AF8C6F7E84152F9FC113A3405414B72E450FEF5CF0CC745CB, message description see Table A.5. Base station startup mode
X coordinate
Y coordinate
Z coordinate
Base station mode and coordinate setting message parameter segment structure diagram2
UShort
Number of bytes
Data type list
Signed character type, the value range is -2\~2—1Unsigned character type, the value range is 0~28Pointer type
Char type array, N is the array length
Signed short integer type, the value range is -215~215-1Unsigned short integer type The value range is 0~216-1GB/T39607—2020
Double
Write method
Number of bytes
Table A.2 (continued) )
Signed integer, value range is 21~231-1Unsigned integer, value range is 0~22-1Signed single precision floating point type. Value range is -2127~2127-1Signed double precision floating point type, value range is -2102~21023-1The message is written in high-order first mode, that is, the high byte of the data is stored at the low address, and the low byte is stored at the high addressA.2
Message content
The message grouping of base station information data, equipment information data and satellite status data is shown in Table A3. Each message group consists of two or four messages. The setting message is completed by the data center to control the base station and set various parameters of the base station; the response message is completed by the base station to return the result status of the setting message; the acquisition message is completed by the data center to obtain various information and data of the base station; the reply message is completed by the base station to return the information required to obtain the message. Table A.3
Data type
Base station information data
Device information data
Message grouping
Message group list
Base station mode and coordinate setting Get the current positioning coordinates and positioning status of the base station in the telegram group Get the firmware version information of the telegram group Get the telegram group
Receiver registration
Receiver registration period information acquisition
Power status acquisition
Timed power on/off setting and acquisition
GNSS board reset
System restart
Restore factory settings
Storage space acquisition
Antenna information setting and acquisition
Meteorological instrument parameter setting and acquisition
Meteorological instrument data setting and acquisition Get
Set and obtain meteorological data fusion
Set and obtain observation data
Including setting, response, obtaining, replying to telegrams including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including setting, response, obtaining, replying to telegrams including setting, response to telegrams
Including setting, response to telegrams
Including setting, response to telegrams
Including setting, response to telegrams||t t||Including acquisition and reply message
Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message A.3
Data type
Equipment information data
Satellite status data
Message example
Table A.3 (continued)
Message grouping
Ephemeris data setting and acquisition
Difference Correction data setting and acquisition
GNSS receiver navigation positioning data setting and acquisition Mobile network dial-up connection
Mobile network dial-up status acquisition
Wired network data transmission setting and acquisition
Wired network connection status acquisition
Serial port parameter setting and acquisition
Serial port data transmission parameter setting and acquisition
File record
File deletion
FTP push setting
Data output off
Satellite system activation status Setting and obtaining
Satellite altitude cutoff angle setting and obtaining
Satellite system UTC time obtaining
Satellite status information obtaining
DOP value obtaining
Base station mode and coordinate setting and obtaining
The setting should meet the following requirements:
Function: Set the base station startup mode and coordinates; Message number: 0x020101;
Data segment: See Figure A.1, parameters see Table A.4; GB/T39607-—2020
Including setting , response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including getting, reply telegram
including setting, response, get, reply telegram including getting, reply telegram
including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response telegram
including setting, response, get, reply telegram including setting, response, get, reply telegram including setting, response telegram
including setting, response, get, reply telegram including setting, response telegram| |tt||Including setting, response, acquisition, reply messageIncluding setting, response, acquisition, reply messageIncluding acquisition, reply message
Including acquisition, reply message
Including acquisition, reply message
Message example: 0x2424010000000201015C107B9A001902C13A035AF8C6F7E84152F9FC113A3405414B72E450FEF5CF0CC745CB, message description see Table A.5. Base station startup mode
X coordinate
Y coordinate
Z coordinate
Base station mode and coordinate setting message parameter segment structure diagram2
UShort
Number of bytes
Data type list
Signed character type, the value range is -2\~2—1Unsigned character type, the value range is 0~28Pointer type
Char type array, N is the array length
Signed short integer type, the value range is -215~215-1Unsigned short integer type The value range is 0~216-1GB/T39607—2020
Double
Write method
Number of bytes
Table A.2 (continued) )
Signed integer, value range is 21~231-1Unsigned integer, value range is 0~22-1Signed single precision floating point type. Value range is -2127~2127-1Signed double precision floating point type, value range is -2102~21023-1The message is written in high-order first mode, that is, the high byte of the data is stored at the low address, and the low byte is stored at the high addressA.2
Message content
The message grouping of base station information data, equipment information data and satellite status data is shown in Table A3. Each message group consists of two or four messages. The setting message is completed by the data center to control the base station and set various parameters of the base station; the response message is completed by the base station to return the result status of the setting message; the acquisition message is completed by the data center to obtain various information and data of the base station; the reply message is completed by the base station to return the information required to obtain the message. Table A.3
Data type
Base station information data
Device information data
Message grouping
Message group list
Base station mode and coordinate setting Get the current positioning coordinates and positioning status of the base station in the telegram group Get the firmware version information of the telegram group Get the telegram group
Receiver registration
Receiver registration period information acquisition
Power status acquisition
Timed power on/off setting and acquisition
GNSS board reset
System restart
Restore factory settings
Storage space acquisition
Antenna information setting and acquisition
Meteorological instrument parameter setting and acquisition
Meteorological instrument data setting and acquisition Get
Set and obtain meteorological data fusion
Set and obtain observation data
Including setting, response, obtaining, replying to telegrams including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including obtaining, replying to telegrams
Including setting, response, obtaining, replying to telegrams including setting, response to telegrams
Including setting, response to telegrams
Including setting, response to telegrams
Including setting, response to telegrams||t t||Including acquisition and reply message
Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message Including setting, response, acquisition and reply message A.3
Data type
Equipment information data
Satellite status data
Message example
Table A.3 (continued)
Message grouping
Ephemeris data setting and acquisition
Difference Correction data setting and acquisition
GNSS receiver navigation positioning data setting and acquisition Mobile network dial-up connection
Mobile network dial-up status acquisition
Wired network data transmission setting and acquisition
Wired network connection status acquisition
Serial port parameter setting and acquisition
Serial port data transmission parameter setting and acquisition
File record
File deletion
FTP push setting
Data output off
Satellite system activation status Setting and obtaining
Satellite altitude cutoff angle setting and obtaining
Satellite system UTC time obtaining
Satellite status information obtaining
DOP value obtaining
Base station mode and coordinate setting and obtaining
The setting should meet the following requirements:
Function: Set the base station startup mode and coordinates; Message number: 0x020101;
Data segment: See Figure A.1, parameters see Table A.4; GB/T39607-—2020
Including setting , response, get, reply telegram including setting, response, get, reply telegram including setting, response, get, reply telegram inc
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.