Enterprise femtocells, forming a grid of self-organising coverage, are genuinely new. So it's not surprising that they are often misunderstood.
On one hand they offer the low cost and self-install simplicity of enterprise WiFi. Yet they also offer all the benefits of 3G cellular with massive data capacity. This is a heady combination, and promises to make in-building cellular affordable for small companies because the femtocells are based on mass-produced hardware, because no radio planning is required and because they can be self installed by the IT guys. They also promise to multiply the uptake of in-building cellular in large enterprises by providing added flexibility and simplicity at a fraction of the cost of today's manually engineered pico/DAS systems.
John Spindler, in his article for Wireless Week, makes a couple of familiar assumptions about enterprise femtocells, which I'm happy to put right.
ASSUMPTION 1: MINIMUM COVERAGE OVERLAP The first assumption is that a grid of enterprise femtocells has minimal coverage overlaps. It doesn't. In fact the femtos deliberately organise themselves into a grid with extensive overlaps.
Interference What femtocells do that's different to picocells is manage interference themselves in real-time rather than rely on the complex RF engineering that would otherwise be required. The femtocells obey the policies set by the mobile operators so will never produce unmanaged interference between each other or with the macro network. For example, femtocells in the grid use algorithms to ensure maximum spatial diversity between scrambling codes.
Signal dominance Making the wrong assumption about coverage overlap leads to worrying about phones flip-flopping in and out of the macro network. But enterprise femtocells provide a strong indoor signal and also hold onto phones using "sticky cell" technology. Together these ensure that flip-flopping doesn't happen, and that's true of any 3G phone.
ASSUMPTION 2: UNDERESTIMATING FEMTOCELL CAPABILITY The second assumption is that femtocells can support only a handful of calls and have a range which is a fraction of a picocell. Not quite: enterprise femtocells can range in capacity from 8-16+ users, and each one has a range approaching today's picocells.
Handovers Femtocells in the grid don't need to do soft handovers because of strong cell overlap, and they don't have to handover very often because their range is not far short of picocells. There is always a battery life penalty when handing-over, but this is more than offset by the massive reduction in handset transmit power. In any case additional battery consumption only occurs when on a call, not when the phone is moving but idle. So the net effect is a major boost in battery life over the macro network.
Over-provisioning? In a grid of enterprise femtocells every femto handles not a handful of users but 8 or 16 or more - providing robust coverage and high capacity throughout the building. Most importantly, it does so more cost-effectively than Pico/DAS solutions that require radio engineers to deploy them.
The bottom line... Ever wondered why wifi access points tend to be installed in a modular fashion, rather than in a pico/DAS-style hierarchy? The answer is because they can be - it's simpler, easier and cheaper. And the same is true of enterprise femtocells.
Hi, I'm running a lab with some XRv9000 (v7.3.1) and an Opendaylight controller (v13.1 (Aluminium)). The goal is to push a Segment Routing LSP from the PCE over the IOS XRv, which is working. However when querying my controller for the...
We have an ASR-9001 and it was running 5.1 and we attempted to turboboot unit to 6.4.1. Then this happened. RP/0/RSP0/CPU0:Apr 19 08:04:04.410 : cfgmgr-rp: %MGBL-CONFIG-0-INIT_FAILURE : Configuration Manager was unable to initialize the Admin Co...
hi,I have PE1 router and i want to connect it to P router. The physical connectivity have to pass through PE2 router. PE2 is already connected to P router. I have two possible probabilitiesFirst: to have L3 connectivity between PE1 and PE2 , so PE1 will a...
Hello everybodyI would like to clarify some things that confound me.The inner label is set to route the packet to our neighbor.The outer label is set to route the packet to the MP-bgp.Quite right?Is the Inner label generated by the PE or by the P?Thank yo...
Hi guys,i've got a ASR9901 acts as BNG, with dynamic-template for subscriber interfaces creation and PPPoE via radius auth, by the RemoteID that the network attach to PADI request. All works fine.Now a new, wholesaler supplier doesn't implement intermedia...