Changeset 5615 in ntrip
- Timestamp:
- Jan 22, 2014, 2:49:30 PM (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/txt/frankfurt.tex
r5614 r5615 397 397 398 398 \begin{frame} 399 \frametitle{Principles of Precise Point Positioning} 400 \framesubtitle{Observation Equations} 401 402 The PPP is based on the processing of the ionosphere-free linear combination of phase 403 observations 404 \be 405 L^{ij}_3 = \varrho^{ij} - c\delta^{ij} + T^{ij} + \bar{N}^{ij}_3 ~, 406 \ee 407 where the ambiguity term is given by 408 \be 409 \bar{N}^{ij}_3 = N^{ij}_3 - l^{ij}_3 410 = \frac{c\;f_2}{f^2_1-f^2_2}\;(n^{ij}_1-n^{ij}_2) + \lambda_3\;n^{ij}_1 - l^{ij}_3 411 \ee 412 and (optionally) the ionosphere-free linear combination of code observations 413 \be 414 P^{ij}_3 = \varrho^{ij} - c\delta^{ij} + T^{ij} + p^{ij}_3 ~, 415 \ee 416 where the code bias $p^{ij}_3$ is the linear combination of biases 417 $p^{ij}_1,p^{ij}_2$ 418 \end{frame} 419 420 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 421 422 \begin{frame} 423 \frametitle{Principles of PPP Service} 424 \framesubtitle{Code Biases} 425 426 Apart from the orbit corrections (will be discussed later) the server has to provide the 427 value $c\delta^{ij}$. That is sufficient for a client processing phase observations only. 428 429 Using the code observations on the client-side is not mandatory. After an initial convergence 430 period (tens of minutes) there is almost no difference between a phase-only client and the client 431 that uses also the code observations. However, correct utilization of accurate code observations 432 improves the positioning results during the convergence period. 433 434 Client which processes code observations either 435 \begin{enumerate} 436 \item has to know the value $p^{ij}_3$ (the value must be provided by the server -- the most 437 correct approach), or 438 \item has to estimate terms $p^{ij}_3$, or 439 \item neglect the bias (de-weight the code observations -- not fully correct). 440 \end{enumerate} 441 Options (2) and (3) mean that the benefit of using the code observations on the client-side (in 442 addition to phase observations) is minor only. 443 444 \end{frame} 445 446 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 447 448 \begin{frame} 449 \frametitle{Principles of PPP Service} 450 \framesubtitle{Handling Code Biases} 451 452 In order to avoid the necessity to disseminate the code biases $p^{ij}_3$ and still guarantee that 453 the client may decently use the code observations we adopted the following approach: 454 455 Denoting the code bias estimated by a server at epoch $t_0$ by $\bar{p}^{ij}_3 = p^{ij}_3(t_0)$ we 456 modify the satellite clock corrections as follows: 457 \be 458 c\bar\delta^{ij} = c\delta^{ij} - \bar{p}^{ij}_3 459 \ee 460 and disseminate $c\bar\delta^{ij}$ instead of $c\delta^{ij}$. This modification has no effect on 461 the processing of phase observations at the client-side (the constant difference is absorb by 462 estimated ambiguities). For the processing of code observations it has the benefit that the client 463 does not see the code bias $p^{ij}_3$ but only 464 \bdm 465 \bar{p}^{ij}_3-p^{ij}_3 466 \edm 467 and we try to keep the difference $\bar{p}^{ij}_3-p^{ij}_3$ lower than a selected threshold. 468 469 \end{frame} 470 471 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 472 473 \section{PPP AR} 474 \subsection{Principles} 475 476 \begin{frame} 477 \frametitle{Principles of PPP with Ambiguity Resolution} 478 \framesubtitle{Observation Equations} 479 480 The PPPAR is in principle based on the processing the following two types of single-difference 481 observations: \\ 482 The ionosphere-free linear combination 483 \be\label{obs_IF} 484 L^{ij}_3 = \varrho^{ij} - c\delta^{ij} + T^{ij} + \bar{N}^{ij}_3 ~, 485 \ee 486 where the ambiguity term is given by 487 \be\label{amb_N3} 488 \bar{N}^{ij}_3 = N^{ij}_3 - l^{ij}_3 489 = \frac{c\;f_2}{f^2_1-f^2_2}\;(n^{ij}_1-n^{ij}_2) + \lambda_3\;n^{ij}_1 - l^{ij}_3 490 \ee 491 and the Melbourne-W\"{u}bbena linear combination 492 \be\label{obs_MW} 493 L^{ij}_w = \lambda_5\;n^{ij}_5 - l^{ij}_w 494 \ee 495 the uncalibrated bias $l^{ij}_3$ is the corresponding linear combination of biases 496 $l^{ij}_1,l^{ij}_2$, the uncalibrated bias $l^{ij}_w$ is the corresponding linear combination of 497 biases $p^{ij}_1,p^{ij}_2,l^{ij}_1,l^{ij}_2$. 498 \end{frame} 499 500 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 501 502 \subsection{Parameters provided by Server} 503 504 \begin{frame} 505 \frametitle{Principles of PPP with Ambiguity Resolution} 506 \framesubtitle{Parameters provided by Server} 507 In addition to orbit corrections, the server(s) has(have) to provide the values 508 \bdm 509 c\delta^{ij} ~,~ l^{ij}_w ~,~ l^{ij}_3 ~~~ \mb{or} ~~~~ (c\delta^{ij} + l^{ij}_3) ~,~ l^{ij}_w 510 \edm 511 Corrections $l^{ij}_w,l^{ij}_3$ depend on the set of fixed single-difference ambiguities on the 512 server-side. This set of fixed ambiguities is not unique - it depends on the constraints applied on 513 the ambiguities. 514 515 There is a difference between correction $l^{ij}_w$ and the narrow-lane correction $l^{ij}_3$. The 516 wide-lane correction $l^{ij}_w$ depends {\em only} on the ambiguities estimated at the 517 server-side. The narrow-lane correction $l^{ij}_3$ depends on the ambiguities and {\em also} on the 518 satellite clock corrections $\delta^{ij}$ estimated at the server-side. 519 520 \end{frame} 521 522 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 523 524 \begin{frame} 525 \frametitle{Principles of PPP with Ambiguity Resolution} 526 \framesubtitle{How many servers?} 527 All three corrections 528 \bdm 529 c\delta^{ij} ~~~ l^{ij}_w ~~~ l^{ij}_3 530 \edm 531 may be estimated together by a single server run (in which case the $c\delta^{ij}$ and $l^{ij}_3$ 532 are indistinguishable and are combined into $c\delta^{ij}+l^{ij}_3$) Or, each of them may be 533 estimated by a separate server run. 534 535 \vspace*{2mm} 536 Current approach: 537 \begin{itemize} 538 \item PPPNB server: estimates $c\delta^{ij}$ 539 \item PPPAR server: uses $c\delta^{ij}$ from PPPNB server and estimates $l^{ij}_w,l^{ij}_3$ 540 \end{itemize} 541 542 \vspace*{2mm} 543 Advantages: PPPAR corrections are compatible with PPPNB corrections (the client may decide between 544 PPP and PPPAR). 545 546 \vspace*{2mm} 547 Disadvantages: additional delay 548 549 \vspace*{2mm} 550 An alternative approach to consider: separate server run for $l^{ij}_w$. 551 552 \end{frame} 553 554 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 555 556 \begin{frame} 557 \frametitle{Principles of PPP with Ambiguity Resolution} 558 \framesubtitle{How to disseminate the corrections?} 559 560 \begin{enumerate} 561 \item The corrections are valid (accurate) on the single- (between satellites) difference 562 level but it is more practical to send the zero-difference (satellite-specific) corrections. 563 \item The corrections are specific for the observation types used for their estimation - e.g. if 564 the C/A code on the first carrier and the P-code on the second carrier have been used at the 565 server side, the client can use the $l^{ij}_w$ correction only if it uses the same two types of 566 code observations. 567 \end{enumerate} 568 569 The corrections $l^{ij}_w,l^{ij}_3$ are actually the combinations of the phase (and in case of 570 $l^{ij}_w$ also code) biases: 571 \begin{eqnarray*} 572 l^{ij}_w & = & \frac{1}{f_1-f_2} \bigl( f_1~l^{ij}_1 - f_2~l^{ij}_2 \bigr) - 573 \frac{1}{f_1+f_2} \bigl( f_1~p^{ij}_1 + f_2~p^{ij}_2 \bigr) ~ 574 \\ 575 l^{ij}_3 & = & \frac{1}{f^2_1-f^2_2} \bigl( f^2_1~l^{ij}_1 - f^2_2~l^{ij}_2 \bigr) 576 \end{eqnarray*} 577 RTCM suggests to send $p^{ij}_1,p^{ij}_2,l^{ij}_1,l^{ij}_2$ directly ... 578 579 \end{frame} 580 581 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 582 583 \begin{frame} 584 \frametitle{Principles of PPP with Ambiguity Resolution} 585 \framesubtitle{How to disseminate the corrections (continuation)?} 586 587 In principle there are altogether 5 values which can be sent by server(s): 588 \bdm 589 c\delta^{ij},p^{ij}_1,p^{ij}_2,l^{ij}_1,l^{ij}_2 590 \edm 591 PPPNB server estimates the $c\delta^{ij}$ and the ionosphere-free 592 linear combination of the code biases 593 \bdm 594 p^{ij}_3 = \frac{1}{f^2_1-f^2_2} \bigl( f^2_1~p^{ij}_1 - f^2_2~p^{ij}_2 \bigr) 595 \edm 596 PPPAR server estimates the $l^{ij}_w$ and $l^{ij}_3$. Assuming that we know the differential code 597 bias 598 \bdm 599 d^{ij}_{p1p2} = p^{ij}_1 - p^{ij}_2 600 \edm 601 The four values 602 \bdm 603 p^{ij}_3 ~~~ l^{ij}_w ~~~~ l^{ij}_3 ~~~~ d^{ij}_{p1p2} 604 \edm 605 can be converted into four biases 606 $p^{ij}_1,p^{ij}_2,l^{ij}_1,l^{ij}_2$. 607 608 \end{frame} 609 610 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 611 612 \begin{frame} 399 613 \frametitle{Precise Point Positioning with PPP (cont.)} 400 614 BNC provides a good framework for the PPP client (observations, orbits, and
Note:
See TracChangeset
for help on using the changeset viewer.