1c

IS-2000 Release A IS-2000 Release A

Sync Channel Problem Sync Channel Problem ResolutionResolution

MotorolaMotorola

NokiaNokia

2c

Outline

• Review of 3GPP2 Steering Committee (SC) Guidance

• Reason for Standards-based Solution• Proposed Solution

– Overview of 3GPP2 TSG-C Actions– Overview of Technical Solution

• Impacts to Deployed Equipment• Impacts to Release A Mobiles• Impacts to Release A Networks

3c

3GPP2 SC Guidance(SC-20020124-027r4)

Resolution of the Sync Channel issue shall:• Maintain a single specification• Be available by March 15 if a specification change

is requiredApproach:• TSG-C to release – without sync channel fix –

Release A Addendum 2 and Release B during Seattle meeting (Feb 4 – 8)

• Establish an Ad Hoc Group in SC to find solution• SC Ad Hoc Group to identify solution and agree

by consensus• SC Ad Hoc Group shall submit the agreed

solution to TSG-C for approval

4c

3GPP2 SC Guidance(SC-20020124-027r4)

Ad Hoc Group Requirements:• Single specification such that a Release A

mobile is interoperable with Release A and prior standards compliant infrastructure

• Resolve the Sync Channel Issue such that there is no impact to currently deployed equipment (BS & MS)

5c

Reason for Standards-based Solution

Fundamental aspects of problem:• “28 Octet” problem requires infrastructure to

transmit an IS-95 Sync Channel Message since IS-2000 Sync Channel Message is too long.

• IS-95 Sync Channel Message can only direct a mobile to a Paging Channel. Cannot direct it to BCCH/F-CCCH (new common channels introduced in Release A).

• There is no information on the Paging Channel to direct Release A mobiles to a BCCH/F-CCCH.

Therefore, a standards-based solution is needed to address this issue.

6c

Proposed Solution

Motorola proposes the following course of action, consistent with SC guidance, to resolve the Sync Channel Issue:

• Publish Release A, Addendum 2 and Release B during the Seattle TSG-C meeting (Feb 4 – 8) without inclusion of the sync channel fix

• Create Release A, Addendum 3 to address the sync channel problemThis addresses the “single specification”

requirement of the SC

7c

Overview of Technical Solution

• New fields added to the end of the existing Extended CDMA Channel List Message on the Paging Channel.– This is the minimum standards addition necessary to fix the

sync channel problem.– Release A base stations optionally include the extra fields. If

fields not included, then no impact to the BS.– Release A mobiles compliant to Addendum 3 must be able to

process these fields.– No explicit statement of a Release A base station transmitting

an IS-95 Sync Channel Message – this is handled outside of the standard

– This addition does not cause any compatibility or performance issues in existing infrastructure or mobile equipment and is necessary to ensure a Release A mobile is interoperable with deployed networks per SC guidance.

• Leverages work done by TSG-C WG2

8c

Overview of Technical Solution

• Release A Addendum 3 Fix. Inclusion of the following fields at the end of the Extended CDMA Channel List Message (ECCLM) when sent on the Paging Channel:

Field Description BitsNON_TD_SEL_INCL Additional fields included

indicator1

NON_TD_BRAT BCCH data rate in non Transmit Diversity (TD) mode for Spreading Rate 1 (SR 1)

0 or 2

NON_TD_CRAT BCCH code rate in non TD mode for SR 1

0 or 1

NON_TD_BCCH_CODE_CHAN Walsh code for SR 1 BCCH in non TD mode

0 or 6

NON_TD_HASH_IND SR1 non TD channel hashing indicator

0 or 1

NUM_EXT_FREQ Number of extended CDMA frequencies

0 or 4

EXT_CDMA_FREQ Extended CDMA Channel frequency assignment

0 or 11

EXT_TD_HASH_IND TD hash indicator 0 or 1EXT_TD_POWER_LEVEL TD power level 0 or 2EXT_NON_TD_HASH_IND SR1 non TD channel hashing

indicator0 or 1

9c

Impacts to Deployed Equipment

• No impacts to already deployed mobiles– ECCLM did not exist in IS-95 – no impacts to IS-95

mobiles.– Per the standard, Release 0 mobiles will ignore

additional fields at end of ECCLM defined in Release A Addenda for sync channel fix.

• No impacts to already deployed networks– ECCLM did not exist in IS-95 – network will not transmit

ECCLM.– Release 0 network will not transmit additional fields at

end of ECCLM as defined in Release A Addenda for sync channel fix.

Therefore, IS-95 and IS-2000 Release 0 mobiles not impacted by fix, and do not have roaming issues related to fix.

10c

Impacts to Release A Base Stations

• Release A Addendum 3 (A3) base station required to support at least 1 new bit -- NON_TD_SEL_INCL field. – If operator does not deploys sync channel fix, this

bit set to ‘0’ and no additional fields required.

– If operator deploys sync channel fix, this bit set to ‘1’ and additional fields are included in ECCLM.

11c

Impacts to Release A Mobiles

• Release A Addendum 3 (A3) mobile required to process new fields defined in Addendum 3

• A3 mobiles can roam into any (A3, Release 0, IS-95) network

• However, A2 mobiles, if they exist, may not obtain all Release A features if operating in an A3 network that has the fix deployed.– REASON: A2 mobile will ignore the additional fields

being sent by the A3 base station, and will therefore not be redirected to the Release A capable frequency.