SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Qualcomm Moderated Thread - please read rules before posting
QCOM 180.88+2.0%Oct 31 3:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Clarksterh who wrote (26294)8/31/2002 10:49:23 AM
From: foundation  Read Replies (1) of 196414
 
re: the lack of technical rigor

Clark,

In my view this is only part of the problem - and perhaps the part that can be most easily rectified.

re: (can) the vendors actually resolve the technical incompatibility issues without getting political?

I think this is the insidious issue... and, in my view, all issues - including and especially conflict resolution - are fundamentally political in committee-based forums, including and especially 3GPP.

3GPP vendors - and especially the powerful, major vendors - fiercely protect their proprietary intellectual property that has been integrated into the standards. And in addition to de facto essential intellectual property, with an evolving standard, vendors are motivated to integrate additional, optional proprietary technology into their individual physical solutions (infrastructure, handsets and software) in order to influence - through successful field application - what may, in evolving standard versions, be injected or perceived as "essential" - or at least functioning.

Also, it is possible, through the integration of additional, optional proprietary technology, for vendors to lock carrier clients into same-vendor upgrades.

So, ironically, competing vendors have multiple vested interests in developing and marketing commercial solutions with additional proprietary content that further exacerbate cross-vendor compatibility issues.

<g>

Ben
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext