Exercises — GNSS — GPS, GLONASS, Galileo, BeiDou
3.5.19 · D4· Physics › Guidance, Navigation & Control (GNC) › GNSS — GPS, GLONASS, Galileo, BeiDou
Constants jo poore document mein use honge (inhe ek baar state kar lete hain taaki koi symbol unexplained na rahe):
Level 1 — Recognition
L1.1
Q: Observation equation mein, har ek chaar symbols ko simple words mein naam do.
Recall Solution
- = satellite tak ka pseudorange: woh distance jo tumne socha ki tune measure ki, apni imperfect clock use karke.
- = true geometric distance (seedhi line) tumse satellite tak.
- = clock-bias distance: tumhari clock error (seconds) ko se multiply karke metres mein convert kiya.
- = leftover errors (atmosphere bending, receiver noise).
L1.2
Q: Ek standard receiver ko 3D fix ke liye kitne satellites chahiye, aur kyun utne hi?
Recall Solution
Chaar. Unknowns hain tumhare teen coordinates aur tumhara clock bias — yani 4 unknowns. Har satellite ek equation deta hai, toh tumhe kam se kam 4 equations chahiye ⇒ 4 satellites.
L1.3
Q: GPS aur Galileo dono same L1/E1 frequency 1575.42 MHz pe broadcast karte hain, phir bhi receiver inhe alag kar leta hai. Yeh kaun sa access method possible banata hai — CDMA ya FDMA — aur ek sentence mein, kaise?
Recall Solution
CDMA (Code Division Multiple Access). Har satellite ek hi frequency share karta hai lekin ek unique pseudo-random code carry karta hai; receiver incoming signal ko har known code ke against correlate karta hai taaki ek ek satellite ko pick out kar sake.
Level 2 — Application
L2.1
Q: Ek GPS signal tumtak pahunchne mein ms leta hai. Yeh kitni straight-line distance correspond karta hai? Kya yeh MEO altitude ke saath consistent hai?
Recall Solution
Distance = speed × time: Kyun: bas "light us time mein kitni door jaati hai" hai. km MEO band ke andar aata hai (~19,000–24,000 km, dekho Orbital Mechanics — MEO/GEO/IGSO), toh sanity check pass ho jaata hai.
L2.2
Q: Tumhari receiver clock fast hai. Isse har pseudorange mein kitne metres ka range error inject hota hai?
Recall Solution
Kyun: observation equation mein bias term literally hai. Ek microsecond m hota hai; do microseconds, m. Isliye timing — geometry nahi — raw GNSS error ko dominate karta hai, aur isliye ko solve karna padta hai, kabhi bhi zero assume nahi karna.
L2.3
Q: Do satellites km aur km pe hain (ek flat 2D duniya). Tumhare measured pseudoranges hain km aur km, aur (unrealistically) tumhari clock perfect hai (). Tum kahan ho? 2D mein kaam karo.
Recall Solution
ke saath pseudoranges sach mein true distances hain, toh tum dono circles pe ho: Dono equations subtract karo — terms cancel ho jaate hain: ko circle 1 mein wapas daalo: Toh km ya km. Figure dekho: do circles do points pe milti hain. Earth pe tum physically impossible wala discard karte ho (jaise satellites ke upar wala point, ya planet ke bahar). Yeh 2D shadow hai uss reason ka ki ambiguity khatam karne ke liye ek extra satellite kyun chahiye.

Level 3 — Analysis
L3.1
Q: GPS satellite clocks ground clocks se +38 μs per day tez tick karte hain. Agar yeh drift correct nahi ki gayi, toh ek din mein implied position error kitni door tak badh jaati hai? Reasoning dikhao.
Recall Solution
Ek uncorrected clock error ek range error ban jaata hai: Kyun: wahi machinery — ki timing error km ki distance error hai. Isliye satellite oscillator ko ground pe pre-detune kiya jaata hai: fix launch se pehle hi bake in ho jaata hai. Yeh Special Relativity — Time Dilation (clock slow hoti hai) aur General Relativity — Gravitational Time Dilation (clock fast hoti hai) ko blend karta hai, jisme GR term jeet jaata hai.
L3.2
Q: ko uske do relativistic pieces mein split karo. Satellite speed m/s lo aur gravitational-potential term de raha hai. Special-relativity slowdown nikalo aur net confirm karo.
Recall Solution
Special relativity moving clock ko fraction se slow karta hai per unit time. Ek din mein ( s ): Net: . ✓ Kyun: SR (motion) aur GR (upar kamzor gravity) opposite directions mein push karte hain; gravitational speed-up jeet jaata hai, aur famous milta hai.
Level 4 — Synthesis
L4.1
Q: Chaar satellites sab horizon ke paas ek hi patch mein cluster hain (tumse almost ek hi direction mein). Geometry matrix idea use karke qualitatively explain karo kyun tumhari vertical position bahut uncertain ho jaati hai, aur isse ek number (GDOP) se connect karo.
Recall Solution
Geometry matrix ki har row tumse ek satellite ki taraf unit line-of-sight vector hoti hai (plus clock column ke liye ek ). Agar chaar satellites almost ek hi direction mein hain, toh woh unit vectors almost parallel hain. Parallel rows ko almost singular bana deti hain (uska inverse blow up ho jaata hai). Kyunki near-singular matrix GDOP ko bada kar deta hai, aur phir ek chhoti si range error ko ek badi position error mein amplify kar deta hai. Vertical sabse zyada suffer karta hai kyunki koi satellite overhead ya neeche nahi hai jo tumhari height ko "pin" kare — figure dekho: jab sab sight-lines horizon skim kar rahi hain, tumhe upar ya neeche move karne se koi bhi range barely change hoti hai. Dekho Dilution of Precision (DOP) aur Least Squares Estimation.

L4.2
Q: Ek carpenter table ko brace karta hai. Ek line mein explain karo ki "legs ko door door faila do" ka principle wahi hai jaise "satellites ko sky mein spread karo," aur phone practically yeh achieve karne ke liye kya action leta hai.
Recall Solution
Widely spread supports wobble resist karte hain kyunki ek chhota push structure ko ab collapse nahi kar sakta — mathematically, spread-out directions geometry matrix ko well-conditioned banate hain taaki errors amplify na hon. Phone yeh achieve karta hai sab chaar constellations ek saath use karke (GPS + GLONASS + Galileo + BeiDou), toh zyada satellites aur zyada directions mein visible hote hain, DOP kam hota hai — urban canyons mein bahut zaroori.
Level 5 — Mastery
L5.1
Q: Linearized least-squares update setup karo (haath se fully invert mat karo) jo chaar pseudoranges ko ek position-and-clock correction mein turn karta hai. State karo: (a) unknown vector, (b) ki har row kya hai, (c) update formula, aur (d) hum iterate kyun karte hain.
Recall Solution
(a) Unknown correction vector — teen position nudges aur clock-bias nudge (metres mein).
(b) Satellite ke liye, ki uski row hai , jahan unit vector hai jo tumhare guessed position se satellite ki taraf point karta hai. Last column mein woh kehta hai "ek clock error saari pseudoranges ko equally shift karta hai."
(c) Measured-minus-predicted residuals ke saath:
(d) Hum iterate karte hain kyunki true equations nonlinear hain (square roots). Taylor linearization sirf guess ke paas accurate hai. Toh hum: guess karo → linearize karo → solve karo → guess update karo → repeat karo jab tak ek tolerance se neeche na aa jaaye (usually 2–3 loops). Yeh exactly Least Squares Estimation hai ek loop mein wrapped; ek moving receiver ke liye tum ise ek Kalman Filter mein feed karte ho ek Inertial Navigation System (INS) ke saath.
L5.2
Q: Ek receiver sirf 3 satellites dekh raha hai lekin yeh bhi jaanta hai ki woh sea level pe hai (altitude = 0). Kya phir bhi fix mil sakta hai? Kitne equations, kitne unknowns?
Recall Solution
Haan. Altitude constraint ek free extra equation hai ("tumhari height 0 hai"). Count karo: unknowns abhi bhi = 4 hain. Equations = 3 pseudoranges + 1 altitude = 4. Chaar equations, chaar unknowns ⇒ solvable. Yeh "altitude aiding" hai, ek real trick jo ships, barometers wale aircraft, aur known-terrain database wale receivers use karte hain.
Recall Ek-line self-test — kya tum yeh fill kar sakte ho?
Standard GNSS fix mein unknowns ki sankhya ::: Chaar — aur clock bias . clock error se range error ::: m. Kaun sa relativity effect GPS clock ko fast chalata hai ::: General relativity (upar kamzor gravity) — yeh special-relativity slowdown ko outweigh karta hai. High GDOP physically kya matlab hai ::: Satellites ek jagah bunched hain, toh chhoti range errors badi position errors mein blow up ho jaati hain. 3 satellites phir bhi fix kaise de sakte hain ::: Ek external constraint add karo (jaise known altitude) 4th equation ke roop mein.