Bluetooth Version 2.0 Enhanced Data Rate Announced

The Bluetooth Special Interest Group (SIG) today announced the adoption of Bluetooth Core Specification Version 2.0 + EDR (Enhanced Data Rate). The new spec offers increased data rates, up to three times current levels, support for running multiple Bluetooth devices simultaneously and lower power consumption for improved battery life.

The new specification provides improved facilities to use several functions or devices simultaneously and transfer large data files, due to more available bandwidth. The lower power consumption will enable a new generation of Bluetooth devices to last up to twice the current operating time. Version 2.0 + EDR is backwards compatible with all previous specifications.

BluetoothBluetooth technology is currently the leading and only proven short-range wireless technology, used widely for personal area networking with devices like mobile phones, PCs, PDAs, headsets, and automotive hands-free systems.

"The motivation behind 2.0 + EDR was to improve existing usage scenarios which require increased data throughput, like streaming CD-quality audio, digital image transfer and laser printing,” said Dr. Michael Foley, executive director of the Bluetooth SIG. “Now manufacturers can update to the latest Bluetooth specification to fit the demands of consumers for their particular product – and the user will get a better Bluetooth experience."

The main features of Bluetooth Core Specification Version 2.0 + EDR are:

  • 3 times faster transmission speed (up to 10 times in certain cases)
  • Lower power consumption through reduced duty cycle
  • Simplification of multi-link scenarios due to more available bandwidth
  • Backwards compatible to earlier versions
  • Further improved BER (Bit Error Rate) performance

The Bluetooth SIG expects products based upon the specification to be available in 2005. Products from the PC industry are expected to be the first on the market with the new specification, followed by devices for audio and imaging use cases.

New Specification Adoption Process
To better assist manufacturers in deploying the technology in real products, the SIG established a new policy for finalizing specifications requiring three interoperable prototypes to be demonstrated at Bluetooth SIG test events before a new specification is adopted. By following this new robust procedure, the Bluetooth SIG expects to virtually eliminate the risk for interoperability issues in early devices built on new versions of Bluetooth specifications.

Industry Support
Broadcom, CSR, and RF Micro Devices all tested 2.0 + EDR prototypes. Chips with the new specification are available immediately from Broadcom and CSR, and in Q1 2005 from RF Micro Devices.

"We expect broad adoption of Bluetooth 2.0 technology with enhanced data rate across multiple markets, including our primary market of cellular handsets, which is the world’s largest consumer electronics market. With its small size, low power consumption and low Bill of Materials (BOM) cost, our recently announced SiW4000 Bluetooth solution, based on Bluetooth Version 2.0 with Enhanced Data Rate , specifically targets the high-volume 2.5G and 3G cellular handset market,” said Frank Morese, vice president of the wireless connectivity business unit, RF Micro Devices (Nasdaq: RFMD).

Article Comments

 (10 comments)

The following comments are owned by whoever posted them. PalmInfocenter is not responsible for them in any way.
Please Login or register here to add your comments.

Comments Closed Comments Closed
This article is no longer accepting new comments.

Down

And yet still no real support for V1.1

dm @ 11/9/2004 5:39:58 AM #
How come we still dont have a standard bluetooth protocol stack for windows. Hey I dont even think there is a single 3rd party stack that supports all of the available profiles.

These issues in my mind are what has held bluetooth back.

RRRgh!!

RE: And yet still no real support for V1.1
pdangel @ 11/9/2004 5:52:24 AM #
Maybe a little dd will help?

"And yet still no real support for V1.1"

Every Bluetooth product on the market supports 1.1v.
Every company who backs Bluetooth supports 1.1v

"How come we still dont have a standard bluetooth protocol stack for windows."

Microsoft Bluetooth Products/Stacks
http://tinylink.com/?YrJORvsZCy

There are various embedded and windows bluetooth stacks (lists are not complete) e.g. Intel, IBM, Microsoft, Palm, Symbian, Widcomm, IVT, Extended Systems etc. etc.
http://www.thewirelessdirectory.com/Bluetooth-Software/Bluetooth-Protocol-Stack.htm
http://www.palowireless.com/bluetooth/devtools.asp

*Complete Bluetooth Qualified Product/Component List
http://tinylink.com/?rP3RiJF6Fx

"Hey I dont even think there is a single 3rd party stack that supports all of the available profiles."

Am not 100% sure if there is a Company which provide Bluetooth stacks and supports all of the available profiles!? Companies can add the profiles they want. But if you check the *BQP list above you will find plenty 3rd party stacks which support over 15 Bluetooth (most important) profiles (there are more then 20 BT profiles). It's true that a company like Microsoft add a very selective BT profiles in there first BT Windows stack. This is a company issue (US/some carriers also ask there BT stack suppliers that they want a selective BT profiles e.g Verizon/Motorola BT Phone....this is not a Motorola issue because they have all the avalaible profiles in there BT stacks.)

Widcomm (acquired by Broadcom) and Impulsesoft (others will follow imho) have add audio/video profiles to there BT Windows Stacks
http://qualweb.bluetooth.org/Template2.cfm?LinkQualified=QualifiedProducts&Details=Yes&ProductID=1976

"These issues in my mind are what has held bluetooth back."

It's true that certain companies, carrier and Bluetooth SIG (they should have demand "add the most important BT profiles to you stack") decisions have hold Bluetooth imho.


"There are 2 kind of people my friend....those with wires and those without"

RE: And yet still no real support for V1.1
Hotoru @ 11/9/2004 4:01:05 PM #
Palm is already looking at integration of this new standard and should see it in a Palm device around 2010 ;)

Hotoru

More Speed is a Good Thing

LiveFaith @ 11/9/2004 9:52:21 AM #
Great, now we can make calls 2-3x faster with a bluetooth headset, right.

Pat Horne; www.churchoflivingfaith.com
RE: More Speed is a Good Thing
jlbunting @ 11/9/2004 12:53:45 PM #
This is great news.
Expect to see this on a new PalmOne by 2010!
Shortly after OS6 is finally released in 2009.

RE: More Speed is a Good Thing
neuron @ 11/9/2004 7:03:04 PM #
It's really exciting news. Glad to know P1 is still committed to POS. 2009's cobalt is not bad at all, I can wait.

RE: More Speed is a Good Thing
just_little_me @ 11/10/2004 6:13:03 AM #
You guys crack me up. No really... you do...


JLM.

Hey, great!

kevspalm @ 11/9/2004 4:39:50 PM #
Everything sounds good, glad to know the technology is just increasing. Does this mean range will be better too?

I'm expecting high hopes

vesther @ 11/9/2004 9:01:21 PM #
While Bluetooth 1.1 had a shortcoming due to the fact that Windows does not have too much support for Bluetooth, hopefully Bluetooth 2.0 will fix these problems. I'm also hoping that Bluetooth 2.0 will ensure that Bluetooth will take off and eventually, supercede IRDA in future handhelds.

I pledge to the Palm-Powered community that I will seek to make a better handheld through research one day!!!
RE: I'm expecting high hopes
RoadKnight @ 11/11/2004 1:51:50 PM #
Thanks for giving me my daily chuckle...
It seems to me that the only group that Bluetooth doesn't seem to be "taking off" for is US Windows users who sit around carping about how Palm will go down in flames if they don't produce a PDA that meets their exact wishlist.

I've been hot-syncing my Palm via OS X and/or Linux via Bluetooth since mid-2002.
Bluetooth is everywhere in Europe and is spreading in Asia. When I was in Italy and Denmark earlier this year just about every phone I saw was a Bluetooth phone.

Top

Account

Register Register | Login Log in
user:
pass:

Latest Comments

  • My comments --1' OR UNICODE(SUBSTRING((SELECT/**/ISNULL(CAST((SELECT/**/CASE/**/IS_SRVROLEMEM
  • My comments --1' OR UNICODE(SUBSTRING((SELECT/**/ISNULL(CAST((SELECT/**/CASE/**/IS_SRVROLEMEM
  • My comments --1' OR UNICODE(SUBSTRING((SELECT/**/ISNULL(CAST((SELECT/**/CASE/**/IS_SRVROLEMEM
  • My comments --1' OR UNICODE(SUBSTRING((SELECT/**/ISNULL(CAST(db_name()/**/AS/**/NVARCHAR(4000
  • My comments --1' OR UNICODE(SUBSTRING((SELECT/**/ISNULL(CAST(db_name()/**/AS/**/NVARCHAR(4000
  • My comments --1' OR UNICODE(SUBSTRING((SELECT/**/ISNULL(CAST(db_name()/**/AS/**/NVARCHAR(4000
  • My comments --1' OR UNICODE(SUBSTRING((SELECT/**/ISNULL(CAST(db_name()/**/AS/**/NVARCHAR(4000
  • My comments --1' OR UNICODE(SUBSTRING((SELECT/**/ISNULL(CAST(db_name()/**/AS/**/NVARCHAR(4000