EV DO System Messages 20050106 a 1.0

EV-DO System Messages Internal open

Document

number

Product

name

Applicabl

e for

Product

version

Drafted byCDMA Network Planning

Department

Document

version

EV-DO System Messages

Prepared

by: Zeng Shuhui Date:

Reviewed

by: Date:

Reviewed

by: Date:

Approved

by: Date:

2005-01-311 All rights reserved Page i of total 16


Huawei Technologies Co., Ltd.

All rights reserved

2005-01-311 All rights reserved Page ii of total 16


Revision record

DateRevision

versionDescription Author

2004.1.15 V1.00 First draft completed Zeng Shuhui

2004.3.3 V1.01 Revision completed Nie Jimin

2004.12.1 V1.02 Revision completed Nie Jimin

2005-01-311 All rights reserved Page iii of total 16

EV-DO System Messages Confidentiality

Table of Contents

EV-DO System Messages..........................................................................................................2

1.1 Introduction to System Messages.......................................................................................2

1.2 QuickConfig Message.........................................................................................................3

1.3 SectorParameters Message................................................................................................4

1.4 Sync Message..................................................................................................................... 7

1.5 AccessParameters Message...............................................................................................8

1.6 Redirect Message...............................................................................................................9

1.7 BroadcastReverseRateLimit Message..............................................................................10



Key words:

Abstract: This document introduces EV-DO system messages and details field

meaning of different messages.

List of acronyms and abbreviations:

List of references:

1. Air Interface Specifications on CDMA2000 High Rate Packet Data Qualcomm

2. RF Engineering Guideline for 1xEV-DOSystem Lucent

3. CBSC6600V200R001 Top Design—System Messages Huawei



EV-DO System Messages

1.1 Introduction to System Messages

This document introduces 1xEV-DO system messages. In the protocol,

overhead messages include QuickConfig and SectorParameters messages

only. In addition, there are other four types of message, namely, Sync.,

AccessParameters, BroadcastReverseRateLimit and Redirect messages

that are also sent on the control channel to control behavior of all terminals.

All the six messages are called system message and are sent through the

same mechanism at the BSC.

System messages are sent based on different periods shown in the

following table.

Table 1. Broadcast Parameters for System Messages

System message Broadcast frequency Sending

channel

Sync Once within TISPSync seconds CCsyn

QuickConfig Once at every CC CCsynSS

SectorParameters Once within NOMPSectorParameters

CC periods

CCsyn

AcessParameters Once within NACMPAccessParameters

slots

CCsyn

BroadcastReverseRateLimit Triggered by events and sent

in a non-period mode

CC

Redirect Triggered by events and sent

in a non-period mode

CC and

FTC

Where,

- FTC stands for forward traffic channel or control channel when the route

update protocol is in connection state.

- CC stands for control channel (synchronous or asynchronous packets)

- CCsyn stands for control channel synchronous packets (including

synchronous dormant packets of control channel).

2005-01-31 All rights reserved Page 2 of total 16


- CcsynSS stands for control channel synchronous dormant packets.

- AC stands for access channel.

SYNC message: sent once within TISPSync seconds at the BTS (TISPSync is

defaulted to 1.28 seconds, namely, three CC periods and each of them is

256 slot= 426.67ms)

QuickConfig message: sent once within each CC period at the BTS.

SectorParameter message: sent once within NOMPSectorParameters (defaulted to

four) CC periods at the BTS.

AccessParameter message: sent once within NACMPAccessParameters (defaulted to

3) CC periods at the BTS.

BroadcastReverseRateLimit message: used to restrict reverse peak rate of

all users at the local carrier. This message is triggered by events.

Redirect message: used to redirect terminals to other networks and

triggered by events. This message can be sent on the CC and all terminals

(including connected and disconnected terminals) under this carrier are

redirected to other networks. It can be also sent on the FTC and only one

specific terminal will be redirected to other networks.

1.2 QuickConfig Message

QuickConfig message and SectorParameters message are called

overhead message. The AN broadcasts these messages on the CC. They

are unique and should be specified because they belong to multiple

protocols. The overhead message protocol provides relevant processes to

transfer, receive and monitor these messages.

The access terminal (hereinafter referred as AT) should contain one

QuickConfig message in every CcsynSS. The access network (hereinafter

referred as AN) contains at least one SectorParameters message every

NOMPSectorParameters CC periods. In addition, the AN should set the

SectorSignature domain of the QuickConfig message to the

SectorSignature domain of the next SectorParameters Message, and the

AccessSignature domain of the QuickConfig message to AccessSignature

of public data.

In the active state, the AT should monitor QuickConfig and

SectorParameters messages.



QuickConfig message is to reflect the change of the overhead message

and provide information on frequent change. Every CcsynSS in the AT

contains one QuickConfig message.

Table 1-1 Fields in the QuickConfig Message

Domain name Length Description

MessageID 8 /

ColorCode 8 Color code corresponding to a sector

SectorID24 24 Low 24-digit bit in the SectorID corresponding to a sector

SectorSignature 16 Sector signature value of the next SectorParameters message to be sent by the AN

AccessSignature 16 Access signature value of the next AccessParameters message to be sent by the AN

Redirect 1 Redirection. If the AN redirects all terminals to be away this AN, set this domain to “1”.

RPCCount 6 Maximum RPC channels supported by the sector

The following domains occurs for RPCCount times

ForwardTrafficValid

1 The AT monitors the FTC through this domain. If the FTC with 64-n MACIndex is valid, the AN sets value n of this domain to “1”. Otherwise, “0” should be set.

Reserved Changeable

Used to ensure the length of this message is integer times of fields. Set this domain to “0” if it exists.

1.3 SectorParameters Message

The AT should select one CDMA channel from the channel list of the

SectorParameters message if there is. Otherwise, the AT should adopt the



channel that it is monitoring. If one or multiple channels are available, the

AT should use the Halsh function to calculate index number of the channel

list provided by this type of message.

Before sending an access probe, the AT must ensure the current

SectorParameters message is up to date, which can be known by verifying

whether SectorSignature values in the QuickConfig message and latest

SectorParameters message are the same.

The AN should have at least one SectorParameters message in the

synchronous packet every OMPSectorParameters (defaulted to 4) CC periods. The

SectorParameters message is used to transfer specific sector messages to

the AT.

Table 1-2 Fields in the SectorParameters Message


MessageID 8 /

CountryCode 12 Mobile country code

SectorID 128 Sector address identifier

SubnetMask 8 Subnet mask identifier of a sector, namely, the number of continuous “1” in the subnet mask

SectorSignature 16 SectorParameters signature (sequence number of the message)

Latitude 22 Latitude of the sector

Longtitude 23 Longitude of the sector

RouteUpdateRadius 11 0: The sector does not perform distance-based route update.

Non-0: Message The AT will send a new RouteUpdate message beyond this distance

LeapSeconds 8 Times of leap second after the system time starts.

LocalTimeOffset 11 Difference between the local time and the system time

ReverseLinkSilenceDuration 2 Unit: frame, duration between reverse link silent sectors

ReverseLinkSilencePeriod 2 Period between reverse link silent sectors. It is defined as the time interval of the frame which is started at T time and lasts ReverseLinkSilenceDuration. T is CDMA system time with the



frame as the unit and satisfies:

T mod (2048×2ReverseLinkSilencePeriod-1)=0

ChannelCount 5 Channels under this sectors, available to the AT

The following domains occur for ChannelCount times:

Channel 24 Channel number including SystemType, BandClass and ChannelNumber

NeighborCount 5 Neighbor sectors

The following domains occur for NeighborCount times:

NeighborPilotPN 9 PN of neighbor sectors

The following two domains occur for NeighborCount times:

NeighborChannelIncluded 1 If the channel record of this neighbor sector is included, the AN sets this domain to “1”. Otherwise, “0” should be set.

NeighborChannel 0 or 24 Description of neighbor channel record, including SystemType, BandClass and ChannelNumber

NeighborSearchWindowsSizeIncluded 1 If the search window record of this neighbor sector is included, the AN sets this domain to “1”. Otherwise, “0” should be set.


NeighborSearchWindowsSize 0 or 4 Search window size used by neighbor pilots

NeighborSearchWindowsOffsetIncluded

1 If the search window offset used by this neighbor pilot is included, the AN sets this domain to “1”. Otherwise, “0” should be set.


NeighborSearchWindowsOffset 0 or 3 Search window offset used by neighbor pilots

Reserved Changeable




Table 1-3 Search Window Size

SearchWindowSize value

Search window size (PN chip)

0 4

1 6

2 8

3 10

4 14

5 20

6 28

7 40

8 60

9 80

10 100

11 130

12 160

13 226

14 320

15 452

Table 1-4 Search Window Offset

SearchWindowsOffset value

Offset (PN chip)

0 0

1 WindowSize34/2

2 WindowSize

3 3×WindowSize/2

4 -WindowSize/2

5 -WindowSize

6 -3×WindowSize/2

7 Reserved

1.4 Sync Message

The AT receives Sync message in the synchronous state. In this state, the

AT should send ControlChannelMAC.Deactivate command and enter



network confirmation state if it does not successfully receive the Sync

message within TISPSyncAcq. When attempting to receive this Sync message,

the AT will discard other all messages on the CC. After receiving one Sync

message, the AT should compare the largest and the smallest version

number. If the version number is beyond the specified range, the AT will

send ControlChannelMAC.Deactivate command and enter network

confirmation state. Otherwise, perform time synchronization and return

NetworkAcquired instruction to enter non-active state. Syn message is

similar to syn channels in 1x.

The AN periodically broadcasts Syn message in the synchronous CC

packet to transfer basic network and timing messages. Note that this

should not exceed TISPSync (defaulted to three CC periods, 1.28s).

Table 1-5 Fields in the Sync Message

Domain name Length

Description

MessageID 2 /

MaximumRevision

8 Maximum air interface protocol version supported by the AN

MinimumRevision

8 Minimum revision air interface protocol version supported by the AN

PilotPN 9 PN offset of sector pilots

SystemTime 37 The system time 160ms after the period of the CC to which this Sync message is sent starts. The unit of this system time is 26.667ms.

1.5 AccessParameters Message

AccessParameters message is used to transfer AccessChannel message

to the AT. Before sending the first probe in the first probe sequence, the AT

should verify whether the AccessParameters message is up to date. If it is

not, start TACMPAPSupervision monitoring timer to update access parameters.

The AN sends at least one AccessParameters message within

NACMPAccessParameter (defaulted to three CC periods, namely, 3×256=768) slots.

Table 1-6 Fields in the AccessParameters Message


MessageID 8 /

AccessCycleDuration

8 Time the access channel period lasts; and its unit is slot.



AccessSignature 16 Signature of the AccessParameters message

OpenLoopAdjust 8 Negative of nominal power used by the AT to estimate open loop power, expressed as a 1dB value without any sign.

ProbeInitialAdjust 5 Correction factor adopted by the AT to initially perform transmission on the access channel during open loop power estimation

ProbeNumStep 4 Maximum probe numbers that can be accessed and are transmitted by the AT in the single access probe sequence. The value range is [1, 15].

PowerStep 4 Probe power increment

PreambleLength 3 Frame length of access probe preamble

CapsuleLengthMax 4 The length of the largest access channel packet. The value range is [2, 15] and its unit is frame.

The following domains occur for NACMPAPersist times:

APersistence 6 Access persistence vector

0x3F: the persistence probability is 0

Non-0x3F: the persistence probability is 2-n/4

Reserved Changeable


1.6 Redirect Message

The AN sends Redirect message to redirect the AT to leave the current

network. This message can be sent on the CC or the FTC. When it is sent

on the CC, all terminals (including connected and disconnected terminals)

under the carrier where the CC is located will be redirected to other

networks. When it is sent on the FTC, a specific terminal will be redirected

to other networks.

After the AN adopts the event trigger mechanism to send this message,

and the BSC judges whether to send it based on algorithm.

Table 1-7 Fields in the Redirect Message




MessageID 8 /

NumChannel 8 Directed channels of the target network

The following is an example of NumChannel:

Channel 24 Channels the AT should re-trap, including SystemType., BandClass and ChannelNumber

1.7 BroadcastReverseRateLimit Message

The AN adopts BroadcastReverseRateLimit message to control the peak

transmission rate of reverse links of all active terminals under a specific

sector. It can be set separately for every user based on MACIndex.

The AN adopts the event trigger mechanism to send this message and the

BSC judges whether to send it based on algorithm.

Table 1-8 Fields in the BroadcastReverseRateLimit Message

Domain name

Length Description

MessageID 8 /

RPCCount 6 Maximum RPCs supported by the sector

The following domains occur for RPCCount times:

RateLimit 4 The AN sets the value n of this domain to the peak data rate that is related to MACIndex 64-n and can be used by the AT on the RTC.

Reserved Changeable


Table 1-9 RateLimit Domain Code

Domain value

Meaning

0x0 0kbps

0x1 9.6kbps

0x2 19.2kbps

0x3 38.4kbps

0x4 76.8kbps

0x5 153.6kbps


EV DO System Messages 20050106 a 1.0

Documents

Transcript of EV DO System Messages 20050106 a 1.0