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 : Nokia Corp. (NOK) -- Ignore unavailable to you. Want to Upgrade?


To: 49thMIMOMander who wrote (1618)10/28/2001 3:04:44 PM
From: Eric L  Read Replies (1) | Respond to of 9255
 
re: 1xRTT Synch-Channel Issue in 3GPP2

Nokia problem of course solved but 3GPP2 TSG-C WG2 still bogged down trying to figure out how to get around the problem.

Several other contributions in October but key document here.

ftp://ftp.3gpp2.org/TSGC/Working/TSG-C_0110/TSG-C_0110_CheJu/Plenary/C00-20011015-102 (WGII MTG-Summary(October)).doc

A good contribution by Nortel somewhat explains the root of the issue and some of the complications in resolving it:

ftp://ftp.3gpp2.org/TSGC/Working/TSG-C_0110/TSG-C_0110_CheJu/Plenary/
C00-20011015-102A

This contribution proposes a method to limit the length of the Sync Channel Message (SCHM) in an IS-2000-A system to 27 octets. This is to avoid problems that occur in some IS95 mobiles when the SCHM reaches 28 octets (the so-called “Sync Channel Issue”). In IS-95B, the length of the SCHM is 208 bits. In IS-2000 Release 0, an 11-bit EXT_CDMA_FREQ field was added that extends the Layer 3 PDU beyond 27 octets. In order to limit the length of the SCHM to 27 octets or less and also preserve backward compatibility with Release 0, any solution to the “Sync Channel Issue” requires that the IS-95B style SCHM be transmitted. However, this would result in the omission of Release-0 and Release-A fields that are needed for the mobile to eventually reach the CDMA Frequency where it is expected to idle and monitor the F-CCCH for page messages (henceforth called F-CCCH Frequency). ... Etc.

Many of my fellow Quidiots think its a Motorola is dumb, like Nokia was dumb and Sony was dumb, and they should but Q chips, problem. Motorola is affected but it's more than a Motorola problem. It is a 1xRTT issue, and one that will no doubt only be totally resolved by (God forbid) adapting the standard.

- Eric -



To: 49thMIMOMander who wrote (1618)10/29/2001 3:54:10 PM
From: Eric L  Respond to of 9255
 
re: Meet Bob Brown (CEO of WAP Forum)

>> New WAP Forum CEO Appointed after Long Search

Simon Buckingham
Mobile Streams
24 October 2001

Just over six months since Scott Goldman resigned in April, the WAP Forum has finally appointed a new CEO. Robert "Bob" Brown is now on board. He sent out the following message to members of the WAP Forum today. (Mobile Streams is NOT a member of the WAP Forum, or any other wireless forum due to our position as independent researchers).

"Ladies and Gentlemen of the WAP Forum:

I am delighted to accept the role as the new CEO of the WAP Forum and would like to take this opportunity to introduce myself.

I come to the WAP Forum from the GSM community where, for the past four years, I was the Executive Director, Secretary/Treasurer of the North American GSM Alliance, LLC, focusing on the strategic needs of the North American Operators who utilize the GSM wireless technology platform. In that time, I also served as Regional Chairman of the GSM-NA, with the responsibility of leading the technical working groups from North America, interfacing with the U.S. and international standards bodies and representing North American interests with the international GSM Association.

In my new role as CEO of the WAP Forum, I will provide worldwide oversight and executive management of the forum's organization from my office in Chicago with continued support from the staff at the Mountain View, CA office. I will be responsible for the overall business, as well as coordination and operational aspects of the WAP Forum worldwide, including the day to day operations of the WAP Forum and its staff, consultants, and vendors. I will also be responsible for overseeing the growth and development of the WAP specifications and driving the awareness of WAP technology to the wireless industry worldwide.

I am excited to be involved with the standard that is driving the wireless Internet and I am committed to seeing WAP grow at explosive rates for years to come. The entire industry benefits from WAP and I am proud to have the opportunity to help foster its growth and success.

My first opportunity to meet many of you was at the recent meeting in Bangkok, Thailand, where I had an opportunity to sit in and observe several working group meetings. Needless to say, I was very impressed by all of the dedicated participants and significant work items being addressed.

To those of you whom I haven't met yet, I look forward to meeting you at the upcoming meeting in Berlin, Germany. As we wrap up our work on 2.0, we will be dedicating much of our time at this meeting to focusing on what is next for WAP. This is a great opportunity to submit proposals, participate in the decision process and drive the continuing development and success of the wireless Internet.

Regards,

Robert L. (Bob) Brown." <<

- Eric -