
A femtocell market number is useful only when its unit, population and time period are clear. Household interest, shipments, installed units and active service each answer a different question. Use the steps below to decide whether two figures can support the same conclusion.
Identify what the market includes
Start with the report’s own definition. A residential femtocell estimate may cover operator-provided home access points, while a broader small-cell forecast can include enterprise indoor and outdoor deployments. Record radio generation, geography, customer type and whether the report counts equipment, sites, networks or revenue.
The Small Cell Forum market forecast landing page is a source for current report editions. Read the edition and methodology behind a figure before comparing it with an older household femtocell forecast. A familiar publisher name does not make changing segment definitions interchangeable.
Separate intention, delivery and use
On a narrow screen, scroll the table sideways. Keyboard users can focus the table and use the arrow keys.
| Measure | Meaning | Additional question |
|---|---|---|
| Survey interest | Respondents express interest under the survey’s conditions | Who was surveyed, how was the question phrased, and at what proposed price or subsidy? |
| Shipments | Units move through a defined sales or distribution boundary | Does this include inventory, replacements or returns? |
| Installed base | Units accumulated under the publisher’s counting rule | Are retired or inactive units removed? |
| Active deployments | Equipment or sites meet an operational activity definition | How recent must activity be, and what exactly is one deployment? |
| Revenue | Money assigned to the stated market | Does it include software, installation or recurring services? |
| Forecast | A modeled future outcome | What baseline, assumptions, scenario and revision date support it? |
As a dated example of method disclosure, SCF’s April 2020 methodology discussion describes operator deployment-plan surveys feeding a model. Planned deployments are inputs to that forecast. Keep the eventual observation separate when evaluating how accurately the forecast performed.
Check a growth claim with a small example
Hypothetical example: a narrowly defined market begins with 100,000 active units, adds 30,000 newly activated units and retires 10,000 units during the year. Its ending active base is 120,000: 100,000 + 30,000 − 10,000. Net growth is 20%. If 40,000 units were shipped, shipment growth and active-base growth would still be separate measures.
For a hypothetical forecast rising from 100,000 to 160,000 units over four annual intervals, compound annual growth is (160,000 ÷ 100,000)1/4 − 1, approximately 12.5%. Count the intervals between endpoints. A report covering five labeled calendar years can contain four growth intervals.
Compare only like quantities. A revenue forecast in dollars cannot establish unit adoption without assumptions about price and included services. A total-market increase can coexist with a decline in residential equipment if another segment grows.
Build a comparison you can revisit
- Save publisher, report title, edition, publication date and the exact chart or table identifier.
- Write the counted object, geography, segment, technology and time period in your own words. Mark actual, estimate or forecast.
- Record methodology access, sample limitations and whether a sponsor has an interest in the result. If a definition is unavailable, mark it unknown.
- Align definitions before calculating change. Show any exclusions or conversions explicitly.
- When observations become available, compare them with the original forecast vintage and explain definition changes separately.
Use a conclusion proportionate to the evidence: “the publisher forecasts growth in this defined segment” is useful when the methodology is available; “femtocells are growing everywhere” usually asks more of the data. For judging individual product announcements alongside market claims, see wireless evidence from announcement to deployment.