<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>4G Domains &#187; Motorola</title>
	<atom:link href="http://4gdomains.com/category/motorola/feed/" rel="self" type="application/rss+xml" />
	<link>http://4gdomains.com</link>
	<description>Domains related to 4G, Wimax, and LTE</description>
	<lastBuildDate>Wed, 23 Dec 2009 02:20:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>WiMAX Profile C is Not a Slam Dunk</title>
		<link>http://4gdomains.com/2009/07/wimax-profile-c-is-not-a-slam-dunk/</link>
		<comments>http://4gdomains.com/2009/07/wimax-profile-c-is-not-a-slam-dunk/#comments</comments>
		<pubDate>Tue, 07 Jul 2009 14:36:42 +0000</pubDate>
		<dc:creator>kwieland</dc:creator>
				<category><![CDATA[4G News]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Motorola]]></category>
		<category><![CDATA[WiChorus]]></category>
		<category><![CDATA[WiMAX]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[As WiMAX standards evolve and drive towards consistent profiles, operators must consider business models and other factors when selecting equipment and solutions from vendors.

]]></description>
			<content:encoded><![CDATA[<p>        <head></p>
<style>
<!--
 table.MsoNormalTable
	{mso-style-parent:"";
	font-size:10.0pt;
	font-family:"Times New Roman";
	}
-->
</style>
<p></head></p>
<p>&nbsp;</p>
<table border="1" width="100%" id="table1" cellpadding="6">
<tr>
<td><b><br />
		<font size="4">Wireless Broadband Perspectives &#8211; WiMAX.com Weekly Series</font><br />
		</b>Sponsored By:<br />
		<img border="0" src="http://www.wimax.com/commentary/blog/blog-2009/july-2009/cisco.jpg" width="117" height="73" title="WiMAX Profile C is Not a Slam Dunk" alt="cisco WiMAX Profile C is Not a Slam Dunk" /><br />
		<i>Featured perspectives from leading thought leaders in the WiMAX &amp; wireless<br />
		broadband industry.</i><br />
&nbsp;</td>
</tr>
</table>
<p>
In his keynote presentation at the WiMAX Forum Global Congress event held in<br />
Amsterdam last month, Barry West, who now heads up the international interests<br />
of Clearwire, said one of his priorities in the coming months was to persuade<br />
operators to adopt WiMAX Profile C.</p>
<p>At first glance, the need to do so might seem strange.&nbsp; Why would any<br />
operator not want to choose Profile C, which stipulates an open and<br />
non-proprietary interface standard (R6) between the BTS and the ASN Gateway?&nbsp;<br />
As Profile C operators are not tied into one vendor for BTS and ASN Gateway<br />
equipment, they can force prices down through playing off different suppliers<br />
against each other.&nbsp; They can also choose the suppliers that can best<br />
support the functionality and services they want to offer over their network<br />
rather than being tied to one vendor that might not be up to the job.</p>
<p>But, as West implies, the case for Profile C is not clear cut; if it were, he<br />
would not need to campaign for its adoption.&nbsp; Despite the apparent<br />
advantages of Profile C, some &#8216;turnkey&#8217; vendors are still successfully tempting<br />
operators with the two other Profiles available between the BTS and ASN Gateway:<br />
Profile A and Profile B.&nbsp; As both Profiles can create vendor lock-ins, they<br />
stand in the way of WiMAX interoperability progress between multiple vendors<br />
and, potentially, lower equipment prices.</p>
<p>In some cases, though, there are strong arguments not to use Profile C,<br />
particularly if operators can avoid the expense of a large ASN Gateway.&nbsp;<br />
While Cisco believes that Profile C is the better choice for WiMAX operators<br />
offering mobility services, not least because it centralizes the decision-making<br />
for call handoffs between different BTSs &#8211; which then makes it easier for the<br />
operator to control RAN traffic and offer QoS &#8211; this functionality is clearly<br />
not necessary for a WiMAX operator focused on fixed and portable services only.&nbsp;<br />
&quot;Where handoff is not required, Profile B can be adequate,&quot; says Paul Sergeant,<br />
Mobile WiMAX Solutions Manager at Cisco.&nbsp; &quot;Profile C still has some<br />
advantages, even in this case &#8211; such as QoS &#8211; but it may not justify the extra<br />
cost.&quot;</p>
<p>Profile B does not define any interface between the BTS and the ASN Gateway, so<br />
it is possible for Profile B vendors to pursue proprietary solutions and lock in<br />
their customers.&nbsp; Due to increased customer demand, however, many of the<br />
big WiMAX suppliers that started out by supplying profile B equipment, including<br />
Cisco (through its acquisition of Navini Networks) are now shifting to Profile<br />
C.&nbsp; According to Sergeant, nearly all of Cisco&#8217;s 20-plus commercially<br />
deployed WiMAX operator customers are moving from Profile B to Profile C.&nbsp;<br />
This is an encouraging sign for Barry West and all those in the WiMAX community<br />
campaigning for open network architectures, particularly if R6 interfaces can be<br />
fairly easily software-installed on Profile B kit as Sergeant indicates.</p>
<p><b>Profile C Stumbling Blocks<br />
</b><br />
One potential fly in the WiMAX interoperability ointment is Motorola, which has<br />
long been a Profile B supporter.&nbsp; Although Motorola&#8217;s WiMAX literature<br />
points out that its wi4 equipment is &#8216;functionally aligned with Profile C&#8217; &#8211; no<br />
doubt largely due to intense pressure from Clearwire to which it supplies<br />
802.16e kit &#8211; there is a feeling in the WiMAX community that Motorola will not<br />
be able to make the transition from Profile B to Profile C as easily as others.&nbsp;<br />
One senior executive of an independent ASN Gateway supplier, who wished to<br />
remain anonymous, told Wimax.com: &quot;Some companies have hardware pieces which are<br />
very difficult to change to Profile C and Motorola is one of those companies.&nbsp;<br />
They may have a hard time making the change [to Profile C].&quot; </p>
<p>One person willing to go on record about Motorola is Peter Ziegelwanger, CTO at<br />
Wimax Telecom, a small operator with a network presence in Austria, Slovakia and<br />
Croatia.&nbsp; &quot;[Profile C] is a complete change in Motorola&#8217;s core network<br />
architecture and has a lot of impact on its existing networks,&quot; he says.&nbsp;<br />
Wimax.com was not able to get a response from Motorola regarding how many of its<br />
customers it has moved from Profile B to Profile C, or to get an update on how<br />
many interoperability partners it has (or is in interoperability testing) for<br />
its BTS and ASN Gateway equipment.&nbsp; However, with at least 19 WiMAX<br />
contracts to its name, as well as what it says is more than 75 WiMAX<br />
&#8216;engagements&#8217; in 44 countries worldwide, Motorola is a major WiMAX player.&nbsp;<br />
The speed that Motorola moves to Profile C will play a big part in how far the<br />
R6 interface is made available in different parts of the world.&nbsp; </p>
<p>Another big Profile C stumbling block is Alcatel-Lucent, which is a keen<br />
advocate of Profile A and has no plans to develop Profile C WiMAX equipment.&nbsp;<br />
While the R6 interface is used between the BTS and the ASN Gateway under Profile<br />
A, the RRM (Radio Resource Management) is split between the BTS and the ASN<br />
Gateway: the RRA (Radio Resource Agent) resides in the BTS while the RRC (Radio<br />
Resource Controller) is placed in the ASN Gateway.&nbsp; The upshot is that<br />
operators using Profile A must have the same supplier for the BTS and the ASN<br />
Gateway.&nbsp; And for some operators, if the price and performance is right,<br />
Profile A is a reasonable (if not ideal) solution.&nbsp; Wimax Telecom, for<br />
example, selected Profile A equipment from Alcatel-Lucent to roll an 802.16e<br />
network in Croatia.&nbsp; </p>
<p>&quot;We do not support an open R6 interface as there has been no market request for<br />
it so far, at least in the &#8216;enhanced wireless DSL&#8217; market segment that we are<br />
targeting, and where we have seen the bulk of market activity in terms of WiMAX<br />
deployments,&quot; an Alcatel-Lucent spokesperson told Wimax.com.&nbsp;<br />
&quot;Additionally, the vast majority of WiMAX deployments are single RAN supplier<br />
deployments, and even in those cases where there are networks supplied by<br />
several RAN vendors they are typically split into different areas/cities, each<br />
of them being supported by one RAN manufacturer.&quot; </p>
<p>Like Motorola, Alcatel-Lucent has a big 802.16e presence around the world.&nbsp;<br />
As of the beginning of 2Q 2009, the French-US supplier was supplying 802.16e kit<br />
for 15 commercial networks worldwide, with a total of 36 Mobile WiMAX contracts<br />
under its belt.&nbsp; Alcatel-Lucent&#8217;s resistance to Profile C is and will be a<br />
big restraining factor on the spread of R6.</p>
<p><b>Profile C Momentum<br />
</b><br />
The Profile C question marks hanging over Motorola, plus the outright Profile C<br />
defiance from Alcatel-Lucent, shouldn&#8217;t detract from the significant amount of<br />
interoperability progress that has been made on IOT and partnership-forming<br />
between different BTS and ASN Gateway vendors via the open R6 standard and<br />
Profile C.&nbsp; Much of the groundwork on this has been done &#8211; through<br />
necessity &#8211; by the smaller standalone BTS vendors that don&#8217;t have the resources<br />
to develop ASN Gateways, such as Alvarion, WiNetworks, Aperto and Airspan.&nbsp;<br />
They need Profile C to get a foothold into the market.&nbsp; </p>
<p>The WiMAX Forum is also embarking on a NWIOT (Network Interoperability Testing)<br />
certification program that will only rubber-stamp equipment using R6 as part of<br />
Profile C.&nbsp; The WiMAX Forum had previously taken the position of letting<br />
the market decide between Profile B and Profile C &#8211; it had earlier dropped its<br />
support of Profile A &#8211; much to the annoyance of the smaller, independent WiMAX<br />
kit suppliers.</p>
<p>The WiMAX Forum&#8217;s unequivocal backing of Profile C is warmly welcomed by the<br />
likes of WiChorus, a standalone supplier of ASN Gateways and Home Agents that<br />
has been active in promoting Profile C through its own IOT initiative, the One<br />
Open WiMAX program.&nbsp; &quot;We have reached the tipping point for Profile C,&quot;<br />
says Rehan Jalil, WiChorus&#8217; CEO, &quot;but still a lot of work needs to be done.&quot;<br />
Part of that WiChorus work, says Jalil, is supporting base station vendors even<br />
if they are not yet fully Profile C compliant.</p>
<p>In the past, turnkey WiMAX kit suppliers would typically say to their<br />
prospective operator customers that Profile A or Profile B was the way to go<br />
unless they wanted to get embroiled in time-consuming IOT with multiple vendors<br />
with little chance of a satisfactory outcome.&nbsp; That argument is much less<br />
convincing now, particularly as Clearwire has been a staunch Profile C supporter<br />
from the beginning.&nbsp; Barry West, when persuading operators to go down the<br />
Profile C route, can also say as part of his sales pitch that they don&#8217;t need to<br />
do any IOT on vendors&#8217; kit that has already been tested on Clearwire&#8217;s network.</p>
<p>Profile C looks the way to go for most operators going forward but it may take a<br />
bit of time yet before it becomes what the open architecture proponents crave &#8211;<br />
a de facto standard. </p>
<p>
<img border="0" src="http://www.wimax.com/commentary/blog/blog-2009/july-2009/kwieland.jpg" width="125" height="128" title="WiMAX Profile C is Not a Slam Dunk" alt="kwieland WiMAX Profile C is Not a Slam Dunk" /><br />
<i>Ken Wieland has been reporting and commentating on the telecom industry for<br />
15 years. He has held various senior editorial positions, including most<br />
recently as Editor of WiMAX Vision magazine at Informa Telecoms &amp; Media. Now<br />
working as a freelance telecoms writer, Ken contributes analysis and opinion<br />
pieces to a number of websites, including the EIU (Economist Intelligence Unit).&nbsp;<br />
He can be contacted at <a href="mailto:ken2wieland@yahoo.co.uk"><br />
ken2wieland@yahoo.co.uk</a>.<br />
</i><br />
&nbsp;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/Wimax-WimaxcomBlog?a=9_Yaw9aYflk:YW3llhBQa_0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/Wimax-WimaxcomBlog?d=yIl2AUoC8zA" border="0" title="WiMAX Profile C is Not a Slam Dunk" alt=" WiMAX Profile C is Not a Slam Dunk" /></img></a> <a href="http://feeds.feedburner.com/~ff/Wimax-WimaxcomBlog?a=9_Yaw9aYflk:YW3llhBQa_0:7Q72WNTAKBA"><img src="http://feeds.feedburner.com/~ff/Wimax-WimaxcomBlog?d=7Q72WNTAKBA" border="0" title="WiMAX Profile C is Not a Slam Dunk" alt=" WiMAX Profile C is Not a Slam Dunk" /></img></a>
</div>
]]></content:encoded>
			<wfw:commentRss>http://4gdomains.com/2009/07/wimax-profile-c-is-not-a-slam-dunk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
