Converged Network: A single network infrastructure that carries multiple traffic types (voice, video, data, IoT sensors) simultaneously
Quality of Service (QoS): Mechanisms that prioritise different traffic types to meet their respective latency, jitter, and bandwidth requirements
DSCP (Differentiated Services Code Point): A 6-bit field in the IP header used to mark packets for QoS treatment at each network hop
Traffic Shaping: Rate-limiting a traffic flow to prevent it from monopolising shared bandwidth; sacrifices burst throughput for predictable behaviour
Traffic Policing: Dropping or marking packets that exceed a configured rate, enforcing bandwidth contracts at network ingress
Network Slicing: Logical partitioning of a physical network into multiple virtual networks, each with dedicated resources; key for 5G IoT
SDN (Software-Defined Networking): Separating the control plane from the data plane, enabling centralised, programmable network management across IoT and IT traffic
41.1 In 60 Seconds
Converged networks replace separate wiring for voice, video, and data with a single IP infrastructure – dramatically reducing costs and enabling IoT automation (e.g., access control triggering HVAC adjustments). Shared wireless media requires channel access mechanisms like CSMA/CA, where devices listen before transmitting and back off on collisions. Quality of Service (QoS) prioritizes critical IoT traffic (alarms, control commands) over best-effort data on these shared networks.
41.2 Learning Objectives
By the end of this section, you will be able to:
Compare Network Architectures: Contrast legacy separate networks with modern converged infrastructure
Evaluate Convergence Benefits: Explain economic, efficiency, and scalability advantages of converged networks
Analyze Channel Access Mechanisms: Describe how CSMA/CA enables shared wireless medium access through carrier sensing, random backoff, and exponential backoff
Apply QoS Concepts: Select and configure Quality of Service policies that prioritize critical IoT traffic over best-effort data
For Beginners: Converged Networks
A converged network carries multiple types of traffic – voice calls, video, and data – over the same infrastructure, like a highway that handles cars, trucks, and buses all at once. This matters for IoT because your smart home devices, security cameras, and voice assistants all share the same network.
Sensor Squad: One Network to Rule Them All!
“Back in the old days, buildings had separate wires for phones, separate cables for video cameras, separate networks for computers, and ANOTHER set of wires for building automation,” said Max the Microcontroller. “Four different systems! Imagine the mess.”
“Now it is all converged onto one IP network,” said Lila the LED. “My smart lighting, Sammy’s temperature data, the security cameras, and even the phone system all share the same network infrastructure. Way cheaper and easier to manage!”
“But sharing creates a problem,” noted Sammy the Sensor. “What if the security cameras are streaming tons of video and my little alarm packet cannot get through?” Max smiled. “That is where Quality of Service comes in. QoS rules give priority to critical traffic. Your fire alarm packet jumps to the front of the line, while the video stream waits a tiny bit.”
Bella the Battery added, “CSMA/CA helps too – before any device transmits on the shared wireless channel, it listens first. If someone else is talking, it waits a random time and tries again. It is like being polite at a dinner party – listen before you speak!”
41.3 Prerequisites
Before diving into this chapter, you should be familiar with:
Smart buildings run on converged networks. Instead of separate wiring for security cameras, access control, HVAC sensors, and voice systems, one IP network carries everything. This dramatically reduces installation costs and enables intelligent automation – your access control can talk to your HVAC to save energy when rooms are unoccupied.
41.4 Traditional Separate Networks
Before convergence, organizations needed separate infrastructure for each service:
Figure 41.1: Legacy separate network infrastructures for phone, video, data, and building systems
Problems:
High cost (multiple infrastructures)
Complex management (different standards)
Energy inefficiency
Limited scalability
41.5 Modern Converged Networks
21st century technological advances enable all services to run over a single data network infrastructure.
Figure 41.2: Modern converged IP network unifying all device types on single infrastructure
Benefits for IoT:
Economic savings: One infrastructure supports all devices
Energy efficiency: Shared power and networking equipment
Scalability: Easy to add new devices and services
Flexibility: Connect anything anywhere
Tradeoff: Converged Network vs Separate Networks
Option A: Single converged IP network for all traffic (voice, video, data, IoT) – lower cost, simpler management, single skill set required
Option B: Separate dedicated networks for different traffic types – guaranteed performance isolation, simpler QoS, no cross-traffic interference
Decision Factors: Choose converged when cost reduction is a priority, when QoS mechanisms are robust enough, or for typical enterprise/smart building deployments. Choose separate networks for safety-critical industrial systems where latency guarantees are mandatory, or when legacy systems cannot be migrated. Modern best practice: converged physical infrastructure with logical separation via VLANs and strict QoS policies – getting benefits of both approaches.
Example: A modern smart building uses one Ethernet/Wi-Fi network for:
Temperature sensors
Security cameras
Access control systems
HVAC control
Lighting systems
Occupancy sensors
Voice communications
41.6 Converged Network Economics
Putting Numbers to It
Converged Network ROI Calculation
Let’s quantify the cost savings for a 10-story office building:
Legacy separate networks (capital cost):
Phone system: PBX + PSTN lines: $80,000
Security cameras: Coax + DVR + monitors: $120,000
Data network: Ethernet switches + routers: $150,000
Building automation: BACnet controllers + proprietary wiring: $250,000
Total capital: $600,000
Annual operational costs (legacy):
Maintenance contracts: 4 systems x $15,000 = $60,000
Specialist labor: Phone tech + AV tech + BAS engineer = $180,000/year
Energy: 4 separate infrastructures = 24 kW x $0.12/kWh x 8,760 hrs = $25,229
Energy: PoE switches = 12 kW x $0.12/kWh x 8,760 hrs = $12,614 (50% energy savings)
Total annual: $132,614 (50% savings)
5-year TCO:
Legacy: $600,000 + (5 x $265,229) = $1,926,145
Converged: $200,000 + (5 x $132,614) = $863,070
Savings: $1,063,075 (55% reduction)
For IoT expansion: adding 500 sensors to converged network = $15/sensor (PoE + IP config) = $7,500. Same on legacy = new BACnet controllers + wiring = $80,000+ (10x more expensive).
Try It: Converged Network ROI Calculator
Show code
viewof numFloors = Inputs.range([1,50], {value:10,step:1,label:"Number of floors"})viewof legacySystems = Inputs.range([2,6], {value:4,step:1,label:"Number of legacy systems"})viewof maintenanceCostPerSystem = Inputs.range([5000,30000], {value:15000,step:1000,label:"Annual maintenance per system ($)"})viewof energyRateKwh = Inputs.range([0.05,0.30], {value:0.12,step:0.01,label:"Energy rate ($/kWh)"})viewof legacyPowerKw = Inputs.range([10,60], {value:24,step:2,label:"Legacy total power draw (kW)"})viewof yearsToProject = Inputs.range([1,10], {value:5,step:1,label:"Projection period (years)"})
Scenario: Your company manages a 10-story office building that currently has four separate networks: traditional phone system (PSTN lines with PBX), security camera system (coax cables with DVR), computer network (Ethernet), and building automation (proprietary BACnet wiring). The CFO asks you to evaluate upgrading to a converged IP network supporting 200 VoIP phones, 500 computers, 100 IP cameras, and 1,000 IoT sensors on one infrastructure.
Current costs: Four separate infrastructures cost approximately $200,000-800,000 to install and maintain.
Think about:
What are the economic trade-offs between maintaining four specialized networks versus one unified IP network?
How does converging voice, video, data, and building automation onto a single network affect operational complexity?
Key Insight: Converged networks use one IP-based infrastructure for all services instead of separate dedicated networks. A single unified network costs $50,000-200,000 to deploy – representing 60-75% cost savings compared to four independent systems. Energy efficiency improves dramatically: one set of switches, routers, and cabling replaces four independent systems. Management simplifies: a single IT team maintains one infrastructure instead of requiring specialists for phone systems, video systems, and building automation. Modern smart buildings leverage Power over Ethernet (PoE) to provide both power and data on the same cable, further reducing installation costs.
Verify Your Understanding:
If you needed to add 500 new IoT environmental sensors to this building, how would deployment differ between the converged network versus the legacy approach? Consider cabling requirements, power delivery, configuration time, and ongoing maintenance.
41.7 Channel Access: CSMA/CA
When multiple wireless devices share the same radio channel, they need a mechanism to avoid collisions. Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) is the foundation of Wi-Fi and many IoT protocols.
41.7.1 How CSMA/CA Works
Carrier Sensing: Before transmitting, each node listens to the channel
Backoff Timer: If channel is busy, node picks a random backoff time from contention window [0, CW]
Countdown: When channel is idle, backoff counter decrements each slot
Transmission: When backoff reaches 0, node transmits
Collision: If multiple nodes reach 0 simultaneously, collision occurs
Exponential Backoff: After collision, CW doubles (up to CW_max), providing fairness
41.7.2 Protocol Efficiency Comparison
Protocol
Max Efficiency
Description
Pure ALOHA
~18.4%
Transmit anytime, high collisions
Slotted ALOHA
~36.8%
Time slots reduce collisions
CSMA (1-persistent)
~53%
Listen before transmit
CSMA/CA
50-70%+
Carrier sensing + backoff
Interactive: CSMA/CA Channel Access Demo
This simulation demonstrates how Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) works in wireless networks like Wi-Fi and IoT protocols. Watch how multiple nodes coordinate access to a shared channel using carrier sensing, random backoff, and exponential backoff after collisions.
41.12 Worked Example: Smart Building Converged Network Power Budget
Scenario: A 5-story office building is migrating from four separate networks (phone, CCTV, data, building automation) to a single converged IP network. The network architect must calculate PoE power budgets and VLAN design for 1,800 converged devices.
41.12.1 Step 1: Device Inventory and Power Requirements
Floor plan (per floor, 5 floors):
VoIP phones: 40 devices x 6.5W (PoE, 802.3af Class 2)
IP cameras: 20 devices x 15W (PoE+, 802.3at Class 4)
Wi-Fi 6 APs: 8 devices x 25W (PoE++, 802.3bt Type 3)
Occupancy sensors: 30 devices x 3W (PoE, 802.3af Class 1)
Smart LED controllers: 50 devices x 7W (PoE, 802.3af Class 2)
Access control panels: 6 devices x 13W (PoE+, 802.3at Class 3)
Environmental sensors: 50 devices x 2W (PoE, 802.3af Class 1)
Digital signage: 4 devices x 25W (PoE++, 802.3bt Type 3)
Intercom panels: 2 devices x 13W (PoE+, 802.3at Class 3)
Per-floor power demand:
Phones: 40 x 6.5 = 260W
Cameras: 20 x 15 = 300W
APs: 8 x 25 = 200W
Occupancy: 30 x 3 = 90W
Lighting: 50 x 7 = 350W
Access: 6 x 13 = 78W
Environmental: 50 x 2 = 100W
Signage: 4 x 25 = 100W
Intercom: 2 x 13 = 26W
Total per floor: 1,504W
Building total: 5 x 1,504 = 7,520W PoE power budget
41.12.2 Step 2: Switch Selection and PoE Budget
Option A: Centralized (2 core switches)
2 x Cisco C9300-48UXM (48 mGig ports, 1,440W PoE budget each)
Total PoE: 2,880W -- INSUFFICIENT for 7,520W demand
Need 6 switches minimum = $84,000
Option B: Distributed (per-floor switching)
5 x 48-port PoE+ switches (740W budget each) = 3,700W
+ 5 x 24-port PoE++ switches (740W budget each) = 3,700W
Total PoE: 7,400W -- still tight
Option C: Distributed with PoE++ (recommended)
5 x Cisco C9300-48UXM (1,440W each) per floor for bulk devices
+ 5 x 24-port PoE++ (480W each) per floor for high-power devices
Total PoE: 5 x (1,440 + 480) = 9,600W (28% headroom)
Cost: 10 switches x $6,500 = $65,000
41.12.3 Step 3: VLAN Segmentation on Converged Network
Key Insight: The converged network saves 60% over 5 years primarily by eliminating dedicated phone and building automation infrastructure. PoE is the enabler – delivering both data and power on a single cable eliminates separate power wiring for cameras, phones, and sensors. However, PoE power budget planning is critical: the 7,520W building demand requires careful switch selection, as a single 48-port switch provides only 740-1,440W depending on model.
41.13 Real-World Case Study: Hospital Network Convergence Failure and Recovery
A 400-bed hospital migrated from four separate networks (clinical devices, patient monitoring, administrative, and HVAC/BMS) to a single converged IP network to reduce costs. The project initially failed, then succeeded after critical design changes.
Phase 1: Failed Convergence (Month 1-4)
The hospital deployed a flat converged network with 2,000 devices on a single VLAN. Results:
Problem
Impact
Root Cause
Patient monitor alarms delayed 2-3 seconds
3 near-miss clinical events
Broadcast storms from 2,000 devices saturated 200 Mbps uplinks
Nurse call stations dropped calls
47 missed calls in first week
VoIP packets queued behind 50 Mbps radiology image transfers
HVAC sensors lost connectivity
Operating room temperature drifted 4 degrees F
ARP broadcast traffic from 2,000 devices consumed 15% of sensor bandwidth
IT help desk overwhelmed
200+ tickets in first month
No visibility into which traffic type caused which problem
The hospital reverted to separate networks at a cost of $180,000 in labor and lost productivity.
Phase 2: Redesigned Convergence (Month 8-14)
A network architect redesigned the converged network with proper segmentation:
VLAN Design (logical separation on shared physical infrastructure):
VLAN 10: Life-Safety (patient monitors, infusion pumps)
- Strict priority QoS (DSCP EF), 100 Mbps guaranteed
- 802.1X authentication, isolated from all other VLANs
- Redundant uplinks with <50ms failover
VLAN 20: Clinical Systems (EMR workstations, imaging)
- High priority QoS (DSCP AF41), 500 Mbps guaranteed
- 802.1X + MAB authentication
VLAN 30: Voice/Nurse Call (VoIP phones, intercoms)
- Voice priority QoS (DSCP EF), 50 Mbps guaranteed
- LLDP-MED auto-VLAN assignment
VLAN 40: Building Systems (HVAC, lighting, access control)
- Medium priority QoS (DSCP AF21), 100 Mbps guaranteed
- IoT-specific NAC policies
VLAN 50: Administrative (office PCs, printers, guest Wi-Fi)
- Best effort QoS (DSCP BE), remaining bandwidth
- Standard 802.1X authentication
Broadcast domain reduction:
Before: 2,000 devices in 1 broadcast domain
After: 5 VLANs averaging 400 devices each
Broadcast traffic per device: reduced 80%
Phase 2 Results:
Metric
Separate Networks
Failed Convergence
Redesigned Convergence
Patient monitor latency
5 ms
200-3,000 ms
8 ms
VoIP call quality (MOS)
4.2
2.1 (unacceptable)
4.0
Broadcast traffic per VLAN
N/A
15% of bandwidth
2% of bandwidth
Annual infrastructure cost
$420,000
N/A (reverted)
$185,000
Number of network staff
6 (specialists)
N/A
3 (generalists)
Key Lesson: Network convergence delivers its 55% cost savings only when combined with proper VLAN segmentation, QoS enforcement, and traffic engineering. A flat converged network is worse than separate networks because it eliminates the natural isolation that separate physical infrastructure provides. The redesigned network saved $235,000 annually while maintaining clinical safety standards.
Common Pitfalls
1. Assuming All IoT Traffic Is Low Priority
Aggregating all IoT sensor data into a best-effort class alongside bulk file transfers means time-critical alarm messages may be delayed behind a large firmware download. Fix: classify IoT traffic by criticality and assign QoS markings accordingly (e.g., alarms → EF, telemetry → AF, batch uploads → BE).
2. Overlooking the Effect of Converged Traffic on IoT Latency
Adding video surveillance traffic to a network that previously carried only sensor data can saturate shared links and increase sensor data latency by 10–100×. Fix: perform a traffic engineering analysis before converging network types, and verify that IoT SLAs can still be met under worst-case combined load.
3. Not Configuring QoS End-to-End
QoS configured at the edge switch is meaningless if the core network re-marks or ignores DSCP values. Fix: verify QoS policies at every hop from IoT sensor to cloud endpoint.
🏷️ Label the Diagram
Code Challenge
41.14 Summary
Legacy networks required separate infrastructure for phone, video, data, and building automation – expensive and complex
Converged networks carry all services on one IP infrastructure, reducing costs 55-75% and simplifying management
CSMA/CA enables shared wireless medium access through carrier sensing, random backoff, and exponential backoff after collisions
Protocol efficiency improves from 18% (Pure ALOHA) to 70%+ (CSMA/CA) through collision avoidance mechanisms
