Nokia Corp. (NOK) 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 : Nokia Corp. (NOK)

NOK 6.910

-0.9%

3:59 PM EST

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Eric L who wrote (2009)	2/16/2002 9:38:29 AM
From: Eric L	Read Replies (1) of 9255

re: 3GPP2 Sync Channel Seattle AdHoc on February 6 & 7, 2002 Two day meeting summary: ftp://ftp.3gpp2.org/SC_OP/Working/Sync_Channel_0202/scsyncchannel_20020213/SC-SCAH-20020213-002A__SC_SCAH_MtgSum-020205-marked.pdf Essentially a new addendum (Addendum 3) to Release A is being considered. Initially the "sync channel" fix was proposed for inclusion in Addendum 2. >> * A contribution on IS-2000 Release A Sync Channel problem resolution (SC-SCAH-20020204- 005AR1) was presented from Motorola and Nokia. This contribution provided the following information: • Fundamental aspect of the problem is that mobiles with the Sync Channel problem cannot receive any Sync Channel message over 27 octets including the IS-2000 Sync Channel message. • Motorola and Nokia believe that a standards-base solution is required. • A new revision to Release A is proposed to implement the Sync Channel fix. • The technical solution is to add some new fields to the end of the existing Extended CDMA Channel List Message on the Paging Channel. • Impacts to deployed equipment: - No impact to deployed mobiles including IS-95 and Release 0 - No impact to deployed networks - Release A Addendum 3 base stations will need to support a NON_TD_SEL_INCL bit to indicate whether or not the Sync Channel fix is deployed on that system - Release A Addendum 3 mobiles will need to process new fields - Release A Addendum 2 mobiles (if deployed) may not obtain all Release A features when operating in a Release A Addendum 3 network where the fix has been deployed. << Also: >> The discussion noted that this proposal was a subset of the proposal that had been previously reviewed by TSG-C WG2. Removed from the WG2 proposal were enhancements that would mitigate system performance degradation problems, and text related to transmitting an IS95-style Sync Channel Message. The Layer 3 text required to implement this proposal was included as an attachment to this proposal (SC--SCAH-20020204005BR1). A WG2 representative estimated that the schedule for publishing Release A Addendum 3 was three (3) months. Since the same change must also be incorporated into Release B and the text integration for both of those releases would have a higher priority than the Release C effort. Motorola agreed that they would make sure that an alternate proposal for consideration by the AdHoc that will include their simplified proposal (-005AR1) plus the enhancements to mitigate system performance degradation problems. That proposal will be accompanied by performance analysis data. A contribution on the Analysis of impact on the MS and infrastructure caused by the sync channel issue (SC-SCAH-20020204-006) was presented by KDDI. This contribution identified four (4) symptoms (S0 through S3) that would be evident for mobiles that included the Sync Channel fix previously developed by TSG-C WG2. This contribution was left open for additional review on a conference call next week to determine if these issues are related to the Sync Channel problem. SCHEDULE: An updated proposal for the Sync Channel resolution schedule (SC-SCAH-20020204-003) was presented by KDDI. This contribution was adopted without objection. LGE, Motorola, And Samsung are working together on "Suggested Guidelines for Sync Channel Resolution Timeline" (3GPP2-C00-20020204-004) which is positive: Ø A Standards approach for the Sync Channel issue will be utilized if a acceptable non-standards solution is not selected Ø All proposals will be evaluated for meeting the requirements as specified by the Steering Committee. Ø February 22 is the deadline for all Sync channel proposals to be submitted to the Ad-Hoc in order to be considered Ø The Ad-Hoc is encouraged to reach a Sync Channel Resolution by March 8th Ø If a standards approach is selected, the Ad-Hoc is encouraged to have drop-in text available and submitted to the appropriate TSG’s on March 11, and no later than March 15 << Latest Motorola & Nokia proposal (SC-SCAH-20020205-005B(MOTproposal-L3_text)-R1.doc) here: ftp://ftp.3gpp2.org/SC_OP/Working/Sync_Channel_0202/scsyncchannel_20020205/ - Eric -

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next