To: Eric L who wrote (2203 ) 4/16/2002 12:10:35 PM From: Eric L Read Replies (1) | Respond to of 9255 re: No Sync on Sync Channel for cdma2000 1xRTT Release A From: SC Draft Meeting Report - March 18, 2002 - Wailea (Maui), Hawaii >> Sync Channel Ad Hoc report Mr. Akira Matsunaga (KDDI), Chair of the 3GPP2 Sync Channel Ad Hoc Group, presented the report of the group's activities as contained in contribution SC-20020318-012. Mr. Matsunaga highlighted that three standards-based solutions had been proposed. During the course of the Ad Hoc's discussions, a consolidated standards-based proposal was agreed upon. However, the Ad Hoc was not able to reach consensus on whether the solution to the sync channel issue should be standards-based or not. Consequently, the Ad Hoc had no recommendation for TSG-C. It was clarified by the Sync Channel Ad Hoc Chair that Ad Hoc discussions had been limited to standards-based solutions. Non-standards based solutions were considered beyond the scope of 3GPP2 and therefore, not discussed within the Ad Hoc. The Ad Hoc requested guidance from the SC on how to proceed on this item. Discussion yielded the following recommendation, which was approved by the Steering Committee without objection. * ACTION 2002/03-01 . TSG-C is to proceed w/rev A Addendum 3 text based on the evaluation information provided in the Sync Channel ad hoc report (Contributions SC-20020318-012, 12A, 12B) and that TSG-C will complete a Revision A addendum 3 text by their closing plenary on April 19. . The Sync Channel ad hoc will convene on or before Sunday, May 12 to reach consensus on whether or not a specification change is required to resolve the synch channel issue. Based on their findings they are to deliver their conclusions to the opening plenary of TSG-C on May 13. . If the findings of the Sync Channel ad hoc are inconclusive, then TSG-C is instructed to proceed forward with release of Revision A Addendum 3 Sync channel fix by May 17 2002. << CDG follow on to the above is March 26, 2002 letter from Sam Samra of CDG to Steve Dennett, 3GPP2 Steering Committee Chairman: >> The CDG Executive Board and Leadership Council on March 18th agreed unanimously to facilitate discussions among carriers and vendors who are members of CDG to explore the possibility of a work around solution to the sync channel message problem. This decision was made to assist the industry to move forward since 3GPP2 by its charter is unable to entertain detailed discussions on non standards based solution to fix this problem. We are convening a face-to-face CDG Synch Channel meeting on Tuesday, April 2 in Toronto to address this issue. The objective of the meeting is to share available information openly among CDG carriers, infrastructure providers, and handset manufacturers, to fully assess the pros and cons of workaround proposals and explore the acceptability of these solutions in fixing the problem without changing the current Release A specifications. The scope of the discussions will be limited to whether carriers have consensus in accepting a work around solution instead of specification fix. CDG has no intention of submitting any agreed workaround solution to 3GPP2 for future adoption by 3GPP2. From the feedback CDG received from the SC meeting in Maui on March 18, 2002, we understand that the Sync Channel Ad Hoc will be meeting on, or before May 12, 2002. We will certainly make every effort to provide input at this meeting. Our intention is not to make or circumvent the decision making authority of 3GPP2, we will be simply bringing in our recommendations as an MRP to move this process along for the good of the CDMA2000 industry. << April 2 has of course come and gone but I have no feedback yet on what resulted. Addendum 3 dates back to the Qualcomm proposal of last November. It is rather unfortunate, IMO, that the Korean carriers and vendors continue to stymie this since even if development is underway on Release A, there is development to be done (first on the standard then on the network) based around Addendum 3 if it is adopted, that can only delay implementation in USA. - Eric -