Qualcomm Moderated Thread - please read rules before posting Message Board

STOCKTALK

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 : Qualcomm Moderated Thread - please read rules before posting

QCOM 172.72

-4.4%

Nov 4 3:59 PM EST

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Ramsey Su who started this subject	2/2/2002 9:08:47 AM
From: foundation	Read Replies (1) of 196444

Sync Channel Update ------- There were more documents added to the January 24 Steering Committee Meeting in Seoul: ftp://ftp.3gpp2.org/SC_OP/Working/SC_OP-0201/SC-20020124_Seoul ========== Final posted draft of the Steering Committee Sync Channel Ad Hoc Proposal: The SC agreed for the Synch Channel issue that; 1. The resolution shall maintain a single specification. 2. The resolution if it requires such a specification change shall be available by March 15 for inclusion in Rec. ITU-R M.1457 revision input. In order to achieve this goal, the SC agreed the following approach; 1. TSG-C to release, without Synch Channel fix, Release A Addendum and Release B in Seattle meeting.* 2. To establish an AHG in SC to find the solution based on the requirements set by the SC below. 3. The AHG to identify the solution and agree to it based on the consensus. 4. Once the AHG reached the consensus, the AHG shall submit the solution to TSG-C for approval according to 3GPP2 procedures. Ad hoc requirements 1. A single specification such that a Release A compliant mobile is interoperable with Release A and all prior standards compliant infrastructure. 2. Resolve the Sync Channel Issue such that there is no impact to currently deployed (i.e., Release 0 or IS-95) equipment (MSs and Infrastructure). ftp://ftp.3gpp2.org/SC_OP/Working/SC_OP-0201/SC-20020124_Seoul /SC-20020124-027r4_Ad%20hoc%20proposal.doc ========== Korean (including Samsung) position: ftp://ftp.3gpp2.org/SC_OP/Working/SC_OP-0201/SC-20020124_Seoul /SC-20020124-023_synch%20channel%20issues.doc ========== KDDI position: ftp://ftp.3gpp2.org/SC_OP/Working/SC_OP-0201/SC-20020124_Seoul /SC-20020124-025_KDDI_SyncCH_resolution.doc ========== MOT and NOK Position: ftp://ftp.3gpp2.org/SC_OP/Working/SC_OP-0201/SC-20020124_Seoul /SC-20020124-026R1_MOT-NOK_prop_Solution_to%20proceed_synch_chan_fixes.doc ========== CDG report - discusses sub numbers, events, etc: ftp://ftp.3gpp2.org/SC_OP/Working/SC_OP-0201/SC-20020124_Seoul /SC-20020124-022_CDG_3GPP2-report.doc ========== My observation of Sync Channel issue: There appears to be little appetite for fragmenting the specification with a regional fix ---- beyond MOT and NOK. It appears that the parties who were holding Release A hostage to a sync channel fix have lost. Agreement on a fix does not appear possible now... and I can't see how the stringent Ad Hoc requirements make a agreement on a patch any more likely by March... This victory can only embolden members who wish to leave the standard - that was not the cause of the problem - alone, without modification... In my view, a recall of non-standard-compliant handsets has become more likely. :-) * Seattle meeting is from February 4 through 8... 307kbs here we come!

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next