Ip.access
UK business
ip.access Limited is a multinational corporation that designs, manufactures, and markets small cells (picocell and femtocell) technologies and infrastructure equipment for GSM, GPRS, EDGE, 3G, 4G and 5G. The company was acquired by Mavenir in September 2020.
The company’s headquarters is based in Cambourne, England. The company also maintains offices in Gurgaon and Pune, India.
ip.access combines IP and cellular technologies to provide 2G, 3G and LTE coverage and for mobile networks. Using satellite backhaul, its products provide coverage to commercial passenger aircraft, ships, and users in remote rural areas.
The firm is a member of 3GPP, CBRS Alliance, European Telecommunications Standards Institute (ETSI), Having previously been an individual member of the Telecom Infra Project, following its acquisition, ip.access continues to be involved through Mavenir's membership.
History
ip.access was founded in December 1999 as a wholly owned subsidiary of TTP Group PLC aimed at developing technologies that would allow multiple radio access technologies to communicate over the Internet. To accommodate its growing staff, in 2006 ip.access relocated to new offices in Cambourne Business Park, Cambridge, where it remains.
In October 2000, TTP Group spun off its communications division (TTP Communications, or TTPCom) in an initial public offering on the London Stock Exchange, and ip.access joined the spin-off as a wholly owned subsidiary of the TTPCom group.
In March 2006, the company secured an £8.5 million round of funding from Intel Capital, Scottish Equity Partners, and Rothschild & Cie Banque.
This brief starts where responsible research should: with the source description of “Ip.access” as uK business. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as uK business. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Aug 12, 2026. The linked authority identifier is Q6064828. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2020, 1999, 2006 and 2000.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Ip.access”, its source revision and the description used here.
- Expand the search: follow Ip.access primary sources, Ip.access archive and access research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Ip.access”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Ip.access” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.