DAS Capacity Planning: Size for Peak Indoor Demand

What a DAS Capacity Plan Includes

A capacity brief documents operating conditions and the expected service experience during the building's busiest credible periods. The underlying information typically includes:

• Peak and normal occupancy by area, including exceptional events the owner expects the system to support.
• Required carriers, technologies and frequency bands, with known gaps in operator participation identified.
• Busy-hour estimates of active cellular users and application demand for each carrier.
• Spaces where demand concentrates and whether peaks in neighboring zones occur at the same time.
• Required user experience and growth assumptions that the RF design and validation plan must address.

Capacity objectives can be expressed in measurable terms without prescribing the number of sectors, radios or antennas. Those are engineering decisions based on service requirements, available carrier resources and the selected architecture. The related DAS RFP Guide describes how service requirements can form a consistent procurement baseline.

Where Peak Demand Concentrates

Capacity planning maps occupancy and anticipated cellular use to the building's floor plans. An auditorium, conference room, cafeteria, registration area or shift-change entrance may concentrate hundreds of users in a relatively small space. Building-wide occupancy averages can conceal these localized peaks.

Time matters as much as location. Adjacent rooms that empty at once can create a surge in one corridor. A hospital shift change may coincide with visiting hours. A convention center can have simultaneous sessions and crowds moving toward the same lobby.

A demand model also accounts for whether these events overlap and whether outdoor transitions or adjoining areas affect the required service footprint. Estimates may draw on facilities schedules, event bookings or expected tenant populations. Future tenant demand remains a planning assumption rather than known traffic.

How Carrier Share and Active Use Affect Demand

Occupants, devices registered on a network and users actively transferring data are different quantities. A person can carry more than one cellular device, and some devices may be using Wi-Fi rather than cellular data during the period being modeled.

The demand model considers the share of users and devices expected on each required mobile operator. Tenant or employee information can inform the estimate, while visitor and contractor populations may have a different carrier mix. National market-share figures are not a reliable substitute for venue-specific information when capacity decisions depend on the result.

Concurrent activity and application requirements are modeled over a defined time interval, with downlink and uplink evaluated separately. Video uploading, live streaming, conferencing, ticketing and cloud applications do not impose the same traffic patterns. Each assumption has a different meaning depending on whether it represents sustained transfer, a short burst or an individual-session performance objective.

Venue type also plays an important role in capacity planning. A stadium or convention center may experience intense, concentrated demand during events, while a hospital, office building or warehouse has different usage patterns throughout the day. These differences influence peak traffic, the balance of uplink and downlink demand, and where network capacity is needed most. Effective DAS capacity planning accounts for how a particular building is used, rather than relying on a universal sizing formula.

For additional insight into how cellular traffic patterns vary across indoor environments, see Ericsson's 2023 study on indoor connectivity and network performance.

Worked Example: From Occupancy to Demand

A hypothetical meeting floor has 800 occupants. In this example, 40% use Carrier A, and 25% of that carrier's users are simultaneously active during the modeled interval.

Estimated active users: 800 x 40% x 25% = 80 Carrier A users.

Illustrative aggregate downlink workload: 80 x 2 Mbps = 160 Mbps.

Illustrative aggregate uplink workload: 80 x 0.5 Mbps = 40 Mbps.

These figures represent assumed application demand, not measured traffic, guaranteed user throughput or the radio capacity that a DAS can deliver. The per-user rates and concurrency percentages are hypothetical teaching inputs, not CTS-recommended design thresholds.

RF engineering evaluates whether those workloads can be supported under the expected radio conditions. Actual deliverable performance depends on available spectrum and carrier participation; radio configuration and resource loading; interference and signal quality; uplink limits; device capabilities; and the distribution and transport architecture. Backhaul requirements also depend on overhead, sharing and operating conditions.

The full capacity model evaluates each carrier and significant demand zone, including normal busy-hour conditions, event peaks and plausible growth where those scenarios materially affect the design. A single calculated Mbps total is not a complete system-sizing specification.

A single calculated Mbps total is not a complete system-sizing specification.

How Carrier Radio Resources Shape DAS Capacity

A DAS distributes radio signals supplied by a carrier-connected, managed or off-air signal source. It does not independently create carrier spectrum or additional radio capacity. Installing more antennas can improve distribution, but may not increase the total traffic the serving radio resources can carry.

A capacity design identifies the carrier radio resources serving each demand zone, the frequency bands and technologies involved, and whether resources are shared with other areas or outdoor users. High-density spaces may need a different radio-resource allocation from nearby low-demand rooms. Engineering documentation describes the selected architecture's current capability and the resources needed for expansion.

For example, an off-air donor antenna and bi-directional amplifier (BDA) can extend available macro-network service indoors, but the result depends on the outdoor signal and the serving macro network's load. An appropriately engineered carrier-connected or managed radio signal source can offer more defined capacity and operating arrangements, subject to the carrier-approved configuration and service terms. The difference matters when proposals show similar coverage but have different busy-hour behavior.

Digital DAS platforms may offer configurable signal routing or sector arrangements, but these capabilities vary by system and implementation. Likewise, a digital indoor small-cell architecture may be evaluated as an alternative to a DAS where it meets the same carrier, coverage and capacity objectives. Neither a product label nor the antenna count substitutes for the engineer's resource and interference analysis.

Transport and Backhaul in Capacity Planning

Carrier-connected signal sources require suitable connectivity to the operator network. Transport planning involves the DAS integrator, signal-source provider, participating carriers and enterprise IT team, each with defined responsibilities.

The transport design establishes who supplies and manages the connection, which bandwidth and performance requirements apply in each direction, and whether the circuit is shared with other building traffic. Latency, packet loss, service availability, security and quality-of-service requirements may matter in addition to headline connection speed.

The hypothetical 160 Mbps downlink and 40 Mbps uplink workload cannot be translated directly into a circuit order. Engineering review considers source configuration, carried traffic, protocols, overhead, contention, additional services and carrier-specific transport specifications. The operating arrangement also identifies responsibility for troubleshooting, configuration changes and escalation.

Why Busy-Hour Validation Goes Beyond Signal Strength

Testing should establish whether the system meets the agreed service objectives in the areas and conditions that matter. Strong signal measurements are useful, but alone they do not show how users experience a heavily loaded network.

The owner's performance objectives and important demand scenarios provide the basis for a testing methodology developed by the DAS integrator and reviewed with participating carriers. Depending on the system, that methodology may combine RF measurements, active-device tests, throughput or application testing, source-utilization data and appropriately planned load observations. Acceptance records document the test conditions, devices, bands, carriers and known limitations.

Full-capacity event testing may not be possible before occupancy. In those cases, commissioning evidence is supplemented by a post-occupancy follow-up plan and defined responsibility for resolving verified shortcomings. The companion article DAS Acceptance Testing: Verify Every Carrier's Service explains the carrier-by-carrier closeout process.

How Capacity Planning Accounts for Growth

Future demand is easier to address when likely changes are documented during design. Expansion triggers may include new tenants, room conversions, larger events, changes in carrier usage or new applications with significant uplink requirements.

Physical provisions for expansion are distinct from actual increases in capacity. Spare fiber, rack space or cabling pathways can reduce future construction work, but additional capacity may still require new carrier radio resources, equipment, software licenses, power, transport, approvals or recurring service charges.

Engineering documentation describes realistic expansion paths and their dependencies. Retained assumptions and design records help the operating team recognize when the building has moved beyond the original plan. Changes in carrier participation and signal-source readiness are also part of the DAS Carrier Activation process.