Core Networking · Study deck

Choosing the Right Network Type

Bandwidth is the amount of data a link can carry in a given time.

Packet Pete is your guide for this deck.

networkphysicalclassification

Packet Pete, the module guide, in a scene from this chapter.

After studying this chapter

Learning objectives

You will be able to:

Explain: The transmitter in the source starts with digital information, applies modulation and pulse shaping, converts the result through a DAC, and uses a mixer driven by a phase-locked-loop carrier for upconversion.
Explain: When that boundary is not recorded, teams blame the "network class" even though the real problem is a pairing policy, gateway queue, credential rotation, backhaul outage, or missing device-to-cloud mapping.
Explain: The classification is credible only when those dependencies are visible and testable, so boundary review becomes part of the architecture rather than a note for later.

Major section

Start With the Deployment Shape · Overview: Classify The Requirement, Not The Brand

Classify the Job Before Choosing a Network: Bandwidth is the amount of data a link can carry in a given time.

A gateway is a device or service that joins different parts of a system.
These devices share a site, but they do not share one network job.

PAN, LAN, and WAN describe useful reach bands, but each band still contains several technology choices.

Major section

Practitioner: Build A Classification Record

A useful network classification record is a small design artifact.

For each device type, name the class, the next boundary, the normal payload, the peak payload, the wake or mobility pattern, the owner of the infrastructure, and the field test that would falsify the choice.
Short-range, high-rate Wi-Fi variants hold one end.

Coverage and throughput are only the first two axes; power, topology, and ownership decide whether the tier is deployable.

Major section

Practitioner: Build A Classification Record (continued)

If a badge depends on doorway readers, the reader density is part of the classification record.

If a camera depends on PoE, switch power and uplink capacity are part of the record.
If a remote meter depends on an operator network, coverage evidence and subscription lifecycle are part of the record.
The illustrated LPWAN entries occupy a long-reach low-rate region, while cellular options vary by generation and configuration.

Major section

Practitioner: Build A Classification Record (continued)

Planned gateways can also turn a short radio link into a wide service.

For each device type, name the class, the next boundary, the normal payload, the peak payload, the wake or mobility pattern, the owner of the infrastructure, and the field test that would falsify the choice.
A classification record still has to add power, ownership, and a field test.
The mistake is forcing all devices into one class for diagram neatness.

The common trade is reach versus throughput, with power and ownership deciding which option is realistic.

Major section

Under The Hood: Each Class Hides A Boundary

Classification is not a protocol stack.

A PAN device still needs local addressing, pairing, channel access, and a bridge to wider services.
A LAN device still needs switch or access-point capacity, power, VLAN or security policy, and backhaul.
The hidden work is usually translation and ownership.
The class is shared.

PAN boundaries are usually reader, phone, hub, or coordinator boundaries.

Major section

Under The Hood: Each Class Hides A Boundary (continued)

Those handoffs may cross site, telecom, and cloud owners.

A WAN device still depends on gateway density, operator coverage, spectrum rules, provisioning, and lifecycle continuity.
The phone, hub, border router, or gateway that performs that handoff changes addressing, trust, timing, retry behavior, and failure visibility.
The Wi-Fi device needs coverage and airtime.

Do not treat range bands as guarantees. Indoor loss, gateway placement, antenna choice, and interference change the actual coverage boundary.

Major section

Under The Hood: Each Class Hides A Boundary (continued)

The phone sits in the middle as the central device, or coordinator.

A short-range device may speak Bluetooth LE, Zigbee, Thread, or another local protocol, but the enterprise system often expects IP topics, HTTP APIs, MQTT messages, or database records.
Ethernet can remove radio uncertainty, but it introduces cable plant, PoE budget, switch-port, VLAN, and maintenance boundaries.
That shape is the personal area network, and it is also its boundary.

Major section

Under The Hood: Each Class Hides A Boundary (continued)

The classification is credible only when those dependencies are visible and testable, so boundary review becomes part of the architecture rather than a note for later.

When that boundary is not recorded, teams blame the "network class" even though the real problem is a pairing policy, gateway queue, credential rotation, backhaul outage, or missing device-to-cloud mapping.
Wi-Fi can reuse building infrastructure, but access-point placement, channel planning, roaming behavior, and client density decide whether the class is actually adequate.
Everything the peripherals report reaches the wider system only through the device in the middle.

Major section

Under The Hood: Each Class Hides A Boundary (continued)

Cellular and LPWAN (LoRaWAN, Sigfox, NB-IoT, or a narrower option such as Weightless) can reach remote assets, but SIM provisioning, roaming policy, regional spectrum rules, gateway density, payload limits, and operator lifecycle become design dependencies.

Whoever controls the phone, reader, hub or coordinator controls pairing, trust, timing, and what the rest of the estate ever gets to see.
One router and access point sits at the centre as the gateway.
A PLC reaches it over Ethernet, a sensor over Wi-Fi, a camera over PoE, and an MQTT broker over IP.

Major section

Under The Hood: Each Class Hides A Boundary (continued)

The Ethernet device needs a cable run and a free switch port.

The camera needs power budget from the same switch that carries its data. Figure: LAN boundaries are access-point shows why calling something a LAN device settles very little.
The cable plant, power budget and coverage plan behind each link are not.
Capacity BoundaryA class can be correct while a deployment is still overloaded.

LAN boundaries are access-point, switch, cable, power, and building-coverage boundaries.

Major section

Under The Hood: Each Class Hides A Boundary (continued)

The gateway does not complete the service; it forwards packets over IP backhaul to network services that deduplicate, authorize, and route them toward the application.

A strong radio link can therefore coexist with a failed service when gateway power, backhaul, roaming, or platform routing is unavailable.
The WAN record should name each boundary, its observable health, the data custody point, and what devices do while the next owner cannot accept traffic.
Gateway BoundaryWhen a PAN or LPWAN device crosses into IP services, the gateway becomes part of the reliability and security design.

WAN boundaries are gateway, operator, backhaul, roaming, and service-continuity boundaries.

Major section

Phoebe's Field Notes: Why a Weak Path Costs Battery, Not Just Signal · From Baseband Bits to an RF Link

At fixed bandwidth, LoRa symbol time is $2^{SF}/BW$ , so moving from SF7 to SF12 makes each symbol 32 times longer.

Packet airtime and transmit energy also depend on the number of payload and overhead symbols, coding, and current draw; they are not automatically 32 times larger.
Classify reach, rate, and energy together.
Frequency still changes how a wave interacts with people, air, building materials, and obstacles, so a band choice is never only a data-rate label.

Major section

Under the Hood: Transmit and Receive Chains · Modulation Trade-off Explorer

The transmitter in the source starts with digital information, applies modulation and pulse shaping, converts the result through a DAC, and uses a mixer driven by a phase-locked-loop carrier for upconversion.

The chain explains why a nominal bit rate is not a complete link claim.

Major section

Physical Media and the Interface Boundary

The IP payload survives, but each link removes and creates its own link frame and physical symbols.

The same packet can cross copper, fibre, and radio without the application changing its meaning.
The controller adds or checks link framing and moves bits to the PHY.
A network interface card is one implementation of that boundary.

Deck summary

Key takeaways

Classify the Job Before Choosing a Network: Bandwidth is the amount of data a link can carry in a given time.

A useful network classification record is a small design artifact.
If a badge depends on doorway readers, the reader density is part of the classification record.
Planned gateways can also turn a short radio link into a wide service.
Classification is not a protocol stack.

Retrieval practice

Recall check 1 of 4

Packet Pete says: answer from memory, then check your reasoning.

Q1A badge sends a small identifier to a phone or doorway reader inside a building. Which classification question should come first?

AWhich cellular plan gives the badge the highest peak WAN rate?

BCan the badge skip gateways and send each identifier directly to cloud services?

CCan a PAN path meet badge range, battery, gateway, and handoff needs before adding LAN or WAN?

DCan the badge use the building's default radio class because the reader network supplies the needed boundary?

Show answer

Answer: C Classify from the device's real communication job: reach, payload, power, gateway boundary, mobility, ownership, and reliability.

Retrieval practice

Recall check 2 of 4

Packet Pete says: answer from memory, then check your reasoning.

Q2A campus design includes low-power room sensors, PoE security cameras, and shuttle tracking. Which classification decision is strongest?

AAssign all devices to LPWAN because the campus area is large.

BUse mesh for sensors, Ethernet for cameras, and WAN for shuttles.

CAssign all devices to Wi-Fi because access points already exist.

DChoose advertised coverage alone without traffic or mobility checks.

Show answer

Answer: B IoT systems often combine PAN, LAN, and WAN tiers.

Retrieval practice

Recall check 3 of 4

Packet Pete says: answer from memory, then check your reasoning.

Q3A low-power network class fits field sensors, but its gateway queue grows and the operator will retire its backhaul plan. What does the classification review need?

AIncrease sensor radio power because stronger uplinks will clear the growing gateway queue and restore delivery.

BUse only the network class label as proof of capacity and continuity.

CSkip follow-up because previous range evidence supposedly settles queue risk.

DTest capacity and name a gateway and backhaul replacement owner and plan.

Show answer

Answer: D Class fit does not resolve overload or service continuity across the gateway.

Retrieval practice

Recall check 4 of 4

Packet Pete says: answer from memory, then check your reasoning.

Q4Which review finding should fail a network classification decision before rollout?

AA recorded class choice using range, cadence, power, gateway, and field evidence.

BA mixed PAN, LAN, and WAN design matched to device traffic and mobility.

CEthernet for fixed cameras and low-power mesh for sparse room sensors.

DA class selected by range alone without measured field coverage.

Show answer

Answer: D Classification decisions fail when they rely on class labels or range slogans instead of measured deployment requirements and boundary evidence.

Print reference

Answers

Answer key.

C · Classify from the device's real communication job: reach, payload, power, gateway boundary, mobility, ownership, and reliability.
B · IoT systems often combine PAN, LAN, and WAN tiers.
D · Class fit does not resolve overload or service continuity across the gateway.
D · Classification decisions fail when they rely on class labels or range slogans instead of measured deployment requirements and boundary evidence.