<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.12-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Femtophilia</title>
	<link>http://blog.telecoms.com/2007/11/06/femtophilia/</link>
	<description>Telecoms industry news and opinion</description>
	<pubDate>Fri, 09 Jan 2009 01:47:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.12-alpha</generator>

	<item>
		<title>by: Dimitris Mavrakis</title>
		<link>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-407</link>
		<pubDate>Sun, 02 Dec 2007 22:03:10 +0000</pubDate>
		<guid>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-407</guid>
					<description>I think we can all agree that past the fanfare, femto cells have way to go in order to evolve (technologically) without being overly fragmented. There are too much uncertainty and issues facing them at the moment.

Also, I do not think that femto cells compete with dual terminal solutions (cellular/WiFi, UMA etc) since the end user simply uses the same mobile phone and could be unaware of the transition. This gives femto cells tremendous pull in the common end user market, while dual terminals are more suitable for business users.

I have written an article on what I think on femto cells on:
www.visionmobile.com/blog/</description>
		<content:encoded><![CDATA[<p>I think we can all agree that past the fanfare, femto cells have way to go in order to evolve (technologically) without being overly fragmented. There are too much uncertainty and issues facing them at the moment.</p>
<p>Also, I do not think that femto cells compete with dual terminal solutions (cellular/WiFi, UMA etc) since the end user simply uses the same mobile phone and could be unaware of the transition. This gives femto cells tremendous pull in the common end user market, while dual terminals are more suitable for business users.</p>
<p>I have written an article on what I think on femto cells on:<br />
<a href="http://www.visionmobile.com/blog/" rel="nofollow">www.visionmobile.com/blog/</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Rajiv Chaudhuri</title>
		<link>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-313</link>
		<pubDate>Wed, 21 Nov 2007 05:45:10 +0000</pubDate>
		<guid>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-313</guid>
					<description>A Femto CPE model is still evolving, so mandating any particular direction may be premature at this point. Having said so though, I would imagine at least for any enterprise deployment, both radio and IP parts will be managed by the operators. Enterprise customers will be reluctant to play an active part with this relatively new technology, as their efforts can be better utilised elsewhere. The SLAs are going to enforced depending on what applications will be run in the enterprise network over the carrier WAN. In the residential context, jury is still tryig out as to what is the best way forward. 
Regarding QoS/QoE, I have got a more optimistic view. In a global context, mobile operators could leverage from ULL/LLU arrangements to deploy their own DSL IP infrastructure or enter into some kind of network sharing arrangement with the incumbent Carriage Service Providers. Truly speaking, they don't need to own the last mile, instead use their own IP core by putting DLSAMs at the incumbent exchange. Although, one IP network sounds simple, Femto architectural and deployment challenges are daunting but not insurmountable moving forward.</description>
		<content:encoded><![CDATA[<p>A Femto CPE model is still evolving, so mandating any particular direction may be premature at this point. Having said so though, I would imagine at least for any enterprise deployment, both radio and IP parts will be managed by the operators. Enterprise customers will be reluctant to play an active part with this relatively new technology, as their efforts can be better utilised elsewhere. The SLAs are going to enforced depending on what applications will be run in the enterprise network over the carrier WAN. In the residential context, jury is still tryig out as to what is the best way forward.<br />
Regarding QoS/QoE, I have got a more optimistic view. In a global context, mobile operators could leverage from ULL/LLU arrangements to deploy their own DSL IP infrastructure or enter into some kind of network sharing arrangement with the incumbent Carriage Service Providers. Truly speaking, they don&#8217;t need to own the last mile, instead use their own IP core by putting DLSAMs at the incumbent exchange. Although, one IP network sounds simple, Femto architectural and deployment challenges are daunting but not insurmountable moving forward.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Moh Yan</title>
		<link>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-308</link>
		<pubDate>Tue, 20 Nov 2007 16:30:45 +0000</pubDate>
		<guid>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-308</guid>
					<description>Regarding OAM aspects of femto-cells, the end-user device is more akin to a CPE (DSL modem etc) than a
canonical base station. Obviously things such as UMTS frequencies, scrambling codes, power levels etc are ostensibly controlled by the operator, but this is not the "cell site" concept.

A more appropriate comparison is to an 802.11x box.
It either works or doesn't. If signal reception is poor
in the premises, move the box to a better position.
you don't get an operator doing a terrain simulation of
your house, nor a field engineer visiting to adjust
antenna tilt etc.

Regarding QoS/QoE aspects, the services invoked by a
user are required at worst to be comparable to that
experienced in the macro network. The (literal) weak
link is not the radio aspects (although coverage etc
by the CPE is not a totally solved problem) , but the
IP connection between the core network and the CPE.
For residential subscribers, this is likely to be an
xDSL link (with all the issues therein) .

And a link not dedicated to the femto env either.
Web browsing, IPTV, gaming etc all will be potentially
making demands of that link. So mobile operators will
be expecting QoS interfaces of access network operators
that are much more than "best efforts" . Which is supposed to be a key feature of the "converged" network is it not.

This begs the question of whether mobile operators
who are not part of a company with its own access
network division (networks and/or LLU experience) will
have their femto dreams smashed by an access provider
not up to the job. Think of the UK, with a Vodafone
having to guarantee QoS in an LLU env that inter-
works with a (pre-21CN) BT Openreach outfit.</description>
		<content:encoded><![CDATA[<p>Regarding OAM aspects of femto-cells, the end-user device is more akin to a CPE (DSL modem etc) than a<br />
canonical base station. Obviously things such as UMTS frequencies, scrambling codes, power levels etc are ostensibly controlled by the operator, but this is not the &#8220;cell site&#8221; concept.</p>
<p>A more appropriate comparison is to an 802.11x box.<br />
It either works or doesn&#8217;t. If signal reception is poor<br />
in the premises, move the box to a better position.<br />
you don&#8217;t get an operator doing a terrain simulation of<br />
your house, nor a field engineer visiting to adjust<br />
antenna tilt etc.</p>
<p>Regarding QoS/QoE aspects, the services invoked by a<br />
user are required at worst to be comparable to that<br />
experienced in the macro network. The (literal) weak<br />
link is not the radio aspects (although coverage etc<br />
by the CPE is not a totally solved problem) , but the<br />
IP connection between the core network and the CPE.<br />
For residential subscribers, this is likely to be an<br />
xDSL link (with all the issues therein) .</p>
<p>And a link not dedicated to the femto env either.<br />
Web browsing, IPTV, gaming etc all will be potentially<br />
making demands of that link. So mobile operators will<br />
be expecting QoS interfaces of access network operators<br />
that are much more than &#8220;best efforts&#8221; . Which is supposed to be a key feature of the &#8220;converged&#8221; network is it not.</p>
<p>This begs the question of whether mobile operators<br />
who are not part of a company with its own access<br />
network division (networks and/or LLU experience) will<br />
have their femto dreams smashed by an access provider<br />
not up to the job. Think of the UK, with a Vodafone<br />
having to guarantee QoS in an LLU env that inter-<br />
works with a (pre-21CN) BT Openreach outfit.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Rajiv Chaudhuri</title>
		<link>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-297</link>
		<pubDate>Sun, 18 Nov 2007 00:43:15 +0000</pubDate>
		<guid>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-297</guid>
					<description>Femtos open up an interesting debate who will be responsible for the management of base-stations at the customer premises. Whether,a mobile customer is a retail or a business entity, ideally the base-station management should be performed by the operators themselves. The reason being, mobile operators need to ensure,  Quality of Experience (QoE) must exceed customer expectations on the service offerings for delivering a viable business proposition with this new technology. Moreover, any chosen business model must guarantee an efficient spectrum utilisation, the most expensive element of the mobile market value chain. 
Interestingly, In order to deliver premium application services over the fixed broadband network, world's leading operators are actively pursuing a pragmatic strategy, where they are responsible for managing  service offering end to end. The customer home gateway is considered as a key network element into such integrated service management plot.    
In like vein, why not, a similar strategy be adopted to deliver voice and data applications using Femtocells over WCDMA/HSPDA+ ? Operators must control the last mile of the wireless access at the customer home.</description>
		<content:encoded><![CDATA[<p>Femtos open up an interesting debate who will be responsible for the management of base-stations at the customer premises. Whether,a mobile customer is a retail or a business entity, ideally the base-station management should be performed by the operators themselves. The reason being, mobile operators need to ensure,  Quality of Experience (QoE) must exceed customer expectations on the service offerings for delivering a viable business proposition with this new technology. Moreover, any chosen business model must guarantee an efficient spectrum utilisation, the most expensive element of the mobile market value chain.<br />
Interestingly, In order to deliver premium application services over the fixed broadband network, world&#8217;s leading operators are actively pursuing a pragmatic strategy, where they are responsible for managing  service offering end to end. The customer home gateway is considered as a key network element into such integrated service management plot.<br />
In like vein, why not, a similar strategy be adopted to deliver voice and data applications using Femtocells over WCDMA/HSPDA+ ? Operators must control the last mile of the wireless access at the customer home.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Moh Yan</title>
		<link>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-288</link>
		<pubDate>Fri, 16 Nov 2007 16:43:26 +0000</pubDate>
		<guid>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-288</guid>
					<description>As someone who has worked on development for clients
producing femto-cell systems, I can tell you
architecture is a significant issue (although my client
has solved some crucial aspects very nicely indeed) .

The service patterns (bit rates, concurrent users etc)
are actually not that big a problem, being more
constrained by the capabilities of the CPE, and the
bit rates supported by the subscriber Internet
connection (which may be competing for resources needed
by surfing, IPTV etc) .

However, the big issues are on the systems engineering
side. The cell management issue (topology, neighbour
cell lists on a per-terminal as opposed to per-cell
basis, downlink scrambling code reuse etc) is a real
killer for networks of potentially 100,000s of cells
that may come and go as easily as a customer switching
on/off the CPE.

Quite a bit of work will be needed to define/
standardise the C-plane/OAM interfaces to control
things such as handover from macro to femto etc.
But from I have seen, worked on, and know, the missing
bits are not too far away.</description>
		<content:encoded><![CDATA[<p>As someone who has worked on development for clients<br />
producing femto-cell systems, I can tell you<br />
architecture is a significant issue (although my client<br />
has solved some crucial aspects very nicely indeed) .</p>
<p>The service patterns (bit rates, concurrent users etc)<br />
are actually not that big a problem, being more<br />
constrained by the capabilities of the CPE, and the<br />
bit rates supported by the subscriber Internet<br />
connection (which may be competing for resources needed<br />
by surfing, IPTV etc) .</p>
<p>However, the big issues are on the systems engineering<br />
side. The cell management issue (topology, neighbour<br />
cell lists on a per-terminal as opposed to per-cell<br />
basis, downlink scrambling code reuse etc) is a real<br />
killer for networks of potentially 100,000s of cells<br />
that may come and go as easily as a customer switching<br />
on/off the CPE.</p>
<p>Quite a bit of work will be needed to define/<br />
standardise the C-plane/OAM interfaces to control<br />
things such as handover from macro to femto etc.<br />
But from I have seen, worked on, and know, the missing<br />
bits are not too far away.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Andy Tiller</title>
		<link>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-275</link>
		<pubDate>Thu, 15 Nov 2007 15:18:48 +0000</pubDate>
		<guid>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-275</guid>
					<description>A key issue is the need for service continuity between the indoor and outdoor networks.  If these are both the same network (i.e. the femtocell scenario), then service continuity comes for free.

If the networks are different (i.e. the WiFi dual mode scenario), then you need extra technology to make sure users can access the same services on the two networks using the same applications on the phone with the same settings.  Mass market consumers are unlikely to want to change their browser settings when switching over from the cellular to the WiFi network.

UMA solves this issue, but the handset choice is poor.  And all UMA handsets today are 2G, which means that they don't have the horsepower to handle high-speed data.  This explains why dual-mode offerings are all about cheap voice calls in WiFi hotspots, rather than about "WiFi-speed" data on your phone.

3G UMA is coming, but by the time we see the handsets 3G femtocells will be a viable alternative.</description>
		<content:encoded><![CDATA[<p>A key issue is the need for service continuity between the indoor and outdoor networks.  If these are both the same network (i.e. the femtocell scenario), then service continuity comes for free.</p>
<p>If the networks are different (i.e. the WiFi dual mode scenario), then you need extra technology to make sure users can access the same services on the two networks using the same applications on the phone with the same settings.  Mass market consumers are unlikely to want to change their browser settings when switching over from the cellular to the WiFi network.</p>
<p>UMA solves this issue, but the handset choice is poor.  And all UMA handsets today are 2G, which means that they don&#8217;t have the horsepower to handle high-speed data.  This explains why dual-mode offerings are all about cheap voice calls in WiFi hotspots, rather than about &#8220;WiFi-speed&#8221; data on your phone.</p>
<p>3G UMA is coming, but by the time we see the handsets 3G femtocells will be a viable alternative.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Todd Spraggins</title>
		<link>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-263</link>
		<pubDate>Wed, 14 Nov 2007 14:58:40 +0000</pubDate>
		<guid>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-263</guid>
					<description>Femto sounds great for voice, but what about data? Does the enterprise really want its data going back out to a public node given privacy (HIPA) and other "compliance" concerns. And what if all I want to do is stream off of my itunes server locally. I think the Teleware solution mentioned in the article http://www.telecoms.com/itmgcontent/tcoms/news/articles/20017393694.html gets close to a better route optimization problem, but again only for voice. 
Finally, I wonder if we have not started another VHS/betamax war. Femto might be a superior technology from several angles (battery, spectral efficiency, quality, seamless HO), but WiFi can be controlled by the end user and is essentially ubiquitous.</description>
		<content:encoded><![CDATA[<p>Femto sounds great for voice, but what about data? Does the enterprise really want its data going back out to a public node given privacy (HIPA) and other &#8220;compliance&#8221; concerns. And what if all I want to do is stream off of my itunes server locally. I think the Teleware solution mentioned in the article <a href="http://www.telecoms.com/itmgcontent/tcoms/news/articles/20017393694.html" rel="nofollow">http://www.telecoms.com/itmgcontent/tcoms/news/articles/20017393694.html</a> gets close to a better route optimization problem, but again only for voice.<br />
Finally, I wonder if we have not started another VHS/betamax war. Femto might be a superior technology from several angles (battery, spectral efficiency, quality, seamless HO), but WiFi can be controlled by the end user and is essentially ubiquitous.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Rajiv Chaudhuri</title>
		<link>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-257</link>
		<pubDate>Wed, 14 Nov 2007 02:23:46 +0000</pubDate>
		<guid>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-257</guid>
					<description>Femto Cells solution direction seems to be intricately linked with the FMC strategy. The role of DSL and Cable is of paramount importance for Femtos success, because these fixed access technologies could provide low-cost backhaul solution to deliver mobile data and voice into the all IP architecture. 

There will some architecture challenges though, as to how fixed and mobile subscribers will be handled in the IP network in relation with authentication, QoS and policy management. One possible business model with Femtos will be to eliminate the need for fixed connection altogether from the customer home. Such approach would simplify or even in some cases initiate the withdrawal of fixed subscriber management function from the Broadband service edge. This is a cost effective infrastructure strategy to deliver a "best fit"  DSL or cable backhaul  for Femtos based WCDMA mobile voice and data.  

Femtos open up a real possibility for an integrated digital home solution, but would require some far reaching changes at the Broadband  Edge  to adapt to the new business model. If this happens, Femtos could deliver a competitive edge to the mobile operators over their fixed network rivals.</description>
		<content:encoded><![CDATA[<p>Femto Cells solution direction seems to be intricately linked with the FMC strategy. The role of DSL and Cable is of paramount importance for Femtos success, because these fixed access technologies could provide low-cost backhaul solution to deliver mobile data and voice into the all IP architecture. </p>
<p>There will some architecture challenges though, as to how fixed and mobile subscribers will be handled in the IP network in relation with authentication, QoS and policy management. One possible business model with Femtos will be to eliminate the need for fixed connection altogether from the customer home. Such approach would simplify or even in some cases initiate the withdrawal of fixed subscriber management function from the Broadband service edge. This is a cost effective infrastructure strategy to deliver a &#8220;best fit&#8221;  DSL or cable backhaul  for Femtos based WCDMA mobile voice and data.  </p>
<p>Femtos open up a real possibility for an integrated digital home solution, but would require some far reaching changes at the Broadband  Edge  to adapt to the new business model. If this happens, Femtos could deliver a competitive edge to the mobile operators over their fixed network rivals.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ravi Gurnani</title>
		<link>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-244</link>
		<pubDate>Mon, 12 Nov 2007 20:59:12 +0000</pubDate>
		<guid>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-244</guid>
					<description>Femtos have a bright future mainly due to following reasons:

1. In-house/in-office wireless coverage is still unstable or inconsistent. Femtos mitigate this problem and provide a "under-the-tower" quality.

2. Though Wi-Fi is a good and already available alternative, its predominantly associated with Laptops (ofcourse there are WiFe cellphones as well). With evolved CDMA or GSM/UMTS technologies, corresponding Femtos provide you the luxury of using the "cell-phone" for "voice" as well as "data".</description>
		<content:encoded><![CDATA[<p>Femtos have a bright future mainly due to following reasons:</p>
<p>1. In-house/in-office wireless coverage is still unstable or inconsistent. Femtos mitigate this problem and provide a &#8220;under-the-tower&#8221; quality.</p>
<p>2. Though Wi-Fi is a good and already available alternative, its predominantly associated with Laptops (ofcourse there are WiFe cellphones as well). With evolved CDMA or GSM/UMTS technologies, corresponding Femtos provide you the luxury of using the &#8220;cell-phone&#8221; for &#8220;voice&#8221; as well as &#8220;data&#8221;.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ian Goetz</title>
		<link>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-235</link>
		<pubDate>Mon, 12 Nov 2007 14:31:02 +0000</pubDate>
		<guid>http://blog.telecoms.com/2007/11/06/femtophilia/#comment-235</guid>
					<description>The two respondees raise valid points. WiFi enabled devices are maturing but two crucial issues remain, the first is number of devices for consumer choice. Most WiFi Devices are in the business phone sector and not attractively priced in the consumer segment targetted by Femto cells. There is also the issue for cellular to WiFi handover - only UMA has truly cracked this issue and most WiFi devices are not UMA capable.

The architecture point is also valid, using an IuB over IP to a standard RNC for femto will never allow true volume deployment due to the limited throughput of the RNC, those femto cell vendors offering a collapsed architecture, in effect and early version of the LTE Node E and those with the UMA based architecture are able to address both throughput and volume deployment.

These devices are the mobile approach to convergence, deploying 3G capacity where it is needed - in-building, with a model where much of the cost of providing that capacity has been covered by the mobile customer who can still use the standard 3G device.</description>
		<content:encoded><![CDATA[<p>The two respondees raise valid points. WiFi enabled devices are maturing but two crucial issues remain, the first is number of devices for consumer choice. Most WiFi Devices are in the business phone sector and not attractively priced in the consumer segment targetted by Femto cells. There is also the issue for cellular to WiFi handover - only UMA has truly cracked this issue and most WiFi devices are not UMA capable.</p>
<p>The architecture point is also valid, using an IuB over IP to a standard RNC for femto will never allow true volume deployment due to the limited throughput of the RNC, those femto cell vendors offering a collapsed architecture, in effect and early version of the LTE Node E and those with the UMA based architecture are able to address both throughput and volume deployment.</p>
<p>These devices are the mobile approach to convergence, deploying 3G capacity where it is needed - in-building, with a model where much of the cost of providing that capacity has been covered by the mobile customer who can still use the standard 3G device.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
