Specialized Wireless Networks and Applications

Introduction and Context

Wireless communication is no longer a single technology domain organized around cellular voice and broadband data. Modern systems are heterogeneous: a temperature sensor may use a low-power wide-area network (LPWAN), a robot may use industrial Wi-Fi or private 5G, a vehicle may exchange safety messages directly with nearby vehicles, and a ship or aircraft may rely on a satellite or hybrid terrestrial–non-terrestrial link. Each network is optimized for a different combination of range, throughput, latency, reliability, energy consumption, mobility, security, and cost.

The engineering challenge is therefore not simply to select the newest radio interface. It is to translate application requirements into a system architecture, choose appropriate technologies, quantify performance, manage interference and mobility, and provide dependable operation under regulatory and environmental constraints. This chapter develops a design-oriented framework for Wi-Fi, Bluetooth, LPWAN, Internet of Things (IoT), vehicular, industrial, satellite, unmanned aerial vehicle (UAV), maritime, public-safety, and integrated terrestrial–non-terrestrial networks.

Learning Objectives

After completing this chapter, the reader should be able to:

1. Relate application requirements to wireless-network selection criteria.

2. Compare the operating principles and design trade-offs of specialized wireless networks.

3. Estimate link-budget, capacity, latency, and energy implications using appropriate models.

4. Design architectures for IoT, industrial, vehicular, satellite, UAV, maritime, and public-safety applications.

5. Evaluate reliability, security, interoperability, regulatory, and ethical issues.

6. Explain how terrestrial and non-terrestrial networks can be integrated.

1. Application Requirements as the Basis of Network Design

A useful design begins with a requirements vector rather than a preferred technology. Important dimensions include:

• Data rate: average and peak payload rate, including protocol overhead.
• Latency: one-way or round-trip delay, and whether a strict deadline applies.
• Reliability: probability of successful delivery within a specified deadline.
• Availability: fraction of time and geographical area in which service is usable.
• Coverage: indoor, outdoor, underground, rural, oceanic, aerial, or global.
• Mobility: pedestrian, vehicular, high-speed aircraft, or moving satellite.
• Energy budget: battery lifetime, energy harvesting, or continuous power.
• Scalability: number of devices, traffic burstiness, and addressability.
• Security and safety: confidentiality, authentication, integrity, functional safety, and resilience against deliberate attack.
• Economic constraints: spectrum, infrastructure, device, subscription, and maintenance cost.

These requirements often conflict. Increasing transmit power can improve coverage but increases interference and battery consumption. A very robust coding scheme improves reliability but reduces useful throughput. Centralized scheduling can offer deterministic latency but may be less flexible than contention-based access. Consequently, technology selection is a multi-objective engineering problem.

A practical classification is:

1. Personal-area networks: short range, low power, such as Bluetooth.

2. Local-area networks: high throughput over homes, campuses, and enterprises, such as Wi-Fi.

3. Wide-area sensor networks: low data rate and long battery life, such as LoRaWAN and NB-IoT.

4. Cyber-physical networks: strict reliability, bounded latency, and operational safety, such as industrial wireless systems.

5. Highly mobile or geographically extensive networks: vehicular, satellite, UAV, and maritime systems.

6. Mission-critical networks: public-safety and emergency communications.

2. Performance Models for Specialized Networks

2.1 Link budget and received power

A first-order free-space link budget is

\[

P_r=P_t+G_t+G_r-L_{fs}-L_{misc},

\]

when all quantities are expressed in decibels or dBm. Here, \(P_t\) is transmit power, \(G_t\) and \(G_r\) are antenna gains, \(L_{fs}\) is free-space path loss, and \(L_{misc}\) represents feeder, polarization, atmospheric, penetration, and implementation losses. Free-space loss is

\[

L_{fs}=20\log_{10}\left(\frac{4\pi d}{\lambda}\right),

\]

where \(d\) is distance and \(\lambda\) is wavelength. The model assumes unobstructed propagation and is not sufficient by itself for urban, indoor, foliage, sea-surface, or satellite channels. A link is feasible only if received power exceeds receiver sensitivity by a design margin:

\[

M=P_r-S,

\]

where \(S\) is sensitivity in dBm. The margin must accommodate fading, interference, implementation uncertainty, and desired availability.

2.2 Capacity and spectral efficiency

For an additive white Gaussian noise channel, the theoretical upper bound is

\[

C=B\log_2(1+\mathrm{SNR}),

\]

where \(C\) is capacity in bit/s, \(B\) is bandwidth in hertz, and SNR is linear rather than decibel-valued. Real systems operate below this bound because of coding gaps, protocol overhead, control traffic, finite block lengths, and interference. In dense networks, the relevant quantity is often signal-to-interference-plus-noise ratio (SINR), not SNR.

2.3 Delay and reliability

End-to-end delay may be decomposed approximately as

\[

D=D_{access}+D_{queue}+D_{processing}+D_{transmission}+D_{propagation}+D_{core}.

\]

This decomposition is useful because each component requires a different remedy. Scheduling and contention affect access delay; admission control affects queuing; packet size and data rate affect transmission time; route and architecture affect propagation and core delay.

For independent transmissions with success probability \(p\), the probability of at least one success in \(N\) attempts is

\[

P_{success}=1-(1-p)^N.

\]

This expression assumes statistically independent attempts. Retransmission does not automatically satisfy a deadline: the number of attempts must fit within the permitted time, and correlated fading or interference may invalidate the independence assumption.

3. Wi-Fi and Bluetooth as Complementary Local Networks

3.1 Wi-Fi

Wi-Fi is based primarily on IEEE 802.11 technologies and is designed for local-area connectivity. Contemporary generations use wider channels, multi-user multiple-input multiple-output (MU-MIMO), orthogonal frequency-division multiple access (OFDMA), beamforming, and improved power management. Wi-Fi 6 and later generations are particularly relevant to dense enterprise and industrial deployments because OFDMA divides a channel into resource units, allowing several users with small or heterogeneous packets to be served efficiently.

Traditional Wi-Fi uses carrier-sense multiple access with collision avoidance (CSMA/CA). A station senses the channel, applies a random backoff, and transmits when permitted. This is effective for general data traffic but does not inherently guarantee deterministic latency. Dense deployments require careful channel planning, transmit-power control, roaming design, and airtime fairness. Throughput is reduced by contention, retransmissions, management frames, protocol overhead, and low-rate stations.

Wi-Fi is appropriate for cameras, augmented-reality terminals, enterprise data, mobile robots, and high-rate local devices. It is less suitable for unattended sensors requiring multi-year battery operation over kilometers, or for safety applications that require hard deterministic guarantees without additional industrial scheduling mechanisms.

Wi-Fi 7 introduces wider channels, multi-link operation, and more flexible modulation and coding. These features can improve peak throughput and latency, but performance remains dependent on spectrum availability, client capability, interference, and implementation quality.

3.2 Bluetooth and Bluetooth Low Energy

Bluetooth is optimized for short-range personal-area connectivity. Bluetooth Classic supports continuous higher-rate applications such as audio, while Bluetooth Low Energy (BLE) emphasizes short packets, low duty cycle, and low energy consumption. BLE uses advertising and connection procedures, services and characteristics, and security modes based on pairing and cryptographic keys.

BLE is valuable for wearables, beacons, medical accessories, asset tags, and commissioning of other devices. Bluetooth Mesh extends connectivity through managed relaying and is useful for lighting and building-control applications, although latency and scalability depend on relay configuration and traffic patterns. Bluetooth networks generally require careful attention to address privacy, key management, interference in the 2.4 GHz band, and device interoperability.

4. LPWAN and IoT Architecture

4.1 LPWAN design philosophy

LPWAN systems trade data rate and sometimes latency for long range, low device cost, and low energy consumption. Typical use cases include metering, environmental monitoring, agriculture, logistics, and infrastructure sensing. Traffic is usually periodic or event-driven, with small payloads.

LoRaWAN uses chirp spread spectrum at the physical layer and a star-of-stars architecture: end devices communicate with gateways, which forward traffic to network servers. Its open ecosystem supports private and public deployments. Adaptive data rate can select spreading factor and transmit power according to link conditions, but long airtime at robust settings increases collision exposure and energy use. Duty-cycle regulation and gateway capacity must be included in planning.

NB-IoT uses licensed cellular spectrum and cellular-grade authentication and management. It provides controlled interference, operator-managed coverage, and strong integration with mobile cores. LTE-M supports higher mobility and data rates than NB-IoT and is more suitable for some tracking and voice-related applications. The choice between unlicensed LoRaWAN and licensed cellular IoT depends on coverage ownership, device volume, latency, security, roaming, and operational control.

4.2 IoT protocol stack and edge computing

An IoT solution includes sensors and actuators, a radio access network, gateways or edge nodes, a data platform, applications, and management functions. Protocols such as MQTT and CoAP are common above the network layer. MQTT uses a broker and publish–subscribe model; CoAP is a lightweight request–response protocol designed for constrained devices.

Edge computing places filtering, anomaly detection, control, and data fusion near the source. It reduces backhaul traffic and can lower response time, but it introduces distributed software, synchronization, patching, and trust-management requirements. A sound architecture separates operational technology (OT) control traffic from less critical information technology (IT) traffic, while enforcing identity, least privilege, segmentation, and secure update mechanisms.

4.3 IoT energy and scalability

For a battery-powered sensor, an approximate average power model is

\[

P_{avg}=\frac{\sum_i P_i t_i}{T},

\]

where \(P_i\) and \(t_i\) are the power and duration of each operating state during observation interval \(T\). Battery lifetime is not simply battery energy divided by average power: temperature, self-discharge, peak-current limitations, regulator losses, and aging must be considered. Long sleep periods can dominate lifetime, but repeated retransmissions and poor coverage may dominate active energy.

Massive IoT deployments require efficient identity provisioning, collision management, firmware distribution, observability, and lifecycle decommissioning. A device that cannot be securely retired remains a cyber-risk even after it stops transmitting.

5. Vehicular and Intelligent Transportation Networks

Vehicular communication includes vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P) interactions. Cooperative awareness messages can convey position, speed, heading, and acceleration, while event messages may warn of hazards. Cellular vehicle-to-everything (C-V2X) and IEEE 802.11-based approaches provide alternative or complementary mechanisms; selection depends on spectrum policy, deployment maturity, congestion behavior, and required interoperability.

Vehicular channels are rapidly time-varying because of vehicle motion, reflections, blockage, and Doppler shift. Safety messages require low delay and high reliability, but not every application needs the same guarantee. Traffic efficiency can tolerate occasional loss, whereas collision avoidance requires stringent deadline reliability and robust localization.

A practical architecture combines direct sidelink communication for local awareness with network connectivity for map updates, cloud coordination, and software maintenance. Security requires pseudonymous credentials, certificate rotation, misbehavior detection, and protection against location tracking. Safety validation must address false messages, sensor disagreement, degraded positioning, and failures of roadside infrastructure.

6. Industrial Wireless Networks

Industrial applications include process control, factory automation, condition monitoring, asset tracking, and worker safety. Their requirements vary widely. A vibration sensor may tolerate seconds of latency, while a closed-loop motion-control system may require bounded millisecond-scale latency, very high availability, and precise synchronization.

Industrial Wi-Fi, WirelessHART, ISA100.11a, private cellular networks, and time-sensitive networking extensions address different portions of this space. Industrial systems emphasize deterministic scheduling, redundancy, time synchronization, coexistence planning, and graceful degradation. A wireless link should not be judged solely by mean throughput; percentile latency, deadline miss ratio, outage duration, and packet error bursts are often more meaningful.

Private 5G can provide managed spectrum, quality-of-service flows, network slicing, edge computing, and mobility. However, it does not eliminate radio uncertainty or the need for application-level safety design. Wireless control should include a safe fallback state, local autonomy, watchdog timers, and independent emergency-stop mechanisms where required.

7. Satellite and Non-Terrestrial Networks

Satellite networks extend coverage to oceans, deserts, mountains, aircraft, and disaster zones. Geostationary Earth orbit (GEO) satellites provide broad fixed coverage but have substantial propagation delay. Medium Earth orbit (MEO) and low Earth orbit (LEO) systems reduce delay and can improve link budgets through shorter range, but LEO constellations require frequent handovers, large-scale tracking, and inter-satellite or gateway coordination.

The propagation delay alone is approximately \(d/c\), where \(d\) is path length and \(c\) is the speed of light. A round trip includes uplink and downlink paths plus gateway and processing delays; therefore, interactive performance cannot be inferred from radio data rate alone. Rain attenuation is important at higher microwave and millimeter-wave frequencies, especially for GEO links and tropical regions. Adaptive coding and modulation, site diversity, fade margins, and gateway diversity can improve availability.

Satellite links are appropriate for backhaul, broadcast, remote sensing, maritime connectivity, aircraft connectivity, emergency restoration, and global IoT. Constraints include spectrum coordination, terminal cost, power, congestion, space debris, gateway dependence, and regulatory jurisdiction. Satellite systems also require secure command and control, supply-chain assurance, and protection against jamming and spoofing.

8. UAV and Aerial Wireless Networks

UAVs can act as terminals, relays, aerial base stations, or sensing platforms. Their altitude may provide line-of-sight connectivity, but the air-to-ground channel is affected by elevation angle, clutter, antenna orientation, platform motion, and interference footprint. A UAV relay may restore connectivity after a disaster, while a swarm may exchange telemetry, payload data, and coordination messages.

Design must jointly consider flight dynamics and communications. Endurance is limited by propulsion energy, payload mass, wind, and radio power. Beam steering, trajectory planning, spectrum reuse, and handover can be optimized together, but a communication optimum may be unsafe or uneconomical for flight operations. Command-and-control links should be separated logically, and often physically, from noncritical payload traffic. Loss-of-link behavior, geofencing, authentication, remote identification, and fail-safe landing procedures are essential.

UAV networks may use cellular coverage, dedicated links, Wi-Fi, mesh protocols, or satellite backhaul. The appropriate choice depends on airspace, altitude, regulatory permissions, required autonomy, and the consequences of link loss.

9. Maritime Wireless Networks

Maritime communication serves ships, offshore platforms, ports, and autonomous surface vessels. Near shore, cellular, Wi-Fi, and microwave links can offer high capacity. Beyond terrestrial coverage, satellite communication is dominant, often combined with store-and-forward operation and local shipboard networks.

The maritime channel has distinctive properties: long unobstructed paths, sea-surface reflection, ducting, weather effects, antenna motion, and sparse infrastructure. Navigation and distress communication have safety-critical status and must not be treated as ordinary broadband traffic. Network design should provide redundancy, power resilience, clear priority policies, and compatibility with maritime distress and safety systems.

Cybersecurity is especially important because vessels may operate for long periods with limited patch access. Segmentation between navigation, propulsion, cargo, crew, and passenger networks reduces the blast radius of compromise. Satellite bandwidth management should distinguish emergency traffic from routine software updates and entertainment data.

10. Public-Safety and Mission-Critical Networks

Police, fire, emergency medical, disaster-response, and critical-infrastructure teams require robust push-to-talk, group communication, location, video, telemetry, and interoperable command systems. Public-safety networks must remain useful during congestion, infrastructure damage, power failure, and intentional interference.

Key mechanisms include priority and pre-emption, group communication, device authentication, direct device-to-device operation, deployable cells, ad hoc relays, and satellite backhaul. Mission-critical broadband can supplement rather than immediately replace narrowband systems because legacy voice coverage, device ecosystems, and operational procedures remain important.

Resilience should be designed in layers: hardened sites, backup power, multiple backhaul paths, portable base stations, local operation during core-network isolation, and rehearsed procedures. Emergency access must be authenticated without creating an unusable burden for responders. Location data and body-camera streams also raise privacy and evidentiary governance questions.

11. Integrated Terrestrial–Non-Terrestrial Networks

An integrated terrestrial–non-terrestrial network (TN–NTN) combines cellular, Wi-Fi, satellite, UAV, and other access technologies under a coordinated service architecture. Integration may occur at the device, access-network, transport, or application layer. A multimode terminal may select an access link based on coverage, cost, latency, energy, congestion, and policy. More advanced systems can maintain simultaneous links for redundancy or traffic aggregation.

A useful selection objective can be expressed conceptually as

\[

J=w_R R+w_L L+w_E E+w_C C+w_A A,

\]

where the terms represent normalized reliability, latency, energy, cost, and availability measures, and the weights reflect application priorities. This is not a universal physical law; it is a decision model that must be calibrated and constrained. Safety-critical applications should impose hard constraints, such as a maximum latency or minimum availability, rather than relying only on a weighted average.

NTN integration introduces Doppler compensation, beam mobility, timing differences, intermittent coverage, feeder-link dependence, and authentication across administrative domains. Session continuity is difficult when an application moves between networks with different addressing, latency, and quality-of-service models. Multi-access edge computing, policy-based routing, multipath transport, and application-layer buffering can reduce disruption.

12. Security, Governance, and Responsible Deployment

Specialized networks expand the attack surface through constrained devices, gateways, cloud services, over-the-air updates, and third-party operators. Security should be lifecycle-based:

1. establish device identity during manufacturing or enrollment;

2. authenticate networks and endpoints mutually;

3. protect confidentiality and integrity in transit and at rest;

4. rotate keys and revoke compromised credentials;

5. secure firmware updates with signature verification and rollback protection;

6. monitor behavior and preserve forensic evidence;

7. securely retire devices and erase sensitive data.

Security mechanisms must respect constraints. Heavy cryptography is not inherently unsuitable for IoT, but key storage, random-number generation, update capability, and energy cost require engineering attention. Artificial intelligence can assist anomaly detection, traffic classification, predictive maintenance, and spectrum management. It should not be assumed to provide security automatically: models can be poisoned, evaded, or misled by distribution shifts. Safety and access decisions require explainability, human oversight, and tested fallback rules.

Regulatory issues include licensed and unlicensed spectrum, power limits, aviation and maritime rules, lawful interception, privacy, data localization, satellite coordination, and electromagnetic compatibility. Engineers must also consider digital exclusion, environmental impact, e-waste, orbital debris, surveillance risks, and equitable access to emergency services.

13. Design Methodology and Best Practices

A robust design process is as follows:

1. Characterize the application: define payloads, deadlines, mobility, coverage, energy, safety consequences, and growth.

2. Classify traffic: periodic, event-driven, control, video, signaling, and management traffic require different treatment.

3. Select candidate technologies: compare radio, spectrum, infrastructure, device, and operational models.

4. Build a propagation and capacity model: include interference, fading, blockage, antenna patterns, and peak load.

5. Design architecture and failover: define edge, gateway, core, satellite, and local-autonomy functions.

6. Quantify service objectives: use percentile latency, deadline reliability, outage duration, battery life, and availability.

7. Validate experimentally: conduct site surveys, mobility tests, load tests, interference tests, and security assessments.

8. Plan lifecycle operations: provisioning, monitoring, updates, spares, incident response, and retirement.

9. Document assumptions: record spectrum, propagation, traffic, device, and regulatory assumptions so the design can be audited.

Common mistakes include selecting based on peak data rate, ignoring uplink traffic, treating coverage maps as guarantees, omitting retransmission energy, mixing safety and routine traffic without priority controls, and assuming that network availability equals application availability.

Applied Case: Illustrative Smart-Port Emergency Network

Background

Consider a fictional but realistic regional port containing cranes, warehouses, autonomous vehicles, tugboats, environmental sensors, and emergency-response teams. The port has terrestrial private 5G and Wi-Fi coverage, but steel structures and moving containers create blockage. A satellite terminal is available for backhaul during terrestrial outages.

Problem

The port authority wants one communications system for crane telemetry, worker alerts, video, asset tracking, ship connectivity, and emergency coordination. A single technology would be inefficient: video requires high capacity, battery sensors require low energy, and emergency services require resilience during infrastructure failure.

Analysis

Traffic is divided into classes. Crane control and emergency alarms require bounded latency and high deadline reliability. Cameras require sustained uplink capacity. Asset tags generate small periodic packets. Ships require a combination of local port access and beyond-horizon connectivity. The environment creates multipath, blockage, and interference risks, while an outage of the terrestrial core must not eliminate local emergency communication.

Approach and solution

The proposed architecture uses private 5G for mobile robots, worker devices, and controlled industrial traffic; Wi-Fi 6/7 for high-capacity indoor and fixed camera zones; BLE for wearable accessories and proximity commissioning; and LPWAN for low-rate environmental and utility sensors. Edge servers at the port process alarms, video analytics, and local control. A separate safety network and independent emergency-stop circuits protect crane operations.

Emergency responders use priority-enabled broadband devices with direct device-to-device capability. Portable cells can be deployed after damage. A satellite link provides backhaul for command traffic and essential sensor summaries when terrestrial backhaul fails. Ship traffic is segmented from crane-control traffic. Identity-based access, signed updates, network segmentation, and continuous monitoring protect the heterogeneous environment.

Outcome

The design avoids forcing high-rate and low-rate devices onto the same access method. Local edge operation preserves essential functions during backhaul loss, while satellite connectivity supports coordination rather than attempting to carry all camera traffic. Redundant paths improve resilience, and explicit traffic classes make performance testable.

Learning points

The case demonstrates that specialized networks should be composed, not treated as mutually exclusive competitors. Requirements, failure modes, and operational procedures determine the architecture. Resilience is achieved through diversity, local autonomy, prioritization, and tested fallback behavior—not merely through nominal radio coverage.

Challenges and Contemporary Developments

Important research and engineering challenges include deterministic wireless control under interference, joint communication and sensing, semantic and task-oriented communications, energy harvesting, reconfigurable intelligent surfaces, non-terrestrial direct-to-device access, open and interoperable network architectures, and secure AI-native management. These developments may improve efficiency, but they also create new verification problems. A system should be adopted because its measured performance and lifecycle properties satisfy a defined application requirement, not because a technology label promises universal improvement.

Chapter Summary

Specialized wireless networks are selected by application requirements involving data rate, latency, reliability, coverage, mobility, energy, security, safety, and cost. Wi-Fi provides high-rate local connectivity, while Bluetooth supports short-range personal and embedded devices. LPWAN and cellular IoT prioritize long battery life and wide-area sensing. Vehicular systems require rapidly changing-channel operation and security for cooperative awareness. Industrial networks emphasize deterministic behavior, synchronization, redundancy, and safe fallback. Satellite and NTN systems extend coverage but introduce delay, Doppler, gateway dependence, and regulatory complexity. UAV and maritime networks must account for mobility, environmental channels, endurance, and safety. Public-safety systems require priority, direct operation, deployable infrastructure, and resilience.

The central design principle is architectural diversity. Integrated terrestrial–non-terrestrial systems can combine access technologies according to context, but interoperability, session continuity, security, and policy must be deliberately engineered. Link budgets, capacity models, delay decomposition, reliability calculations, and energy models provide useful first estimates, while field testing is essential. Responsible deployment also requires lifecycle security, privacy protection, regulatory compliance, environmental consideration, and human oversight of AI-enabled functions.

Key Terms

Application requirements: Quantified service needs such as latency, reliability, coverage, and energy consumption.

LPWAN: Low-power wide-area network optimized for small payloads and long battery life.

IoT: Networked system of sensing, actuation, connectivity, computation, and applications.

OFDMA: Multiple-access method assigning orthogonal subcarriers or resource units to users.

MU-MIMO: Multi-user multiple-input multiple-output transmission serving several users spatially.

CSMA/CA: Contention method in which stations sense the channel and avoid collisions probabilistically.

Link budget: Accounting of transmitted power, antenna gains, propagation loss, and other losses.

SINR: Ratio of desired signal power to interference plus noise power.

Edge computing: Processing located near data sources or users to reduce transport and response requirements.

V2X: Vehicle-to-everything communication, including V2V, V2I, V2N, and V2P.

Mission-critical communication: Communication whose failure can seriously affect safety or emergency operations.

NTN: Non-terrestrial network using satellites or aerial platforms.

GEO: Geostationary Earth orbit.

LEO: Low Earth orbit.

Network slicing: Logical partitioning of shared network resources for differentiated services.

Deadline reliability: Probability that a packet or transaction succeeds within a specified time limit.

Duty cycle: Fraction of time a transmitter is permitted or configured to occupy a channel.

Fail-safe state: Condition designed to minimize harm after a fault or loss of communication.

Multi-access edge computing: Edge processing supporting multiple access networks and nearby applications.

Spectrum coexistence: Coordinated operation of multiple radio systems sharing or using adjacent spectrum.

Review Questions

Short Answer Questions

1. Why is peak data rate insufficient as the sole criterion for selecting a specialized wireless network?

2. Distinguish Wi-Fi from Bluetooth Low Energy in terms of typical application and energy objective.

3. What is the purpose of a link margin?

4. Name two reasons why satellite propagation affects interactive applications.

5. Why should industrial wireless systems include a safe fallback state?

Long Answer Questions

1. Compare Wi-Fi, Bluetooth, LoRaWAN, NB-IoT, and private 5G across coverage, energy, mobility, throughput, and management.

2. Explain the architecture and security requirements of an IoT system using edge computing.

3. Discuss the channel, mobility, and safety challenges in vehicular wireless communication.

4. Explain how satellite, UAV, and terrestrial networks can complement one another in disaster response.

5. Develop a lifecycle security and governance plan for a large industrial IoT deployment.

Analytical / Application Questions

1. A remote environmental-monitoring system sends small packets every 15 minutes and must operate for several years on a battery. Evaluate whether Wi-Fi, BLE, LoRaWAN, or NB-IoT is most appropriate, and state the assumptions that could change your decision.

2. Design a communication architecture for an automated port that must continue essential operation after loss of terrestrial backhaul. Specify technologies, traffic priorities, edge functions, and fallback mechanisms.

3. A public-safety agency must provide broadband video, voice group communication, and location services during a major flood. Propose a terrestrial–NTN strategy and identify the principal reliability, security, regulatory, and ethical risks.

Multiple Choice Questions with Answers

Question 1

Which metric is most appropriate for evaluating a safety-critical packet that must arrive before a deadline?

A. Peak advertised data rate

B. Deadline reliability

C. Number of network names

D. Average battery capacity of unrelated devices

Correct Answer: B. Deadline reliability

Question 2

In the link-budget equation, a positive design margin indicates that:

A. Received power exceeds receiver sensitivity by the margin

B. Transmit power is lower than antenna gain

C. Propagation loss is zero

D. Interference has been eliminated

Correct Answer: A. Received power exceeds receiver sensitivity by the margin

Question 3

Which technology is generally most suited to short-range, low-energy wearable accessories?

A. GEO satellite broadband

B. Bluetooth Low Energy

C. Maritime radar

D. Long-haul microwave backhaul

Correct Answer: B. Bluetooth Low Energy

Question 4

What is a principal characteristic of LPWAN traffic?

A. Small payloads and low device energy consumption

B. Continuous multigigabit video per sensor

C. Mandatory hard real-time motion control

D. Only indoor operation

Correct Answer: A. Small payloads and low device energy consumption

Question 5

Why can edge computing benefit industrial IoT?

A. It removes the need for device authentication

B. It reduces local response time and backhaul traffic

C. It guarantees that radio links never fade

D. It eliminates all software maintenance

Correct Answer: B. It reduces local response time and backhaul traffic

Question 6

Which factor is especially important in LEO satellite networks?

A. Absence of handovers

B. Beam and satellite mobility requiring tracking and coordination

C. Zero propagation delay

D. Operation without spectrum regulation

Correct Answer: B. Beam and satellite mobility requiring tracking and coordination

Question 7

Which feature is central to resilient public-safety communication?

A. Priority and pre-emption for emergency traffic

B. Unrestricted access for every unidentified device

C. Disabling local communication during backhaul failure

D. Using only entertainment traffic during disasters

Correct Answer: A. Priority and pre-emption for emergency traffic

Question 8

What does the SINR account for that SNR does not?

A. Device battery age

B. Interference power

C. Antenna color

D. Application payload meaning

Correct Answer: B. Interference power

Question 9

In the illustrative smart-port case, why were multiple wireless technologies used?

A. To ensure every device used identical radio hardware

B. Because different traffic classes have different requirements

C. To avoid using edge computing

D. Because satellite links always have the highest capacity

Correct Answer: B. Because different traffic classes have different requirements

Question 10

Which statement best describes an integrated terrestrial–non-terrestrial network?

A. A network restricted to one terrestrial access technology

B. A coordinated architecture combining terrestrial and satellite or aerial access

C. A system that cannot perform handover

D. A network that does not require authentication

Correct Answer: B. A coordinated architecture combining terrestrial and satellite or aerial access