4G, 5G and Emerging 6G Architecture

Introduction and Context

Mobile communication has evolved from voice-oriented cellular systems into programmable, software-intensive platforms supporting broadband access, industrial automation, connected vehicles, immersive media, and machine intelligence. Fourth-generation (4G) systems established all-IP mobile broadband through LTE. Fifth-generation (5G) systems extend this foundation with flexible radio access, service-based core networks, virtualization, edge computing, and differentiated service classes. Emerging sixth-generation (6G) research seeks to integrate communication, sensing, artificial intelligence, computing, and new spectrum resources into a deeply intelligent network fabric.

The architectural transition is as important as the increase in data rate. LTE primarily optimized a relatively homogeneous mobile broadband service. 5G instead supports three broad service families: enhanced Mobile Broadband (eMBB), Ultra-Reliable and Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These services have conflicting requirements. High throughput needs substantial bandwidth and favorable radio conditions; URLLC needs predictable delay and reliability; mMTC requires efficient support for very large populations of low-rate devices. No single static network configuration can optimize all three. Network slicing, cloud-native cores, virtualized RAN, edge computing, and Open RAN therefore become architectural mechanisms for customization and scalability.

This chapter evaluates the air interfaces and architectures of LTE and 5G New Radio (NR), explains their enabling technologies, and critically examines private networks, virtualization, Open RAN, and prospective 6G capabilities.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Compare LTE and 5G NR air-interface design and deployment characteristics.

2. Explain the architecture and governance of network slicing.

3. Evaluate cloud RAN, virtualized RAN, Open RAN, and edge-computing alternatives.

4. Relate eMBB, URLLC, and mMTC requirements to engineering design choices.

5. Assess private 5G networks and their industrial applications.

6. Identify technical, economic, regulatory, ethical, and security limitations.

7. Critically evaluate likely directions for 6G research and deployment.

1. From LTE to 5G: Architectural Evolution

1.1 LTE architecture

LTE uses an Evolved Packet System consisting of the Evolved-UTRAN radio access network and the Evolved Packet Core (EPC). The principal radio node is the eNodeB. It performs scheduling, radio-resource management, mobility functions, and connection to the EPC. The EPC includes the Mobility Management Entity, Serving Gateway, Packet Data Network Gateway, and Home Subscriber Server. Control-plane and user-plane functions are logically distinct, although LTE was not originally designed as a fully cloud-native system.

LTE uses OFDMA in the downlink and SC-FDMA in the uplink. The latter was selected partly to reduce terminal peak-to-average power ratio and therefore improve handset power efficiency. LTE supports scalable channel bandwidths, frequency-division duplex and time-division duplex operation, MIMO, adaptive modulation and coding, and carrier aggregation. LTE-Advanced increased peak performance through enhanced MIMO, coordinated multipoint, relay improvements, and carrier aggregation.

1.2 5G system architecture

The 5G system separates the Next Generation Radio Access Network (NG-RAN) from the 5G Core (5GC). A gNodeB may be divided into a Central Unit (CU) and one or more Distributed Units (DUs). The CU can itself be separated into control-plane and user-plane functions. This decomposition supports flexible placement: latency-sensitive functions may be near the radio site, while less time-critical functions can be centralized or placed in a regional cloud.

The 5GC adopts a service-based architecture. Functions such as the Access and Mobility Management Function, Session Management Function, User Plane Function, Policy Control Function, Authentication Server Function, and Network Repository Function communicate through service-based interfaces. This approach improves modularity and enables software lifecycle practices such as automated deployment, scaling, observability, and continuous updating. It also introduces dependencies on cloud orchestration, APIs, secure service discovery, and inter-function authorization.

A major architectural distinction is the possibility of independent control-plane and user-plane placement. For example, a User Plane Function can be deployed at an enterprise edge to keep industrial traffic local, while authentication and policy services remain in a central operator cloud.

2. Comparing the LTE and 5G NR Air Interfaces

2.1 Common principles

Both LTE and NR use OFDM-based transmission, adaptive modulation and coding, hybrid automatic repeat request, channel-state feedback, scheduling, and MIMO. In both systems, link adaptation attempts to select a transport format appropriate to instantaneous channel conditions. A simplified link-budget relationship is

P_r = P_t G_t G_r / L,

where P_r is received power, P_t is transmitted power, G_t and G_r are antenna gains, and L is total dimensionless propagation and implementation loss. In decibel form, multiplication becomes addition and loss terms are subtracted. This equation is applicable to a specified link budget and does not by itself predict throughput, because interference, coding, scheduling, and protocol overhead also matter.

2.2 Numerology and scalable subcarrier spacing

LTE generally uses 15 kHz subcarrier spacing for its principal OFDM numerology. 5G NR supports scalable subcarrier spacing commonly represented by

Δf = 15 × 2^μ kHz,

where μ is a non-negative numerology index for the standard NR numerologies. Increasing Δf shortens the OFDM symbol duration and slot duration, improving suitability for low-latency operation and higher-frequency phase-noise environments. However, larger spacing reduces the number of subcarriers in a fixed bandwidth and can increase sensitivity to coverage and oscillator limitations. The equation describes nominal numerology values; actual deployment must also account for cyclic prefix, frame structure, bandwidth, and regulatory constraints.

NR supports mini-slots and flexible slot formats. A transmission need not always wait for a conventional full slot, which helps URLLC. LTE has more rigid timing structures, although later enhancements introduced additional flexibility.

2.3 Spectrum and deployment

LTE was widely deployed in sub-1 GHz, mid-band, and some higher bands. 5G NR extends operation into sub-6 GHz bands and millimeter-wave bands. Low bands provide broad coverage and penetration; mid-band spectrum provides a practical balance between capacity and coverage; high bands provide large contiguous bandwidth but suffer greater propagation loss, blockage, and atmospheric attenuation.

5G may operate in Non-Standalone (NSA) mode, where NR is anchored to an LTE EPC, or Standalone (SA) mode, where NR connects to the 5GC. NSA accelerates initial deployment but cannot expose the full set of 5G core and slicing capabilities. SA is more appropriate for advanced industrial services, native 5G policy control, and independent lifecycle management.

2.4 MIMO and beam management

LTE introduced increasingly capable spatial multiplexing and closed-loop MIMO. NR expands antenna arrays and emphasizes beam-based operation, especially at high frequencies. Beam sweeping, measurement, reporting, and recovery are necessary because narrow beams are more vulnerable to user movement and blockage. Massive MIMO can increase spectral efficiency and coverage through spatial multiplexing and beamforming, but it raises hardware, calibration, energy-consumption, and computational requirements.

A useful idealized upper bound for a bandwidth-limited link is Shannon capacity:

C = B log₂(1 + S/N),

where C is capacity in bit/s, B is bandwidth in hertz, and S/N is received signal-to-noise ratio as a linear ratio. The expression assumes an ideal channel and Gaussian signaling; practical throughput is lower because of coding gaps, interference, protocol overhead, finite blocklength, and channel variation. It shows why both bandwidth and signal quality matter, but it should not be mistaken for a guaranteed user data rate.

2.5 Air-interface assessment

LTE is mature, widely interoperable, and cost-effective for broad mobile broadband. Its limitations include less flexible timing, less native support for differentiated logical networks, and architectural dependence on EPC-era assumptions. NR provides greater flexibility in numerology, duplexing, bandwidth, beam operation, scheduling, and network integration. Nevertheless, NR is not automatically superior in every deployment: a low-band LTE network may provide better coverage and energy efficiency than a high-band NR deployment, and the business case may not justify extensive densification.

3. Service Classes and Performance Trade-offs

Enhanced Mobile Broadband

eMBB supports high-throughput services such as video, fixed wireless access, cloud gaming, and augmented or virtual reality. Design priorities include bandwidth, spectral efficiency, multi-antenna gain, backhaul capacity, and sustained mobility performance. Peak rate is a poor sole metric; experienced throughput, coverage probability, congestion behavior, and energy consumption are often more relevant.

Ultra-Reliable and Low-Latency Communications

URLLC targets applications such as motion control, protection systems, collaborative robotics, and mission-critical communications. Reliability must be defined over a packet size, latency bound, operating time, and channel condition. A statement such as “99.999% reliability” is incomplete unless the event and time interval are specified.

Latency includes device processing, scheduling, radio transmission, retransmission, transport, queuing, and application processing. Reducing radio transmission time alone may not produce an end-to-end low-latency service. Techniques include mini-slots, configured grants, packet duplication, pre-emption, local user-plane breakout, deterministic transport, and redundant paths. These techniques consume resources and may reduce capacity for other users.

Massive Machine-Type Communications

mMTC supports large numbers of sensors and actuators that often transmit small, infrequent messages. Important design concerns are efficient random access, battery life, coverage enhancement, device cost, scalable identity management, and overload control. mMTC traffic is not simply “many smartphones”; its traffic distribution, synchronization behavior, security needs, and economic model are different.

4. Network Slicing

A network slice is a logically isolated, end-to-end set of network resources and functions configured to meet a service policy. A slice may include radio resources, transport paths, core functions, edge applications, security controls, and monitoring. It is not necessarily a physically separate network.

A practical slice lifecycle includes:

1. Design: define service-level objectives, topology, security, and resource policy.

2. Onboarding: validate descriptors, images, licenses, and compatibility.

3. Instantiation: deploy virtual or physical functions and connect them.

4. Operation: monitor performance, faults, security, and capacity.

5. Scaling and healing: adjust resources or replace failed components.

6. Termination: remove resources and securely erase residual data.

The management and orchestration layer translates business or application requirements into technical policies. Isolation may be achieved through dedicated spectrum, scheduler policies, virtual networks, admission control, compute reservations, and separate user-plane paths. Isolation is not absolute merely because functions are virtualized. Shared CPUs, caches, accelerators, transport links, and orchestration platforms can create interference or common failure modes.

A slice should therefore be evaluated against measurable indicators: latency distribution rather than only mean latency, packet-loss probability, availability, throughput, jitter, geographic coverage, recovery time, and security-event response. Slice conflicts can arise when a high-priority URLLC service pre-empts resources from eMBB, or when an overloaded shared transport network defeats otherwise adequate radio performance.

5. Cloud, Virtualized, and Open RAN

5.1 Cloud RAN and virtualized RAN

In traditional distributed RAN, baseband processing is closely associated with the radio site. Cloud RAN centralizes some processing in a data center, potentially improving coordination and resource pooling. Virtualized RAN (vRAN) implements network functions using software on commercial off-the-shelf servers, often with hardware acceleration for demanding signal processing.

Centralization can reduce equipment duplication and simplify upgrades, but it imposes stringent fronthaul requirements. The required bandwidth and timing precision depend on the functional split. A split that transports lower-level samples can demand high, relatively constant fronthaul capacity, whereas a higher-layer split can reduce transport requirements but place more processing at the distributed site. Consequently, there is no universally optimal split.

5.2 Open RAN

Open RAN is an ecosystem and architectural approach emphasizing open, interoperable interfaces among radio units, distributed units, central units, near-real-time control components, and non-real-time management components. RAN Intelligent Controllers can host applications that optimize policy, mobility, energy, or interference behavior. The objective is to reduce dependence on vertically integrated supply chains and encourage innovation.

Open interfaces do not guarantee plug-and-play interoperability. Interoperability must be tested across timing, performance, management, security, certification, and lifecycle behavior. Multi-vendor integration can increase operational complexity, troubleshooting effort, and responsibility for end-to-end performance. Intelligent control applications must also be constrained so that optimization does not destabilize radio operation.

5.3 Evaluation criteria

A RAN architecture should be assessed using total cost of ownership, energy per delivered bit, coverage, synchronization performance, software maturity, supply-chain resilience, security exposure, automation capability, and operational skill requirements. Centralization is attractive where fiber, power, and cloud infrastructure are available. Distributed processing is often preferable where transport is constrained or service continuity is critical.

6. Edge Computing and Private 5G

Edge computing places computation and storage close to users, devices, or radio access points. It reduces transport distance, supports data locality, and enables rapid interaction between local sensors and applications. Typical uses include machine vision, augmented reality, industrial control, video analytics, and connected-vehicle coordination.

Edge computing does not guarantee low latency. Application execution, queueing, container startup, database access, security inspection, and synchronization can dominate the latency budget. Engineers should construct an end-to-end budget and measure tail latency, not only averages.

A private 5G network is a non-public mobile network deployed for an enterprise, campus, utility, port, mine, or public agency. It may use locally licensed, shared, or operator-provided spectrum. Benefits include controlled coverage, predictable policy, local breakout, device identity management, mobility, and integration with operational technology. Challenges include spectrum authorization, indoor propagation, industrial safety, device ecosystem maturity, operational staffing, and integration with existing Wi-Fi, Ethernet, fieldbus, and safety systems.

Private 5G is justified when mobility, deterministic policy, wide-area sensor coverage, or cellular security provides value beyond industrial Ethernet or Wi-Fi. A technology decision should compare the complete lifecycle cost and required performance rather than assuming that 5G is inherently superior.

7. Security, Governance, and Responsible Deployment

5G increases the software and interface attack surface. Threats include compromised virtual-machine images, insecure APIs, rogue or cloned devices, signaling abuse, supply-chain compromise, denial of service, misconfigured slices, cloud-admin privilege escalation, and attacks on edge infrastructure. Security should be designed across device, radio, transport, core, cloud, orchestration, application, and supply-chain layers.

Important practices include hardware-rooted identity, mutual authentication, least-privilege access, signed software images, vulnerability management, segmentation, secure boot, continuous monitoring, tested backups, and incident-response exercises. Slice isolation must be validated under overload and attack conditions.

Governance issues include lawful interception, data retention, cross-border data transfer, competition, spectrum licensing, critical-infrastructure resilience, and accessibility. Network telemetry may reveal location, behavior, industrial processes, or health-related patterns. Data minimization, purpose limitation, strong access controls, and transparent retention policies are therefore essential.

Artificial intelligence is increasingly used for traffic prediction, anomaly detection, energy optimization, beam management, and autonomous operations. AI models can fail under distribution shift, produce opaque decisions, or amplify biased data. Safety-critical control should retain bounded behavior, fallback mechanisms, human oversight, and auditable logs.

8. Illustrative Case: Private 5G for a Smart Manufacturing Campus

Background

Consider an illustrative automotive manufacturing campus with autonomous guided vehicles, machine-vision inspection, robotic cells, and maintenance sensors. The campus currently uses Wi-Fi for mobile devices and wired Ethernet for fixed machines.

Problem

The operator wants mobility for vehicles and cameras, local processing of high-resolution video, reliable control communications, and separation between production traffic and visitor Internet access. The existing network suffers from congestion in areas where metal structures and moving machinery change propagation conditions.

Analysis

The application inventory identifies three traffic groups. Inspection video is an eMBB-like workload requiring high uplink capacity. Robot coordination is a URLLC-like workload requiring bounded latency and high availability. Battery sensors are mMTC-like workloads requiring low energy consumption and scalable access. A single best-effort WLAN policy cannot satisfy all objectives.

The latency budget is decomposed into device processing, radio scheduling, transport, edge inference, and control response. Measurements show that placing vision inference in a regional cloud creates unacceptable tail latency, whereas an on-campus edge cluster is adequate. The design also identifies a common failure risk: if the edge cluster, local transport switch, and power system share one room, radio redundancy alone will not provide end-to-end availability.

Approach and solution

The proposed architecture uses a standalone 5G core with a local User Plane Function, a campus 5G NR radio network, an edge cluster for machine vision, and integration with the wired industrial network. Logical policies separate production control, video, sensors, and guest traffic. Critical robot traffic receives admission control and protected resources; video is rate-controlled; sensors use energy-efficient access procedures. Wired Ethernet remains the preferred connection for stationary safety-critical machines where it is economically and technically superior.

Security includes device certificates, separate administrative domains, signed edge workloads, network telemetry, and a tested manual fallback. The design is piloted in one production zone before campus-wide deployment.

Outcome

In this illustrative scenario, the principal benefit is not a headline data rate. It is controlled mobility, local data processing, policy separation, and improved operational visibility. The pilot also reveals that radio coverage is only one part of reliability; power, edge computing, transport, application software, and human procedures must be engineered together.

Learning points

1. Service classification should precede technology selection.

2. Tail latency and failure domains matter more than nominal peak performance.

3. Private 5G should coexist with Ethernet and Wi-Fi where those technologies are better suited.

4. Slicing is useful only when policies are enforceable and monitored.

5. Pilot measurements should include failure, recovery, security, and lifecycle operations.

9. Emerging 6G Capabilities and Research Directions

6G is not yet a finalized commercial system; its capabilities remain research and standardization objectives. Likely themes include sub-THz and terahertz communication, extreme MIMO, integrated sensing and communication, AI-native control, distributed intelligence, semantic or goal-oriented communications, non-terrestrial network integration, digital twins, and stronger support for cyber-physical systems.

Integrated sensing and communication would use radio signals for both data transfer and environmental perception. This could support positioning, mapping, gesture recognition, and industrial monitoring, but it raises difficult questions about sensing resolution, calibration, interference, privacy, and liability when network-derived perceptions are wrong.

Sub-THz systems may provide very wide bandwidth, but propagation loss, blockage, molecular absorption, oscillator phase noise, hardware efficiency, and beam alignment are significant obstacles. Reconfigurable intelligent surfaces may shape propagation in selected environments, yet their practical gain depends on placement, control overhead, channel knowledge, and element efficiency.

AI-native networks may dynamically configure radio, compute, and transport resources. Research must distinguish genuine performance improvement from moving complexity into an opaque model. Reproducibility, explainability, robustness, energy cost, and safe fallback are important evaluation criteria.

6G may also integrate terrestrial, aerial, and satellite links. Such integration can improve coverage and resilience but introduces long and variable propagation delays, regulatory coordination, Doppler compensation, roaming complexity, and expanded attack surfaces. Sustainability will be a central requirement: energy consumption, embodied carbon, electronic waste, and the environmental cost of dense infrastructure must be included in architecture decisions.

10. Design and Evaluation Framework

A rigorous architecture evaluation should proceed through the following questions:

1. What service is being delivered? Define traffic, mobility, reliability event, latency bound, coverage, security, and availability.

2. Where are the constraints? Examine spectrum, propagation, transport, compute, power, devices, and operations.

3. Which functions must be centralized? Select functional splits and edge locations according to measurable latency and capacity requirements.

4. What is shared and what is isolated? Identify common failure domains, resource contention, and security boundaries.

5. How will performance be measured? Use distributions, percentiles, outage probability, energy per bit, recovery time, and lifecycle cost.

6. How will the system fail safely? Define redundancy, degraded modes, manual intervention, and recovery procedures.

7. Is the business and regulatory model viable? Consider spectrum, interoperability, procurement, skills, privacy, and total cost of ownership.

This framework prevents architecture from being selected solely on peak data rate or marketing terminology.

Challenges and Limitations

Important limitations include uncertain returns on dense 5G deployments, high energy consumption of massive MIMO and cloud infrastructure, difficult multi-vendor integration, insufficient industrial device support, complex orchestration, and dependence on high-quality transport. Network slicing can be difficult to monetize and does not eliminate physical resource contention. URLLC claims may be overstated if application and transport components are ignored. Open RAN may improve supply-chain diversity but can increase integration and operational burdens. 6G concepts face substantial hardware, propagation, standardization, sustainability, and governance challenges.

Best Practices

• Start with measurable application requirements rather than a technology label.
• Use standalone 5G when native 5G core functions are actually required.
• Engineer the complete end-to-end latency and reliability budget.
• Treat spectrum, transport, power, compute, and security as first-class design constraints.
• Validate slices under congestion, faults, and attacks.
• Use open interfaces with conformance, interoperability, and performance testing.
• Place edge workloads according to data locality and tail-latency requirements.
• Retain Ethernet, Wi-Fi, and LTE where they are more suitable.
• Measure energy per useful service delivered, not only radio efficiency.
• Apply privacy, secure lifecycle management, AI governance, and incident-response practices from the beginning.

Chapter Summary

LTE established scalable all-IP mobile broadband using OFDM-based radio access, MIMO, adaptive transmission, and the EPC. 5G NR retains these foundations while adding scalable numerology, flexible slot structures, beam-centric operation, broader spectrum options, and a service-based 5G Core. Its architecture supports eMBB, URLLC, and mMTC, but these services impose competing requirements that must be managed through scheduling, policy, slicing, edge computing, and careful end-to-end engineering.

Cloud RAN and vRAN provide pooling and software flexibility, while Open RAN seeks interoperable interfaces and a broader supplier ecosystem. Neither approach removes the need for synchronization, transport capacity, security, testing, and operational expertise. Private 5G can offer controlled mobility and local processing, but it should be compared fairly with Ethernet and Wi-Fi. Network slicing provides logical customization, yet effective isolation requires measurable policies and attention to shared failure domains.

Emerging 6G research combines communication with sensing, AI, edge intelligence, non-terrestrial networking, and new spectrum. Its success will depend not only on higher performance but also on safety, sustainability, privacy, resilience, interoperability, and economically justified deployment.

Key Terms

LTE: Fourth-generation mobile system based on the Evolved Packet System.

5G NR: Fifth-generation New Radio air interface.

EPC: LTE Evolved Packet Core.

5GC: Service-based 5G Core network.

eMBB: Enhanced Mobile Broadband service category.

URLLC: Ultra-Reliable and Low-Latency Communications.

mMTC: Massive Machine-Type Communications.

Numerology: NR configuration defining subcarrier spacing and related timing.

Massive MIMO: Use of many antenna elements for beamforming and spatial multiplexing.

NSA: 5G deployment anchored to LTE and EPC.

SA: 5G deployment using NR with the 5G Core.

Network slice: Logical end-to-end network customized for a service.

Cloud RAN: RAN architecture that centralizes selected processing in cloud infrastructure.

vRAN: RAN functions implemented as software on virtualized computing resources.

Open RAN: RAN approach emphasizing open, interoperable interfaces and intelligent control.

Edge computing: Computing placed near users, devices, or access networks.

Private 5G: Non-public mobile network operated for a defined organization or site.

Integrated sensing and communication: Joint use of radio infrastructure for data transfer and sensing.

Review Questions

Short Answer Questions

1. What are the principal differences between LTE EPC and the 5G service-based core?

2. Why does 5G NR support scalable subcarrier spacing?

3. Define eMBB, URLLC, and mMTC.

4. What is the purpose of a network slice?

5. Why does edge computing not automatically guarantee low latency?

Long Answer Questions

1. Compare LTE and 5G NR air interfaces in terms of numerology, spectrum, MIMO, timing flexibility, and deployment modes.

2. Explain the lifecycle of a network slice and discuss the limits of logical isolation.

3. Evaluate cloud RAN, vRAN, and Open RAN with respect to performance, cost, interoperability, and security.

4. Discuss the architecture and business justification of a private 5G network.

5. Examine the technical and governance challenges likely to shape 6G.

Analytical / Application Questions

1. Design an architecture for a factory requiring machine-vision uplink capacity, mobile robots, and low-power sensors. Justify the placement of radio, core, edge, and application functions.

2. A proposed URLLC service reports very low radio transmission time but experiences high application response delay. Identify the missing parts of the end-to-end latency budget and recommend measurements.

3. A network operator wants to use Open RAN to reduce vendor dependence. Develop an evaluation plan covering interoperability, synchronization, security, energy consumption, operational complexity, and total cost of ownership.

Multiple Choice Questions with Answers

Question 1

Which feature is most characteristic of the 5G Core compared with the LTE EPC?

A. Service-based network functions

B. Exclusive use of circuit switching

C. Removal of packet data gateways

D. Dependence on SC-FDMA in the core

Correct Answer: A. Service-based network functions

Question 2

In the NR numerology relationship Δf = 15 × 2^μ kHz, increasing μ generally produces what effect?

A. Longer slot duration

B. Shorter OFDM symbol and slot duration

C. Removal of cyclic prefix

D. Lower carrier frequency

Correct Answer: B. Shorter OFDM symbol and slot duration

Question 3

Which service category is primarily associated with very large populations of low-rate sensors?

A. eMBB

B. URLLC

C. mMTC

D. FDD

Correct Answer: C. mMTC

Question 4

What is a principal purpose of deploying a User Plane Function near an industrial site?

A. To increase handset battery voltage

B. To enable local traffic breakout and reduce transport delay

C. To replace all radio antennas

D. To eliminate device authentication

Correct Answer: B. To enable local traffic breakout and reduce transport delay

Question 5

Which statement about network slicing is correct?

A. It always requires a physically separate network

B. It provides logical customization but shared resources can remain common failure points

C. It removes the need for monitoring

D. It guarantees identical latency for every application

Correct Answer: B. It provides logical customization but shared resources can remain common failure points

Question 6

What is a significant practical challenge of Open RAN?

A. It cannot use software processing

B. Multi-vendor integration and performance validation can be complex

C. It prohibits intelligent controllers

D. It operates only on satellite spectrum

Correct Answer: B. Multi-vendor integration and performance validation can be complex

Question 7

For an ideal link with B = 1 MHz and S/N = 3, the Shannon capacity is closest to which value?

A. 0.5 Mbit/s

B. 1.0 Mbit/s

C. 2.0 Mbit/s

D. 4.0 Mbit/s

Correct Answer: C. 2.0 Mbit/s

Question 8

Which factor is especially important at millimeter-wave frequencies?

A. Beam blockage and propagation loss

B. Absence of antenna arrays

C. Inability to use OFDM

D. Elimination of channel variation

Correct Answer: A. Beam blockage and propagation loss

Question 9

Why may a private 5G network be selected over Wi-Fi in an industrial campus?

A. It always has lower equipment cost

B. It can provide controlled mobility, cellular identity, and policy separation

C. It requires no spectrum authorization

D. It eliminates the need for wired networks

Correct Answer: B. It can provide controlled mobility, cellular identity, and policy separation

Question 10

Which is a prospective 6G capability?

A. Integrated sensing and communication

B. Exclusive reliance on circuit-switched voice

C. Removal of edge computing

D. Abolition of spectrum regulation

Correct Answer: A. Integrated sensing and communication