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)
NOK 5.935+1.1%Nov 21 9:30 AM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: 49thMIMOMander who wrote (1618)10/28/2001 3:04:44 PM
From: Eric L  Read Replies (1) 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 -
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext