ArticleslgStudy

astronomy

Paul Baran

Paul Baran is a astronomy topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Paul Baran rather than just read about it. In short: Paul Baran (born Pesach Baran ; April 29, 1926 – March 26, 2011) was a Polish-American engineer who was a pioneer in the development of computer networks. He was one of the two independent inventors of packet switching, which is today the dominant basis for data communications in computer networks worldwide, and went on to start several companies and develop other technologies that are an essential part of modern di…

Paul Baran — main illustration
Paul Baran — illustration

Key takeaways

  • Paul Baran belongs to astronomy; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect Paul Baran to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of Paul Baran from memory before moving on to harder problems.

Reference excerpt

Paul Baran (born Pesach Baran ; April 29, 1926 – March 26, 2011) was a Polish-American engineer who was a pioneer in the development of computer networks. He was one of the two independent inventors of packet switching, which is today the dominant basis for data communications in computer networks worldwide, and went on to start several companies and develop other technologies that are an essential part of modern digital communication.

Early life He was born in Grodno (then in the Second Polish Republic, and since 1945 part of Belarus) on April 29, 1926. He was the youngest of three children in his Lithuanian Jewish family, with the Yiddish given name "Pesach". His family moved to the United States on May 11, 1928, settling in Boston and later in Philadelphia, where his father, Morris "Moshe" Baran (1884–1979), opened a grocery store. He graduated from Drexel University (then called Drexel Institute of Technology) in 1949, with a degree in electrical engineering. He then joined the Eckert-Mauchly Computer Company, where he did technical work on UNIVAC models, the first brand of commercial computers in the United States. In 1955 he married Evelyn Murphy, moved to Los Angeles, and worked for Hughes Aircraft on radar data processing systems. He obtained his master's degree in engineering from UCLA in 1959, with advisor Gerald Estrin while he took night classes. His thesis was on character recognition. While Baran initially stayed on at UCLA to pursue his doctorate, a heavy travel and work schedule forced him to abandon his doctoral work.

Packet switched network design

After joining the RAND Corporation in 1959, Baran took on the task of designing a "survivable" communications system that could maintain communication between end points in the face of damage from nuclear weapons during the Cold War. Then, most American military communications used high-frequency connections, which could be put out of action for many hours by a nuclear attack. Baran decided to automate RAND Director Franklin R. Collbohm's previous work with emergency communication over conventional AM radio networks and showed that a distributed relay node architecture could be survivable. The Rome Air Development Center soon showed that the idea was practicable. Using the minicomputer technology of the day, Baran and his team developed a simulation suite to test basic connectivity of an array of nodes with varying degrees of linking. That is, a network of n-ary degree of connectivity would have n links per node. The simulation randomly "killed" nodes and subsequently tested the percentage of nodes that remained connected. The result of the simulation revealed that networks in which n ≥ 3 had a significant increase in resilience against even as much as 50% node loss. Baran's insight gained from the simulation was that redundancy was the key. His first work was published as a RAND report in 1960, with more papers generalizing the techniques in the next two years. After proving survivability, Baran and his team needed to show proof of concept for that design so that it could be built. That involved high-level schematics detailing the operation, construction, and cost of all the components required to construct a network that leveraged the new insight of redundant links. The result was one of the first store-and-forward data layer switching protocols, a link-state/distance vector routing protocol, and an unproved connection-oriented transport protocol. Explicit detail of the designs can be found in the complete series of reports On Distributed Communications, published by RAND in 1964. The design flew in the face of telephony design of the time by placing inexpensive and unreliable nodes at the center of the network and more intelligent terminating 'multiplexer' devices at the endpoints. In Baran's words, unlike the telephone company's equipment, his design did not require expensive "gold plated" components to be reliable. The Distributed Network that Baran introduced was intended to route around damage. It provided connection to others through many points, not one centralized connection. Fundamental to the scheme was the division of the information into "blocks" before they were sent out across the network. That enabled the data to travel faster and communications lines to be used more efficiently. Each block was sent separately, traveling different paths and rejoining into a whole when they were received at their destination.

Selling the idea After the publication of On Distributed Communications, he presented the findings of his team to a number of audiences, including AT&T engineers (not to be confused with Bell Labs engineers, who at the time provided Paul Baran with the specifications for the first generation of T1 circuit that he used as the links in his network design proposal). In subsequent interviews, Baran mentioned how the AT&T engineers scoffed at his idea of non-dedicated physical circuits for voice communications, at times claiming that Baran simply did not understand how voice telecommunication worked. Donald Davies, at the National Physical Laboratory in the United Kingdom, also thought of the same idea and implemented a trial network. While Baran used the term "message blocks" for his units of communication, Davies used the term "packets," as it was capable of being translated into languages other than English without compromise. He applied the concept to a general-purpose computer network. Davies's key insight came in the realization that computer network traffic was inherently "bursty" with periods of silence, compared with relatively-constant telephone traffic. It was in fact Davies's work on packet switching, not Baran's, that initially caught the attention of the developers of ARPANET at the Symposium on Operating Systems Principles in October 1967. Baran was happy to acknowledge that Davies had come up with the same idea as him independently. In an e-mail to Davies, he wrote:

… excerpt ends here. Continue reading the full article.

Illustrations

Paul Baran illustration
Paul Baran: The "block message" as suggested by Paul Baran in 1964; his initial proposal in 1962 was the first use of the concept of a data packet.
The "block message" as suggested by Paul Baran in 1964; his initial proposal in 1962 was the first use of the concept of a data packet.

Worked examples

Example 1 — a first encounter with Paul Baran

Start with the simplest possible case. Write down what Paul Baran claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In astronomy, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Paul Baran before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Paul Baran ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Paul Baran

In research
Paul Baran appears in astronomy research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses Paul Baran in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
Paul Baran is common in secondary-school and first-year university syllabi. It links to neighbouring topics 1926 births, 2011 deaths, 20th-century American inventors, so understanding it makes those chapters shorter.
In everyday life
Look for Paul Baran outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.
Ask Teacher Smith questions about this articleOpens your AI tutor with a question about “Paul Baran” →

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Paul Baran in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what Paul Baran means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain Paul Baran out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Paul Baran in simple terms?

Paul Baran (born Pesach Baran ; April 29, 1926 – March 26, 2011) was a Polish-American engineer who was a pioneer in the development of computer networks. He was one of the two independent inventors of packet switching, which is today the dominant basis for data communications in computer networks…

Why does Paul Baran matter?

Because it connects several astronomy ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Paul Baran?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Paul Baran.

Tags

  • 1926 births
  • 2011 deaths
  • 20th-century American inventors
  • American businesspeople in the telecommunications industry
  • American people of Belarusian-Jewish descent
  • American people of Polish-Jewish descent
  • Belarusian Jews
  • Benjamin Franklin Medal (Franklin Institute) laureates
  • Drexel University alumni
  • Fellows of the American Academy of Arts and Sciences
  • Internet pioneers
  • National Medal of Technology recipients

Keep exploring