throbber
2/21/2020
`
`802.11n deal imminent, says Broadcom exec | EE Times
`
`
`
`
`
`DESIGNLINES
`
`| WIRELESS AND
`NETWORKING
`ttps://www.eetimes.com/designline/wireless-
`and-networking-designline/>
`DESIGNLINE
`802.11n deal imminent, says Broadcom exec
`
`<h
`
`By EETimes < https://www.eetimes.com/author/eetimes/> 10.03.2005
`
` 0
`
`
`MADRID, Spain – The logjam that has delayed agreement on the IEEE 802.11n high data-
`rate WLAN standard will be broken soon, and a standard agreed by the middle of next
`year, a senior executive from Broadcom Corp. told the World Broadband Forum.
`
`Michael Hurlston, vice president of the communications chip company’s wireless and home
`networking business unit, also suggested there would be interoperable products on the
`market soon after.
`
`Speaking to EE Times after the session comparing different technologies that are vying for
`distributing video over home networks – such as powerline, Home PNA, coax and Wi-Fi,
`Hurlston said the standardization effort is “plagued by difficult issues and far too much
`politics”, but said Broadcom is optimistic discussions between the competing groups,
`WWiSE and TGn Sync would come up with a solution.
`
`“If people go off and develop a subset of the standard outside of the IEEE 802.11 working
`groups, the end game would be to bring back such as splinter group into the fold,” said
`Hurlston.
`
`He was referring to suggestions that Intel Corp, Atheros Communications Inc and Marvell
`Semiconductors, and including Broadcom itself, have linked on an interoperable physical
`and media access controller layer and plan to submit this to the IEEE by November.
`
`This move has angered several of the task groups members.
`
`RELATED ARTICLES
`
`
`
`https://www.eetimes.com/802-11n-deal-imminent-says-broadcom-exec/
`
`1/2
`
`
`
`Bell Northern Research, LLC, Exhibit 2009, Page 1 of 1
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket