KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesUntethered: Digital Mobile Telephony, Satellite Positioning and the SmartphoneEngineering · ElectricalLesson 4/14← PrevNext →
GuidePublished 4 Aug 2026Updated 13 Aug 202611 min readBy Kevin JoginTelecommunicationsInstrumentationElectronicsStandards
On this page

Ask about this page

KEVOS AIUntethered: Digital Mobile Telephony, Satellite Positioning and the Smartphone

KEVOS knowledge first · trusted web sources when needed

Knowledge LibraryEngineeringElectrical EngineeringKL-ENG-HIST-1663

Untethered: Digital Mobile Telephony, Satellite Positioning and the Smartphone

Cellular reuse turned fixed capacity into capacity that scales with infrastructure. Satellite positioning solved for the receiver’s clock as a fourth unknown. And a free universal service became a common-mode risk precisely because it was free and universal.

Part 4 of 14 Period 1991-2007 Milestones 3 Reading 5 min Updated 2026-08-04

01Executive summary

Three milestones that separated communication from place, made position a free service, and then folded a dozen devices into one.

GSM service began in 1991, agreed across many countries so that a handset and its subscriber identity worked across borders. GPS reached full operational capability in 1995, providing position and precise time to any receiver without that receiver transmitting anything. The smartphone arrived as a category in 2007 and consolidated telephone, camera, navigator, music player, computer and sensor platform into one object.

ReuseThe cellular idea: use the same frequency again beyond an interference distance
4Satellites needed for a position fix: three dimensions plus receiver clock error
PassiveA satellite positioning receiver transmits nothing at all
SIMSubscriber identity separated from the handset it sits in

02The cellular idea, and what GSM added

Early mobile radio used one powerful transmitter covering a whole city. Since a frequency in use cannot be reused anywhere within range, total capacity equalled the number of channels in the allocated band — a few dozen simultaneous calls for an entire metropolis.

The cellular concept inverts this. Use many low-power transmitters, each covering a small area, and reuse the same frequency in any cell far enough away that interference is acceptable. Capacity now scales with the number of cells rather than the number of channels. Making cells smaller increases capacity further, at the cost of more sites and more handovers.

Consequence

Handover becomes essential

A moving subscriber crosses cells mid-call, so the network must transfer the connection without interruption. This requires continuous measurement, a decision policy and signalling — complexity that exists solely because cells are small.

Consequence

Capacity is bought with sites

More capacity means more cells, which means more sites, backhaul and planning consent. Mobile network economics are dominated by site acquisition and civil works rather than by radio.

Consequence

Power control matters constantly

Handsets and base stations continuously adjust transmit power to the minimum adequate, limiting interference into neighbouring cells and extending battery life. The system is a distributed control loop.

Consequence

Identity separates from hardware

GSM put subscriber identity on a removable module, so the subscription is independent of the handset. Separating identity from device is a clean architectural decision with consequences well beyond telephony.

Why the standardisation mattered more than the radio

GSM’s technical choices were reasonable rather than remarkable. Its significance is that a large group of countries agreed one specification in advance, so equipment from many manufacturers interoperated and subscribers roamed internationally. That agreement created a market large enough to drive handset cost down rapidly, which in turn drove adoption. As with the shipping container in the previous series, the standard was worth more than any technology inside it.

03Satellite positioning: solving for time as well as place

Each satellite broadcasts its position and the time of transmission. A receiver measures arrival time, multiplies the difference by the speed of light, and obtains a range. Three ranges would fix a position in three dimensions if the receiver’s clock were perfect.

It is not. A receiver cannot carry an atomic clock, and an error of one microsecond is about 300 metres of range error. The elegant part of the design is that receiver clock error is treated as a fourth unknown and solved for alongside the three position coordinates. One extra satellite turns an intractable requirement into a solvable system — and as a by-product every receiver obtains time far more accurately than it could otherwise, which is why satellite positioning underpins the timing of power grids, financial systems and telecommunications networks.

Relativity is an engineering correction, not a curiosity

Satellite clocks run at a measurably different rate from clocks on the ground: slower from their velocity, faster from being higher in Earth’s gravitational field, with the second effect dominating. The net offset is tens of microseconds per day, which is kilometres of position error if uncorrected. It is corrected in the satellite clock rate and in the receiver’s computation. This is one of the very few places where general relativity is a routine design input rather than a theoretical matter.

Why the receiver being passive is the important property

A positioning receiver transmits nothing. That gives unlimited user capacity, since there is no contention for anything, and it means position can be determined without disclosing that you are determining it. Both properties come from a single architectural choice: broadcast the reference, compute at the edge. The same structure appears in time distribution, differential correction services and public-key certificate distribution.

And why dependence on it is now a risk

Received signals are extremely weak and are trivially jammed or spoofed. Because so much infrastructure has adopted satellite timing as a free and accurate reference, a common-mode failure now propagates far beyond navigation. Holdover oscillators, alternative time sources and plausibility checking are standard mitigations, and the general lesson is that a free, universally adopted service becomes a single point of failure precisely because it is free and universally adopted.

04The smartphone: integration as the achievement

Every component of a smartphone existed beforehand. Touch screens, mobile data, cameras, accelerometers, positioning and portable computers were all available. The milestone is that a combination reached the point where each function was good enough that carrying a dedicated device stopped being worthwhile.

Enabling conditions that had to arrive together
ElementWhat had to be true
Capacitive multi-touchAccurate finger input without a stylus, allowing the display to be the entire interface and the keyboard to be virtual
Lithium-ion energy densityA day of mixed use in a pocketable mass, which no earlier chemistry could deliver
Low-power system-on-chipApplication processor, radio, graphics and signal processing integrated within a thermal budget with no fan
Packet mobile dataAlways-on data rather than dial-up sessions, making network-dependent applications usable
MEMS sensorsCheap accelerometers, gyroscopes and magnetometers, giving orientation and motion at negligible cost
Third-party software distributionA route for developers to reach users directly, which turned the device into a platform rather than a product

The last row is the one engineers most often undervalue. The hardware integration was impressive but replicable. What made the category durable was that the device became a substrate others could build on — the same platform argument as the microprocessor and TCP/IP, arriving in a consumer product.

05Takeaways for current practice

  • Reuse beats allocation. Spatial reuse converted a fixed capacity into one that scales with infrastructure density.
  • Turn an impossible requirement into an extra unknown. Solving for receiver clock error removed the need for an atomic clock in every receiver.
  • Broadcast the reference, compute at the edge. It gives unlimited capacity and requires no disclosure by the user.
  • Free universal services become common-mode risks. Identify what would fail together, and provide holdover or an independent check.
  • Integration is a real achievement, but platform status is what endures. Enabling others to build determines whether a product becomes a category.

Australian references relevant to this part include ACMA spectrum licensing instruments, AS/NZS 2772 for radiofrequency exposure, and AS/NZS 61000 for electromagnetic compatibility. Cited by number for orientation only — verify currency.

Previous in seriesEthernet, cryptography, TCP/IP, the WebNext in seriesUtility compute and learned featuresSeries indexMilestones of the Modern Era, 1970-2020

KL-ENG-HIST-1663 · KEVOS® Knowledge Library · Engineering / Electrical Engineering

  • Telecommunications
  • Instrumentation
  • Electronics
  • Standards
  • History of Engineering
  • Electrical Engineering

Original KEVOS® synthesis. Historical dates, attributions and device descriptions are drawn from general engineering history; the analysis, structure, standards commentary and Australian practice notes are our own. Figures are indicative and are given for teaching purposes — verify against the governing standard or manufacturer data before using them in design.

© KEVOS® — Precision to Vision. Prepared by Kevin Jogin.

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Untethered: Digital Mobile Telephony, Satellite Positioning and the Smartphone. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to carry the subject from function and assumptions through design evidence, verification and controlled release. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Apply Untethered: Digital Mobile Telephony, Satellite Positioning and the Smartphone by beginning with the duty, not the component or software command. Convert the key ideas—satellite, positioning, smartphone, place, time—into measurable requirements and interfaces. Record operating and non-operating environments, duty cycle, expected life, loads, energy sources, human interaction and reasonably foreseeable abnormal conditions. When a value is not a project requirement or verified supplier datum, identify it as an assumption or illustrative value.

Create a calculation and evidence trail that another competent person can audit. Every input should carry a source, unit, revision and uncertainty or tolerance where relevant. Every model should state its boundary conditions and limitations. Keep nominal capacity separate from design capacity, and keep verification margin separate from an arbitrary safety factor. If a code or standard governs the work, confirm the applicable edition and contractual status rather than copying a number from a secondary summary.

Design for manufacture, assembly, inspection, operation and maintenance at the same time. A technically valid geometry can still fail because it cannot be fixtured, measured, cleaned, guarded, reached or replaced. Review process capability, datum or reference strategy, tolerance accumulation, access, error-proofing and changeover. Where people interact with plant, apply the hierarchy of controls and consult those who will operate, clean, maintain and recover the equipment.

Plan verification before release. Define the characteristic, method, equipment, sample or test condition, acceptance criterion, record and responsible person. Validation then asks a different question: whether the resulting system is effective and suitable in the intended use context. A passed drawing check or analysis does not by itself validate usability, maintainability or production performance.

Step-by-step operating method

  1. Define the duty. Capture the required function, interfaces, operating environment, life, loads and unacceptable outcomes.
  2. Establish the model. Identify governing principles, units, material or process data, assumptions and uncertainty.
  3. Develop alternatives. Compare feasible concepts against performance, manufacturability, safety, maintainability and cost.
  4. Verify the design. Use analysis, test, inspection or demonstration with acceptance criteria defined before execution.
  5. Release and learn. Baseline the design, control changes, retain evidence and feed operating results into the next revision.

Illustrative design review record

Illustrative values only. Build a one-page record with the required function, input sources, assumptions, governing load or process condition, failure consequences, selected concept, verification method and acceptance criterion. Mark every numerical input as project requirement, verified supplier data, measured value, calculation output or assumption. Review the weakest evidence first. If an assumption can change safety, compliance, interchangeability or capacity, it must be resolved before release rather than buried in a calculation note.

Evidence classQuestionRelease expectation
RequirementWhat must the design do and under which conditions?Approved and traceable
InputWhere did the load, property, tolerance or process limit come from?Source, unit and revision recorded
AnalysisWhich model and assumptions connect input to result?Checkable calculation or simulation
VerificationHow will conformity be demonstrated?Method and acceptance criterion agreed
ValidationWill the solution work for intended users and conditions?Representative use evidence

Common failure modes and recovery actions

1. Watch for

Starting detailed design before interfaces and operating limits are agreed.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Using catalogue or typical values as though they were certified project inputs.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Checking nominal performance while ignoring tolerances, degradation and foreseeable misuse.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Confusing verification of requirements with validation of user need.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Releasing drawings or procedures without configuration, inspection and change controls.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.

Review checklist

  • What function and failure consequence govern this decision?
  • Which inputs are measured, specified, assumed or illustrative?
  • How will conformity be demonstrated and recorded?
  • What change would invalidate the current evidence?
  • Are mandatory requirements distinguished from recommendations and illustrative values?
  • Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
  • Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
  • Is there a named owner and a trigger for review, escalation, change or retirement?

Questions for deeper application

What is the most important distinction a practitioner must preserve when applying Untethered: Digital Mobile Telephony, Satellite Positioning and the Smartphone?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Which assumption about satellite would change the result most if it proved false?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

What evidence would allow an independent reviewer to reproduce or challenge the conclusion?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Which boundary, exception or failure case has not yet been tested?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

What must be handed over, monitored or reviewed after the immediate work is complete?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Authoritative references and use notes

The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.

  • NASA Systems Engineering Handbook — NASA. Used for requirements, design, verification, validation and technical management. Accessed 2026-08-13.
  • Identify, assess and control hazards — Safe Work Australia. Used for hazard identification, risk assessment, controls and review. Accessed 2026-08-13.

Continue learning

Networks and Protocols: Ethernet, Public-Key Cryptography, TCP/IP and the WebGuide · ElectricalNEXT LESSON →Computation as Infrastructure: Utility Computing and Machine Learning at ScaleGuide · ElectricalThe Programmable Machine: The Microprocessor, Flash Memory and Lithography ScalingGuide · ElectricalStoring Energy: The Lithium-Ion Cell, Hybrid Traction and Grid-Scale BatteriesGuide · Mechanical
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®