Chapter 2: Design & Development

1. From Planning to Design: The Multi-Carrier Engineering Handoff

Chapter 1 established which carriers are participating, confirmed their consent status under 47 CFR § 20.21, and established the RF exposure and feasibility baseline. Design & Development takes those per-carrier inputs and produces an actual engineered system — one that has to satisfy every participating carrier's own technical review simultaneously, not just meet a single unified specification.

Designing for Multiple, Independent Reviewers

This is where the multi-carrier reality from Chapter 1 becomes a genuine design constraint rather than just a coordination headache. Each carrier's RF engineering team will independently evaluate the design against their own internal targets for signal strength and quality on their own spectrum — meaning a single design has to simultaneously satisfy several sets of criteria, not one.

2. The iBwave Workflow for Cellular — RSRP & SINR

The public safety series used -95 dBm and DAQ (voice intelligibility) as its core acceptance metrics. Cellular design uses a different, LTE/5G-specific pair: RSRP and SINR — reflecting that cellular service isn't just voice, but also data throughput, which raw signal strength alone can't predict.

RSRP — Reference Signal Received Power

RSRP measures raw signal strength in dBm, the coverage half of the picture. Each carrier sets its own design target; the ranges below are common rules of thumb:

SINR — Signal-to-Interference-plus-Noise Ratio

SINR, expressed in dB, is the quality half of the picture — how usable the signal actually is once interference and noise are accounted for. Higher SINR unlocks higher-order modulation and dramatically higher throughput:

iBwave's cellular design workflow mirrors the process from the public safety series (floor plan import, material tagging, antenna placement, propagation prediction, iteration) but predicts and reports RSRP and SINR at every point instead of dBm and DAQ — and does so per carrier, per band, since each carrier's spectrum and power levels differ.

3. Link Budget & Active vs. Passive DAS Design Decisions

The link budget mechanics from the public safety series carry over directly — EIRP, path loss, and link margin are the same physics regardless of which spectrum is involved. What changes for cellular design is a fundamental architecture decision the link budget results feed directly into: does this building need an active DAS, or will a passive DAS suffice?

The link budget calculation is what actually answers this question objectively: if the passive distribution losses (cable, splitters, taps) between the donor signal and the farthest antenna leave inadequate RSRP margin, an active architecture is required — not a preference, but a result the math produces.

4. ANSI/TIA-568, TIA-569 & TIA-607 — Pathways, Grounding, and Topology

Once the active/passive decision is made, the physical cabling connecting the headend (where donor signal enters the building and, for active/fiber-based systems, where remote radio units are fed from) to every antenna location has to be designed to recognized telecommunications standards — not improvised.

ANSI/TIA-568 — Cabling Standard

TIA-568 governs structured cabling itself — copper (twisted pair) and fiber optic cable types, connector standards, and performance categories. For a cellular DAS, this standard governs the data/control links between headend equipment and any fiber-fed remote radio units, as well as general structured cabling supporting the system's management and monitoring infrastructure.

ANSI/TIA-569 — Pathways and Spaces

TIA-569 governs something different: not the cable itself, but the physical spaces and pathways that carry it — telecommunications rooms (TRs), the main telecommunications room (MTR), cable tray and conduit pathway requirements, and environmental provisions (temperature, humidity, power) for those spaces. TIA-569 is also directly referenced by BICSI 006 (Section 5) as a companion standard specifically for DAS headend space requirements.

ANSI/TIA-607 — Bonding and Grounding

Grounding and bonding have their own companion standard. TIA-607 covers the telecommunications bonding backbone, the bus bars in each telecommunications room, and the bonding of racks, cable tray, and equipment, so that every space in the system shares a common, low-impedance reference to the building's electrical ground. A DAS headend full of active equipment, with coax and fiber running to every floor, needs this designed in from the start.

5. BICSI 006 & TIA-569 — Headend Room Design

ANSI/BICSI 006 — DAS-Specific Requirements

BICSI 006, Distributed Antenna System (DAS) Design and Implementation Best Practices, is purpose-built for DAS work specifically — unlike TIA-568/569, which are general telecommunications standards a DAS project happens to use. BICSI 006 distinguishes mandatory ("shall") requirements from advisory ("should") recommendations, covering personnel safety, RF system design methods, telecommunications infrastructure design, installation/commissioning methods, and electromagnetic compatibility — the same mandatory/advisory distinction that runs through the public safety series' code language.

TIA-569's Environmental Requirements for the Headend Room

• Room sizing: Minimum dimensions scaled to the area served — a starting baseline around 150 square feet (14 m²) for smaller buildings, scaling upward for larger served areas
• Floor loading: Structural capacity sufficient for headend equipment racks, batteries (for active systems), and cable tray/pathway infrastructure
• Thermal/HVAC: Dedicated climate control appropriate to the heat load of active equipment — a headend room running active amplification and RRU baseband equipment generates real heat that passive distribution never did
• Power provisioning: Dedicated electrical circuits sized to actual equipment load, not shared with unrelated building systems
• Access control: Restricted to authorized telecommunications personnel, consistent with the room housing life-safety-adjacent, carrier-sensitive equipment

6. RRU Architecture & C-RAN Design Considerations

For active systems built around fiber-fed Remote Radio Units (RRUs) rather than a traditional single-location BDA, the design phase has to plan an entirely different physical architecture — one that has no real equivalent in the public safety series, where a single BDA at one headend location is the standard pattern.

Centralized Baseband, Distributed Radio

In a C-RAN-style (Centralized Radio Access Network) active DAS, the baseband processing equipment stays centralized at the headend, while the actual RF-transmitting radio units — the RRUs — are physically distributed throughout the building, closer to the antennas they serve. Fiber backbone cabling (governed by TIA-568/569, Section 4) carries digitized signal from the centralized baseband to each distributed RRU location, which then converts it back to RF for local antenna distribution.

Why This Architecture Exists

• Reduced RF-over-coax distance: RF signal degrades over coax distance; digitized signal over fiber does not degrade the same way. Placing RRUs close to their antenna zones minimizes the RF-over-coax run to a short final distribution leg, rather than running a long coax run from a single central point.
• Scalability: Additional RRU locations can be added to extend coverage without re-engineering the entire headend.
• Multi-carrier flexibility: Some RRU platforms support multiple carriers/bands from a shared physical unit, simplifying the "satisfy every carrier simultaneously" challenge from Section 1.

With the design package complete — link budget, active/passive determination, per-carrier RSRP/SINR predictions, TIA-568/569 pathway plan, and (where applicable) RRU architecture — the project is ready for Chapter 3: Implementation & Commissioning, where this design becomes installed, carrier-certified hardware.

Final Assessment — Chapter 2: Design & Development

Answer all 10 questions. A score of 80% or higher (8 of 10) is required to pass and receive your certificate.