Interface Specification for
MADOCA‐SEAD

Japan Aerospace Exploration Agency
revB : July 2019
revA : February 2017
NC : October 2016

Preface
JAXA develops the tool to estimate Multi‐GNSS orbit and clock precisely, called “MADOCA(Multi‐GNSS Advanced Demonstration tool for Orbit and Clock Analysis)”, and provides theestimated products, called “MADOCA‐products”, from “MADOCA‐SEAD(Multi‐GNSS Advanced
Demonstration tool for Orbit and Clock Analysis Supply of “MADOCA‐PPP”‐Enabled
Advanced Demonstration system).
This document describes the data interface specification required by MADOCA‐products
Users.
In addition, there is no technical change from IS‐QZSS Version 1.7.

Disclaimer
JAXA pays close attention from every aspect, but does not guarantee any availability andprecision of the product. JAXA also assumes no responsibility for any damages occurring whena MADOCA‐products user uses a product. JAXA may interrupt, stop and terminate productdistribution. Notice that JAXA bears no responsibility for any resulting damages of a MADOCA‐
products user.

Revision Recode
Code

Date

Description

NC

October 2016

Initial release (No Change)A

February 2017

Chage of Message Type for FCB(Table 4.1‐1, 4.2.3‐1, Table 5.5‐1～5.5‐4)
Correction of the definition about “the Number of QZSS Satelltes” (Table 4.1‐1,
5.1‐2, 5.2‐2, 5.3‐2, 5.4‐2, 5.5‐2)
Clarification of the definition about “UDI” (Table 5.1‐1～5.5‐4)
Correction of erroneous description (Table 5.2‐4)

B

July 2019

Additional notes on applicable documents (2.1)
Deletion of description about MADOCA product via Satellite (4.2.3, 4.2.4)
Addition of Quasi‐Zenith Satellite Information at the time of B revision
establishment (5.1(2))
Update of description about MADOCA‐SEAD system(Fig 3‐1, Chap 4, Table 5.1‐1 ~5.5‐4)
Clarification of MADOCA undefined data field. (Table 5.5‐1 ~ 5.5‐4)

Table of Contents
1. SCOPE ........................................................................................................................... 1
2. DOCUMENTS ................................................................................................................ 1
2.1 APPLICABLE DOCUMENTS ............................................................................................................ 1
2.2 REFERENCE DOCUMENTS............................................................................................................. 1

3. OVERVIEW OF MADOCA‐SEAD ...................................................................................... 2
4. PUBLISHED PRODUCTS.................................................................................................. 2
4.1 VIA INTERNET .............................................................................................................................. 3
4.2 VIA SATELLITE ............................................................................................................................ 5
4.3 PUBLISHED SITE ......................................................................................................................... 75 DATA FORMAT................................................................................................................ 8
5.1 SSR ORBIT CORRECTION MESSAGES ........................................................................................... 8
5.2 SSR CODE BIAS MESSAGES ....................................................................................................... 18
5.3 SSR URA QUALITY MESSAGES................................................................................................... 25
5.4 SSR HIGH RATE CLOCK CORRECTION MESSAGES ..................................................................... 30
5.5 CARRIER PHASE BIAS ................................................................................................................. 35i

1. ScopeThis interface specification, called “IS‐MADOCA‐SEAD”, presents the overview of
MADOCA‐SEAD (Multi‐GNSS Advanced Demonstration tool for Orbit and Clock Analysis
Supply of “MADOCA‐PPP”‐Enabled Advanced Demonstration system) and an data interface
required by the MADOCA‐products Users.

2. Documents
2.1 Applicable Documents(1) Japan Aerospace Exploration Agency, “Interface Specification of QZSS”, ver.1.8,(TBD)
2016.
(2)RTCM SPECIAL COMMITTEE NO. 104, RTCM Paper 228‐2013‐SC104‐STD, RTCM
STANDARD 10403.2 DIFFERENTIAL GNSS (GLOBAL NAVIGATION SATELLITESYSTEMS) SERVICES – VERSION 3 with Amendment 2, Nov, 2013.
(3) RTCM SPECIAL COMMITTEE NO. 104, RTCM Paper 107‐2014‐SC104‐818,
Proposal of new RTCM SSR Messages SSR Stage 1: Galileo, QZSS, SBAS. BDS for
RTCM STANDARD 10403.2, v.6, May, 2014.
(4) RTCM SPECIAL COMMITTEE NO. 104, Proposal of new RTCM SSR Messages SSR
Stage 2: Satellite Phase Biases for RTCM STANDARD 10403.2, v.5, April, 2014.
(5) RTCM STANDARD 10410.1 NETWORKED TRANSPORT OF RTCM via INTERNET
PROTOCOL (Ntrip) ‐ Version 2.0, June, 2011.
* Above RTCM format documents are published for a fee by RTCM. Draft versions are
published ONLY to RTCM members.
2.2 pReference Documents(1) M. Ge et al., Resolution of GPS carrier‐phase ambiguities in Precise Point
Positioning (PPP) with daily observation, J Geod., 2008.

1B

3. Overview of MADOCA‐SEAD
MADOCA‐SEAD is the demonstration system for the precise positioning using the precise
information of the satellite orbit and clock. This system estimates the orbit and clock ofMulti‐GNSS, such as GPS, QZS, GLONASS, Galileo and BeiDou, precisely and provides theestimated products as the correction information for satellite navigation message, called“MADOCA‐products”. Figure 3‐1 shows the overview of MADOCA‐SEAD system.

B

Figure 3‐1 Overview of MADOCA‐SEAD System

4. Published Products

B

The MADOCA‐SEAD can provide the MADOCA‐products as the following;(1)Via Internet
MADOCA‐products follow the international standard format “RTCM10403.2” (Reference:
Applicable Documents(2),(3),(4)) basically and use NTRIP Protocol (Reference: Applicable
Document(5)).
(2)Via Satellite
MADOCA‐SEAD can store the MADOCA‐products to the low‐rate format based on theinternational standard format “RTCM10403.2” (Reference: Applicable Documents(2),(3),(4))(3)On FTP Server
MADOCA‐products follow the international standard format “RTCM10403.2” (Reference:
Applicable Documents(2),(3),(4)) or SP3c format and are published on the JAXA’s FTP server.

2

4.1 Via Internet
4.1.1 Protocol
MADOCA‐SEAD adopts NTRIP protocol. Please refer to the Applicable Document(5) for thedetails.
4.1.2 Format
MADOCA‐SEAD adopts the “RTCM SSR(State Space Representation)” in the international
standard format “RTCM10403.2” except for some messages (Reference: Table 4.1‐1 Note 5). In
the RTCM SSR format, “Message Type Number” is defined for each correction information
type, such as the orbit , clock, URA or code biases and MADOCA‐products Users can receive
only their required information. Table 4.1‐1 shows the list of message type number provided
from MADOCA‐SEAD. Please refer to Applicable Documents(2),(3),(4) and the section 5 in thisdocument for the details.

4.1.3 Considerations for Use(1)Handling of SSR‐IOD Value
The MADOCA‐products are provided as the correction information for Satellite Navigation
Message. IODE value, which indicates the corrected Satellite Navigation Message, is included
only in the SSR Orbit Correction Message (Reference: Table 4.1‐1) and the other SSR Messages
are linked by “SSR‐IOD”, which is incremented when the estimation of orbit and clock is
updated. So, MADOCA‐products Users should use the SSR Messages of the same SSR‐IOD
value. Please refer to the applicable documents(2),(3),(4) for the details.

3

Table 4.1‐1 List of Message type number provided from MADOCA‐SEAD
Message TypeNo.

Message Name
NumberNo. of bits

1

1057

SSR GPS Orbit Correction

68＋135×NS※2

2

1059

SSR GPS Code Bias

67＋11×NS※2＋19×ΣNCB※3

3

1061

SSR GPS URA

67＋12×NS※2

4

1062

SSR GPS High Rate Clock Correction

67＋28×NS※2

5

1063

SSR GLONASS Orbit Correction

65＋134×NS※2

6

1065

SSR GLONASS Code Bias

64＋10×NS※2＋19×ΣNCB※3

7

1067

SSR GLONASS URA

64＋11×NS※2

8

1068

SSR GLONASS High Rate Clock Correction

64＋27×NS※2

91240※1

SSR GALILEO Orbit Correction

68＋137×NS※2

101242※1

SSR GALILEO Code Bias

67＋11×NS※2＋19×ΣNCB※3

111244※1

SSR GALILEO URA

67＋12×NS※2

121245※1

SSR GALILEO High Rate Clock Correction

67＋28×NS※2

131246※1SSR QZSS Orbit Correction

66※6＋133×NS※2

141248※1SSR QZSS Code Bias

65※6＋9×NS※2＋19×ΣNCB※3

151250※1SSR QZSS URA

65※6＋10×NS※2

161251※1SSR QZSS High Rate Clock Correction

65※6＋26×NS※2

171258※1

SSR BDS Orbit Correction

68＋161×NS※2

181260※1

SSR BDS Code Bias

67＋11×NS※2＋19×ΣNCB※3

191262※1

SSR BDS URA

67＋12×NS※2

201263※1

SSR BDS High Rate Clock Correction

67＋28×NS※2

21

11※5

SSR GPS Carrier Phase Bias

69＋28×NS※2＋49×ΣNPB※4

22

12※5

SSR GALILEO Carrier Phase Bias

69＋28×NS※2＋49×ΣNPB※4

23

13※5

SSR QZSS Carrier Phase Bias67※6＋26×NS※2＋49×ΣNPB※4

24

14※5

SSR BDS Carrier Phase Bias

69＋28×NS※2＋49×ΣNPB※4

Remarks※1 Defined in the RTCM draft version format (Reference: Applicable Document(3)).
※2 NS：The number of satellites.
※3 NCB：The number of Code Biases per individual satellite.
※4

NPB：The number of Carrier Phase Biases per individual satellite. MADOCA‐SEAD provides Carrier Phase Biases pereach frequency of individual satellite.

※5 Carrier Phase Biases are provided in the original format based on RTCM draft version format (Reference: Applicable
Document(4)). As of September 2016, JAXA uses 2065, 2067, 2068 and 2070 as the message type number for Carrier
Phase Biases of GPS, GALILEO, QZSS and BDS. However, in order to avoid the duplication of these message type
numbers with RTCM official message type number defined in the future, these message type numbers is changed tothe different numbers (11, 12, 13 and 14: reserved for experimental use in RTCM official format) in Feburuary 2017.
※6 4 bits are assigned to the DF for “the number of QZSS satellites”. In tihe future, the No of bits for this DF will bechanged to “6 bits” in order to follow RTCM official message.

44.2 Via Satellite

B

MADOCA‐SEAD can provide MADOCA‐products at low data rate..
4.2.1 MADOCA‐LEX Signal Property
N/A
4.2.2 MADOCA‐LEX Structure
4.2.2.1 LEX Message Structure
N/A
4.2.2.2 Compact massage format
Figure 4.2.2‐3 shows compact massage format data section structure.

Figure 4.2.2‐3 Compact message format(1) TOW countThe 20‐bit Time of Week (TOW) count at the beginning of the data section indicates the time(seconds into week) at the beginning of the next one‐second message. The valid range is from0 to 604799. The TOW in the last message of the week is set to “0” and the TOW in the firstmessage of the week is set to “1”.
(2) Transmission Week No (WN)
The 13 bits from bit 21 to bit 33 in the data section constitute a binary expression for themodulo‐8192 GPS Week Number at the start of that message.

5

(3) SSR message partThe rest bits in data section from bit 34 to bit 1695 store some MADOCA‐products based on
RTCM SSR format and the transmitted messages are almost the same as via internet(Reference: Table 4.1‐1 and Table 4.2.3‐1). Only the “SSR Variable Length Data Message” partof each RTCM SSR message is stored and the other parts (preamble, reserved section, RTCM
SSR message length and CRC) is NOT stored to reduce the amount of data. And the blank bits
are set to “0”.
B
4.2.3 Update Interval
N/A
4.2.4 Considerations for Use
N/A

6

4.3 Published Site
MADOCA Products are published on JAXA’s WEB site. The type of published MADOCA
Products are shown in Table 4.3‐1.

Product Type

Table 4.3‐1 Published MADOCA Products
FormatUploadMADOCA
Real Time Products

・RTCM SSR format(Reference: Applicable Documents(2),(3),(4) and Section 5)・SP3c format

WEB

MADOCA
Offline Products‐ Final‐ Rapid‐ Ultra Rapid

・SP3c format

WEB

7

B

5 Data Format
5.1 SSR Orbit Correction Messages
The contents of SSR Orbit Correction Messages for GPS, GLONASS, QZSS, GALILEO and BDS
are shown from Table 5.1‐1 to Table 5.1‐5. The content and format of them follows RTCM SSR
format (Reference: Applicable Documents(2),(3)). A symbol beginning with "DF" in the column"Remarks" indicates “Data Field” defined in RTCM format. The update interval of thecorrection massage is published on the website(http://mgmds01.tksc.jaxa.jp).

B(1)GPS (Message Type Number: 1057)
The contents of SSR GPS Orbit Correction Messages are shown in Table 5.1‐1.
Table 5.1‐1 SSR GPS Orbit Correction Messages (Message Type Number: 1057)
#

1

Name
Message Number

Data

No. ofType

Bitsuint 12

12

Possible Range

Contents

0 ~ 4095

SSR Message Type Number

Remarks
DF002(Value:1057)
GPS Epoch Time 1suint 2020

0 ~ 604799[s]2

GPS reference time (FullDF385

seconds since the beginningof the GPS week)3

SSR Update Interval

bit (4)0 ~ 15

4

The SSR Update Intervals for

DF391

this message.
Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same

4

Message Number andEpoch Time (1: multiple
message transmitted)
Satellite Reference5

bit (1)

1

0 or 1

Datum

Orbit corrections refer toDF375

Satellite Reference Datum(0:ITRF, 1:Regional)

6

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for

DF413

SSR in this message.
7

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

8

SSR Solution ID

uint 4

4

0 ~ 15SSR Solution ID number

DF415

No. of Satellites

uint 6

6

0 ~ 63

Number of Satellites

DF387

9
included in the message
Subtotal (#1 ~ #9)

68#10 ~ #17 are repeated for each satellites (1 ~ NS (No. of Satellites))
10

GPS Satellite ID

uint 6

6

1 ~ 32GPS IODE

uint 8

8–

GPS Satellite ID

DF068

IODE value of broadcast

DF071

ephemeris used for
11
calculation of Correction
Differences.

8

B

12

13

14

15

Delta Radial

Delta Along Track

Delta Cross‐Track

Dot Delta Radial

int 22

int 20

int 20

int 21

22

20

20

21

±209.7151[m]±209.7148[m]±209.7148[m]±1.048575[m/s]

Radial orbit correction for

Resolution:
0.1[mm]broadcast ephemeris.

DF365

Along‐Track orbit correction

Resolution:
0.4[mm]for broadcast ephemeris.

DF366

Cross‐Track orbit correction

Resolution:
0.4[mm]for broadcast ephemeris.

DF367

Velocity of Radial orbit

Resolution:
0.001[mm/s]

correction for broadcast

DF368

ephemeris.
16

Dot Delta Along‐ Trackint 1919±1.048572[m/s]

Velocity of Along‐Track orbit

Resolution:
0.004[mm/s]

correction for broadcast

DF369

ephemeris.
17

Dot Delta Cross‐ Trackint 1919±1.048572[m/s]

Velocity of Cross‐Track orbit

Resolution:
0.004[mm/s]

correction for broadcast

DF370

ephemeris.
Subtotal(#10 ~ #17)
Total

135
68 + 135 × NS

9(2) QZSS (Message Type Number: 1246)
The contents of SSR QZSS Orbit Correction Messages are shown in Table 5.1‐2.
Table 5.1‐2 SSR QZSS Orbit Correction Messages (Message Type Number: 1246)
#

Name

1

Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range

Contents

0 ~ 4095

SSR Message Type Number

Remarks
DF002(Value:1246)
2

QZSS Epoch Time 1suint 2020

0 ~ 604799[s]QZSS Reference timeDF460※1(Full seconds since thebeginning of the GPS week)3

SSR Update Interval

bit (4)

4

0 ~ 15The SSR Update Intervals

DF391

for this message.
4

Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same
Message Number andEpoch Time (1: multiple
message transmitted)

5

Satellite Reference Datum

bit (1)

1

0 or 1

Orbit corrections refer toDF375

Satellite Reference Datum(0:ITRF, 1:Regional)
6

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for

DF413

SSR in this message.
7

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

8

SSR Solution ID

uint 4

4

0 ~ 15SSR Solution ID number

DF415

9

No. of Satellites

uint 4

4

0 ~ 15

Number of Satellites

Original DF

included in the message
Subtotal (#1 ~ #9)66#10 ~ #17 are repeated for each satellites (1 ~ NS (No. of Satellites))
10

QZSS Satellite ID

uint 44

1 ~ 10QZSS Satellite ID※2

DF429

11

QZSS IODE

uint 88

0 ~ 255

IODE value of broadcast

DF434

ephemeris used for
calculation of Correction
Differences.
12

13

Delta Radial

Delta Along Trackint 22

int 202220±209.7151[m]±209.7148[m]10Radial orbit correction for

Resolution:
0.1[mm]broadcast ephemeris.

DF365

Along‐Track orbit correction

Resolution:
0.4[mm]for broadcast ephemeris.

DF366

B

14

15

Delta Cross‐Trackint 20Dot Delta Radial

int 2120±209.7148[m]21±1.048575[m/s]

Cross‐Track orbit correction

Resolution:
0.4[mm]for broadcast ephemeris.

DF367

Velocity of Radial orbit

Resolution:
0.001[mm/s]

correction for broadcast

DF368

ephemeris.
16

Dot Delta Along‐ Trackint 1919±1.048572[m/s]

Velocity of Along‐Track

Resolution:
0.004[mm/s]

orbit correction forDF369

broadcast ephemeris.
17

Dot Delta Cross‐ Trackint 1919±1.048572[m/s]

Velocity of Cross‐Track orbit

Resolution:
0.004[mm/s]

correction for broadcast

DF370

ephemeris.
Subtotal (#10~#17)

133

Total

66 + 133 × NS

※1 Defined in draft version of RTCM (Refer to Applicable Document(3)).
※2 QZSS satellite ID is defined as below; (This information is as of revB establishment. For the latest information,
Refer to PS/IS‐QZSS documents published by the Cabinet Office.)

QZSS Satellite ID
QZSS Satellite PRNID
PRN number

Satellite name

1

193

QZS‐1

2

194

QZS‐2

3

195

QZS‐4

4

196

‐

5

197

‐

6

198

‐

7

199

QZS‐3

8

200

‐

9

201

‐

10

202

‐

11

B

(3) GALILEO (Message Type Number: 1240)
The contents of SSR GALILEO Orbit Correction Messages are shown in Table 5.1‐3.
Table 5.1‐3 SSR GALILEO Orbit Correction Messages (Message Type Number: 1240)
#

Name

1

Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range

Contents

0 – 4095

SSR Message Type Number

Remarks
DF002(Value:1240)
2

GALILEO Epoch Time 1suint 20

20

0 – 604799[s]GALILEO Reference

DF458※1

time(Full seconds since thebeginning of the GALILEO
week)
3

SSR Update Interval

bit (4)

4

0 – 15The SSR Update Intervals

DF391

for this message.
4

Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same
Message Number andEpoch Time (1: multiple
message transmitted)

5

Satellite Reference Datum

bit (1)

1

0 or 1

Orbit corrections refer toDF375

Satellite Reference Datum(0:ITRF, 1:Regional)
6

IOD SSRuint 4

4

0 – 15

Issue Of Data number for

DF413

SSR in this message.
7

SSR Provider ID

uint 16

16

0 – 65535

SSR Provider ID number

DF414

8

SSR Solution ID

uint 4

4

0 – 15SSR Solution ID number

DF415

9

No. of Satellites

uint 6

6

0 – 63

Number of Satellites

DF387

included in the message
Subtotal (#1 ~ #9)

68#10 ~ #17 are repeated for each satellites (1 ~ NS (No. of Satellites))
10

GALILEO Satellite ID

uint 6

6

0 – 63GALILEO Satellite ID

DF252

11

GALILEO IODnav I/NAV

uint 10

10

0 – 1023

IODE value of broadcast

DF459※1

ephemeris used for
calculation of Correction
Differences.
12

13

14

Delta Radial

Delta Along Track

Delta Cross‐Trackint 22

int 20

int 20222020±209.7151[m]±209.7148[m]±209.7148[m]12Radial orbit correction for

Resolution:
0.1[mm]broadcast ephemeris.

DF365

Along‐Track orbit correction

Resolution:
0.4[mm]for broadcast ephemeris.

DF366

Cross‐Track orbit correction

Resolution:
0.4[mm]for broadcast ephemeris.

DF367

B

15

Dot Delta Radial

int 2121±1.048575[m/s]

Velocity of Radial orbit

Resolution:
0.001[mm/s]

correction for broadcast

DF368

ephemeris.
16

Dot Delta Along‐ Trackint 1919±1.048572[m/s]

Velocity of Along‐Track

Resolution:
0.004[mm/s]

orbit correction forDF369

broadcast ephemeris.
17

Dot Delta Cross‐ Trackint 1919±1.048572[m/s]

Velocity of Cross‐Track orbit

Resolution:
0.004[mm/s]

correction for broadcast

DF370

ephemeris.
Subtotal(#10～#17)
Total

137
68 ＋ 137 × NS

※1 Defined in draft version of RTCM (Refer to Applicable Document(3)).

13(4) GLONASS (Message Type Number: 1063)
The contents of SSR GLONASS Orbit Correction Messages are shown in Table 5.1‐4.
Table 5.1‐4 SSR GLONASS Orbit Correction Messages (Message Type Number: 1057)
#

Name

1

Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range

Contents

0 – 4095

SSR Message Type Number

Remarks
DF002(Value:1057)
2

GLONASS Epoch Time 1suint 17

17

0 – 86399 [s]

GLONASS reference time

DF386

(Full seconds since thebeginning of the GLONASSday)
3

SSR Update Interval

bit (4)

4

0 – 15The SSR Update Intervals

DF391

for this message.
4

Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same
Message Number andEpoch Time (1: multiple
message transmitted)

5

Satellite Referencebit(1)

1

0 or 1

Datum

Orbit corrections refer toDF375

Satellite Reference Datum(0:ITRF, 1:Regional)

6

IOD SSRuint 4

4

0 – 15

Issue Of Data number for

DF413

SSR in this message.
7

SSR Provider ID

uint 16

16

0 – 65535

SSR Provider ID number

DF414

8

SSR Solution ID

uint 4

4

0 – 15SSR Solution ID number

DF415

9

No. of Satellites

uint 6

6

0 – 63

Number of Satellites

DF387

included in the message
Subtotal (#1 ~ #9)

65#10 ~ #17 are repeated for each satellites (1 ~ NS (No. of Satellites))
10

GLONASS Satellite ID

uint 55

1 – 24

GLONASS Satellite ID

DF384

11

GLONASS IOD

uint 8

8

0 – 255

IODE value of broadcast

DF392

ephemeris used for
calculation of Correction
Differences.
12

Delta Radial

int 2222±209.7151[m]14Radial orbit correction for

Resolution:
0.1[mm]broadcast ephemeris.

DF365

B

13

Delta Along Trackint 2020±209.7148[m]Along‐Trackorbit

correction for broadcast

Resolution:
0.4[mm]DF366

ephemeris.
14

Delta Cross‐Trackint 2020±209.7148[m]Cross‐Trackorbit

correction for broadcast

Resolution:
0.4[mm]DF367

ephemeris.
15

Dot Delta Radial

int 2121±1.048575[m/s]

Velocity of Radial orbit

Resolution:
0.001[mm/s]

correction for broadcast

DF368

ephemeris.
16

Dot Delta Along‐ Trackint 1919±1.048572[m/s]

Velocity of Along‐Track

Resolution:
0.004[mm/s]

orbit correction forDF369

broadcast ephemeris.
17

Dot Delta Cross‐ Trackint 1919±1.048572[m/s]

Velocity

of

orbit

correction

broadcastephemeris.
Subtotal (#10~#17)
Total

134
65 + 134×NS

15

Cross‐Trackfor

Resolution:
0.004[mm/s]
DF370

(5) BDS (Message Type Number : 1258)
The contents of SSR BDS Orbit Correction Messages are shown in Table 5.1‐5.
Table 5.1‐5 SSR BDS Orbit Correction Messages (Message Type Number: 1258)
#

Name

1

Message Number

Data

No. ofType

Bitsuint 12

12

Possible range

Contents

0 ~ 4095

SSR Message Type Number

Remarks
DF002(Value：1258)
2

BDS Epoch Time 1suint 2020

0 ~ 604799[s]BDS reference time (FullDF465※1

seconds since thebeginning of the BDS week)3

SSR Update Interval

bit (4)0 ~ 15

4

The SSR Update Intervals

DF391

for this message.
4

Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same
Message Number andEpoch Time (1: multiple
message transmitted)

5

Satellite Reference Datum

bit (1)

1

0 or 1

Orbit corrections refer toDF375

Satellite Reference Datum:(0:ITRF, 1:Regional)
6

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for

DF413

SSR in this message.
7

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

8

SSR Solution ID

uint 4

4

0 ~ 15SSR Solution ID number

DF415

9

No. of Satellites

uint 6

6

0 ~ 63

Number of Satellites

DF387

included in the message
Subtotal (#1 ~ #9)

68#10 ~ #18 are repeated for each satellites (1 ~ NS (No. of Satellites))
10

BDS Satellite ID

uint 6

6

0 ~ 63

BDS Satellite ID

DF466※1

11

BDS toe Modulo

bit (10)10

0 ~ 8184

BDS ephemeris reference

DF470※1

time toe modulo‐8192
12

BDS IOD CRC

bit (24)

24

0 ~ 1073741823

Issue of Data for BDS

DF471※1

derived from CRC overbroadcasted ephemeris andclock parameters.
13

Delta Radial

int 2222±209.7151[m]Radial orbit correction forbroadcast ephemeris.

16

Resolution:
0.1[mm]
DF365

B

14

Delta Along Trackint 2020±209.7148[m]Along‐Track orbit correction
for broadcast ephemeris.

Delta Cross‐Trackint 2020±209.7148[m]15

Cross‐Track orbit correction
for broadcast ephemeris.

Dot Delta Radial

int 2121±1.048575[m/s]16

Velocity of Radial orbit
correction for broadcast

Resolution:
0.4[mm]
DF366
Resolution:
0.4[mm]
DF367
Resolution:
0.001[mm/s]
DF368

ephemeris.
Dot Delta Along‐ Trackint 1919±1.048572[m/s]17

Velocity of Along‐Trackorbit correction for

Resolution:
0.004[mm/s]
DF369

broadcast ephemeris.
Dot Delta Cross‐ Trackint 1919±1.048572[m/s]18

Velocity of Cross‐Track orbit
correction for broadcast
ephemeris.

Subtotal (#10~#18)
Total

161
68 + 161×NS※1 Defined in draft version of RTCM (Refer to Applicable Document(3)).

17Resolution:
0.004[mm/s]
DF370

5.2 SSR Code Bias Messages
The contents of SSR Code Bias Messages for GPS, GLONASS, QZSS, GALILEO and BDS are
shown from Table 5.2‐1 to Table 5.2‐5. The content and format of them follows RTCM SSR
format (Reference: Applicable Documents(2), (3)). A symbol beginning with "DF" in thecolumn "Remarks" indicates “Data Field” defined in RTCM format. The update interval data
field of code bias message is fixed at the maximum value because it is longer than the rangethat can be represented by the RTCM SSR format.

B(1) GPS (Message Type Number : 1059)
The contents of SSR GPS Cpde Bias Messages are shown in Table 5.2‐1.
Table 5.2‐1 SSR GPS Code Bias Messages (Message Type Number: 1059)
#

1

Name
Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range

Contents

0 – 4095

SSR Message Type Number

Remarks
DF002(Value:1059)
GPS Epoch Time 1suint 20

20

0 – 604799[s]2

GPS reference time (FullDF385

seconds since thebeginning of the GPS week)3

SSR Update Interval

bit (4)

4

0 – 15The SSR Update Intervals

B
DF391

for this message.(Value:15)
Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same

4

Message Number andEpoch Time (1: multiple
message transmitted)

5

IOD SSRuint 4

4

0 – 15

Issue Of Data number for

DF413

SSR in this message.
6

SSR Provider ID

uint 16

16

0 – 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint 4

4

0 – 15SSR Solution ID number

DF415

No. of Satellites

uint 6

6

0 – 63

Number of Satellites

DF387

8
included in the message
Subtotal (#1 ~ #8)

67#9 ~ #12 are repeated for each satellites (1 ~ NS (No. of Satellites: see #8))
9

10

GPS Satellite ID

uint 6

6

1 – 32GPS Satellite ID

DF068

No. of Code Biases

uint 5

5

0 – 31

Number of Code Biases

DF379

for one individual

Processed

satellite
Subtotal (#9 + #10)

11

#11 and #12 are repeated for NCB (No. of Code Biases Processed: see #10) times

18GPS Signal and11

uint 5

5

0 – 31

No. of Code Bias Indicator

Tracking Modeto specify the GPS signal

Indicator

and tracking mode

Code Bias

int 1414±81.91[m]12Subtotal(#11+#12)
Total

19
67＋11×NS＋19×ΣNCB

19

DF380

Code Bias for specified

Resolution:
0.01[m]SignalDF383

(2) QZSS (Message Type Number: 1248)
The contents of SSR QZSS Code Bias Messages are shown in Table 5.2‐2.
Table5.2‐2 SSR QZSS Code Bias Correction Messages (Message Type Number: 1248)
#

Name

1

Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range

Contents

0 – 4095

SSR Message Type Number

Remarks
DF002(Value:1248)
2

QZSS Epoch Time 1suint 20

20

0 – 604799[s]QZSS Reference time (FullDF460※1

seconds since thebeginning of the GPS week)3

SSR Update Interval

bit (4)

4

0 – 15The SSR Update Intervals

DF391

for this message.(Value:15)
4Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same
Message Number andEpoch Time (1: multiple
message transmitted)

5

IOD SSRuint 4

4

0 – 15

Issue Of Data number for

DF413

SSR in this message.
6

SSR Provider ID

uint 16

16

0 – 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint 4

4

0 – 15SSR Solution ID number

DF415

8

No. of Satellites

uint 4

4

0 – 15

Number of Satellites

Originaｌ DF

included in the message
Subtotal (#1 ~ #8)

65#9 ~ #12 are repeated for each satellites (1 ~ NS (No. of Satellites: see #8))
9

QZSS Satellite ID

uint 44

1 – 10QZSS Satellite ID※2

DF429

10

No. of Code Biases

uint 5

5

0 – 31

Number of Code Biases for

DF379

Processed

one individual satellite

Subtotal (#9 + #10)

9#11 and #12 are repeated for NCB (No. of Code Biases Processed: see #10) times
11

12

QZSS Signal anduint 5

5

0 – 31

No. of Code Bias Indicator

Tracking Modeto specify the QZSS signal

Indicator

and tracking mode※3

Code Bias

int 14

Subtotal(#11+#12)
Total

14

±81.91[m]Code Bias for specified

Resolution:
0.01[m]SignalDF383

1965＋9×NS＋19×ΣNCB※1 Defined in draft version of RTCM (Refer to Applicable Document(3)).
※2 Defined in Table 5.1‐2 Note2.
※3 Indicator to specify the QZSS signal and tracking is defined as below;

20

DF461※1

BIndicator to specify the QZSS signal and tracking
ID

QZSS Signal and Tracking

0

L1 C/A

1

L1 L1C (D)2

L1 L1C (P)3

L2 L2C (M)4

L2 L2C (L)5

L2 L2C (M+L)

6

L5 I

7

L5 Q

8

L5 I+Q

9～

Reserved21

(3) GALILEO (Message Type Number : 1242)
The contents of SSR GALILEO Code Bias Messages are shown in Table 5.2‐3.
Table 5.2‐3 SSR GALILEO Code Bias Messages (Message Type Number: 1242)
#

Name

1

Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range

Contents

0 – 4095

SSR Message Type Number

Remarks
DF002(Value:1242)
2

GALILEO Epoch Time 1suint 20

20

0 – 604799[s]GALILEO Reference time

DF458※1(Full seconds since thebeginning of the GALILEO
week)
3

SSR Update Interval

bit (4)

4

0 – 15The SSR Update Intervals

DF391

for this message.(value:15)
4Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same
Message Number andEpoch Time (1: multiple
message transmitted)

5

IOD SSRuint 4

4

0 – 15

Issue Of Data number for

DF413

SSR in this message.
6

SSR Provider ID

uint 16

16

0 – 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint 4

4

0 – 15SSR Solution ID number

DF415

8

No. of Satellites

uint 6

6

0 – 63

Number of Satellites

DF387

included in the message
Subtotal (#1 ~ #8)

67#9 ~ #12 are repeated for each satellites (1 ~ NS (No. of Satellites: see #8))9
10

GALILEO Satellite ID

uint 6

6

0 – 63GALILEO Satellite ID

DF252

No. of Code Biases

uint 5

5

0 – 31

Number of Code Biases for

DF379

Processed

one individual satellite

Subtotal (#9 + #10)

9#11 and #12 are repeated for NCB (No. of Code Biases Processed: see #10) times
GALILEO Signal and11

uint 5

5

0 – 31

Tracking Mode Indicator

No. of Code Bias Indicator

DF382

to specify the Galileo signal
and tracking mode

Code Bias

int 1414±81.91[m]12Subtotal(#11+#12)
Total

Code Bias for specified

Resolution:
0.01[m]SignalDF383

19
67＋11×NS＋19×ΣNCB※1 Defined in draft version of RTCM (Refer to Applicable Document(3)).

22B(4) GLONASS (Message Type Number : 1065)
The contents of SSR GLONASS Code Bias Messages are shown in Table 5.2‐4.
Table 5.2‐4 SSR GLONASS Code Bias Messages (Message Type Number: 1065)
#

1

Name
Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range

Contents

0 ~ 4095

SSR Message Type Number

Remarks
DF002(Value:1065)
GLONASS Epoch Time 1suint 1717

0 ~ 86399 [s]

GLONASS reference time

DF386

(Full seconds since the2
beginning of the GLONASSday)
3

SSR Update Interval

bit (4)0 ~ 15

4

The SSR Update Intervals

DF391

for this message.(Value:15)
Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same

4

Message Number andEpoch Time (1: multiple
message transmitted)

5

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for

DF413

SSR in this message.
6

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint 4

4

0 ~ 15SSR Solution ID number

DF415

No. of Satellites

uint 6

6

0 ~ 63

Number of Satellites

DF387

8
included in the message
Subtotal (#1 ~ #8)

64#9 ~ #12 are repeated for each satellites (1 ~ NS (No. of Satellites: see #8))
9
10

GLONASS Satellite ID

uint 55

1 ~ 24

GLONASS Satellite ID

DF384

No. of Code Biases

uint 5

5

0 ~ 31

Number of Code Biases for

DF379

Processed

one individual satellite

Subtotal (#9 + #10)

10

#11 and #12 are repeated for NCB (No. of Code Biases Processed: see #10) times
GLONASS Signal and11

uint 5

5

0 ~ 31

Tracking Mode Indicator

No. of Code Bias Indicator

DF380

to specify the GLONASS
signal and tracking mode

Code Bias

int 1414±81.91 [m]12
Subtotal(#11+#12)
Total

19
64 + 10×NS+ 19×∑NCB

23

Code Bias for specified

Resolution:
0.01[m]SignalDF383

B

(5) BDS (Message Type Number : 1260)
The contents of SSR BDS Code Bias Messages are shown in Table 5.2‐5.
Table 5.2‐5 SSR BDS Code Bias Messages (Message Type Number: 1260)
#

1

Name
Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range

Contents

0 ~ 4095

SSR Message Type Number

Remarks
DF002(Value：1260)
BDS Epoch Time 1suint 2020

0 ~ 604799[s]2

BDS reference time (FullDF465※1

seconds since thebeginning of the BDS week)3

SSR Update Interval

bit (4)0 ~ 15

4

The SSR Update Intervals

DF391

for this message.(Value:15)
Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same

4

Message Number andEpoch Time (1: multiple
message transmitted)

5

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for

DF413

SSR in this message.
6

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint 4

4

0 ~ 15SSR Solution ID number

DF415

No. of Satellites

uint 6

6

0 ~ 63

Number of Satellites

DF387

8
included in the message
Subtotal (#1 ~ #8)

67#9 ~ #12 are repeated for each satellites (1 ~ NS (No. of Satellites: see #8))
9
10

BDS Satellite ID

uint 66

0‐63

BDS Satellite ID

DF466※1

No. of Code Biases

uint 5

5

0 ~ 31

Number of Code Biases for

DF379※1

Processed

one individual satellite

Subtotal (#9 + #10)

11

#11 and #12 are repeated for NCB (No. of Code Biases Processed: see #10) times
BDS Signal and Tracking
11

uint 5

5

0 ~ 31Mode Indicator

No. of Code Bias Indicator

DF467※1

to specify the BDS signal
and tracking mode

Code Bias

int 1414±81.91 [m]12
Subtotal(#11+#12)

19
67 + 11×NS+ 19×∑NCB※1 Defined in draft version of RTCM (Refer to Applicable Document(3)).

24

Code Bias for specified

Resolution:
0.01[m]Signal

DF383

B

5.3 SSR URA quality Messages
The contents of SSR URA quality Messages for GPS, GLONASS, QZSS, GALILEO and BDS are
shown from Table 5.3‐1 to Tble 5.3‐5. The content and format of them follows RTCM format(Reference: Applicable Documents(2),(3)). A symbol beginning with "DF" in the column"Remarks" indicates “Data Field” defined in RTCM format. The update interval of thecorrection massage is published on the website.

B(1) GPS (Message Type Number : 1061)
The contents of SSR GPS URA Messages are shown in Table 5.3‐1.
Table 5.3‐1 SSR GPS URA Messages (Message Type Number: 1061)
#

1

Name
Message Number

Data

No.

Type

of Bits

uint12

12

Possible range
0 ~ 4095

Contents
SSR Message Type Number

Remarks
DF002(Value:1061)
GPS Epoch Time 1s

uint2020

0 ~ 604799[s]2

GPS reference time (FullDF385

seconds since the beginningof the GPS week)3

SSR Update Intervalbit(4)

4

0 ~ 15The SSR Update Intervals for

DF391

this message.
Multiple Message

bit(1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same

4

Message Number and Epoch
Time (1: multiple message
transmitted)

5

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for SSR

DF413

in this message.
6

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint4

4

0 ~ 15SSR Solution ID number

DF415

No. of Satellites

uint6

6

0 ~ 63

Number of Satellites included

DF387

8
in the message
Subtotal (#1 ~ #8)67#9 and #10 are repeated for each satellites (1 ~ NS (No. of Satellites: see #8))
9

GPS Satellite ID
SSR URA

uint 6bit(6)

6

1 ~ 32

6

bits 3~5: 0~7
bits 0~2: 0~7

10

GPS Satellite ID

DF068

SSR User Range Accuracy

DF389(URA) (1 sigma) represented
by a combination of
URA_CLASS (high 3 bits) and
URA_VALUE (low 3 bits).

Subtotal (#9+#10)
Total

12
67 + 12×NS

25

B

(2) QZSS (Message Type Number: 1250)
The contents of SSR QZSS URA quality information Messages are shown in Table 5.3‐2.

Table5.3‐2 SSR QZSS URA Messages (Message Type Number: 1250)
#

1

Name
Message Number

Data

No. ofType

Bitsuint 12

12

Possible range
0 ~ 4095

Contents

Remarks

SSR Message Type Number

DF002(Value:1250)
QZSS Epoch Time 1suint 2020

0 ~ 604799[s]2DF460※1

QZSS Reference time (Fullseconds since the beginningof the GPS week)3

SSR Update Interval

bit (4)

4

0 ~ 15The SSR Update Intervals for

DF391

this message.
Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same

4

Message Number and Epoch
Time (1: multiple message
transmitted)

5

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for SSR

DF413

in this message.
6

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint 4

4

0 ~ 15SSR Solution ID number

DF415

No. of Satellites

uint 4

4

0 ~ 15

Number of Satellites included

Original DF

8in the message
Subtotal (#1 ~ #8)

65#9 and #10 are repeated for each satellites (1 ~ NS (No. of Satellites: see #8))
9

QZSS Satellite ID

uint 4

4

SSR URA

bit (6)

6

1 ~ 10bits 3~5: 0~7
bits 0~2: 0~7

10

QZSS Satellite ID ※2

DF429

SSR User Range Accuracy

DF389(URA) (1 sigma) represented
byacombination

of

URA_CLASS (high 3 bits) and
URA_VALUE (low 3 bits).
Subtotal (#9+#10)
Total

10
65 + 10×NS※1 Defined draft version of RTCM (refer to Applicable Document(3)).
※2 Defined in Table 5.1‐2 Note 2.

26

B

(3) GALILEO (Message Type Number : 1244)
The contents of SSR GPS URA Messages are shown in Table 5.3‐3.
Table 5.3‐3 SSR GALILEO URA Messages (Message Type Number: 1244)
#

1

Name
Message Number

No.

Type

of Bits

uint 12

12

Possible range
0 ~ 4095

Contents
SSR Message Type Number

Remarks
DF002(Value:1244)
GALILEO Epoch2

Datauint 2020

0 ~ 604799[s]Time 1s

GALILEO Reference time (FullDF458※1

seconds since the beginningof the GALILEO week)3

SSR Update Interval

bit (4)

4

0 ~ 15The SSR Update Intervals for

DF391

B

this message.
Multiple

Messagebit (1)

1

0 or 1

Indicator

Indicatorfortransmitting

DF388

messages with the same

4

Message Number and Epoch
Time (1: multiple message
transmitted)

5

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for SSR

DF413

in this message.
6

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint 4

4

0 ~ 15SSR Solution ID number

DF415

No. of Satellites

uint 6

6

0 ~ 63

Number of Satellites included

DF387

8
in the message
Subtotal (#1 ~ #8)67#9 and #10 are repeated for each satellites (1 ~ NS (No. of Satellites: see #8))9

GALILEO Satellite ID

uint 6

6

SSR URA

bit (6)

6

0 ~ 63
bits 3~5: 0~7
bits 0~2: 0~7

10

GALILEO Satellite IDDF252

SSR User Range Accuracy

DF389(URA) (1 sigma) represented
by a combination of
URA_CLASS (high 3 bits) and
URA_VALUE (low 3 bits).

Subtotal (#9+#10)
Total

12
67 + 12×NS※1 Defined draft version of RTCM (refer to Applicable Document(3)).

27

(4) GLONASS (Message Type Number : 1067)
The contents of SSR GLONASS URA Messages are shown in Table 5.3‐4.
Table 5.3‐4 SSR GLONASS URA Messages (Message Type Number: 1067)
#

Name

1

Message Number

No.

Type

of Bits

uint 12

12

Possible range
0 ~ 4095

Contents

Remarks

SSR Message Type Number

DF002(Value:1067)
GLONASS Epoch2

Datauint 1717

0 ~ 86399 [s]Time 1s

GLONASS reference time (FullDF386

seconds since the beginningof the GLONASS day)3

SSR Update Interval

bit (4)

4

0 ~ 15The SSR Update Intervals for

DF391

this message.
Multiple

Messagebit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same

4

Message Number and Epoch
Time (1: multiple message
transmitted)

5

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for SSR

DF413

in this message.
6

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint 4

4

0 ~ 15SSR Solution ID number

DF415

No. of Satellites

uint 6

6

0 ~ 63

Number of Satellites included

DF387

8
in the message
Subtotal (#1 ~ #8)64#9 and #10 are repeated for each satellites (1 ~ NS (No. of Satellites: see #8)
9

GLONASS Satellite

uint 55

1 ~ 24bit (6)

6

bits 3~5: 0~7

GLONASS Satellite ID

DF384

SSR User Range Accuracy

DF389

ID
SSR URA

bits 0~2: 0~7
10(URA) (1 sigma) represented
by a combination of
URA_CLASS (high 3 bits) and
URA_VALUE (low 3 bits).

Subtotal (#9+#10)
Total

11
64 + 11×NS

28

B

(5) BDS (Message Type Number : 1062)
The contents of SSR BDS URA Messages are shown in Table 5.3‐5.
Table 5.3‐5 SSR BDS URA Messages (Message Type Number: 1062)
#

1

Name
Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range
0 ~ 4095

Contents

Remarks

SSR Message Type Number

DF002(Value：1262)
BDS Epoch Time 1suint 2020

0 ~ 604799[s]2

BDS reference time (FullDF465※1

seconds since the beginningof the BDS week)3

SSR Update

bit (4)

4

0 ~ 15IntervalMultiple Message

The SSR Update Intervals

DF391

for this message.
bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same

4

Message Number andEpoch Time (1: multiple
message transmitted)

5

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for

DF413

SSR in this message.
6

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint 4

4

0 ~ 15SSR Solution ID number

DF415

No. of Satellites

uint 6

6

0 ~ 63

Number of Satellites

DF387

8
included in the message
Subtotal (#1 ~ #8)67#9 and #10 are repeated for each satellites (1 ~ NS (No. of Satellites: see #8))
9

BDS Satellite ID

uint 6

6

SSR URA

bit (6)

6

0 ~ 63
bits 3~5: 0~7
bits 0~2: 0~7

BDS Satellite ID

DF466※1

SSR User Range Accuracy

DF389(URA) (1 sigma)
represented by a

10
combination of URA_CLASS(high 3 bits) and
URA_VALUE (low 3 bits).
Subtotal (#9+#10)
Total

12
67 + 12×NS※1 Defined draft version of RTCM (refer to Applicable Document(3)).

29B

5.4 SSR High Rate Clock Correction Messages
The contents of SSR High Rate Clock Correction Messages for GPS, GLONASS, QZSS, GALILEO
and BDS are shown from Table 5.4‐1 to Tble 5.4‐5. The content and format of them are basedon RTCM format (Reference: Applicable Documents(2),(3)) and please refer to section 4.2.4 inthis document about their difference. A symbol beginning with "DF" in the column "Remarks"
indicates “Data Field” defined in RTCM format. The update interval of the correction massage
is published on the website.

B(1) GPS (Message Type Number: 1062)
The contents of SSR GPS High Rate Clock Correction Messages are shown in Table 5.4‐1.
Table5.4‐1 SSR GPS High Rate Clock Correction Messages (Message Type Number: 1062)
#

Name

1

Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range

Contents

0 ~ 4095

SSR Message Type Number

Remarks
DF002(Value:1057)
GPS Epoch Time 1suint 2020

0 ~ 604799[s]2

GPS reference time (FullDF385

seconds since the beginningof the GPS week)3

SSR Update Interval

bit (4)

4

0 ~ 15The SSR Update Intervals for

DF391

this message.
Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same

4

Message Number and Epoch
Time (1: multiple message
transmitted)

5

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for

DF413

SSR in this message.
6

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint 4

4

0 ~ 15SSR Solution ID number

DF415

No. of Satellites

uint 6

6

0 ~ 63

Number of Satellites

DF387

8
included in the message
Subtotal (#1 ~ #8)67#9 and #10 are repeated for each satellites (1 ~ NS (No. of Satellites: see #8))
9
10

GPS Satellite ID

uint 6

6

1 ~ 32High Rate Clockint 2222±209.7151 [m]Correction
Subtotal (#9+#10)
Total

GPS Satellite ID

DF068

High Rate Clock correction

DF390

Value
28
67 + 28×NS

30

B

(2) QZSS (Message Type Number: 1251)
The contents of SSR QZSS High Rate Clock Correction Messages are shown in Table 5.4‐2.
Table5.4‐2 SSR QZSS High Rate Clock Correction Messages (Message Type Number: 1251)
#

1

Name
Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range
0 ~ 4095

Contents
SSR Message Type Number

Remarks
DF002(Value:1251)
QZSS Epoch Time 1suint 2020

0 ~ 604799[s]2

QZSS Reference time (FullDF460※1

seconds since the beginningof the GPS week)3

SSR Update Interval

bit (4)

4

0 ~ 15The SSR Update Intervals for

DF391

this message.
Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same

4

Message Number and Epoch
Time (1: multiple message
transmitted)

5

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for SSR

DF413

in this message.
6

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint 4

4

0 ~ 15SSR Solution ID number

DF415

No. of Satellites

uint 4

4

0 ~ 15

Number of Satellites included

Original DF

8in the message
Subtotal (#1 ~ #8)

65#9 and #10 are repeated for each satellites (1 ‐–NS (No. of Satellites: see #8))
9
10

QZSS Satellite ID

uint 44

1 ~ 10High Rate Clockint 2222±209.7151 [m]Correction

DF429

High Rate Clock correction

DF390

Value

Subtotal (#9+#10)
Total

QZSS Satellite ID (※2)

26
65 + 26×NS※1 Defined draft version of RTCM (refer to Applicable Document(3)).
※2 Defined in Table 5.1‐2 Note2.

31B

(3) GALILEO (Message Type Number: 1245)
The contents of SSR GALILEO High Rate Clock Correction Messages are shown in Table 5.4‐3.
Table5.4‐3 SSR GALILEO High Rate Clock Correction Messages (Message Type Number: 1245)
#

1

Name
Message Number

No.

Type

of Bits

uint 12

12

Possible range
0 ~ 4095

Contents
SSR Message Type Number

Remarks
DF002(Value:1245)
GALILEO Epoch Time2

Datauint 2020

0 ~ 604799[s]1s

GALILEO Reference time (FullDF458※1

seconds since the beginningof the GALILEO week)3

SSR Update Interval

bit (4)

4

0 ~ 15The SSR Update Intervals for

DF391

this message.
Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same

4

Message Number and Epoch
Time (1: multiple message
transmitted)

5

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for SSR

DF413

in this message.
6

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint 4

4

0 ~ 15SSR Solution ID number

DF415

No. of Satellites

uint 6

6

0 ~ 63

Number of Satellites included

DF387

8
in the message
Subtotal (#1 ~ #8)67#9 and #10 are repeated for each satellites (1 ~ NS (No. of Satellites: see #8))9
10

GALILEO Satellite ID

uint 6

6

0 ~ 63High Rate Clockint 2222±209.7151 [m]Correction
Subtotal (#9+#10)
Total

GALILEO Satellite ID

DF252

High Rate Clock correction

DF390

Value
28
67 + 28×NS※1 Defined draft version of RTCM (refer to Applicable Document(3)).

32B(4) GLONASS (Message Type Number: 1068)
The contents of SSR GLONASS High Rate Clock Correction Messages are shown in Table 5.4‐4.
Table 5.4 4 SSR GLONASS High Rate Clock Correction Messages (Message Type Number: 1068)
#

Name

1

Message Number

No.

Type

of Bits

uint 12

12

Possible range
0 ~ 4095

Contents
SSR Message Type Number

Remarks
DF002(Value:1068)
GLONASS Epoch2

Datauint 1717

0 ~ 86399 [s]Time 1s

GLONASS reference time (FullDF386

seconds since the beginning of
the GLONASS day)3

SSR Update Interval

bit (4)

4

0 ~ 15The SSR Update Intervals for

DF391

this message.
Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same

4

Message Number and Epoch
Time (1: multiple message
transmitted)

5

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for SSR in

DF413

this message.
6

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint 4

4

0 ~ 15SSR Solution ID number

DF415

No. of Satellites

uint 6

6

0 ~ 63

Number of Satellites included

DF387

8
in the message
Subtotal (#1 ~ #8)67#9 and #10 are repeated for each satellites (1 ~ NS (No. of Satellites: see #8))
9
10

GLONASS Satellite ID

uint 55

1 ~ 24High Rate Clockint 2222±209.7151 [m]Correction
Subtotal (#9+#10)
Total

GLONASS Satellite ID

DF384

High Rate Clock correction

DF390

Value
28
67 + 28×NS

33B

(5) BDS (Message Type Number: 1263)
The contents of SSR BDS High Rate Clock Correction Messages are shown in Table 5.4‐5.
Table 5.4 5 SSR BDS High Rate Clock Correction Messages (Message Type Number: 1263)
#

1

Name
Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range
0 ~ 4095

Contents
SSR Message Type Number

Remarks
DF002(Value:1263)
BDS Epoch Time 1suint 2020

0 ~ 604799 [s]2

BDS reference time (FullDF465※1

seconds since the beginningof the BDS week)3

SSR Update Interval

bit (4)

4

0 ~ 15The SSR Update Intervals for

DF391

this message.
Multiple Message

bit (1)

1

0 or 1

Indicator

Indicator for transmitting

DF388

messages with the same

4

Message Number and Epoch
Time (1: multiple message
transmitted)

5

IOD SSRuint 4

4

0 ~ 15

Issue Of Data number for SSR

DF413

in this message.
6

SSR Provider ID

uint 16

16

0 ~ 65535

SSR Provider ID number

DF414

7

SSR Solution ID

uint 4

4

0 ~ 15SSR Solution ID number

DF415

No. of Satellites

uint 6

6

0 ~ 63

Number of Satellites included

DF387

8
in the message
Subtotal (#1 ~ #8)67#9 and #10 are repeated for each satellites (1 ~ NS (No. of Satellites: see #8))
9
10

BDS Satellite ID

uint 6

6

0 ~ 63High Rate Clockint 2222±209.7151 [m]Correction
Subtotal (#9+#10)
Total

BDS Satellite ID

DF466※1

High Rate Clock correction

DF390

Value
28
67 + 28×NS※1 Defined draft version of RTCM (refer to Applicable Document(3)).

34B

5.5 Carrier Phase Bias
The contents of SSR Carrier Phase Bias Correction Messages for GPS, GLONASS, QZSS,GALILEO and BDS are shown in Table 5.5‐1 to Table 5.5‐5. In MADOCA‐SEAD, carrier phasebiases are provided per each frequency of individual satellite and used for PPP‐AR with themethod of FCB (Fractional Cycle Bias)(Reference: Reference Document(1)).
A notation that starts with "DF" in the column "Remarks" indicates the corresponding Data
Field in the documentation of RTCM version 10403.2 (Reference: Applicable Documents(2),(3),(4)) excluding the column Standard deviation for carrier phase biases. The unused data
fields, which are described as “Not defined in MADOCA” in the remarks column, are set tozero. The update interval of the correction massage is published on the website.

B(1) GPS (Message Type Number: 11※1)
The contents of SSR GPS Carrier Phase Bias Correction Messages are shown in Table5.5‐1.
Table5.5‐1 SSR GPS Carrier Phase Bias Correction Messages (Message Type Number: 11※1)
#

1

Name
Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range
0 ~ 4095

Contents

Remarks

SSR Message Type Number

DF002(Value: 11※1)
GPS Epoch Time 1suint 2020

0 ~ 604799[s]2

GPS reference time (Fullseconds

since

DF385

the

beginning of the GPS week)3

SSR Update Interval

bit (4)

4

0 ~ 15The SSR Update Intervals

DF391

for this message.
Multiple Message

bit (1)

1

Indicator

0 or 1

Indicator for transmitting(fix to 0)

messages with the same

4

DF388

Message Number andEpoch Time (1: multiple
message transmitted)
IOD SSRuint 44

5

0 ~ 15

Issue Of Data number for

DF413(fix to 0)

SSR in this message.

Not defined in
MADOCA

67

8

9

SSR Provider ID

uint 16

16

0 ~ 65535(fix to 0)

SSR Solution ID

uint 4

4

0 ~ 15(fix to 0)

Dispersive Bias

bit (1)

1Consistency Indicator
MW Consistency
Indicator

0 or 1(fix to 0)

bit (1)

1

0 or 1(fix to 0)

35

DF414
Not defined in
MADOCA
DF415
Not defined in
MADOCA
DF486※2
Not defined in
MADOCA
DF487※2
Not defined in
MADOCA

B

10

No. of Satellites

uint 6

6

0 ~ 63

Number of Satellites

DF387

included in the message
Subtotal (#1 ~ #8)

69#11 ~ #20 are repeated for each satellites (1 ~ NS (No. of Satellites: see #10))
11

12

GPS Satellite ID

uint6

6

1 ~ 32GPS Satellite ID

DF068

No of Phase Biases

uint5

5

0 ~ 31

No of Phase Biases

DF479※2

Processed

Processed for one
individual satellite

Yaw Angle

uint9

9

13

0 ~ (2 – 1/256)

Yaw Angle

DF480※2

Yaw Rate

DF481※2B[semi‐circles](fix to 0)
Yaw Rate

int8

8±(127/8192)[semi‐circles /second](approx. ±2.79

14[degree/second])(fix to 0)
Subtotal (#11~ #14)28

#15 ~ #20 are repeated for NPB (No. of Phase Biases Processed: see #12) times
GPS Signal and15

uint 5

5

0 ~ 31

Tracking Mode

GPS Signal and Tracking

DF382

Mode Indicator

Indicator
16

17

18

Signal Integer

uint 1

1

Indicator
Signals Wide‐Lane(fix to 0)
bit (2)

2

Integer Indicator
Signal Discontinuity

00, 01, 10, 11(fix to 00)

uint 4

4Counter
Phase Bias (FCB)

0 or 1

0 ~ 15(fix to 0)

int 2020±52.4287 [m]Phase Bias (FCB)

19

DF483※2
Not defined in
MADOCA
DF484※2
Not defined in
MADOCA
DF485※2
Not defined in
MADOCA
Resolution:
0.0001[m]DF482(※2)

Standard deviation
20

uint 1717

0 ~ 13.1071 [m]of Phase Bias (FCB)
Subtotal (#15 ~ #20)
Total

Standard deviation of

Resolution:
0.0001[m]Phase Bias (FCB)

Orignal DF

49
69 + 28×NS+ 49×∑NPB※1 As of September 2016, JAXA has been using "2065" as Message Type Number for Carrier Phase Bias of GPS, However,this message type is changed to “11” in Feburuary 2017 (Reference: Table 4.1‐1 Note 5).
※2 Defined in draft version of RTCM (ref er to Applicable Document(3)).
※3 Defined draft version of RTCM (refer to Applicable Document(4)).

36B(2) QZSS (Message Type Number: 13※1)
The contents of SSR QZSS Carrier Phase Bias Correction Messages are shown in Table5.5‐2.
Table5.5‐2 SSR QZSS Carrier Phase Bias Correction Messages (Message Type Number: 13※1)
#

1

Name
Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range
0 ~ 4095

Remarks
Contents
SSR Message Type Number

DF002(Value: 13※1)
QZSS Epoch Time 1suint 2020

0 ~ 604799[s]2

QZSS Reference time (FullsecondssinceDF460※2

thebeginning of the GPS week)3

SSR Update Interval

bit (4)

4

0 ~ 15The SSR Update Intervals

DF391

B

for this message.
Multiple Message

bit (1)

1

Indicator

0 or 1

Indicator for transmitting(fix to 0)

messages with the same

4

DF388

Message Number andEpoch Time (1: multiple
message transmitted)

5

6

7

IOD SSR

SSR Provider ID

uint 164

16

0 ~ 15

Issue Of Data number for(fix to 0)

SSR in this message.

0 ~ 65535(fix to 0)

SSR Solution ID

uint 4

4

0 ~ 15(fix to 0)

Dispersive Bias
8uint 4bit (1)

1Consistency

0 or 1(fix to 0)

DF413
Not defined in
MADOCA
DF414
Not defined in
MADOCA
DF415
Not defined in
MADOCA
DF486※3
Not defined in
MADOCA

Indicator
9

10

MW Consistency

bit (1)

1

Indicator
No. of Satellites

DF487※3
Not defined in
MADOCA

0 or 1(fix to 0)

uint 4

4

0 ~ 15

Number of Satellites

Original DF

included in the message
Subtotal (#1 ~ #8)

67#11 ~ #20 are repeated for each satellites (1 ~ NS (No. of Satellites: see #10))
11

12

QZSS Satellite ID

uint4

4

1 ~ 10QZSS Satellite ID

DF429※2

No of Phase Biases

uint5

5

0 ~ 31

No of Phase Biases

DF479※3

Processed

Processed for one
individual satellite

Yaw Angle
13

uint9

9

0 ~ (2 – 1/256)[semi‐circles](fix to 0)37

Yaw Angle

DF480※3

B

Yaw Rate

int8

8±(127/8192)[semi‐circles /second]Yaw Rate

DF481※3

B(approx. ±2.79

14[degree/second])(fix to 0)
Subtotal (#11 ~ #14)

26

#15 ~ #20 are repeated for NCB (No. of Carrier Phase Biases Processed: see #12) times
QZSS Signal and15

uint 5

5

0 ~ 31

Tracking Mode

QZSS Signal and Tracking

DF461※3

Mode Indicator

Indicator
16

17

18

Signal Integer

uint 1

1

Indicator
Signals Wide‐Lane(fix to 0)
bit (2)

2

Integer Indicator
Signal Discontinuity

00, 01, 10, 11(fix to 00)

uint 4

4Counter
Phase Bias (FCB)

DF483※4
Not defined in
MADOCA
DF484※4
Not defined in
MADOCA
DF485※4
Not defined in
MADOCA

0 or 1

0 ~ 15(fix to 0)

int 2020±52.4287 [m]Phase Bias (FCB)

19

Resolution:
0.0001[m]DF482(※4)

Standard deviation
20

uint 1717

0 ~ 13.1071 [m]of Phase Bias (FCB)

Standard deviation of

Resolution:

Phase Bias (FCB)

0.0001[m]Original DF

Subtotal (#15 ~ #20)
Total

49
67 + 26×NS+ 49×∑NPB※1 As of September 2016, JAXA has been using "2068" as Message Type Number for Carrier Phase Bias of QZSS,
However, this message type is changed to “13” in Feburuary 2017(Reference: Table 4.1‐1 Note 5).
※2 Defined in draft version of RTCM (refer to Applicable Document(3)).
※3 Defined in draft version of RTCM (refer to Applicable Document(4)).

38B

(3)GALILEO (Message Type Number: 12※1)
The contents of SSR GALILEO Carrier Phase Bias Correction Messages are shown in
Table5.5‐3.
Table5.5‐3 SSR GALILEO Carrier Phase Bias Correction Messages (Message Type Number:12※1)
#

1

Name
Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range
0 ~ 4095

Contents

Remarks

SSR Message Type Number

DF002

※1

(Value: 12 )GALILEO Epoch Time2

uint 2020

0 ~ 604799[s]1s

GALILEO Reference time

DF458※2(Full seconds since thebeginning of the GPS week)3

SSR Update Interval

bit (4)

4

0 ~ 15The SSR Update Intervals

DF391

for this message.
Multiple Message

bit (1)

1

Indicator

0 or 1

Indicator for transmitting(fix to 0)

messages with the same

4

DF388

Message Number andEpoch Time (1: multiple
message transmitted)
IOD SSRuint 4

4

5

6(fix to 0)

SSR Provider ID

uint 16

16

Issue Of Data number for
SSR in this message.

SSR Solution ID

uint 4

4

0 ~ 15(fix to 0)

Dispersive Bias

bit (1)

1Consistency

DF413
Not defined in
MADOCA
DF414
Not defined in
MADOCA
DF415
Not defined in
MADOCA
DF486※3
Not defined in
MADOCA

0 ~ 65535(fix to 0)

7

8

0 ~ 150 or 1(fix to 0)

Indicator
9

10

MW Consistency

bit (1)

1

Indicator
No. of Satellites

DF487※3
Not defined in
MADOCA

0 or 1(fix to 0)

uint 6

6

0 ~ 63

Number of Satellites

DF387

included in the message
Subtotal (#1 ~ #8)

69#11 ~ #20 are repeated for each satellites (1 ~ NS (No. of Satellites: see #10))
11

12

GALILEO Satellite ID

uint6

6

1 ~ 32GALILEO Satellite ID

DF252

No of Phase Biases

uint5

5

0 ~ 31

No of Phase Biases

DF479※3

Processed

Processed for one
individual satellite

39

B

13

Yaw Angle

uint9

9

0 ~ (2 – 1/256)

Yaw Angle

DF480※3

Yaw Rate

DF481※3B[semi‐circles](fix to 0)
14

Yaw Rate

int8

8±(127/8192)[semi‐circles /second](approx. ±2.79[degree/second])(fix to 0)

Subtotal (#11 ~ #14)28

#15 ~ #20 are repeated for NCB (No. of Carrier Phase Biases Processed: see #12) times
GALILEO Signal and15

uint 5

5

0 ~ 31

Tracking

GALILEO Signal andDF382

Tracking Mode Indicator

Mode Indicator
16

17

18
19

Signal Integer

uint 1

1

Indicator
Signals Wide‐Lane(fix to 0)
bit (2)

2

Integer Indicator
Signal Discontinuity

00, 01, 10, 11(fix to 00)

uint 4

4Counter
Phase Bias (FCB)

0 or 1

0 ~ 15(fix to 0)

int 2020±52.4287 [m]Phase Bias (FCB)

DF483※3
Not defined in
MADOCA
DF484※3
Not defined in
MADOCA
DF485※3
Not defined in
MADOCA
Resolution
0.0001[m]DF482※3Standard deviation20

uint1717

0 ~ 13.1071 [m]of Phase Bias (FCB)
Subtotal (#15 ~ #20)
Total

Standard deviation of

Resolution:
0.0001[m]Phase Bias (FCB)

Original DF

49
69 + 28×NS+ 49×∑NPB※1 As of September 2016, JAXA has been using "2067" as Message Type Number for Carrier Phase Bias of GALILEO,
However, this message type is changed to “12” in Feburuary 2017(Reference: Table 4.1‐1 Note 5).
※2 Defined draft version of RTCM (refer to Applicable Document(3)).
※3 Defined draft version of RTCM (refer to Applicable Document(4)).

40B(4) BDS (Message Type Number: 14※1 )The contents of SSR BDS Carrier Phase Bias Correction Messages are shown in Table5.5‐4.
Table5.5‐4 SSR BDS Carrier Phase Bias Correction Messages (Message Type Number: 14※1)
#

1

Name
Message Number

Data

No.

Type

of Bits

uint 12

12

Possible range

Contents

0 – 4095

SSR Message Type Number

Remarks
DF002※1(Value: 14 )BDS Epoch Time 1suint 20

20

0 – 604799[s]2

BDS Reference time (FullDF465※2

seconds since thebeginning of the GPS week)3

SSR Update Interval

bit (4)

4

0 – 15The SSR Update Intervals

DF391

B

for this message.
Multiplebit (1)1

MessageIndicator

0 or 1

Indicator for transmitting(fix to 0)

messages with the same

4

DF388

Message Number andEpoch Time (1: multiple
message transmitted)
IOD SSRuint 44

5

0 – 15

Issue Of Data number for

DF413(fix to 0)

SSR in this message.

Not definedin MADOCA

6

7

8

9

10

SSR Provider ID

uint 1616

DF414
Not definedin MADOCA
DF415
Not definedin MADOCA
DF486※3
Not definedin MADOCA
DF487※3
Not definedin MADOCA

0 – 65535(fix to 0)

SSR Solution ID

uint 4

4

0 – 15(fix to 0)

Dispersive Bias

bit (1)

1Consistency Indicator
MW Consistency(fix to 0)
bit (1)

1

Indicator
No. of Satellites

0 or 10 or 1(fix to 0)

uint 6

6

0 – 63

Number of Satellites

DF387

included in the message
Subtotal (#1 ~ #8)

69#11 ~ #20 are repeated for each satellites (1 ~ NS (No. of Satellites: see #10)
11

12

BDS Satellite ID

uint 6

6

0 – 63

BDS Satellite ID

DF466※2

No of Phase Biases

uint 5

5

0 – 31

No of Phase Biases

DF479※3

Processed

Processed for one
individual satellite

Yaw Angle
13

uint 990 – (2 –1/256)[semi‐circles](fix to 0)

41

Yaw Angle

DF480※3

B

Yaw Rate

int 8

8

±(127/8192)

Yaw Rate

DF481※3[semi‐circles /Bsecond]14(approx. ±2.79[degree/second])(fix to 0)
Subtotal (#11 ~ #14)28

#15 ~ #20 are repeated for NCB (No. of Carrier Phase Biases Processed: see #12) times
BDS Signal and15

uint 5

5

0 – 31

Tracking Mode

BDS Signal and Tracking

DF467※2

Mode Indicator

Indicator
16

17

18

Signal Integer

uint 1

1

Indicator
Signals Wide‐Lane(fix to 0)
bit (2)

2

Integer Indicator
Signal Discontinuity

00, 01, 10, 11(fix to 0)

uint 4

4Counter
Phase Bias(FCB)

0 or 1

0 – 15(fix to 0)

int 2020±52.4287 [m]Phase Bias (FCB)

19

DF483※3
Not definedin MADOCA
DF484※3
Not definedin MADOCA
DF485※3
Not definedin MADOCA
Resolution:
0.0001[m]DF482※3Standard deviation of20

uint 17

17

0 – 13.1071 [m]Phase Bias (FCB)
Subtotal (#15 ~ #20)
Total

Standard deviation of

Resolution:
0.0001[m]Phase Bias (FCB)

Original DF

49
69 + 28×NS+ 49×∑NPB※1 As of September 2016, JAXA has been using "2070" as Message Type Number for Carrier Phase Bias of BDS,
however, this message type is changed to “14” in Feburuary 2017(Reference: Table 4.1‐1 Note 5).
※2 Defined draft version of RTCM (refer to Applicable Document(3)).
※3 Defined draft version of RTCM (refer to Applicable Document(4)).

42B