<?xml version="1.0"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Engadget - Comments for FCC starts up white spaces database, devices now inevitable</title>
<link>http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</link>
<description>Engadget Comments for FCC starts up white spaces database, devices now inevitable</description>
<image>
<url>http://www.engadget.com/media/feedlogo.gif</url>
<title>Engadget</title>
<link>http://www.engadget.com</link>
</image>
<language>en-us</language>
<copyright>Copyright 2012 Weblogs, Inc. The contents of this feed are available for non-commercial use only.</copyright>
<generator>Blogsmith http://www.blogsmith.com/</generator><item><title><![CDATA[Comments on FCC starts up white spaces database, devices now inevitable]]></title><link>http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</link><guid isPermaLink="true">http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</guid><description><![CDATA[I'm sorry did I hear some1 say  Google Voip through white spaces? O.o]]></description><dc:creator><![CDATA[Shaka]]></dc:creator><pubDate>Dec 1st 2009 6:17AM</pubDate></item><item><title><![CDATA[Comments on FCC starts up white spaces database, devices now inevitable]]></title><link>http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</link><guid isPermaLink="true">http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</guid><description><![CDATA[@Eternity No.]]></description><dc:creator><![CDATA[Kieran]]></dc:creator><pubDate>Dec 1st 2009 6:34AM</pubDate></item><item><title><![CDATA[Comments on FCC starts up white spaces database, devices now inevitable]]></title><link>http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</link><guid isPermaLink="true">http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</guid><description><![CDATA[I just woke up, please bear with me here....]]></description><dc:creator><![CDATA[Shaka]]></dc:creator><pubDate>Dec 1st 2009 7:19AM</pubDate></item><item><title><![CDATA[Comments on FCC starts up white spaces database, devices now inevitable]]></title><link>http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</link><guid isPermaLink="true">http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</guid><description><![CDATA[@Eternity My understanding of Google Voice is that it doesn't use VOIP, it uses regular cellular phone connections augmented by software and a small amount of data.  To receive a call, someone calls your Google Voice number, and Google Voice starts calling all of your phones associated with that number in order to reach you.  If it cannot reach you, it allows the caller to record a voice message which it stores for playback, turns into text to send you a message, etc.  To make a phone call, you initiate the call in the Google Voice application, which makes a phone call to a Google phone line, which routes your call to the number you designated to receive your call.  <br><br>VOIP over cellular data networks doesn't have the quality or consistency to function as well as cellular phone calls.  Google Voice avoids VOIP, to its advantage.  Look at the comment below yours....I do think it's possible for Google Voice to function in white spaces, but I don't really know.]]></description><dc:creator><![CDATA[dennis]]></dc:creator><pubDate>Dec 1st 2009 9:04AM</pubDate></item><item><title><![CDATA[Comments on FCC starts up white spaces database, devices now inevitable]]></title><link>http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</link><guid isPermaLink="true">http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</guid><description><![CDATA[@(Unverified)  <br>That may be true over 3g but I am positive 4G will have better throughput and latency and of-course consistent speed. Also, Google bought Gizmo which uses SIP if I am not mistaken. I expect a major game change in the wireless industry next year after Google has all of it's cards ready to shake the mobile industry.]]></description><dc:creator><![CDATA[Shaka]]></dc:creator><pubDate>Dec 1st 2009 9:09AM</pubDate></item><item><title><![CDATA[Comments on FCC starts up white spaces database, devices now inevitable]]></title><link>http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</link><guid isPermaLink="true">http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</guid><description><![CDATA[@Eternity  <br>4G is being developed to accommodate the QoS and rate requirements set by forthcoming applications like wireless broadband access, Multimedia Messaging Service (MMS), video chat, mobile TV, HDTV content, Digital Video Broadcasting (DVB), minimal services like voice and data, and other services that utilize bandwidth.<br><br>The 4G working group has defined the following as objectives of the 4G wireless communication standard:<br><br>A spectrally efficient system (in bits/s/Hz and bits/s/Hz/site),[1]<br><br>High network capacity: more simultaneous users per cell,[2]<br><br>A nominal data rate of 100 Mbit/s while the client physically moves at high speeds relative to the station, and 1 Gbit/s while client and station are in relatively fixed positions as defined by the ITU-R,[3]<br><br>A data rate of at least 100 Mbit/s between any two points in the world,[3]<br><br>Smooth handoff across heterogeneous networks,[4]<br>Seamless connectivity and global roaming across multiple networks,[5]<br><br>High quality of service for next generation multimedia support (real time audio, high speed data, HDTV video content, mobile TV, etc)[5]<br>Interoperability with existing wireless standards,[6] and<br>An all IP, packet switched network.[5]<br><br>Citations<br>^ "4G - Beyond 2.5G and 3G Wireless Networks". MobileInfo.cm. Retrieved 2007-03-26.<br>^ Jawad Ibrahim (December 2002). "4G Features" (PDF). Bechtel Telecommunications Technical Journal. Retrieved 2009-08-22.<br>^ a b Young Kyun, Kim; Prasad, Ramjee (2006). 4G Roadmap and Emerging Communication Technologies. Artech House 2006. pp. 12–13. ISBN 1-58053-931-9.<br>^ Sadia Hussain, Zara Hamid and Naveed S. Khattak (May 30 - 31, 2006). "Mobility Management Challenges and Issues in 4G Heterogeneous Networks". ACM Proceedings of the first international conference on Integrated internet ad hoc and sensor networks. Retrieved 2007-03-26.<br>^ a b c Werner Mohr (2002). "Mobile Communications Beyond 3G in the Global Context" (PDF). Siemens mobile. Retrieved 2007-03-26.<br>^ Noah Schmitz (March 2005). "The Path To 4G Will Take Many Turns". Wireless Systems Design. Retrieved 2007-03-26.<br><br>yes via wikipedia]]></description><dc:creator><![CDATA[TerrorX]]></dc:creator><pubDate>Dec 1st 2009 9:57AM</pubDate></item><item><title><![CDATA[Comments on FCC starts up white spaces database, devices now inevitable]]></title><link>http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</link><guid isPermaLink="true">http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</guid><description><![CDATA[@TerrorX  <br>+1<br>So ummm yeah.. I CAN'T WAIT! :)]]></description><dc:creator><![CDATA[Shaka]]></dc:creator><pubDate>Dec 1st 2009 12:11PM</pubDate></item><item><title><![CDATA[Comments on FCC starts up white spaces database, devices now inevitable]]></title><link>http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</link><guid isPermaLink="true">http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</guid><description><![CDATA[The Google Phone works on White Spaces for unlimited free wireless Internet and unlimited free Gizmo Google Voice calls.]]></description><dc:creator><![CDATA[Charbax]]></dc:creator><pubDate>Dec 1st 2009 7:49AM</pubDate></item><item><title><![CDATA[Comments on FCC starts up white spaces database, devices now inevitable]]></title><link>http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</link><guid isPermaLink="true">http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</guid><description><![CDATA[Blackberry's need not apply.]]></description><dc:creator><![CDATA[jeff]]></dc:creator><pubDate>Dec 1st 2009 9:20AM</pubDate></item><item><title><![CDATA[Comments on FCC starts up white spaces database, devices now inevitable]]></title><link>http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</link><guid isPermaLink="true">http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</guid><description><![CDATA[Couldn't the WSD just scan the frequencies to find the right one? I don’t really understand why it would need GPS signal and then reference a database? Wouldn’t you already have an established connection to reference the database?  Also if it was just scanning it would be quicker when moving from zone to zone or channel to channel. Sure it would kill the battery faster but it would be easier. Maybe I am just missing something. ]]></description><dc:creator><![CDATA[James]]></dc:creator><pubDate>Dec 1st 2009 10:03AM</pubDate></item><item><title><![CDATA[Comments on FCC starts up white spaces database, devices now inevitable]]></title><link>http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</link><guid isPermaLink="true">http://www.engadget.com/2009/12/01/fcc-starts-up-white-spaces-database-devices-now-inevitable/</guid><description><![CDATA[Wow I used to have that phone a few years ago. The motorola A630 I believe. It was a great little phone. So tiny yet packed a full keyboard on the inside and another numeric keypad on the outside. It was really well built too. Still have it tucked away somewhere and it works perfectly. ]]></description><dc:creator><![CDATA[Ramifications]]></dc:creator><pubDate>Dec 1st 2009 11:40AM</pubDate></item></channel></rss>
